Running console doctrine:schema:update --force brings up errors

Product Support
1

Your software
My Mautic version is: 3.1
My PHP version is: 7.3

Your problem
My problem is: I’ve updated to 3.0, and then 3.1 using the method outlined here - https://mauteam.org/mautic/mautic-admins/mautic-update-how-to-dont-click-that-button/

But running console doctrine:schema:update --force seems to bring up errors:

Annotation 2020-08-30 182837
Annotation 2020-08-30 182837786×441 7.48 KB

Prior to this I ran console doctrine:migration:migrate and got:

Annotation 2020-08-30 182613
Annotation 2020-08-30 182613825×517 6.24 KB

I’ve still managed to update successfully, but I am concerned some of the DB specific stuff isn’t executing correctly.

Any advice would be much appreciated!

Thanks,

2

Did you run the migration and migration with --force before and after you updated?

If you get stuck restore from a backup and run these steps through slowly. If your database migration fails your Mautic install will do very unexpected things like run into random and weird errors. So it’s crucial that the migration succeeds before you call the upgrade good.

3

If you use the mautic:update:find , mautic:update:apply and mautic:update:apply --finish there is no need to manually run the schema update. @Yosu_Cadilla is no doubt an expert and I don’t speak for him, but I believe that post is most relevant when updating from Mautic 2.x to Mautic 3.x not necessarily from Mautic 3.x to 3.x. Hopefully he will chime in and clarify.

4

Hi guys,

That guide on my blog is in fact meant for M2 to M2 upgrades and has not been tested with M2 to M3 upgrades.

Please keep in mind that for upgrading from M2 to M3 you need to first upgrade to 2.16.3 before you do the jump.

I’ve been working on an M2 to M3 upgrade guide for a while, hope I’ll be able to publish it soon enough…

1 Like