Weird bug with customized Cafe Pro Theme

Beaver Builder
1

So I was trying to update my site in two phases. Eventually I won’t be using the Cafe Pro theme. But there are also a lot of content changes along with new branding and styling for my site. So I had what would be the brilliant thought of starting with the content, then restyling/branding the site. But my current theme is not cooperating with me or Beaver Builder. I am getting a terribly annoying bug that is basically rendered BB useless. When I add a new module, new row, or new template, weird things happen to my page…the only way to get back to the default BB editor is to refresh the page. This works most of the time. But sometimes, I lose whatever changes/updates I’ve made so I’m stuck in a loop unable to make and actually save the changes. Please see the images I’ve provided below. I trying disabling quite a few plugins to no avail. I changed the theme to the basic TwentyTwelve and BB is working now. But that sort of defeats the purpose of my original plan. ARGH!

Any ideas what could be causing the bug? I thought BB worked fine with Genesis Themes.

And then I get this every now and again…(just in some places of the backend)
Fatal error: Call to a member function get_option() on boolean in /home/techiemu/public_html/wp-content/plugins/genesis-dambuster/classes/class-plugin.php on line 164

Screenshot of BB bug + Cafe Pro theme
screenshot of BB bug

2

Apparently it IS a plugin conflict. There were a few plugins I didn’t have turned on in my dev site that were activated in my live site. I went through and basically turned a lot of them off and now its working again. I’m not sure which one. Is there an easier way to test plugin conflicts with BB other than (1) turn plugin on (2) launch BB (3) try to change something and test for bug (4) no bug (5) close BB (6) turn another plugin on (7) etc. etc. There are a couple of added steps in there not needed on a “regular” site. Quite frankly I don’t think I have the patience to do that right now. I have a migraine just thinking about it. Don’t judge me…I have terrible allergies today. :wink:

3

Hi Kary,

Unfortunately, the most efficient way to diagnose which plugin is causing your issue is to disable all active plugins. Once disabled, you will need to enable one plugin at a time. Once you enabled one plugin, check to see if the issue has returned, if it hasn’t disable that plugin and move onto the next one.

Repeat this process until you find the culprit. I understand this is a tedious task, but it is the best method of finding out which plugin is causing the issue.

Thanks,
Danny