I’m new to this so hoping fix is obvious to you. Some pages are find and behave as expected. We have other pages that display fine on the website but we can’t load the text into Page Builder. It goes through the motions but what comes up an empty Siteorigin editor box. Revert to text takes it back to the editor how it originally was. If we touch the page in “text” it’ll break. By break I mean it starts to display in the web browser with formatting codes being interpreted as text, ie: u003ch2 style=u0022text-align: left;u0022u003eWe think like the end useru003cbr /u003enBecause we… .
As I said, some pages are fine. They will load into page builder fine and revert to text fine. It’s inconsistent and also strange that the “broken” ones display fine in the browser until we touch them. Then it interprets the codes as text. Again, this is only for ones that do not really import anything into page buider. Interesting that it is inconsistent: some work and some don’t.
Any thoughts?
Hi
Thanks for reaching out.
When able, please, try checking for a working baseline. Does the issue persist if you temporarily deactivate all plugins except for those plugins authored by SiteOrigin?
I will try that.
By the way, I also I tried this which sounded promising:
Thread: Site content lost when clicking Page Builder tab on Classic Editor
And I was able to get the code back into page builder but it still displays as gibberish in the previews.
Will report back when I’ve confirmed the working baseline.
Thanks for the update.
The thread linked above involves both the Block and Classic Editor. If you’d like to send a screenshot of the situation you’re seeing you can upload screenshots to imgur.com or any cloud sharing site like Dropbox.
Thanks again.
Thanks for the responses, Andrew.
Disabling the plug-ins doesn’t change anything.
I have put a couple of screen captures and a screen shot here:
https://www.dropbox.com/s/h3crxpdbexe4qyq/SiteOrigin.zip?dl=0
It’s as if some of the pages have become “unassociated” with Page Builder. Could their be some header corruption or something?
Thanks for the update.
The page in question was originally created in the WordPress Block Editor. A SiteOrigin Layout Block was inserted and content was added. The page was then opened in the WordPress Classic Editor and switched to the Page Builder tab. It would be easiest to use the WordPress page revision system to roll back to an earlier version of the page before it was opened in the Page Builder tab. Alternatively, the code has to be manually edited to remove the wrapping Editor Widget markup before it can be opened in the Block Editor.
Assuming you can roll the page back, the following can be carried out:
* Roll the page back to an earlier version.
* Open the page in the Block Editor. You can do this by deactivating the Classic Editor plugin or enabling the Classic Editor option to allow editing in both editors.
* Once in the Block Editor, open the SiteOrigin Layout Block, click the Layouts button, click Download Layout. A JSON file will be downloaded to your desktop.
* Open the page in the Classic Editor as it is in your screencast. Clear the contents completely in the Text tab. Switch to the Page Builder tab and import the JSON file from LayoutsImport/ExportImport Layout.
Thanks, Andrew.
That enables the page to load into Page Builder but it still displays like it did before, with the codes being output like text as per the screen shot I sent.
Before opening the page in the Block Editor, were you first able to roll back the page to a point where it hadn’t been opened in the Page Builder tab?
The markup indicated in the following screenshot is a sign the page hasn’t been rolled back far enough: https://imgur.com/a/9RMOPNO. There will be closing tags for the indicated markup out of screen that also must not be present to open the page in the Block Editor.
If the answer is yes, you were able to roll the page back successfully and then open it in the Block Editor, please, run a plugin conflict test in that state. The earlier plugin conflict test was most likely run while testing in the Classic Editor. Once you’ve successfully opened the page in the Block Editor and assuming the SiteOrigin Layout Block is operating normally, try seeking a working baseline. Temporarily deactivate all plugins at once except for Page Builder and the Widgets Bundle. In that state, does the issue persist?
If you would rather not troubleshoot the Block Editor issue you can export the layout from the SiteOrigin Layout Block and then open the page in the
Classic Editor, clear the contents and import the layout from Layout >
Import/Export in the Page Builder tab.
I appreciate your time and suggestions, Andrew. I’ve spent some time with them.
There is no page that I cannot open in the block editor. I have my choice of editors, block or classic. Working and non-working pages will both open in block editor.
I looked at a couple of the pages I’m having trouble with and there’s nothing to roll back to.
Somehow, what has happened to these pages is that the special characters have been translated to unicode and so instead of a quote we have the text string u0022. It’s just interpreted like a string and so the formatting is gone, forms aren’t accessed, etc.
Thanks for the further feedback, appreciate it.
Please, can I confirm that the preview issue in the Block Editor was checked with all plugins deactivated except for the Widgets Bundle and Page Builder? I’m not sure if the earlier plugin test carried out was done so while checking only the Classic Editor issue we were previously discussing.
Will do, Andrew. I do some more testing when I can and let you know but for now want to acknowledge that I’ve seen your last. Thanks very much.
Thanks for your reply. Super, that’ll be great!
* Test a problematic SiteOrigin Layout Block in the Block Editor with all plugins deactivated except for the Widgets Bundle and Page Builder.
* If a working baseline can’t be found temporarily switch to a default theme like Twenty Nineteen while leaving all plugins deactivated except for the Widgets Bundle and Page Builder.
Thanks again! Chat when you can.
Andrew, I able to get much of these pages back by exporting/importing the layout with classic editor deactivated. There’s still some formatting to do but I’m getting through it, kind of. Thanks for the guidance.
I’m happy to hear about progress but would have liked to have solved this for you. We don’t usually offer direct support in our free tier, but I don’t mind taking a look in this case. If you’d like us to, perhaps email [email protected] with a link to this thread. If there isn’t sensitive sales or marketing data in your WordPress admin, we can send instructions to create a new account, so we can take a look and see if we can perhaps spot an issue.
That’s a nice offer, Jamie. Thank you. I’d appreciate it if you would take a look. How do you feel about a screen share?
No worries. I’ll be back online tomorrow in my time zone. Unfortunately, we don’t offer screen share support at this time.
Andrew, with your guidance I was able to get where I needed to be. Thanks very much. Saved a lot of work being able to export the layouts with the block editor.
Thanks for the update. That’s great news, nicely done! If any SiteOrigin queries arise in the future, please, let us know.
Cheers for now.
Andrew