Support » Plugin: WooCommerce » Update 4.4.0 Causes Fatal Errors

  • Resolved usat009


    Once I updated to 4.4.0 it caused fatal errors in the JetPack Plugin an the WPRocket Plugin, instantly making my backend inaccessible outside of WPEngines recovery mode. I had to role back the website three hours, losing all of today’s work (my fault since i should have backed up before performing the update).

    It seemed like the errors would start appearing across more plugins as it was first WPRocket, and i disabled it temporarily, existed recovery mode, then it failed again, citing Jetpack fatal error, and i wasn’t going to stick around and see what else started failing so i rolled it back to before the WooCommerce update.

    And other users reporting critical failures after this update?

Viewing 15 replies - 1 through 15 (of 45 total)
  • Rahim


    Hi @usat009

    Same here.

    After update to 4.4, I had to deactivate the WP Rocket by renaming its folder via file manager!

    Same here. For me I had to rename the entire Woocommerce plugin folder to access the dashboard and get past the Fatal Error screen.

    This is the error I get:

    Fatal error: Uncaught Error: Call to undefined method League\Container\Definition\Definition::withArgument() in /home/pjmatos/public_html/ Stack trace: #0 /home/pjmatos/public_html/ WP_Rocket\ServiceProvider\Options->register() #1 /home/pjmatos/public_html/ League\Container\ServiceProvider\ServiceProviderAggregate->register('options') #2 /home/pjmatos/public_html/ League\Container\Container->get('options') #3 /home/pjmatos/public_html/ WP_Rocket\Plugin->load() #4 /home/pjmatos/public_html/ rocket_init('') #5 /home/pjmatos/public_html/ WP_H in /home/pjmatos/public_html/ on line 37

    Same here, just finished a client website with deadline in 6 hours, then updated to Woocommerce 4.4.0. and my site crashed with fatal php error. The database was updated to the new version. How the heck can I go back now. I am on fire!!!!!!!!!

    Warning: Declaration of ET_Theme_Builder_Woocommerce_Product_Variable_Placeholder::get_available_variations() should be compatible with WC_Product_Variable::get_available_variations($return = ‘array’) in /home/customer/www/ on line 8
    Warning: Cannot modify header information – headers already sent by (output started at /home/customer/www/ in /home/customer/www/ on line 1296

    This issue can be temporary fixed by renaming the wp-rocket folder.

    Same issues, i tried to rename wp-rocket and deleted cache but I have still problem

    I rename foder plugin Rocket.
    Then it is ok

    • This reply was modified 3 years, 6 months ago by nguyenquyetvn.

    Same here, glad I installed 4.4 on a test system first. Hiding the WP Rocket plugin folder eliminated the error. I’m holding off installing 4.4 on my live system until this is resolved.

    People: Always install updates on a test system first! Plugins like Duplicator can create a new copy of your site in a sub-folder in about 15 minutes and save you a lot of heartache and headache.

    In my case it seems to be a compatibility issue with Divi Theme Builder and WooCommerce 4.4.0.

    Same here. I hope there is a quick fix for it, cause the site speed suffers without WP Rocket and CDN.

    I solved for now rolling previous version 4.3.3

    Same problem. Reverted woocommerce to 4.3.3 I hope the db is not all messed up now b/c I had tried to update to wc 4.4.0!

    Need WP-Rocket AND Woo-Commerce latest versions to work togetharrr!

    • This reply was modified 3 years, 6 months ago by chonkat.

    Yup, same thing for me, had to disable WPRocket for now…

    Just realized it also breaks for me the analytics section of woocommerce even with wp rocket disabled.

    Same problem hier. Reverted woocommerce to 4.3.3 until there is a solution.

    • This reply was modified 3 years, 6 months ago by capitancapo.
Viewing 15 replies - 1 through 15 (of 45 total)
  • The topic ‘Update 4.4.0 Causes Fatal Errors’ is closed to new replies.