• Resolved mattfuaux

    (@mattfuaux)


    I couldn’t find an actual fix for this issue online so here’s one I found myself:

    The Issue:
    There are multiple migration files during updates which aren’t getting run and numerous threads here with Column Not Found errors (usually after a plugin update). Several answers include manually running a table alter query to the database. This would fix one problem then ten more would show up.

    The Fix:
    I don’t know why Mailpoet haven’t posted this themselves but there is a CLI tool for running migrations hidden in the plugin files. Firstly you will want to go to the wp_mailpoet_migrations file in your database and delete all the entries. This will remove any history of the migrations being run (so the next part will actually re-run). Then ssh into your wordpress instance and run the following script:

    wp mailpoet:migrations:run

    This will re-run all the migrations and fix all of the databases up. Hope this helps and you can finally put auto-updates back on instead of sitting at version 4.00

    • This topic was modified 2 years, 6 months ago by mattfuaux.
Viewing 1 replies (of 1 total)
  • Plugin Support Dani F. a11n

    (@danielinhou)

    Hi there @mattfuaux 👋🏽!

    Thank you for reaching out to MailPoet Support!

    I don’t know why Mailpoet haven’t posted this themselves but there is a CLI tool for running migrations hidden in the plugin files. 

    This is interesting. I have just shared this with the MailPoet developers so that they can study it. We’ll document the workaround in our knowledgebase if they find it useful.

    Cheers and thank you so much for contributing!

Viewing 1 replies (of 1 total)

The topic ‘SQLSTATE[42S22]: Column not found !!FIX!!!’ is closed to new replies.