Upgrade PS 8.2.1 to 9.0.3

[PeNov]

Prerequisites

• I understand and accept the project's code of conduct.
• I have already searched in existing issues and found no previous report of this bug.

Describe the bug and add attachments

Hello,

I tried to update prestashop three times and failed, report was already sent after update.

All modules were up to date. Non essential modules were disabled.

First and second attempt – fail with many warnings and errors:

But main error was:
[2026-02-04 00:26:47] CRITICAL - ErrorHandler - home/www/domain.cz/www/test.domain.cz/classes/db/DbPDO.php line 149 - PrestaShopException: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'json NOT NULL, description varchar(255) COLLATE utf8mb4_unicode_ci NOT NU' at line 8…

Failure during DB command (87 query lefts): CREATE TABLE IF NOT EXISTS PREFIX_api_client

Configuration:
PHP 8.4.16, DB: 10.1.48-MariaDB-0+deb9u2, InnoDB, DbPDO, memory limit: 512M, time of execution: 180s, max. file: 60M, Update assistant: 7.5.1

I solved this problem by updating the database to 11.8.3-MariaDB-0+deb13u1 from Debian-log.

Third attempt – fail with many warnings and errors:

But main error was:

[2026-02-06 13:43:10] INFO - UpdateDatabase - Probíhá aktualizace databáze. Zbývá 71 dotazů
[2026-02-06 13:43:11] CRITICAL - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/classes/db/DbPDO.php line 149 - PrestaShopException: SQLSTATE[HY000]: General error: 1709 Index column size too large. The maximum column size is 767 bytes

Failure during DB command (71 query lefts): ALTER TABLE PREFIX_orders CHANGE reference reference VARCHAR(255);

Configuration:
PHP 8.4.16, DB: 11.8.3-MariaDB-0+deb13u1 from Debian-log, InnoDB, DbPDO, memory limit: 512M, time of execution: 180s, max. file: 60M, Update assistant: 7.5.1

Please give me advice on how to solve this problem.

Thank you
Best regards
PN

Expected behavior

Successful update. :-)

Steps to reproduce

Standard update procedure.
Backup without images, Disable non-essential modules - yes, Regenerate emails - yes.

PrestaShop version(s) where the bug happened

8.2.1

How you installed PrestaShop

No response

PHP version(s) where the bug happened

8.4.16

Your company or customer's name goes here (if applicable).

No response

[PeNov]

Hi,

I wanted to add some more screenshots to the bug report.

So I tried the update for the fourth time. A strange thing happened - the update was successfully completed. Absolutely nothing was changed in the server configuration, just nowhere.

How is this possible? :-)

I would like the update to work the first time and not the fourth time. :-)

Do you have any explanation?

Thank you

PS:
The update was successful but the report contains hundreds of warnings:
e.g.:

[2026-02-09 12:49:21] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Models/PrestashopRelease.php line 47 - PrestaShop\Module\AutoUpgrade\Models\PrestashopRelease::__construct(): Implicitly marking parameter $distribution as nullable is deprecated, the explicit nullable type must be used instead

[2026-02-09 12:49:24] WARNING - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Task/Update/UpdateFiles.php line 121 - is_link(): open_basedir restriction in effect. File(/**admin_folder**/themes/default/js/vendor/jquery-passy.LICENSE) is not within the allowed path(s): (/home/www/tmp:/home/www/domain.cz/www/test.domain.cz:/etc/ssl/certs:/usr/share/php:/usr/share/geoip)
[2026-02-09 12:49:24] WARNING - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Task/Update/UpdateFiles.php line 143 - is_dir(): open_basedir restriction in effect. File(/**admin_folder**/themes/default/js/vendor/jquery-passy.LICENSE) is not within the allowed path(s): (/home/www/tmp:/home/www/domain.cz/www/test.domain.cz:/etc/ssl/certs:/usr/share/php:/usr/share/geoip)
[2026-02-09 12:49:24] WARNING - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Task/Update/UpdateFiles.php line 166 - is_file(): open_basedir restriction in effect. File(/**admin_folder**/themes/default/js/vendor/jquery-passy.LICENSE) is not within the allowed path(s): (/home/www/tmp:/home/www/domain.cz/www/test.domain.cz:/etc/ssl/certs:/usr/share/php:/usr/share/geoip)

