Hello,
Strange issue. I have installed Twenty Fifteen on an existing website and the Page Builder connect is not updated.
I can move the widgets, add new rows or delete them, but when I update the page (save it), the content reverts to as it was before the update.
I have tried other themes and it is not a problem.
Please advise! ASAP!!!
Thanks
Hi wn
Thanks for reaching out. I’m unfortunately not able to replicate the problem on my side. Hard to say what might be up so you’ll need to try troubleshoot.
1. Are you running Page Builder 2.0.3? Update everything at Dashboard > Updates.
2. De-activate all other plugins and check Page Builder on a new page.
3. Check for any JS errors when using Page Builder: http://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors#Step_3:_Diagnosis.
Andrew, thanks for your reply.
1. I have the latest Page Builder 2.0.3 build. All other plugins updated. No errors of any type anywhere.
2. I tried it on another wordpress install with totally different set of plugins and same results for an existing page.
3. This issue is only for Twenty Fifteen theme. All other themes I have tried work as expected.
4. On your suggestion, I created a **new** page under Twenty Fifteen and the problem is not replicated.
So, do not know where it is coming from.
Any further thoughts?
If you email me privately, I will be willing to give to admin access to a test setup.
BTW, on a new page, I did it without deactivating all other plugins.
Deactivated all plugins except Page Builder and no show for an update on existing page.
New Page is not an issue.
Please advise.
Thanks for your effort here. We’d definitely like to get this sorted out. Please could you email us on [email protected] with set of temporary login details and I’ll take a look ASAP. Please can you send everything in one email from yourself and include a link back to this thread so I can reference things. We can easily lose track of automated WP emails, hence the request for a single mail.
Thanks again :)
Hi wn
This is a known bug with WordPress itself. Basically if you start creating a site using a theme that has page templates (like most previous default WordPress themes), then switch to a theme that doesn’t’ have any page templates, WordPress triggers a silent error that prevents Page Builder from ever getting the chance to save its content.
You can track the status of that bug here – we’re hoping for a fix soon. Especially seen as Twenty Fifteen is the first default WordPress theme not to include any page templates.
https://core.trac.wordpress.org/ticket/29269
The solution is to switch to a theme that has page templates (like Twenty Twelve), edit the page, change the page template to default, save the page, then switch back to the theme you were using.
Greg, but this is only if the page was created with a theme with page template.
All new pages with Twenty Fifteen do not seem to be inflicted with bug.
So, are you saying that for the “current” pages, the bug exists but for “new” pages, the bug does not exist?
That is correct. The bug comes up on pages where you’ve set a page template, then move to a theme without a page template. New pages won’t have a page template set, so they won’t trigger the error.
You can read more about the bug on that trac ticket I linked, but it essentially comes down to the page having a page template set that doesn’t exist anymore. Hopefully, when they fix the bug, WordPress will be smart enough to just revert to the default page template.
Well, thanks for your update on this. Glad it has nothing to with Page Builder plugin.
I read up on that ticket. It seems there is no urgency to fix it on their part. It was reported five months ago and I think there has been perhaps two updates of WP in the interval and it has not see daylight.
So, the choice may come to take a chance or abandon the theme!
BTW, a point of reference for this ticket; even though the ticket shows delays in response; Andrew has been most helpful via emails with me and my hosting provider in getting to the bottom of this.
So, I thank your team for stepping up in what I thought was a scary issue.
Thanks for your understanding and patience here, we appreciate it. Agreed, it’s been some time since this bug was reported. Hopefully the WP.org team will be able to attend soon.
Chat soon :) Cheers.