I am using Page Builder 2.2 on a WP 4.3 install. (Widgets Bundle 1.5 is also present with a Vantage theme)
Tonight, randomly the page builder editor tab has vanished from all parts of my pages, posts, etc. There were no modifications made, no plugins, no recent updates.
I reran an upgrade to WP 4.3, and reran an upgrade for PB 2.2 with no results. When I add the page building section (via the screen options, as I thought that was the issue), it just loads a dropdown box that has nothing in it. When trying to edit a page that’s been modified with the page builder plugin, the page just hangs. It loads the WP template, but it doesn’t display any of the editor.
I can still view settings, and the troubleshooting info, but none of the actual consoles come up.
Any ideas?
Hi Michael
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? 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.
Hey Andrew,
I had done a search and noticed that was the primary recommendation yesterday. I did this with no results.
What is so strange is that it happened fairly randomly. There were no changes made to any settings, or new plugins installed between the time that it did work and when it did not. (This was over the span of just a few hours too).
When looking at Edge’s console, it doesn’t yield any errors either.
Thanks
Edit to add just now.
I started to get a hunch that something might be up browser wise, so I tried logging in from Chrome, and IE11 and got results. I’m not really sure why Edge would suddenly drop the functionality, so I’m going to try and purge internet files and see if that helps things along.
Meanwhile, any thoughts as to what would cause this on the Site Origin end, or should we chalk this up to an Edge bug?
Thanks
Thanks for your feedback.
I realise after reading through the forums it might seem like we send out plugin conflict recommendation all the time! They do account for a huge amount of the challenges we face though, so always a good place to start. The idea is to try strip away everything until things work again. Then, slowly rebuild the installation until it breaks, thereby exposing the issue. With a lot of these challenges we aren’t sure what the problem is till we’re further down the testing process.
Can we login and take a look? Instructions to follow…
Would it be possible for you to create a temporary admin account for us so we can log in and take a look? You can create the account with the following email address:
[email protected]
Just navigate to Users > Add New in your WordPress admin. Enter siteorigin for the username and [email protected] for the email address. Make sure you’ve selected Administrator for the role and enabled the “Send Password” field so we receive the details.
Once we’re finished taking a look, you can delete this account. We’ll let you know when to do that.
Hey Andrew – no worries…I used to be a project manager for a message board platform. :)
It looks like a file history purge did solve the problem and Page Builder is showing back up. Do you still want access to see if you can replicate an issue with Edge?
Let me know.
Thanks for the update. No need to login right now. So you cleared the cache in Edge and it fixed the issue? Is that what you meant by file history?
Page Builder not showing up as a tab is caused by a JavaScript failure. It’s usually a plugin conflict but isn’t limited to this cause.
That’s correct.
What puzzles me about that is that I’m under the impression it still should have shown as an error in Edge’s console, but it didn’t. Unless Edge knew somehow that the issue was within it’s own cached files.
If Page Builder’s tab isn’t loading, then yes, I’d expect to see evidence of that in the Console. Mmm! Strange. Clearing the cache is an easy fix. If this happens again, please, let me know and we’ll do testing in this regard.
Sounds good Andrew, thanks for getting back to me!
For sure :) Chat further if anything comes up.
Cheers for now.