Home>Support>SiteOrigin Layout Builder crashes when used in Appearance > Customise section

SiteOrigin Layout Builder crashes when used in Appearance > Customise section

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].

Hi,
I’m not sure when this started happening but every time I try to amend a section of my homepage using the Customise(Appearance) area of WordPress… specifically the parts setup using the “Layout Builder”, when I then click “Open Builder” the page crashes. This has been tested on several web browsers.

I have taken a copy of the URL from when the page crashes and pasted this into Notepad to view it and its a huge URL String that seems never ending. I was unable to post a copy of it here unfortunately as your forums blocked me from doing so.

Does anyone know how to resolve so that I can amend the sections of my homepage that use “Layout Builder” ?

Thanks
Greg

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

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

    Hi Greg

    Thanks for reaching out.

    There are a few possible causes. Do you have a bit of a technical background? If so, you could use FTP or your hosting file manager to change WP_DEBUG from false to true in your WordPress wp-config.php file located in the root WordPress folder. You can also add WP_DEBUG_LOG which will write a log file to the wp-content folder. More on that here https://www.wpbeginner.com/wp-tutorials/how-to-set-up-wordpress-error-logs-in-wp-config/. If you’re able to set up error logging and replicate the error, there is a good chance an error will be written to the debug file. Is that perhaps something you might be up for?

  2. 4 years, 9 months ago greghhh888

    Hi Andrew,
    I have managed to set this up.
    Here is what I see:
    [30-Sep-2020 13:46:57 UTC] PHP Deprecated: wpcf7_scan_shortcode is deprecated since Contact Form 7 version 4.6! Use wpcf7_scan_form_tags instead. in /var/www/vhosts/mywebsite.co.uk/httpdocs/wp-content/plugins/contact-form-7/includes/functions.php on line 378
    [30-Sep-2020 13:46:57 UTC] PHP Notice: Undefined variable: attribut_new_tab in /var/www/vhosts/mywebsite.co.uk/httpdocs/wp-content/themes/zerif-lite/footer.php on line 104

    Are these easy to fix ?
    Thanks

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

    Hi Greg

    Thanks for the update.

    At the end of this process, please, remember to disable debug so that warnings, notices, and errors don’t print to your site when you aren’t actively troubleshooting.

    The above aren’t serious and aren’t likely to be involved with the issue. Are there any notices printed to the screen (besides the above) when the issue occurs in the Customizer?

  4. 4 years, 9 months ago greghhh888

    Hi Andrew, no, nothing appears. The Chrome page responds with “This site cannot be reached, the website unexpectedly closed the session”
    As mentioned in the OP the URL string returned is abnormally long.
    Thanks,
    Greg

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

    Thanks.

    Are there errors in red text in the console when the issue occurs? Here is how to check https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis.

  6. 4 years, 9 months ago greghhh888

    Yes:

    ti-customizer-notify-customizer.js?ver=5.5.1:99 Uncaught TypeError: jQuery(…).live is not a function
    at HTMLDocument. (ti-customizer-notify-customizer.js?ver=5.5.1:99)
    at i (jquery.js?ver=1.12.4-wp:2)
    at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:2)
    at Function.ready (jquery.js?ver=1.12.4-wp:2)
    at HTMLDocument.J (jquery.js?ver=1.12.4-wp:2)

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

    Thanks. You should be able to rectify that using the following plugin https://wordpress.org/plugins/enable-jquery-migrate-helper/. It’ll also let you know which plugins are an issue with regards to the WordPress core removing jQuery Migrate.

  8. 4 years, 9 months ago greghhh888

    OK I will give that a go. Thanks Andrew

  9. 4 years, 9 months ago greghhh888

    Yes that worked, appreciate the help.

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

    Super, glad to hear that helped. It might be worth reaching out to the plugin or theme author/s mentioned in the jQuery Migrate Helper warning to ask if they can resolve the issue. Once warnings are no longer showing you can remove the jQuery Migrate Helper plugin.

  11. 4 years, 9 months ago greghhh888

    Okay will do. Thanks again

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

    Sure, no problem. Cheers for now :)

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