plugin killed site on update

  • Resolved snyggapa

    (@snyggapa)


    1 year, 4 months ago

    Updated to the latest version and the site choked with this FYI:

    Any idea on the cause? I had to put wordpress in recovery mode as it killed the entire site. Disabled the plugin, completed the updates of everything else, reenabled the plugin and it looks OK for now. But I don’t think you should have untrapped errors

    Thanks

    When seeking help with this issue, you may be asked for some of the
    following information:
    WordPress version 6.7.1
    Active theme: WSLC theme Astra (version 1.0.0)
    Current plugin: WooCommerce Square (version 4.8.5)
    PHP version 8.2.26 Error Details

    An error of type E_ERROR was caused in line 451 of the file
    /home/myroot/mysite.org/wp-content/plugins/woocommerce-square/woocommerce-square.php.
    Error message: Uncaught Error: Class
    "WooCommerce\Square\Admin\Product_Editor_Compatibility" not found in
    /home/myroot/mysite.org/wp-content/plugins/woocommerce-square/woocommerce-square.php:451
    Stack trace: 0 /home/myroot/mysite.org/wp-includes/class-wp-hook.php(324):

    WooCommerce_Square_Loader->declare_features_compatibility('') 1 /home/myroot/mysite.org/wp-includes/class-wp-hook.php(348):

    WP_Hook->apply_filters(NULL, Array) 2 /home/myroot/mysite.org/wp-includes/plugin.php(517):

    WP_Hook->do_action(Array) 3 /home/myroot/mysite.org/wp-content/plugins/woocommerce/includes/class-woocommerce.php(832):

    do_action('before_woocomme…') 4 /home/myroot/mysite.org/wp-includes/class-wp-hook.php(324):

    WooCommerce->init('') 5 /home/myroot/mysite.org/wp-includes/class-wp-hook.php(348):

    WP_Hook->apply_filters(NULL, Array) 6 /home/myroot/mysite.org/wp-includes/plugin.php(517):

    WP_Hook->do_action(Array) 7 /home/myroot/mysite.org/wp-settings.php(704):

    do_action('init') 8 /home/myroot/mysite.org/wp-config.php(109):

    require_once('/home/myroot…') 9 /home/myroot/mysite.org/wp-load.php(50):

    require_once('/home/myroot…') 10 /home/myroot/mysite.org/wp-admin/admin-ajax.php(22):

    require_once('/home/myroot…') 11 {main}

    thrown
Viewing 8 replies - 1 through 8 (of 8 total)
  • Reynier (a11n)

    (@reynierc)

    1 year, 4 months ago

    Hi @snyggapa

    Thanks for sharing the details! I understand that this happened after updating Square for WooCommerce right?

    From what you’ve provided it looks like the plugin is trying to use a class,WooCommerce\Square\Admin\Product_Editor_Compatibility which it couldn’t find.

    Here’s what I think might be causing the issue and how to fix it. It may be due to missing or corrupt files. The plugin files might not be complete or could have gotten damaged, especially after updates. Deleting the plugin and reinstalling it might help resolve this.

    Could you try this solution and let me know if it works? Also, check if other plugins like WooCommerce need updates. Version incompatibilities might be causing the issue. (Please make sure to back up your site before troubleshooting)

    If the issue persists, a bit more details would be helpful to check for other angles. We’d need system status report to look further. You can find it by going to WooCommerce → Status, selecting Get system report, and then Copy for Support.

    Thread Starter snyggapa

    (@snyggapa)

    1 year, 4 months ago

    Hi. Correct, this happened upon update and is now resolved.

    If you search your forum for “Product_Editor_Compatibility” it seems that this class missing is a common cause to kill your customer’s sites. Is there any way that the call to this can be trapped so that if not found it doesn’t take wordpress down with it?

    Considering how ofhen the same error occurs across different customers of yours, I would suspect that there is some endemic but occasional issue that you would do well to at least defensively code for

    Thanks

    Reynier (a11n)

    (@reynierc)

    1 year, 4 months ago

    Hi @snyggapa

    Thank you for the update and I’m glad to know it’s now resolved. I understand how these incomplete updates can be frustrating.

    Corrupted files can sometimes occur due to a few reasons. During an update, files might not download or install completely due to interruptions in the internet connection, server issues, or conflicts with other plugins.

    These incomplete installations can lead to missing or corrupted files which you have experienced recently. It’s always a good practice to back up your site and ensure a stable connection during updates.

    THRIVE – Web Design Gold Coast

    (@deanoakley)

    1 year, 4 months ago

    I also have this issue. Was there a fix coming?

    Thread Starter snyggapa

    (@snyggapa)

    1 year, 4 months ago

    Doesn’t look like it because square seem to deny that there is a problem, despite numerous reports of the same issue and instead blaming a somewhat unlikely “corrupt installation” – all going corrupt in the same way.

    Mahfuzur Rahman

    (@mahfuzurwp)

    1 year, 4 months ago

    Hi @snyggapa,

    I appreciate you sharing this. If you’ve come across multiple reports of this same issue, could you share those with us? That would help us better understand the pattern and investigate further.

    Looking forward to your reply!

    Thread Starter snyggapa

    (@snyggapa)

    1 year, 4 months ago

    https://ww.wp.xz.cn/search/Product_Editor_Compatibility+intext%3A%22Plugin%3A+WooCommerce+Square%22/

    finds 4 occasions. for a product with not that massive installed based that looks like more than a coincidence and at least worth trapping an potential error here and not just die and take the entire site down

    Thanks

    Zee

    (@doublezed2)

    1 year, 4 months ago

    Hello snyggapa,

    Thank you for sharing the links to the other threads.

    I reviewed all 4 threads and noticed that this one mentions a different issue.
    The other three threads look relevant.

    Please note that WooCommerce Square has over 80000 active installations.
    This kind of issue was reported only 3 times in the past several months.
    This suggests the problem is related to the website configuration.

    Please refer to this thread; it mentioned enabling the opcache.save_comments in PHP settings resolved the issue. The PHP documentation recommends having this option enabled.

    I suggest you contact your host and make sure the opcache.save_comments option is enabled.
    Let me know what they say about this.

    Regarding the management of missing class calls.
    I value your input and will ensure that it is communicated to our developers for their consideration. While we cannot guarantee prompt modifications, your feedback is important for enhancing the plugin’s functionality.

    I truly appreciate your cooperation and patience.

    Best regards.

    • This reply was modified 1 year, 4 months ago by Zee. Reason: Rewrite
Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘plugin killed site on update’ is closed to new replies.