• Resolved videsigns.ca

    (@videsignsca)


    HI there,

    I’m getting the error below on several websites, can you help provide insight into what the problem is? I cannot access any MailPoet areas on the websites affected:

    Migration “MailPoet\Migrations\Db\Migration_20240725_182318_Db” failed. Details: An exception occurred while executing a query: SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘step_key’ in ‘where clause’

    I did migrate the websites from a different server a month ago but haven’t had any problems until now.

    Thanks for your time,

    • This topic was modified 3 months, 3 weeks ago by videsigns.ca.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter videsigns.ca

    (@videsignsca)

    The error goes away when I revert to the previous version of Mailpoet. Any ideas of how to fix this so I can update the plugin?

    Thank you

    I am getting the same issue on one of our sites. The roll-back approach in the previous post doesn’t work if you are using the premium version of the plugin.

    Thanks

    Plugin Support Dani F. a11n

    (@danielinhou)

    Hi there ????!

    Thank you for reaching out to MailPoet Support!

    After reviewing the error message you’ve shared, it appears to be related to a specific database column that MailPoet is unable to locate. I’ll share some steps that have helped resolve similar issues. Please follow the steps below carefully:

    1. Back-Up Your Site and Database: Before proceeding with any changes, it’s crucial to ensure that you have a complete backup of your site and database. This step will safeguard your data, allowing you to restore your site to its current state if needed.
    2. Access phpMyAdmin from your website hosting settings.
    3. Locate the *_mailpoet_migrations table in the database.
    4. Delete all the entries in the *_mailpoet_migrations table. This action will force the migrations to re-run and update the database tables with the necessary columns.
    5. Deactivate and Reactivate the MailPoet Plugin: Although this step may not always be necessary, it can help ensure that the changes take effect properly. Navigate to the “Plugins” section of your WordPress dashboard, deactivate MailPoet, and then reactivate it.
    6. Test the Solution: Ideally, these steps should be performed on a staging site to avoid impacting your live site. If you don’t already have a staging environment set up, we recommend using the WP Staging plugin, which you can find here:?WP Staging Plugin.
      ?

    Important: Before proceeding with these steps, it’s critical to ensure that you have a complete backup of your site and database. This measure would safeguard your data in case of any unintended complications during the process.

    Doing this should prevent those errors from showing up again. Also ensure you’re using the latest version of the MailPoet plugin.

    Cheers!

    Thread Starter videsigns.ca

    (@videsignsca)

    Thanks so much, that worked great!

    Hi,

    This advice worked well. No error messages

    Thank You!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.