Update 4.4.13 -> 5.2.6 table `bundle_grapesjsbuilder` does not exist

[jschleucher]

Your software
My Mautic version is: 4.4.13
My PHP version is: 8.3.21
My Database type and version is: MariaDB 10.11.11

Your problem
My problem is:
I am trying to update (CLI, non-composer-based) via php bin/console mautic:update:apply which suggest an update to 5.2.6. During the DB-migration, migration 20240611103824 fails, because the table bundle_grapesjsbuilder does not exist.

These errors are showing in the log:

[2025-06-09T09:20:41.488258+00:00] console.CRITICAL: Error thrown while running command "doctrine:migrations:migrate". Message: "There is no table with name "jgdmauticdb.bundle_grapesjsbuilder" in the schema." {"exception":"[object] (Doctrine\\DBAL\\Schema\\Exception\\TableDoesNotExist(code: 10): There is no table with name \"jgdmauticdb.bundle_grapesjsbuilder\" in the schema. at /var/www/jgd/mautic/vendor/doctrine/dbal/src/Schema/Exception/TableDoesNotExist.php:16)","command":"doctrine:migrations:migrate","message":"There is no table with name \"jgdmauticdb.bundle_grapesjsbuilder\" in the schema."} {"hostname":"begegnungmautic","pid":1522000}

Yes, the different rootdir is expected.

Steps I have tried to fix the problem:

• cache:clear and retrying - problem persists
• doctrine:schema:update --force - fails (Cannot change column 'client_id': used in a foreign key constraint FK_D2B4847B19EB6921)

This system was a v2.15 install handed to me with 0 documentation. I have updated it 2.15.xx(forgot to write that down) → 3.2.4 → 4.4.13; everything CLI-based, non-composer.

[jschleucher]

Sorry, php version is wrong.

Active Version is

• mautic 4.4.13
• php 8.0.30

I have tried updates to 5.2.6 with php8.0.30 and php8.3.21.

[joeyk]

Did you have the GrapesJS builder active in Mautic 4?

[jschleucher]

No, we do not use GrapesJS.

[joeyk]

It is the default form Mautic 5 on. I suggest to enable the GrapeJS plugin in M4, so it creates the table for you. Then you can disable it, upgrade and turn it off.
Joey

[jschleucher]

I can confirm that that fixed the issue (I had some other failing migrations, but they are unrelated and could be fixed manually).