“Plugin could not be activated because it triggered a fatal error.”

  • Resolved klasicken

    (@klasicken)


    3 years, 2 months ago

    Woocommerce plugin shows this fatal error when i try to activate it. It’s a new site and a first time activation. I’m also experiencing it on another site.

    Fatal error: Uncaught mysqli_sql_exception: Table ‘mywevqdr_wp541.wpm2_actionscheduler_actions’ doesn’t exist in /home/mywevqdr/WPCrashCourse.klasicken.com/wp-includes/wp-db.php:2056 Stack trace: #0 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-includes/wp-db.php(2056): mysqli_query() #1 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-includes/wp-db.php(1945): wpdb->_do_query() #2 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-includes/wp-db.php(2695): wpdb->query() #3 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-admin/includes/upgrade.php(2749): wpdb->get_results() #4 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Abstract_Schema.php(135): dbDelta() #5 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Abstract_Schema.php(63): ActionScheduler_Abstract_Schema->update_table() #6 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php(36): ActionScheduler_Abstract_Schema->register_tables() #7 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(57): ActionScheduler_DBStore->init() #8 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler.php(158): ActionScheduler_HybridStore->init() #9 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php(55): ActionScheduler::init() #10 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php(61): action_scheduler_initialize_3_dot_3_dot_0() #11 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/includes/class-woocommerce.php(509): include_once(‘/home/mywevqdr/…’) #12 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/includes/class-woocommerce.php(172): WooCommerce->includes() #13 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/includes/class-woocommerce.php(131): WooCommerce->__construct() #14 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/woocommerce.php(47): WooCommerce::instance() #15 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-content/plugins/woocommerce/woocommerce.php(62): WC() #16 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-admin/includes/plugin.php(2286): include_once(‘/home/mywevqdr/…’) #17 /home/mywevqdr/WPCrashCourse.klasicken.com/wp-admin/plugins.php(191): plugin_sandbox_scrape() #18 {main} thrown in /home/mywevqdr/WPCrashCourse.klasicken.com/wp-includes/wp-db.php on line 2056

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

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

  • Hello,

    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
    • Test to see if the issue has been resolved

    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.

    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 2 replies - 1 through 2 (of 2 total)
  • The topic ‘“Plugin could not be activated because it triggered a fatal error.”’ is closed to new replies.