SiteOrigin breaks WP Customizer

  • Resolved Frank Shrum

    (@frankshrum)


    7 years, 2 months ago

    Customizer quit working so I deactivated all plugin to find what broke it. Black Studio TinyMCE Widget was the culprit… Leaving it deactivated I proceeded to reactivate everything except Black Studio TinyMCE Widget and it broke again so back to square 1.

    I went and deactivated everything and started reactivating them alphabetically, i.e all A’s, then all B’s, then all C’s and so on…

    I got to the “S’s” and it broke again. Deactivated the “S’s” and started reactivating them one at a time getting to SiteOrigin Widgets Bundle and they broke again. Deactivated that and then I reactivated SiteOrigin Widgets by CodeLights and it broke, again, so I deactivated it.

    I proceeded to reactivate all the rest of the plugins and the site never broke again.

    For what it’s worth from me, I believe your problem is Black Studio TinyMCE. I had to quit using your editor widget to get my sit to stop breaking a few weeks ago until you got something fixed concerning Black Studio TinyMCE and now their plugin is broke and so is your plugin and both of them are throwing the exact same error, whatever this error might be.

    btw I did try WordPress’ themes to see if it could be my theme, but it did the same thing with them.

    Below is what I documented as I discovered this problem and sought to find what’s causing it.

    Testing. Is this what’s breaking WP Customizer? Black Studio TinyMCE Widget

    YEP!!! This is what is breaking WP Customizer… Black Studio TinyMCE Widget

    Reactivated everything and found that another plugin’s breaking it the same way…

    Here’s the plugin I found breaking it, now – SiteOrigin Widgets Bundle

    Now this one breaks it – SiteOrigin Widgets by CodeLights

    Ok here’s what I’ve found breaking the Customizer in WordPress:

    Black Studio TinyMCE Widget, then SiteOrigin Widgets Bundle, and finally SiteOrigin Widgets by CodeLights

    btw I’ll be posting this exact same problem to the other plugins as I posted here.

    Hope y’all get this fixed, soon.

    Shalom,
    Frank Shrum

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Contributor alexgso

    (@alexgso)

    Hi Frank,

    That sounds like you’ve reached the memory limit. You need to apply a pretty hands on fix to resolve this issue. This article would be a good read as it’ll outline how to change it. You’ll need to edit wp-config.php. If you’re unfamiliar with FTP, I would recommend asking your hosting provider for help with editing this file.

    Thread Starter Frank Shrum

    (@frankshrum)

    Thanks, but this did not work.

    Even tho I never told you I received any error messages, which I did not receive, I tried your solution then reactivated the plugins and, wouldn’t you know it, they broke the WP Customizer, again, so I disabled them again.

    Any other ideas?

    Thanks.
    Frank

    Plugin Contributor alexgso

    (@alexgso)

    Hi Frank,

    Please enable WP_DEBUG and enable the plugins once more. Enabling WP_DEBUG will require once again editing wp-config.php.

    Enabling the plugins will cause an error again but at least this time you’ll be able to see the error message due to WP_DEBUG being visible. If you can’t see an error message, can you send me a screenshot of what you see?

    • This reply was modified 7 years, 2 months ago by alexgso. Reason: Added WP_DEBUG Codex link
    Thread Starter Frank Shrum

    (@frankshrum)

    ok. Here’s what I get:

    I took this just as the page started loading, but before the beginning part of the page appeared:

    Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; shaHelper has a deprecated constructor in /home/XXXXXXX/public_html/XXXXXXX/wp-content/plugins/amazon-product-in-a-post-plugin/inc/amazon-product-in-a-post-sha256.inc.php on line 39

    Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/XXXXXXX/public_html/XXXXXXX/wp-content/plugins/amazon-product-in-a-post-plugin/inc/amazon-product-in-a-post-sha256.inc.php:39) in /home/XXXXXXX/public_html/XXXXXXX/wp-content/plugins/essential-real-estate/public/partials/property/class-ere-compare.php on line 38

    Notice: add_utility_page is deprecated since version 4.5.0! Use add_menu_page() instead. in /home/XXXXXXX/public_html/XXXXXXX/wp-includes/functions.php on line 3831

    Notice: has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/XXXXXXX/public_html/XXXXXXX/wp-includes/functions.php on line 4023

    Notice: Undefined variable: bare_url in /home/XXXXXXX/public_html/XXXXXXX/wp-content/plugins/slider-video/Slider-Video.php on line 34

    Notice: Undefined variable: comment_id in /home/XXXXXXX/public_html/XXXXXXX/wp-content/plugins/slider-video/Slider-Video.php on line 34

    After activating the Black Studio Widget the error message through this. It is the same as above but with additional warnings about another plugin:

    Warning: Cannot modify header information – headers already sent by (output started at /home/XXXXXXX/public_html/XXXXXXX/wp-content/plugins/amazon-product-in-a-post-plugin/inc/amazon-product-in-a-post-sha256.inc.php:39) in /home/XXXXXXX/public_html/XXXXXXX/wp-includes/pluggable.php on line 1210

    Warning: Cannot modify header information – headers already sent by (output started at /home/XXXXXXX/public_html/XXXXXXX/wp-content/plugins/amazon-product-in-a-post-plugin/inc/amazon-product-in-a-post-sha256.inc.php:39) in /home/XXXXXXX/public_html/XXXXXXX/wp-includes/pluggable.php on line 1210

    Plugin Contributor alexgso

    (@alexgso)

    Hi frankshrum,

    Thanks, to clarify, what happens if you disable all plugins but the “problematic” plugins? Does this issue remain? If it doesn’t, please try activating plugins one by one until the issue remains.

    Hi frankshrum,
    We are the creators of the Amazon Product in a Post plugin – which I can see you have some warnings/notices originating from.

    Our Plugin will be update this week to resolve some of those Warning Notices (and some other things, too). In the meantime, you can (and should) disable the notices/warnings on your site if it is live. The Amazon Plugin has a “Quick Fix – Hide Warning Notices” Option that basically sets the “display_errors” ini flag to off. They will still write to a error log, but will not disrupt the normal loading of the site. You can check that and save the options and see if it helps any.

    Whenever a notice or warning writes to the browser output before the headers are loaded, it prevents anything that relies on writing additional data to the headers from completing, i.e., redirecting, etc. (that is what those “Warning: Cannot modify header information” warnings are coming from).

    It may not solve your issues completely, but it is a start in the right direction.

    Warm regards,
    Don

    I just re-read the thread saw you enabled WP_DEBUG – and, of course, once you disable WP_DEBUG, those warnings will also go away.

    But for what its worth, the Amazon Plugin will be updated this week with those fixes in it.

    Best of Luck!
    Don

    Thread Starter Frank Shrum

    (@frankshrum)

    Ok sorry for being so late. I’m up in the night answering this for ya.

    alexgso (@alexgso) wrote: what happens if you disable all plugins but the “problematic” plugins? Does this issue remain?

    Yes is remains. As long as these 3 plugins are active the issue remains. When I disable these plugins none of the rest of the plugins break it. Now these plugins individually break the site the same way. I disabled everything and reactivated these plugins one at the time and they each one broke the site individually.

    _______
    Don Fischer (@prophecy2040) Thank you for this knowledge. I included them in this because they appeared along with the others. Yes, I changed the DEBUG script back to false after the testing.

    Thank you for your diligence in seeing this and addressing it as you told me, here.

    I hope this helps. It’s 3:46 a.m. here in the Philippines right now so if you ask anything else I will be back in a few hours as I need to get some sleep.

    Thanks.

    Plugin Contributor alexgso

    (@alexgso)

    Hi frankshrum,

    Just to confirm. what happens if you disable all plugins but the “problematic” plugins? In other words, what happens if only those plugins are enabled (as in, no plugins outside of the “problematic” plugins are active)? If it still occurs, what happens if you temporarily change theme?

    Thread Starter Frank Shrum

    (@frankshrum)

    alexgso

    (@alexgso) wrote: —>> Just to confirm. what happens if you disable all plugins but the “problematic” plugins? In other words, what happens if only those plugins are enabled (as in, no plugins outside of the “problematic” plugins are active)? If it still occurs, what happens if you temporarily change theme? <<—

    ok I’ve deactivated ALL plugins.

    The site works.

    Activated Black StudioTinyMCE Widget.

    The site works.

    Activated SiteOrigin Widgets Bundle.

    The site works.

    Activated SiteOrigin Widgets by CodeLights.

    The site works.

    Activate all other plugins including these 3 and the site breaks again.
    {Continues}

    Thread Starter Frank Shrum

    (@frankshrum)

    {Continued}

    Deactivate all plugins except these 3 and it works again.

    Activated plugins starting with “A”. leaving Black StudioTinyMCE Widget active and it breaks the site.

    Deactivated Black Studio TinyMCE Widget and the site works again.

    Activated SiteOrigin Widgets Bundle and the site broke again.

    Deactivated SiteOrigin Widgets Bundle and the site worked again.

    Activated SiteOrigin Widgets by CodeLights and the site broke again.

    Deactivated SiteOrigin Widgets by CodeLights and the site worked again.

    At this point I deactivated SiteOrigin Widgets by CodeLights then activated Black Studio TinyMCE Widget and started deactivating each of the “A’s” one at a time to see which one is involved with interacting with it.

    Ok When I deactivated each one the site continued to break until I deactivated the Amazon Associates Link Builder plugin and the site worked again.

    I decided to turn on the other 2 plugins, SiteOrigin Widgets Bundle and SiteOrigin Widgets by CodeLights, at the same time as Black Studio TinyMCE Widget and the site continued to work.

    I decided to reactivate all the other plugins I’m using except the Amazon Associates Link Builder plugin and the site continued to work properly.

    It looks like I did not go far enough to verify the plugin that was breaking the other plugins. I was looking for what plugins were breaking the site, not searching to see which plugins are breaking other plugins.

    Thank you for pushing me to go RE-check everything and now I have learned another lesson that will help me to troubleshoot problems that happen with my site so that, perhaps, in the future I will diagnose it more properly than I did this time.

    Sorry for misdiagnosing this problem. I’ll be more diligent to get it right should I have any more problems like this.

    • This reply was modified 7 years, 2 months ago by Frank Shrum. Reason: I edited this to mark it as resolved
Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘SiteOrigin breaks WP Customizer’ is closed to new replies.