Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
Hi Greg,
I have the same problem like TJPS. And I haven’t any caching plugins …
I build page http://ibpolsoft.kylos.pl/test2/wp/ – ca 1h ago, after widget update, page has crashed.
Hi Szwolinski
Just to clarify, a crash would be your entire page not rendering at all. This appears to be more along the lines of a layout conflict. I see extra classes are being added to some wrappers inside your Page Builder content, namely grid_push_box. I’m not sure if this is coming from a theme or plugin, but you could try running a general conflict test.
If you’d prefer to skip the test, you can switch back to the legacy layout engine, which might work, but you’ll lose out on several key features from the new update. Navigate to SettingsPage BuilderLayoutUse Legacy Layout Engine – and change that to Always.
If you want to go the troubleshooting route – here’s a video on the process:
The first thing to check is server-side caching through plugins like W3 Total Cache, WP Super Cache, etc. If you have any of these caching/performance plugins installed, try clearing their cache and see if that helps.
It might also be browser cache. Try clearing your browser cache, and then refreshing the page to see if that helps.
You can read more about this sort of issue on the WordPress codex.
Next, you can try running a plugin conflict text. You can start by 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.
I went back widget to ver. 2.4.25 – now it works …
Glad to hear it. If you’re using any themes or plugins that might be manipulating Page Builder content, it’s worth contacting their developers to ask them to make their products Page Builder 2.5 compatible.