I just saw a post regarding this (was just posted an hour ago) and I’m having this exact same problem. I tried replying to their question, but I get a message that comments are closed for that item??
Here is the issue I’m having: With Page Builder plugin activated, when I try and edit any page, I get nothing but a blank page. When I disable Page Builder, everything works fine.
A little additional info – this has to be related to the “Classic Editor” and/or “Page Builder” update that just happened. Classic editor updated from V. 0.4 to 0.5 and Page Builder updated from V. 2.9.0 to 2.9.1. I have 88 WordPress sites and usually update all my sites plugins at once using ManageWP, but fortunately today, I was in a rush and only logged into one site to make a quick update of one page. I saw the couple of plugins needed to be updated, so I went ahead and updated them before making the page edits. It was then that I saw the problem. I tried the usual, clearing the cache, trying a different browser, trying a private browser – nothing worked. I then started checking my other sites and all other sites are working fine (they have not been updated yet). I tried using the “Customize” button instead of editing the page and that is when I noticed the customizer page had a strange notice about “Edit Widget: SiteOrigin Accordion” and a box which said “Add widget class” and nothing else on the page. it was then I realized that it was a PageBuilder problem. Once that is disabled, everything works fine.
I am a Premium user and have emailed support about this, their first response was to tell me that no one else is having this issue, so it must be a conflict with another plugin. I’ve emailed them back with the above additional info. I hope SiteOrigin is able to get this fixed quickly, I use their page builder on all my sites.
Hi Kelly
Thanks for reaching out.
The forum is, unfortunately, only open to the poster and SiteOrigin at the moment. If you’re a premium user and already chatting with Alex on email, that’s the best and quickest support channel to be using. At times, we might require a test to be run or we might have to ask a few questions. Plugin conflict tests are really helpful for troubleshooting. At times they might seem like a pain but they give us a lot of information without much effort. We’re always doing our very best to get you to a solution in the least possible amount of emails and the least possible time. Alex will reply to your email shortly. Thanks for your support.
You just answered this exact same question from another poster from four hours ago – you told him that you will be releasing an update to fix this problem within 12 hours. Is that correct or not?? You need to talk to each other and answer this issue with one answer.
Hi Kelly,
The thread you’re referring too is related to a SiteOrigin Widgets Bundle update issue and doesn’t affect SiteOrigin Page Builder.
The first answer I got from Alex said that it must be a conflict from a different plugin because no one else has had the problem. I just looked at the home page of this Support Forum and EIGHT of the fifteen posts on the first page are asking about this EXACT problem starting a couple of DAYS ago!!
Is the problem going to be fixed with an update – if so, WHEN will this update be coming?? I have dozens of sites using this plugin, I paid for the unlimited Premium version. This needs to be fixed AND you need to get your act together when answering this question for the people who are posting here (and also obviously those of us emailing for our PAID premium support). I paid for premium support and had to find the answer (at least I hope it’s the correct answer) here on your forum.
Hi Kelly.
Thanks for your reply. I carefully read your report and chatted to Alex before replying. We’re a small team and all very much on the same page. I didn’t think your issue was the same as the one you’ve mentioned which is why I didn’t mention it. The issue discussed in the other thread pertains to the Widgets Bundle. An update fixing the problem will be released in the next 12 hrs. If you’d like to check if to see if this problem may have impacted your WordPress install you can follow these steps:
1. Go to Plugins, make sure the Widgets Bundle plugin is installed activated.
2. Go to Plugins > SiteOrigin Widget and make sure the Layout Slider widget is activated.
3. Try to edit a Page Builder page. If you’re seeing a blank page in that event then there is a good chance you’ve run into the problem discussed on other threads. The best way to resolve that would be to reach out to your hosts and request they upgrade your PHP version to version 7+. This upgrade should be done before the end of the year regardless due to PHP 5 security support being discontinued.
If possible, please transition over to email so as to not split your support up over two channels. Thanks.
Really? Because I just went back into my site – reactivated Page Builder and deactivated Widget Bundle – that fixed it as well. Obviously these issues are the same.
Super, that sounds like great progress. Please, see my steps above for resolving. Either ask your hosts to move you up to PHP 7+ which is a good idea on its own. WordPress recommends PHP 7.2+, alternatively pause development for a little bit while we release an update for the Widgets Bundle.
Yes, it is the same issue. If I deactivate Widget Bundle the problem is fixed.
Will the update later today fix this? I tried upgrading my site to PHP version 7.1.7 and it breaks my site completely – nothing works at all. Will your update fix this without having to update my PHP?
Sorry, I meant to reply via email. I don’t mean to make this more confusing.
The update will fix the PHP 5 issue which means you don’t need to upgrade to PHP 7 for the moment although that’s something your hosts might request next year.
The update for the Widgets Bundle has been pushed to WordPress.org. If you head over to DashboardUpdates, it should be there already or soon.
Sorry for the hassle, all the best with your sites. If any further questions arise, please send us an email. Thanks.
Just updated and it worked!
Thanks so much for the answers and the fix.
Sorry I got pushy and irritated with you guys, I had a very angry client breathing down my neck and I passed that on to you…my apologies!
I’ll have to get with my host and see what’s going to with the PHP update. I found I CAN update to 7.0, but not 7.1 – I will put this on my list of things to look into J
Super, really glad to hear you’re up and running.
So sorry we missed this PHP 5 during our release testing phase. Usually, we can get you the answer you need right away. Unfortunately, Alex and I misread your description and got too focused on the Page Builder deactivation aspect. I wish it could have been quicker. Hopefully, you can smooth things over with your client now. Sorry, you were in that position.
When you have time in the future, try to look into PHP 7+. Usually, your whole site won’t break. It’s worth figuring out which plugins/sections are breaking and why. For example, on a site I run, we had a very old slider plugin which broke when we moved to PHP 7+. We had to upgrade the slider plugin to resolve the issue. Their latest version didn’t suffer the same problem. Turning on WP_DEBUG in your WordPress wp-config.php file is really handy to see what errors are being displayed.
All the best :)