Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
Hello,
I notice a severe issue with the page builder: If I click on “edit” I get a blank (empty) content aera, which means that I can’t edit the content. I tried with different browsers but the behavior remains the same. This is a big problem, because I can’t edit the page. This problem only occurs with text widgets, other widgets work fine. The link to the page is https://dev.crg.world/de/yachtcharter/silver-wind. Any thoughts what I can do?
Thank you,
Sascha
Hi Sascha
Please, go to DashboardUpdates, if there is an update for Page Builder and the Widgets Bundle, run them, that should resolve the issue.
Hi Andrew,
thank you – unfortunately there is no update for Page Builder, and the issue sill exists. Any other ideas?
Thanks again,
Sascha
What version of Page Builder are you using, if you go to Plugins you can check there.
If you’re using a caching plugin, try clearing it.
If you are using Page Builder by SiteOrigin version 2.5.10 then you should do a plugin conflict test.
Page: Identifying Plugin Issues
Thank you Andrew, I’m using the “SiteOrigin Widgets Bundle” in version 10.1.4.4 – what would you recommend to do?
Update: I also cleared the caches (CDN, proxy, memcache, browser), but the issue didn’t change.
Edit: The relevant information probably is: “Page Builder for Create” in version Version 10.2.4.5
Update: I deleted the plugin and reinstalled it (version 2.5.10) from your website and now the issue is gone! Many thanks for your support.
Sascha
Thanks for the update. Sounds like you were using a forked version of Page Builder. Glad to hear the issue is now resolved.
All the best :)
Hello Andrew,
I’d like to reopen this case since I noticed an issue after the update which I can’t understand/resolve:
If I open (edit) a text widget after the update to page builder 2.5.10 and save it again – even with exactly the same content – the layout/design of the output is destroyed. This is weird since I didn’t touch any layout/design settings. Therefore I don’t know how this is happening and what to do to not destroy the layout/design.
Please have a look at these two pages, before the update and after the update (just opened and saved the widget):
1) before: https://dev.crg.world/de/yachtcharter/silver-before/
2) after: https://dev.crg.world/de/yachtcharter/silver-after/
Can you explain what’s happening there and what I can do to edit the widget without destroying the layout/design?
Thanks for your help!
Sascha
Tags are being stripped out, a
tag for example is removed so the CSS won’t work anymore. In the Text widget, make sure that the setting to automatically add paragraphs is disabled. Next, try editing the Text widget in the Text tab and not the Visual tab. Any change?
Hello Andrew,
many thanks for your suggestions. I already used the Text tab and I can’t see the “automatically add paragraphs” checkbox in the current version of page builder (see screenshot). Any other ideas?
Thanks again,
Sascha
Screenshot: http://imgur.com/a/Dv9xa
I’m not sure why those tags would be stripped out on save. You can perhaps try on a demo page, moving the working contents from a Text widget to the Text tab of a SiteOrigin Editor widget. Any better after editing?
Hello Andrew,
thanks for this idea. I tried it and copied the working contents from the Text widget to the Text tab of a SiteOrigin Editor widget, but the result ist very similar:
https://dev.crg.world/de/yachtcharter/silver-after-editor
I also tried to change the settings on the page
https://dev.crg.world/wp-admin/options-general.php?page=siteorigin_panels
but couldn’t find a setting to resolve the issue (I had good hope to disable “add Widget Class” but it didn’t change anything).
Do you have any idea what’s going on and suggestions what I can do?
Thanks,
Sascha
Thanks for trying. The span classes are being stripped out on save. What you can do is redo the markup. For example, before save it is:
If you change that to:
The divs will remain, they aren’t being stripped out like the span tags. You’d then need to change the targeting CSS.
Before:
After:
Hi Andrew,
I just wanted to let you know that your solution worked perfectly and the issue is now resolved! :-)
Thank you very much for your amazing support!
Best regards,
Sascha
Glad that helped :) Cheers.