Critical error upgrading 2.0.0 > 2.0.1

  • Resolved dmac

    (@darrenmcentee)


    1 year, 9 months ago

    Hi, getting the following when upgrading from 2.0.0 to 2.0.1.

    Current plugin: Easy WP SMTP (version 2.0.1)
PHP version 8.1

Error Details
=============
An error of type E_ERROR was caused in line 44 of the file /zzz/yyy/public_html/wp-content/plugins/easy-wp-smtp/vendor/woocommerce/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php. Error message: Uncaught RuntimeException: Error saving action: Error saving action: Duplicate entry '0' for key 'PRIMARY' in /zzz/yyy/public_html/wp-content/plugins/easy-wp-smtp/vendor/woocommerce/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44
Stack trace:
#0 /zzz/yyy/public_html/wp-content/plugins/easy-wp-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(242): ActionScheduler_DBStoreMigrator->save_action(Object(ActionScheduler_Action), NULL)
#1 /zzz/yyy/public_html/wp-content/plugins/easy-wp-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_ActionFactory.php(177): ActionScheduler_HybridStore->save_action(Object(ActionScheduler_Action))
#2 /zzz/yyy/public_html/wp-content/plugins/easy-wp-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->store(Object(ActionScheduler_Action))
#3 /zzz/yyy/public_html/wp-content/plugins/easy-wp-smtp/
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Dake

    (@dakeg)

    Hi @darrenmcentee

    Thanks for reaching out to us and we’re sorry to hear that you ran into an error while updating Easy WP SMTP.

    I have informed our developers about this and we will get back to you as soon as we have an update.

    Plugin Support Dake

    (@dakeg)

    Hi @darrenmcentee

    Thank you for your patience.

    This error is related to the Action Scheduler (3d party library) database table.

    Our developers suspect that the most likely reason is that “auto-increment” was not set for the?actionscheduler_actions?table.

    The ideal solution would be to set auto-increment for the?action_id?column and remove the record with ID “0” which was created without auto-increment and has the wrong ID.

    Ideally, we would recommend backing up your website before performing these database table changes.

    Thread Starter dmac

    (@darrenmcentee)

    Thank you @dakeg, that fixed the issue i was having, and it is back working again.

    For anyone else with the same issue, here are further details:

    To enable auto increment for a column in phpMyAdmin:

    Click on?Table?>?Structure?tab > Under?Action?Click Primary (set as primary).
    Click on?Change?on the pop-up (or new window), check?A_I.
    Also make sure you have selected?None?selected in the Default column.

    Your’s may look different depending on your server’s phpMyAdmin version:

    Plugin Support Dake

    (@dakeg)

    Hi @darrenmcentee

    You’re welcome, glad we could help.

    Also, thank you very much for sharing a screenshot of your fix ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Critical error upgrading 2.0.0 > 2.0.1’ is closed to new replies.