PHP fatal after 4.8.0 update

  • Resolved Austin Ginder

    (@austinginder)


    2 months, 1 week ago

    After updating to v4.8.0 my frontend is seeing a PHP error. Here is the related error in the server logs. Downgrading to v4.7.3 does work as a workaround.

    2024/09/18 11:41:22 [error] 32263#32263: *305304 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Error: Class "WooCommerce\Square\Admin\Product_Editor_Compatibility" not found in /www/public/wp-content/plugins/woocommerce-square/woocommerce-square.php:451
    Stack trace:
    #0 /www/public/wp-includes/class-wp-hook.php(324): WooCommerce_Square_Loader->declare_features_compatibility('')
    #1 /www/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
    #2 /www/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #3 /www/public/wp-content/plugins/woocommerce/includes/class-woocommerce.php(832): do_action('before_woocomme...')
    #4 /www/public/wp-includes/class-wp-hook.php(324): WooCommerce->init('')
    #5 /www/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
    #6 /www/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #7 /www/public/wp-settings.php(700): do_action('init')
    #8 /" while reading response header from upstream, client: x, server: x, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php8.1-fpm.sock:", host: "x:13901", referrer: x
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @austinginder,

    Thank you for reaching out.

    I understand you’re experiencing a PHP error after updating to v4.8.0.

    The error log you provided indicates that the class “WooCommerce\Square\Admin\Product_Editor_Compatibility” is not found in the WooCommerce Square plugin. This could be due to a compatibility issue between the latest version of WooCommerce and the WooCommerce Square plugin.

    Did you already have a chance to run a conflict test by having only WooCommerce and Square for WooCommerce as the active plugins, then switching to a default theme like Storefront or Twenty Twenty-Four? You can run the test from a staging site to avoid messing with your live site.

    While downgrading to v4.7.3 is a temporary workaround, we understand that this is not the ideal solution. Could you also share your system status report so that we can have a better understanding of your site environment?

    Also seeing this fatal error.

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @jimrgbssmg,

    Also seeing this fatal error.

    Sorry to hear that you are experiencing the same issue.

    However, to align with?forum best practices, please create a new topic so that we can address your issue(s) separately.
    You can create a new thread here:?https://www.ads-software.com/support/plugin/woocommerce/#new-topic-0
    Thanks for understanding!

    Thread Starter Austin Ginder

    (@austinginder)

    I believe I have found a fix. It would appear that the websites affected where never properly configured to work with WooCommerce Square. Here are the steps I took.

    wp plugin install woocommerce-square --version=4.7.3 --force
    wp plugin toggle woocommerce-square
    wp plugin toggle woocommerce-square
    wp cache flush

    This seems to restore WordPress with a new message to ensure PHP’s opcache.save_comments is enabled. Next reach out to your web host to have them enable that as described here. Last you should be safe to update WooCommerce Square to the latest version.

    I’ve now encountered this bug on 4 different website. The root issue appears to be that PHP’s opcache.save_comments was never enabled and the plugin isn’t properly detecting that.

    lenashore

    (@lenashore)

    @austinginder – Thanks for this info. I’m in the same boat. Will try this!

    UPDATE: That was the solution!!! Thank you!

    • This reply was modified 2 months ago by lenashore.
Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.

Tags