Getting error when trying to deactive this plugin

  • Resolved Mindas22

    (@mindas22)


    5 years, 7 months ago

    Hi, I am trying to deactivate and remove this plugin, but getting page:

    The site is experiencing technical difficulties. Please check your site admin email inbox for instructions.

    nginx error logs gives this:

    2019/08/07 10:50:14 [error] 9753#9753: *390924 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function _doing_it_wrong(), assed in /var/www/example.com/public_html/wp-content/plugins/woocommerce-admin/includes/page-controller/class-wc-admin-page-controller.php on line 193 and exactly 3 expected /var/www/example.com/public_html/wp-includes/functions.php:4735
    Stack trace:
    #0 /var/www/example.com/public_html/wp-content/plugins/woocommerce-admin/includes/page-controller/class-wc-admin-page-controller.php(193): _doing_it_wrong(‘get_current_pag…’Current page re…’)
    #1 /var/www/example.com/public_html/wp-content/plugins/woocommerce-admin/includes/page-controller/class-wc-admin-page-controller.php(368): WC_Admin_Page_Controller->get_currepage()
    #2 /var/www/example.com/public_html/wp-content/plugins/woocommerce-admin/includes/page-controller/page-controller-functions.php(49): WC_Admin_Page_Controller->is_registered_p()
    #3 /var/www/example.com/public_html/wp-co” while reading response header from upstream, client: 79.xx.xx.xxx, server: example.com, request: “GET /wp-admin/tools.php?paswift-performance&subpage=deactivate&swift-nonce=aab15d9eb1 HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php/php7.3-fpm.sock:”, host: “example.com”, referrer: “https://example.com/wp-admin/plugins.php”

    Thanks for support!

Viewing 1 replies (of 1 total)
  • Thread Starter Mindas22

    (@mindas22)

    I could resolve this by deactivating WooCommerce Admin plugin first.
    Then Swift Performance Lite deactivated with no issues.

Viewing 1 replies (of 1 total)
  • The topic ‘Getting error when trying to deactive this plugin’ is closed to new replies.