#109662"Migrate user profile settings to JSON format" upgrade wizard fails with silenced PHP error (reporting "Update failed!" only)
Description
The PHP error is silenced via a catch-Throwable in
https://github.com/TYPO3/typo3/blob/5b0ba8a1eca8b2ccfa39320a2de66676a2eea151/typo3/sysext/backend/Classes/Upgrades/UserSettingsMigration.php#L90-L92
If it is unsilenced, the following stack trace becomes visible in devtools network inspection:
(1/1) #1476107295 TYPO3\CMS\Core\Error\Exception PHP Warning: Array to string conversion in /var/www/html/vendor/doctrine/dbal/src/Driver/Mysqli/Statement.php line 73 in /var/www/html/vendor/typo3/cms-core/Classes/Error/ErrorHandler.php line 142 at TYPO3\CMS\Core\Error\ErrorHandler -> handleError ( ) at mysqli_stmt -> execute ( ) in /var/www/html/vendor/doctrine/dbal/src/Driver/Mysqli/Statement.php line 73 at Doctrine\DBAL\Driver\Mysqli\Statement -> execute ( ) in /var/www/html/vendor/doctrine/dbal/src/Connection.php line 905 at Doctrine\DBAL\Connection -> executeStatement ( ) in /var/www/html/vendor/doctrine/dbal/src/Connection.php line 483 at Doctrine\DBAL\Connection -> update ( ) in /var/www/html/vendor/typo3/cms-core/Classes/Database/Connection.php line 289 at TYPO3\CMS\Core\Database\Connection -> update ( ) in /var/www/html/vendor/typo3/cms-backend/Classes/Upgrades/UserSettingsMigration.php line 75 at TYPO3\CMS\Backend\Upgrades\UserSettingsMigration -> executeUpdate ( ) in /var/www/html/vendor/typo3/cms-core/Classes/Service/UpgradeWizardsService.php line 276 at TYPO3\CMS\Core\Service\UpgradeWizardsService -> executeWizard ( ) in /var/www/html/vendor/typo3/cms-install/Classes/Controller/UpgradeController.php line 1117 at TYPO3\CMS\Install\Controller\UpgradeController -> upgradeWizardsExecuteAction ( ) in /var/www/html/vendor/typo3/cms-install/Classes/Middleware/Maintenance.php line 236 at TYPO3\CMS\Install\Middleware\Maintenance -> process ( ) in /var/www/html/vendor/typo3/cms-core/Classes/Http/MiddlewareDispatcher.php line 111
This is probably a consequence of the following change:
> 93726: [BUGFIX] Fix double JSON encoding of backend user settings | https://review.typo3.org/c/Packages/TYPO3.CMS/+/93726
It passes an array – https://review.typo3.org/c/Packages/TYPO3.CMS/+/93726/9/typo3/sysext/backend/Classes/Upgrades/UserSettingsMigration.php#80 – which is expected to be encoded based on the type, but seems not to work properly.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 2
History 5
-
Benjamin Franzke changed Related to #109638 <span data-processor="relativetime" data-value="2026-04-21T10:13:10+00:00" > 04/21/26, 10:13 </span>
-
Benjamin Franzke changed Related to #109663 <span data-processor="relativetime" data-value="2026-04-21T10:20:05+00:00" > 04/21/26, 10:20 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-04-21T11:23:51+00:00" > 04/21/26, 11:23 </span>
-
Benjamin Franzke commented and changed status
NewRejected <span data-processor="relativetime" data-value="2026-04-21T11:55:22+00:00" > 04/21/26, 11:55 </span> -
Philipp Kitzberger commented <span data-processor="relativetime" data-value="2026-05-15T16:19:31+00:00" > 05/15/26, 16:19 </span>
I’ve set up a local ddev environment (a while ago) following these instructions: https://docs.typo3.org/m/typo3/guide-contributionworkflow/main/en-us/Appendix/SettingUpTypo3Ddev.html#setting-up-typo3-with-ddev
In .ddev/config the MariaDB version was pinned to 10.3 which resulted in the problem described above. After upgrading to 10.4 the DB compare & update finished as expected.
Seems I’ve been using a MariaDB version that is too old, see Environment report:
Therefore database analyzer is stuck with trying the following change:
…which causes the schema analyzer to never notice that we expect the array to be JSON encoded, because the database schema is not reported as JSON.
Marking as “Rejected” for now.