Hello,
I am using :
Wordpress 5.0.3
SiteOrigin Page Builder 2.10.0
Start Theme
I am facing the here below problem.
In the WordPress Back office, when I try to open a page built with SiteOrigin Editor, there is wheel turning indefinitely.
To stop the wheel running, it is necessary to click anywhere inside the block rectangle and to click on the pencil button (Edit layout).
Then, when I try to edit the content of a Layout block, this content is blank !
I have only a few plugins installed, as follows :
Contact Form 7
Easy FancyBox
MetaSlider
Proxy Cache Purge
Restaurant Reservations
SiteOrigin Widgets Bundle
StartWP Extended
It seems that several other webmasters meet the same problem of blank content when trying to edit a block built with SiteOrigin Page Builder.
The advice often given on the forum is to de-activate all other plugins. But as far as I could read, it seems that it does not solve the problem in most cases.
Is there any recommend way to solve the matter ?
I thank you in advance for any reply
Patrick
Hi Patrick,
I’m sorry to hear you’re having issues using the SiteOrigin Layout block. Unfortunately, we’re not too sure why you’re facing this.
This test is what we always recommend running first before looking at possible causes because the vast majority of issues are as a result of plugin confits. Please run a plugin conflict test to rule out any conflicting plugins as that likely will identify the issue you’re facing.
For reference, here’s the typical plugin conflict test we recommend following:
Try disabling all non-SiteOrigin plugins and see if this fixes the issue. You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.