I just wanted to report a potential conflict between Responsive Lightbox Gallery and SiteOrigin PageBuilder (also have the widget bundle installed).
I have been finding that some of my WordPress pages randomly stop showing any PageBuilder content (including widgets). Instead of seeing the PageBuilder box with Rows and widgets, I get a blank box. It appears empty but, if you drag a selection, it actually contains code. Once the pages are broken, they do not come back.
The live webpage functions perfectly fine but I am unable to edit my pages in wordpress.
It has previously worked fine but I am finding that the confict seems to happen more frequently now.
I have just deactivated the Responsive Lightbox Gallery and hey presto, my PageBuilder dialogue has returned.
I am very new to this so apologies in advance if I have missed any important information.
If so, please let me know and I will try to provide any information I can.
SiteOrigin – Responsive Lightbox Gallery conflict
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Teef
Thanks for reporting. I’m not immediately getting an error when activating Responsive Lightbox Gallery and Page Builder by SiteOrigin. If you can, please do a quick test. Does the issue persist if Responsive Lightbox Gallery and Page Builder are the only two activated plugins?
Hi Andrew,
Thanks for getting back to me. Apologies, I think I was a little quick out of the gate. When I found the issue, I turned off the last plugin that I had installed (Responsive Lightbox Gallery) and this fixed my problem. Since reporting, the problem has reoccurred so I think some more investigation is required.
Still on the learning curve.
Thanks again.
Thanks for the update. Try temporarily deactivating all non-SiteOrigin plugins. Do you have a working baseline? If so, reactivate your plugins one by one, testing for the issue after each activation. Once the issue reoccurs, try testing with only SiteOrigin plugins and the plugin you think is causing the problem, that should help with a final confirmation.