Home>Support>Custom HTML and HTML anywhere breaks plugin

Custom HTML and HTML anywhere breaks plugin

I have a fresh brand new install of WordPress v4.9, with a fresh install of SiteOrigin Page Builder v2.5.16. Whenever I try to add custom HTML widget, or add HTML to any text widget, it breaks my page and I have to bring back the previous revision.


When I save it refreshes here:


If I click the pagebuilder button it brings up the visual screen, but if I go into the items they are blank. Also if I check the front page it is broken, only half of the content is there that should be:


It’s missing the rev slider.

Only way to get things back is to bring back a previous revision. This renders the plugin not usable since I cannot create custom content.

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 2 years, 4 months ago jfreak53

    Anything?? It’s crazy that the plugin doesn’t support custom HTML!

  2. 2 years, 4 months ago Andrew Misplon Hi, I Work Here

    Hi, at the moment I can’t replicate this. Page Builder “falling over” like that is usually the result of a JavaScript conflict. Please, try a quick plugin conflict test, depending on the result, we’ll work the issue from there. This can be done with a test page if you’d like.

    1. Go to Pages > Add New, create a test page, click Layouts > Clone Pages and clone the page you’ve been having an issue with.

    2. Plugins. Temporarily deactivate all plugins except for Page Builder and the Widgets Bundle. All at once.

    3. Try save the Custom HTML widget, does the issue persist? If the issue does not persist, reactivate your plugins one by one and try save the Custom HTML widget after each plugin is reactivated. Start with Rev. slider.

    If you have a caching plugin, please, clear that before deactivating all non-SiteOrigin plugins.

    Let me know how the above goes. If the issue doesn’t resolve with all non-SiteOrigin plugins deactivated, the plugin conflict test has failed and you can reactivate all plugins at once as there isn’t a conflicting plugin to find.

  3. 2 years, 4 months ago jfreak53

    I will try that, but I don’t think that’s it, it only happens when my HTML contains double quotes. This works:


    This does not work:


    But I will try the plugin thing.

  4. 2 years, 4 months ago Andrew Misplon Hi, I Work Here

    Thanks. One moment, I’ll test again.

  5. 2 years, 4 months ago Andrew Misplon Hi, I Work Here

    I can still save ok with the same widget contents as you. If you could try the plugin conflict test, that would be awesome.

  6. 2 years, 4 months ago jfreak53

    It only happens when Chronoforms 5 is activated.

  7. 2 years, 4 months ago Andrew Misplon Hi, I Work Here

    Thanks. I see the issue. Nicely done for finding it.

    I’ve logged the issue and asked the team to take a look. Unfortunately, I don’t have an exact estimate on solving this problem. I don’t have a hotfix solution I can offer. I’ll update you as soon as we’ve taken a deeper look.

    (I notice that this plugin serves a fatal error when I try save a form. I have to switch from PHP 7 to a version of PHP 5 to save without a fatal error. There are also several notices present when I output a form via a shortcode in the regular WP editor. If you turn on `’WP_DEBUG’` you’ll see those.)

  8. 2 years, 4 months ago Andrew Misplon Hi, I Work Here

    Hopefully, we can at least narrow the issue down in the next day. Once that’s done I’ll be able to better predict when we can solve the issue. Sorry I don’t have a hotfix to offer, wish I did.

  9. 2 years, 4 months ago jfreak53

    That’s fine! As long as someone knows about it! Thank you!!

  10. 2 years, 4 months ago Andrew Misplon Hi, I Work Here

    Thanks for your understanding, it’s most appreciated. I’ll update here as soon as we know more.

  11. 2 years, 4 months ago Andrew Misplon Hi, I Work Here

    Hi again :) Alex at SiteOrigin was able to take a look for us. Unfortunately, it appears that Chrono Forms 5 is filtering everything on the page, regardless of whether its a shortcode or not. This wholesale filtering of the content is breaking Page Builder. There isn’t any way for Page Builder to stop this happening. If you’d like to know more from a technical perspective, in this thread: https://siteorigin.com/thread/apply_filter-on-string-returns-unexpected-result-with-page-builder/, Greg discusses filtering with a developer.

    Because plugins have a lot of power, it isn’t always possible for Page Builder to prevent third-party conflicts. We do as much as possible to prevent third-party plugins impacting Page Builder, unfortunately, this is one of those instances where we aren’t able to prevent the conflict.

    I really wish we had better news. Thanks for reading.

  12. 2 years, 4 months ago jfreak53

    Though I understand the problem you see on your end, other page builders do not have this problem, so why does SiteBuilder? I am correctly using Avada, and WPBakery, both with ChronoForms5, without any problems. Both of them have Custom HTML sections that also are on the same pages as a ChronoForms shortcode. So why do they play nice but this does not?

    I’m not just blowing smoke here, I am a developer with 16 years in the field, if they don’t have issues with this neither should this plugin.

  13. 2 years, 4 months ago Andrew Misplon Hi, I Work Here

    Thanks for your feedback and further info.

    What I’ve observed in my local testing is that the issue is completely independent of the Custom HTML widget. It isn’t currently possible to successfully save a Chrono Forms 5 shortcode in Page Builder by SiteOrigin.

    During testing I created a new page, inserted a Text widget, inserted a Chrono Forms 5 shortcode into that Text widget in Page Builder by SiteOrigin and saved. Page Builder can’t properly save and the contents are dropped into the regular editor. A conflict is preventing Page Builder by SiteOrigin from correctly saving the contents.

    The shortcode working in Avada and Visual Composer and not in Page Builder by SiteOrigin is super unfortunate and definitely not what we want to happen. I’ve logged this issue on our side. If the Chrono Forms 5 developers wanted to work with us to resolve this, we’d be happy to help out. I wish I could do more and fix this for you right away. Given the small size of our team and Chrono Forms 5 only having 800+ active installs, it’s very hard to jump this to the very top of the development list. I realise this won’t be at all what you want to hear. Despite our best intentions, this is unfortunately, the situation we’re in at the moment. If I had a hotfix solution, I’d definitely send one. We’ve checked all the possible quick fixes.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More