PHP error undefined function should_display_compatibility_notices()

  • Resolved Demian

    (@demian85)


    3 years, 1 month ago

    Hi,

    My Environment updated to 6.2.0 and I was not able to log in to the backend. I then downgraded to 5.8.0, but it gives me the following stack trace error. I am not able to figure out what is going on, disabling other plugins does not help, also not able to open the backend. I do not use woocommerce-block or gutenberg:

    [15-Feb-2022 17:29:04 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function Automattic\WooCommerce\Blocks\Domain\should_display_compatibility_notices() in /public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/Domain/Bootstrap.php:130
Stack trace:
#0 /public_html/wp-includes/class-wp-hook.php(307): Automattic\WooCommerce\Blocks\Domain\Bootstrap->Automattic\WooCommerce\Blocks\Domain\{closure}('')
#1 /public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
#2 /public_html/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
#3 /public_html/wp-admin/admin-header.php(303): do_action('admin_notices')
#4 /public_html/wp-admin/plugins.php(605): require_once('/home/demian/do...')
#5 {main}
  thrown in /public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/Domain/Bootstrap.php on line 130
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Demian

    (@demian85)

    I downgraded to 6.1.1 and now WooCommerce is working again. Still this error when updating to 6.2.0 is strange, and I am wondering how I can fix this.

    Mirko P.

    (@rainfallnixfig)

    Hi there ??

    This kind of problem is usually caused by a conflict with your theme or with another plugin. The best way to determine this is to:

    • Temporarily switch your theme to Storefront
    • Disable all plugins except for WooCommerce
    • Repeat the action that is causing the problem

    If you’re not seeing the same behavior after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated.

    Reactivate the theme first and check again. Then, go on and reactivate your other plugins one by one, testing after each, until you find the one causing conflict.

    You can find a more detailed explanation on how to do a conflict test here: https://docs.woocommerce.com/document/how-to-test-for-conflicts/.

    I’d also suggest installing a plugin called Health Check & Troubleshooting. This is a plugin developed by the WordPress community and it allows you to disable plugins without affecting your current site visitors.

    Thanks.

    Thread Starter Demian

    (@demian85)

    @rainfallnixfig

    Thank you for your (standard) reply. But did you read my initial message? I have done this. With everything deactivated. So what’s next?

    Hi @demian85

    Thanks for getting back.

    I understand that you have deactivated all plugins. Did you also change the theme to Storefront as advised by @rainfallnixfig ? Conflict test is the standard and the most effective way to narrow down to problem-sources in WooCommerce setups which is why we recommend the test and insist on conducting it fully.

    From the stack trace error you shared above it seems that there is some custom coding in the site. Please disable all custom coding and let us know if you are experiencing the same error.

    If the issue still persists, please share with us the following:

    1. System Status: You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.
    2. Fatal Error Log: Share a copy of any fatal error log found under WooCommerce > System Status > Logs (if available).
    Margaret S. woo-hc

    (@margaretwporg)

    We haven’t heard back from you in a while, so I’m going to mark this thread as resolved – we’ll be here if and/or when you are ready to continue.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘PHP error undefined function should_display_compatibility_notices()’ is closed to new replies.