This has happened twice on my site now – once at the beginning when we didn’t have backups and I had to rebuild the site and now, just before going live. I’ve finally tracked the glitch down to SiteOrigin judging by other comments on here.
I love this plugin and want to start using it more but I can’t risk it if the glitch keeps happening.
Basically, I edit the front page and most times it’s fine then others, it loses all of the content and doesn’t have any WP revisions to roll it back. This last time it also affected the header file and although the coding was there – wp wouldn’t display it.
It’s too big a site to rebuild so all we can do it rollback to backups which is fine (although annoying) whilst it’s still not live but when it goes live could be an issue. And, as it’s not the client’s fault, I’ll be paying for it. I usually use visual editor but thought I’d give this a try this time.
Does it happen in premium? If it can be guaranteed, I would consider buying it for this site as it would save me a lot of time and stress but if it’s still happening on the premium there’s no way I’d pay for it and I’ll carry on using Visual Editor.
Can this issue be fixed, perhaps – looks like it’s been going on for at least a year judging by other comments on the thread? When I put debug on it mentioned wp enqueue script being an issue if that helps – I don’t have the exact message but it quoted this: /wp-includes/functions.php on line 3995
Hi Suzi,
Could you link me specicially to another thread you think your issue is similiar to?
Could you please tell me the version number of SiteOrigin Page Builder? What theme are you using?
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.
—
To clarify, there are no outstanding issues that match your description so it’s unlikely upgrading to premium will help.
Hello,
I have a similar issue, but I have narrowed down the cause of my problem.
I disabled all of my Plugins except for the page builder Plugins and everything worked. When I found the Plugin that was not working it was an out dated audio player. I can solve my problem by myself by getting a new audio player Plugin, but this info may help you. Try deactivating and reactivating your Plugins.
Hope it does help,
Have a good day :)
Hi,
Unfortunately, most of the plugins are very essential, I’ve deleted any I thought we could do without. You’ll appreciate we’ve been building this for months and we can’t just start backtracking and removing/replacing plugins which affect content.
They’re mainly premium plugins and most we have swapped out since it was originally built for alternatives – could it be more than one plugin with a conflict? Surely, it’s better to have a page builder plugin that works with nearly all plugins?
All software on the site is on it’s current version and I’m not using any ‘outdated software’ plugins.
Secondly, as the fault has only happened twice, I don’t want to tempt fate by trying purposely to recreate it. The site is going live this week and we cannot afford any more delays. But once the company is launched and the press has died down then we’ll be able to schedule in some maintenance. Fingers crossed it won’t happen in between but as I suspect it’s when the homepage is edited, which has the most page builder aspects, we’ll avoid doing that.
Originally, when it first happened, I deactivated every plugin and changed the theme to see if it would bring the content back but it didn’t. Once it’s gone it’s gone and a backup restore is the only way to bring it back. I also tried repairing the database and optimising it. Oh, and the site was also moved to different hosting to make sure there wasn’t some glitch with it. Like I said originally, I did a lot of research to bring me to the point that I do now think it’s page builder at fault – whether it’s a plugin conflict or not, I suspect it has something to do with wp enqueue script’s as that was the error this time.
This week, I don’t have a lot of time to invest in this issue so I’m just hoping it doesn’t do it again and taking regular backups to ensure if it does we can just restore but ideally, I’d like a cure so the client isn’t panicking. I’m sorry I can’t be more help at this stage but I hope you can do some investigating your side or at least log the issue in case anyone else brings it up and then you’ll know.
Hi Suzi,
Plugin conflicts aren’t really something that can be accounted for. It’s just something that happens and when it does, if we don’t find out what they are we aren’t able to avoid / forward the issue on (if it’s not our fault). To clarify, no plugin needs to be made compatible with ours so there aren’t any specific requirements to be able to use a plugin. With all of that said, SiteOrigin Page Builder is compatible with at least 90% of plugins (ie. millions of plugins) out there. There are only a few instances where issues arise, but when they do, they can be very noticeable. I would seriously recommend a plugin conflict test as that is honestly the only way forward at this point.
I would recommend making a staging site (we recommend Duplicator for this) and testing it on that site in that case. A 1:1 clone of your website will be able to provide the results without it having to affect your main website.
So running a plugin conflict after the issue has occurred won’t provide any answers as to what may have caused it. It also won’t be able to undo the damage for obvious reasons.
Regarding your point about “wp enqueue script’s”, could you clarify? Specifically, was there an error in the browser console? If this happens again can you please send me said error? Please refer to this guide (https://www.wickedlysmart.com/hfjsconsole/) on how to access your browser console.
St this stage, it’s very unlikely this issue isn’t a plugin conflict issue. We sadly have nothing to go on at this point without further information. I would love to help but we need to rule out a plugin conflict before being able to proceed.