[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Models/PrestashopRelease.php line 47 - PrestaShop\Module\AutoUpgrade\Models\PrestashopRelease::__construct(): Implicitly marking parameter $distribution as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_accounts/vendor/lcobucci/jwt/src/Token.php line 67 - PrestaShop\Module\PsAccounts\Vendor\Lcobucci\JWT\Token::__construct(): Implicitly marking parameter $signature as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_accounts/vendor/lcobucci/jwt/src/Token.php line 67 - PrestaShop\Module\PsAccounts\Vendor\Lcobucci\JWT\Token::__construct(): Implicitly marking parameter $claimFactory as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_accounts/vendor/lcobucci/jwt/src/Token.php line 257 - PrestaShop\Module\PsAccounts\Vendor\Lcobucci\JWT\Token::isExpired(): Implicitly marking parameter $now as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_distributionapiclient/vendor/guzzlehttp/promises/src/functions.php line 24 - GuzzleHttp\Promise\queue(): Implicitly marking parameter $assign as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_distributionapiclient/vendor/guzzlehttp/promises/src/functions.php line 260 - GuzzleHttp\Promise\each(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_distributionapiclient/vendor/guzzlehttp/promises/src/functions.php line 260 - GuzzleHttp\Promise\each(): Implicitly marking parameter $onRejected as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_distributionapiclient/vendor/guzzlehttp/promises/src/functions.php line 285 - GuzzleHttp\Promise\each_limit(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_distributionapiclient/vendor/guzzlehttp/promises/src/functions.php line 285 - GuzzleHttp\Promise\each_limit(): Implicitly marking parameter $onRejected as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_distributionapiclient/vendor/guzzlehttp/promises/src/functions.php line 307 - GuzzleHttp\Promise\each_limit_all(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:09] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_mbo/ps_mbo.php line 294 - ps_mbo::installTables(): Implicitly marking parameter $table as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:10] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_distributionapiclient/vendor/symfony/stopwatch/Stopwatch.php line 65 - Symfony\Component\Stopwatch\Stopwatch::openSection(): Implicitly marking parameter $id as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:10] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_distributionapiclient/vendor/symfony/stopwatch/Stopwatch.php line 104 - Symfony\Component\Stopwatch\Stopwatch::start(): Implicitly marking parameter $category as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:10] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_distributionapiclient/vendor/symfony/stopwatch/Section.php line 50 - Symfony\Component\Stopwatch\Section::__construct(): Implicitly marking parameter $origin as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:22] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_mbo/vendor/prestashop/prestashop-accounts-installer/src/Installer/Installer.php line 38 - PrestaShop\PsAccountsInstaller\Installer\Installer::__construct(): Implicitly marking parameter $link as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:22] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_mbo/src/Addons/Provider/AddonsDataProvider.php line 103 - PrestaShop\Module\Mbo\Addons\Provider\AddonsDataProvider::__construct(): Implicitly marking parameter $moduleChannel as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:22] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_mbo/src/Addons/ApiClient.php line 316 - PrestaShop\Module\Mbo\Addons\ApiClient::processRequestAndReturn(): Implicitly marking parameter $attributeToReturn as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:22] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_mbo/src/Module/CollectionFactory.php line 45 - PrestaShop\Module\Mbo\Module\CollectionFactory::filter(): Implicitly marking parameter $filters as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:22] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_mbo/src/Module/ModuleBuilder.php line 83 - PrestaShop\Module\Mbo\Module\ModuleBuilder::build(): Implicitly marking parameter $database as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:22] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_mbo/src/Module/SourceRetriever/SourceRetrieverInterface.php line 36 - PrestaShop\Module\Mbo\Module\SourceRetriever\SourceRetrieverInterface::get(): Implicitly marking parameter $expectedModuleName as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:23] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_linklist/src/Core/Grid/Query/LinkBlockQueryBuilder.php line 38 - PrestaShop\Module\LinkList\Core\Grid\Query\LinkBlockQueryBuilder::getSearchQueryBuilder(): Implicitly marking parameter $searchCriteria as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:23] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_linklist/src/Core/Grid/Query/LinkBlockQueryBuilder.php line 73 - PrestaShop\Module\LinkList\Core\Grid\Query\LinkBlockQueryBuilder::getCountQueryBuilder(): Implicitly marking parameter $searchCriteria as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:23] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_linklist/src/Form/ChoiceProvider/AbstractDatabaseChoiceProvider.php line 59 - PrestaShop\Module\LinkList\Form\ChoiceProvider\AbstractDatabaseChoiceProvider::__construct(): Implicitly marking parameter $shopIds as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:25] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_distributionapiclient/vendor/guzzlehttp/guzzle/src/HandlerStack.php line 61 - GuzzleHttp\HandlerStack::__construct(): Implicitly marking parameter $handler as nullable is deprecated, the explicit nullable type must be used instead
[2026-02-09 12:51:25] DEBUG - ErrorHandler - /home/www/domain.cz/www/test.domain.cz/modules/ps_mbo/src/Handler/ErrorHandler/ErrorHandlerInterface.php line 33 - PrestaShop\Module\Mbo\Handler\ErrorHandler\ErrorHandlerInterface::handle(): Implicitly marking parameter $data as nullable is deprecated, the explicit nullable type must be used instead

Thank you
Best regards
PN

[Hlavtox]

@PeNov

Historically, the maximum length for indexed columns was 767 bytes. If you have a mb4 column, the size is 255 x 4 = 1020 bytes, that's why it throws this error. In the past, it was resolved by enabling innodb_large_prefix, but this value is now default for a long time and even removed from recent versions. 🤔

That's why many columns are limited to 191 characters in our database, for this reason. - PrestaShop/PrestaShop#16176

However, it's possible that the table still has an old format that doesn't use it. Could you run this in the DB you are upgrading and tell me what is the row_format?

SHOW TABLE STATUS LIKE 'ps_orders';

If I wrote some nonsense, I am sorry. :-)

Ping @Quetzacoalt91 @kpodemski @jolelievre

[PeNov]

Hi @Hlavtox

This test subdomain is continuously updated from version - I guess PS 1.5.

Here is the DB status after the fourth update:

Here is the status after reverting to the first backup:

Are multiple collations OK? ( ---, utf8mb3_... , utf8mb4_...)

Thanks
BR
PN

[AureRita]

Hi @PeNov ,

Thank you for your report, for your information, we put the new autoupgrade issue's directly on the autoupgrade repo, which allows us to better find the related issues. I'll put in the correct repository

I tried to reproduce your issue but currently I can't, when I verified my DB I have utf8mb3_... , utf8mb4_... but no -----
as you can see :

Could you try with no collation "----" ?

Thank you @Hlavtox for the help on this issue !

Waiting for feedback

[PeNov]

Hi @AureRita, @Hlavtox

What exactly should I test? (DB after rollback is mostly without collation).

The store that was rolled back seems to be working normally. I haven't tested it in depth, it's a test installation.

Thank you
BR
PN