DB Migration Error after update

  • Resolved icypeakcreative

    (@icypeakcreative)


    1 year ago

    Hey dear MailPoet-Team,

    after updating to PHP 8.2 and MailPoet 4.35.0 the plugin throws the following error:

    Migration “MailPoet\Migrations\Db\Migration_20230111_120000” failed. Details: An exception occurred while executing ‘
    ALTER TABLE wp_mailpoet_segments
    ADD display_in_manage_subscription_page tinyint(1) NOT NULL DEFAULT 0
    ‘:

    SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: ‘0000-00-00 00:00:00’ for column ‘deleted_at’ at row 1

    I tried reinstalling the plugin already but the error is still there.
    What can I do?

    Thanks in advance! ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Chris Moreira – a11n

    (@chrism245)

    Hello there,

    Does this problem persist if you downgrade PHP to 7.4? As that’s the most stable version and the one we suggest: https://kb.mailpoet.com/article/152-minimum-requirements-for-mailpoet-3#php_version

    Thread Starter icypeakcreative

    (@icypeakcreative)

    I’m sorry, it seems like I wont be able to test this. My hosting agency only allows me to downgrade to PHP 8.0 which unfortinately doesn’t help.

    Plugin Support B C. a11n

    (@battouly)

    Hi @icypeakcreative,

    Thanks for letting us know. I will leave this thread open for now while we investigate it further.

    I will check with the team and see if there’s a known workaround.

    Thanks.

    Plugin Support B C. a11n

    (@battouly)

    Hi?@icypeakcreative,

    I investigated this further for you.

    The missing column can occur due to SQL issues or limitations during an upgrade. For example, some servers do not accept a default value of 00:00:00 for time, and this can lead to incomplete database tables.

    Since this error is not due directly to our plugin but to a setting on your MySQL server, we recommend reaching out to a developer if you are not one or someone comfortable handling Databases.

    If you’re comfortable accessing your database and making the changes yourself, you need to find the corresponding database table (it will be in the full error) and update the mentioned column to NULL instead of 0.

    I hope this helps.

    Thread Starter icypeakcreative

    (@icypeakcreative)

    Yes! That did the trick! Seems like really old entrys in the db didn’t get updated from 0 to NULL automatically.

    Thank you for your help! ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘DB Migration Error after update’ is closed to new replies.