WooCommerce Plugin Warning after Update

  • Resolved narisara

    (@narisara)


    4 years, 11 months ago

    I have Problem about updating/activate the WooCommerce Plugin,

    at First I tried to update the plugin, then the Website went down
    and showing the WARNING Message below;—-

    Then I contacted to the Hosting Service to help me DEACTIVATE the plugin,
    I got the website back then tried to ACTIVATE the plugin, and it again bring the Website down.

    Right now they have deactivated it for me, But I don’t know how I will arrange to make make it work? Can I have a support please. Thank you in advance.

    —————————————————————————–
    Warning: include_once(/var/www/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php): failed to open stream: No such file or directory in /var/www/wp-content/plugins/woocommerce/includes/class-woocommerce.php on line 489

    Warning: include_once(): Failed opening ‘/var/www/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php’ for inclusion (include_path=’.:/opt/remi/php73/root/usr/share/pear:/opt/remi/php73/root/usr/share/php:/usr/share/pear:/usr/share/php’) in /var/www/wp-content/plugins/woocommerce/includes/class-woocommerce.php on line 489

    Warning: require(/var/www/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/Package.php): failed to open stream: No such file or directory in /var/www/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 87

    Fatal error: require(): Failed opening required ‘/var/www/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/Package.php’ (include_path=’.:/opt/remi/php73/root/usr/share/pear:/opt/remi/php73/root/usr/share/php:/usr/share/pear:/usr/share/php’) in /var/www/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 87

    Notice: is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /var/www/wp-includes/functions.php on line 5313

    Notice: is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /var/www/wp-includes/functions.php on line 5313
    There has been a critical error on this website. Please check your site admin email inbox for instructions.

    Learn more about troubleshooting WordPress.
    ——————————————-

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • mother.of.code

    (@imazed)

    The Mother of Code

    4 years, 11 months ago

    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 problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, 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.

    mtg169

    (@mtg169)

    4 years, 11 months ago

    The warnings and notices you can ignore.

    The fatal error is coming directly from your WooCommerce files, so disabling other plugins isn’t going to help. The solution would be to fully delete the WooCommerce plugin and files and reinstall because this file woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php is trying to include woocommerce/packages/woocommerce-blocks/src/Package.php and it apparently doesn’t exist in your WooCommerce plugin files.

    Plugin Support Tseten a11n

    (@tibetanitech)

    4 years, 11 months ago

    I understand you are referring to the fatal error related to the WooCommerce files you see on your site after updating WooCommerce.

    I looked into my test site with the WooCommerce version 5.3.0 and I can assure you that I don’t have any fatal error logs that you mentioned.

    Usually, isolated behavior like what you describe and which has not displayed during our cross testing can be related to code with another plugin or a theme that is causing a potential conflict of some kind.

    Please do a full conflict test as mentioned by my colleague and let us know how that goes.

    MayKato

    (@maykato)

    4 years, 11 months ago

    Hi @narisara

    We’ve not heard back from you in a while, so I’m marking this thread as resolved. Hopefully, you were able to find a solution to your problem! If you have further questions, please feel free to open a new topic.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘WooCommerce Plugin Warning after Update’ is closed to new replies.

Tags