Hi,
After installing and activating the SiteOrigin Page Builder plug-in, content on some pages completely disappeared.
When editing those pages, all the content shows up in the Page Builder editor, but when previewing the page’s content doesn’t load.
However, once the Page Builder plug-in is deactivated, all content came back.
Please kindly advise if this is a known issue and how to resolve this issue, client specifically requested the installation of Page Builder, but this issue is preventing the use of Page Builder right now.
Best,
Loretta
Hi Loretta,
Preface: By disabling SiteOrigin Page Builder, you’re seeing the very basic fallback layout – that’s not a sign that it’s working, only that the fallback is visible.
This sounds like it could be a plugin conflict issue. Can you 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.
Hi Alex,
Tried disabling all other plugins one by one and clearing the cache, this issue only appears when the PageBuilder plugin is activated.
Using a SiteOrigin theme is NOT an option for this project as we’re already committed to a particular theme, and switching to the WP default theme (Twenty Seventeen) and clearing the cache doesn’t resolve this PageBuilder issue either.
Please kindly advise if there’s solution for this particular issue.
Best,
Loretta
Hi Loretta,
Please note that we weren’t suggesting that you change your theme to one of our themes, only that you temporarily try a default theme (one of the themes that comes with WordPress – Twenty Seventeen for example) as that’ll rule out a possible theme conflict. Temporarily changing theme will not result in you losing your theme settings.
If that doesn’t help, Cloudflare’s Rocket Loader is causing issues for certain people. Are you using Cloudflare / Rocket Loader? If so, please exclude WP Admin from Cloudflare. The linked article title isn’t directly related to this error, but the provided instructions in the article will tell you how to disable Cloudflare in the WP Admin directory.
Hi Alex,
Temporary switched to the WP default theme (Twenty Seventeen) and clearing the cache, but it didn’t resolve the issue.
We are not not using Cloudflare/Rocket Loader, any suggestions on how to resolve this issue?
Best,
Loretta
Hi Loretta,
Would it be possible for you to create a temporary admin account for us so we can log in and take a look?
This is a private message.
Hi Alex,
All set, let me know how it goes.
Best,
Loretta
Hi Loretta,
Unfortunately, we haven’t received an email from your website yet – typically they’re instant. Can you please try setting up the account again? Please note that you’ll receive notification automatically when we receive an email from your website.
This is a private message.
Hi Alex,
Just send an email to [email protected] with URL, username, and password.
Let me know if that works and if there’s a solution to the issue.
Best,
Loretta
Hi Loretta,
Thanks, it appears as though there’s a PHP error. Please enable WP_DEBUG. This requires editing wp-config.php so if you need help with this, I would reach out to your hosting provider for assistance with this.
Hi Alex,
I’ll submit a ticket to our hosting provider to get this done.
Anything else need to be done while they’re at it?
Best,
Loretta
Hi Alex,
Added the below code to the config to enable debugging:
// Enable WP_DEBUG mode
define( ‘WP_DEBUG’, true );
// Enable Debug logging to the /wp-content/debug.log file
define( ‘WP_DEBUG_LOG’, true );
// Disable display of errors and warnings
define( ‘WP_DEBUG_DISPLAY’, false );
@ini_set( ‘display_errors’, 0 );
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( ‘SCRIPT_DEBUG’, true );
Let me know if you need anything from my end.
Best,
Loretta
Hi Loretta,
Thanks, but WP_DEBUG_DISPLAY prevents me from actually seeing the error. Errors are now logged in a file in your wp-content directory. Can you please replicate this issue again and then send me the contents of your debug.log file in your wp-content directory? Ideally please upload the file to pastebin.com. Alternatively, please enable WP_DEBUG_DISPLAY so I can see the error directly.
Hi Alex,
Enabled WP_DEBUG_DISPLAY
// Enable display of errors and warnings
define( ‘WP_DEBUG_DISPLAY’, true );
@ini_set( ‘display_errors’, 0 );
Best,
Loretta
Hi Loretta,
Thanks. Based on the resulting output, I suspect this is a plugin conflict. Can you 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.
Hi Alex,
Deactivated ALL other plugins and the issue persists, same with switching to the WP default Twenty Seventeen theme.
Please advise if this issue is resolvable? And if not, what alternative plugin we could use in place of the Page Builder plugin.
Best,
Loretta
Hi Loretta,
At this stage, we’re unsure if this issue is resolvable – we’re still in the discovery stage as we don’t know why this is happening.
Are you able to clone the affected page? To do this, please create a new page and enable Page Builder. Click the LayoutsButton and click Clone: Pages. Find and clone the broken page and save. Does it display without issue?
Hi Alex,
Cloned an affected page, new test page is same as affected page, nothing displays.
Source ode of affected page:
view-source:https://pvhsupply-com-develop.go-vip.co/normal-procedures/continual-procedures/vendor-management/
Source code of test page:
view-source:https://pvhsupply-com-develop.go-vip.co/16769-2/
FYI, most every page is having this issue when Page Builder is activated.
Please advise on next steps.
Best,
Loretta
Hi Loretta
According to the linked pages, the version of SiteOrigin Widgets Bundle is incomplete. Are you able to access WP AdminPluginInstalled Plugins? If so, please deactivate and delete SiteOrigin Widgets Bundle, then reinstall SiteORigin Widgets Bundle.
If you’re unable to access that page, please connect to your website using FTP and navigate to wp-content/plugins and delete so-widgets-bundle. If you ned help with assitaince with this, please reach out to the hosting provider with assistance with this. Once deleted, please reinstall SiteOrigin Widgets Bundle.