1.0.3 is not a solution

  • Hi,

    1.0.3 is not a real solution, because if try to deactivate the plugin on one site (multisite-setup) this error occurs.

    2024/05/15 13:15:05 [error] 356221#356221: *74089 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught Error: Call to undefined method WC_Legacy_REST_API_Plugin::remove_notice() in …s/httpdocs/wp-content/plugins/woocommerce-legacy-rest-api/includes/class-wc-legacy-rest-api-plugin.php:129
    Stack trace: 0 /home/snowpaws/httpdocs/wp-includes/class-wp-hook.php(324): WC_Legacy_REST_API_Plugin::on_plugin_deactivated() 1 /home/snowpaws/httpdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 2 /home/snowpaws/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action() 3 /home/snowpaws/httpdocs/wp-admin/includes/plugin.php(828): do_action() 4 /home/snowpaws/httpdocs/wp-admin/plugins.php(211): deactivate_plugins() 5 {main}

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

  • You’re correct, those guys apparently don’t know what they are doing!

    How could this happen? Is there nobody who test before launch?!

    @keeslamper
    Obviously not…

    Had to deactivate because the website crashed.
    WooCommerce is getting worse with every update.

    Strange. I updated to v1.0.3 on all of my agency Woocommerce websites without issues.

    Thread Starter snowpaws

    (@snowpaws)

    @ericreynolds007 have you tried to disable this plugin in the backend? That is where this issue occured again. Since I do not need the rest api, I used the time to remove it completly.

    Regards, Mario

    I disabled the plugin because triggers fatal error.

    The crazy thing is I did not install this plugin. This was installed automatically by WooCommerce. I did not have the legacy rest api activated. Unacceptable from a plugin owned by Automattic

    Barry

    (@barryhughes-1)

    We’re very sorry for this further miss, and are working on a fix.

    @barryhughes-1 I did post a solution in the “v1.0.2 Critical Error” thread which should point you in the right direction.

    A new version is out (1.0.4), fixing the fatal error and should be stable. We deeply apologize for the inconvenience and disruption this has caused.

    easiest solution is to don’t install it automatically without any admin interaction. There are almost 5 million woocommerce stores online, you can’t test all possible combinations of php/server/plugins that might happen.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘1.0.3 is not a solution’ is closed to new replies.