Upgrade v2.16.0 to v3.0.2

@voisd Apologies for the late reply.

The migration 20180329185634 belongs to Mautic 2, which means that your upgrade is stuck in step 3 of the process: https://docs.mautic.org/en/mautic-3-upgrade/upgrade-steps#3-apply-mautic-2-database-migrations. At this stage, you can still use your Mautic 2 installation as if nothing has happened.

This migration should have been executed in the past already, because it’s two years old: https://github.com/mautic/mautic/tree/2.16/app/migrations - weird that that didn’t happen on your installation.

In order to proceed, we need all database migrations for Mautic 2 executed on your instance. You can trigger that process with app/console doctrine:migrations:migrate, which will most likely give you the error you posted above.

I looked at the specific migration and can you please do the following:

  1. Open app/migrations/Version20180329185634.php
  2. Remove line 32, which has this code in it:
    $this->addSql("ALTER TABLE {$this->prefix}lead_event_log DROP FOREIGN KEY $fkName"); --> please don’t touch other parts of this file!
  3. Run app/console doctrine:migrations:migrate again. Fingers crossed you won’t see any other errors now :crossed_fingers:
  4. If the migrations succeeded, try to open the Mautic 3 upgrade script again.

Hope this helps!

2 Likes