Plugin throws fatal error. Fix instructions don’t work.

  • Resolved bwebdev

    (@bwebdev)


    1 year, 8 months ago

    Our website was getting a fatal error after upgrading to v2.0.x. The error log indicated a missing database table:

    “Fatal error: Uncaught mysqli_sql_exception: Table ‘reach4life_1.wp_actionscheduler_actions’ doesn’t exist in /var/www/html/reach4life_1/wp-includes/wp-db.php:2056”

    After removing the plugin and reinstalling our site worked but we could not reactivate the plugin because of the missing table. I followed the instructions shown here to recreate the tables with the Action Scheduler plugin:

    https://wpmailsmtp.com/docs/how-to-troubleshoot-action-scheduler-issues-wp-mail-smtp-2-1-1/#install-action-scheduler

    However the Action Scheduler plugin also fails to activate due to the same missing table:

    Fatal error: Uncaught mysqli_sql_exception: Table ‘reach4life_1.wp_actionscheduler_actions’ doesn’t exist in /var/www/html/reach4life_1/wp-includes/wp-db.php:2056

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Dake

    (@dakeg)

    Hi @bwebdev

    Thanks for reaching out and we’re sorry to hear that you are experiencing issues with setting up the Action Scheduler tables.

    Based on what you’ve described so far.

    It is most likely a database issue. To be more specific, the database user you are using or the database itself does not allow new table creation.

    Please check any DB error logs if you have access to those. Please also check the table creation permissions for the DB user that is used for your website.

    If you are not certain what we are referring to, please reach out to your website host support.

    Thread Starter bwebdev

    (@bwebdev)

    It turns out that the site in question was running an old version of WordPress: v5.8.2. After we updated to v6.1.1, Easy WP SMTP could be activated without problems. Your plugin and Action Scheduler list WordPress 5.2 as the minimum version so that shouldn’t have been an issue.

    Plugin Support Dake

    (@dakeg)

    Hi @bwebdev

    Thank you for sharing this with us, we’re glad to hear the issue has been resolved, but we apologize for the inconvenience.

    I have informed our developers about the 5.2 minimum version compatibly issue you experienced, so we can look into it further.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plugin throws fatal error. Fix instructions don’t work.’ is closed to new replies.