Upgrade PS from 8.0.4 to 8.1.0 - Error upgrading Doctrine schema #33021

PeNov · 2023-06-27T10:36:41Z

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,

during the upgrade PS 8.0.4 to PS 8.1.0 these errors are show's:

Error during database upgrade. You may need to restore your database.
Error upgrading Doctrine schema

Log:
log_804_to_810.txt

Seams that PS works as version 8.1.0 now. It is not fully tested.

Are you able suggest me necessary steps?

For example:
A) Roll back to 8.0.4 and wait to new version
B) Repair something in the database (run commands) for correct working of e-shop.

Thank you
Best regards
Petr

Expected behavior

Upgrade without errors.

Steps to reproduce

All modules was upgraded to newest including 1-Click Upgrade module (4.16.0)
Go to 1-Click Upgrade and Upgrade - standard as many times before.

PrestaShop version(s) where the bug happened

8.0.4 to 8.1.0

PHP version(s) where the bug happened

7.4.33

If your bug is related to a module, specify its name and its version

autoupgrade v4.16.0

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

No response

Hlavtox · 2023-06-27T10:46:11Z

laravel/framework#24711 (comment)

This happens because utf8mb4 uses 4 bytes per character, and the email column has a 255 character length which is greater than the limit 767 bytes. 255 x 4bytes = 1020b.

To fix this the email column length should be at most 191. 191 x 4 bytes = 764b.

Solution = Use utf8 instead utf8mb4 OR change name column length to 191 chars.

Ping @PrestaShop/committers

sallemiines · 2023-06-27T12:43:30Z

Hello @PeNov
Could you please try the proposed solution Use utf8 instead utf8mb4 OR change name column length to 191 chars. as @Halvatox said .

Waiting for your feedback !
Thank you !

darkf3d3 · 2023-06-27T13:17:57Z

I got the same error when upgrading from 1.7.7.7 to 8.1 (the same website it's upgraded correctly to 8.0.4).
I tried performing the upgrade 3 times, and I get always the same errors:
`All files upgraded. Now upgrading database...

Updating database schema...
Executing: CREATE TABLE ps_authorized_application (id_authorized_application INT UNSIGNED AUTO_INCREMENT NOT NULL, name VARCHAR(255) NOT NULL, description LONGTEXT NOT NULL, UNIQUE INDEX UNIQ_475B9BA55E237E06 (name), PRIMARY KEY(id_authorized_application)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB
15:09:52 CRITICAL [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "An exception occurred while executing 'CREATE TABLE ps_authorized_application (id_authorized_application INT UNSIGNED AUTO_INCREMENT NOT NULL, name VARCHAR(255) NOT NULL, description LONGTEXT NOT NULL, UNIQUE INDEX UNIQ_475B9BA55E237E06 (name), PRIMARY KEY(id_authorized_application)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB':
SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes" ["exception" => Doctrine\DBAL\Exception\DriverException { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => """ An exception occurred while executing 'CREATE TABLE ps_authorized_application (id_authorized_application INT UNSIGNED AUTO_INCREMENT NOT NULL, name VARCHAR(255) NOT NULL, description LONGTEXT NOT NULL, UNIQUE INDEX UNIQ_475B9BA55E237E06 (name), PRIMARY KEY(id_authorized_application)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB':\n \n SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes """]
In AbstractMySQLDriver.php line 128:
An exception occurred while executing 'CREATE TABLE ps_authorized_applicati
on (id_authorized_application INT UNSIGNED AUTO_INCREMENT NOT NULL, name VA
RCHAR(255) NOT NULL, description LONGTEXT NOT NULL, UNIQUE INDEX UNIQ_475B9
BA55E237E06 (name), PRIMARY KEY(id_authorized_application)) DEFAULT CHARACT
ER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB':
SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was t
oo long; max key length is 767 bytes
In Exception.php line 18:
SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was t
oo long; max key length is 767 bytes
In PDOConnection.php line 141:
SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was t
oo long; max key length is 767 bytes
prestashop:schema:update-without-foreign [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--id_shop [ID_SHOP]] [--id_shop_group [ID_SHOP_GROUP]] [--]
[DEV] ajax request : rollback

Errors
Error during database upgrade. You may need to restore your database.
Error upgrading Doctrine schema`

PeNov · 2023-06-27T14:07:19Z

Hello @sallemiines and @Hlavtox,

Yes sure, I can make test.

But I need more information’s about these two scenarios.

Should I go back to version PS 8.0.4 firstly without any changes?

A) Change config/database.php
The folder config does not contain file database.php

B) change name column length to 191 chars
I can try it. But table ps_authorized_application does not exit. Where I makes this change? On the 1-click update script?

Thank you
Best regards
Petr

mflasquin · 2023-06-28T07:33:42Z

Hi @PeNov you can try to change in src/PrestaShopBundle/Entity/AuthorizedApplication.php::56

kpodemski · 2023-06-28T07:44:49Z

@darfk3d3 @PeNov

could you guys provide us with more information about your DB server? You can ask hosting provider, or go to the phpMyAdmin or some other database GUI, so that we know what is the default encoding on your server, not the encoding you have in the tables.

This is what I see after login:
https://capture.dropbox.com/DkAww4gg5qhLuLwH

After getting into the database, you can also see whether you have MyISAM or InnoDb tables.

darkf3d3 · 2023-06-28T07:50:08Z

@kpodemski
Sure, here's mine:

mflasquin · 2023-06-28T07:53:27Z

Hi @darfk3d3, can you provide some other informations from tables like this :

darkf3d3 · 2023-06-28T07:57:46Z

@mflasquin

This is just a part, let me know if you need more tables...

kpodemski · 2023-06-28T08:00:14Z

@darfk3d3 all good, thanks

PeNov · 2023-06-28T11:50:21Z

Hello Krystian @kpodemski ,
Here is screen after login to phpMyAdmin:

Tables have more type of the collation. For example: utf8mb4_general_ci, utf8_unicode_ci, utf8_general_ci, latin1_swedish_ci

MySQL info:
Verze MySQL: 10.1.48-MariaDB-0+deb9u2
Engine MySQL: InnoDB
Driver MySQL: DbPDO

Server info:
Apache/2.4.56 (Debian)
PHP version: 7.4.33
Memory limit: 256M
Max. time execution: 180
Max. size of the uploaded file: 60M

Thank you
Best regards
Petr

ChillCode · 2023-06-28T13:39:32Z

Without testing I guess this new table requires a really big INDEX and is reaching the limits of your MariaDB version:

In the link you'll find an explanation:

https://dev.mysql.com/doc/refman/8.0/en/innodb-limits.html

To check row format:

SHOW VARIABLES LIKE 'innodb_default_row_format';

Result:

innodb_default_row_format | dynamic

If you can upgrade MariaDB I think problem will be solved easily since the default ROW FORMAT is DYNAMIC.

https://mariadb.com/kb/en/innodb-dynamic-row-format/

As stated in the previous link may this works for you both if you cannot upgrade:


## Innodb settings to bypass error of max size 737
innodb-file-format=barracuda
innodb-file-per-table=ON
innodb-large-prefix=ON
## Above 3 didnot work so i added below
innodb_default_row_format = 'DYNAMIC'

Source

May the docs should reflect this new requirement to upgrade to a greater MariaDB version that allows 3072bytes as stated in the links posted.

joecoolio66 · 2023-06-28T16:41:59Z

We don't understand... is this a bug? Is this a new requirement? Why is there issue here?

darkf3d3 · 2023-06-28T19:14:20Z

If you can upgrade MariaDB I think problem will be solved easily since the default ROW FORMAT is DYNAMIC.

I asked my hosting about upgrading MariaDB version. They said me that it can be done, but it will be done serverwide and the operation is not reversible, so I'm not sure about this because I have dozen of website of the server, and I'm not sure about MariaDB versions compatibility.

ghost · 2023-06-28T19:24:39Z

Im also getting "database" errors at the end of auto-upgrade, doesn't really seem to be database related though

PHP Version 8.1.16
MySQL version: 10.4.30-MariaDB

[INTERNAL] /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php line 180 - Symfony\Component\Config\Exception\LoaderLoadException: There is no extension able to load the configuration for "api_platform" (in "/home/devel/public_html/app/config/config.yml"). Looked for namespace "api_platform", found ""framework", "security", "twig", "monolog", "swiftmailer", "doctrine", "sensio_framework_extra", "prestashop", "translation_tools", "tactician", "fos_js_routing"" in /home/devel/public_html/app/config/config.yml (which is being imported from "/home/devel/public_html/app/config/config_prod.yml"). #0 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php(104): Symfony\Component\Config\Loader\FileLoader->doImport() #1 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/FileLoader.php(66): Symfony\Component\Config\Loader\FileLoader->import() #2 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(197): Symfony\Component\DependencyInjection\Loader\FileLoader->import() #3 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(133): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->parseImports() #4 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/DelegatingLoader.php(40): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->load() #5 /home/devel/public_html/app/AppKernel.php(211): Symfony\Component\Config\Loader\DelegatingLoader->load() #6 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(697): AppKernel->registerContainerConfiguration() #7 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(593): Symfony\Component\HttpKernel\Kernel->buildContainer() #8 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(136): Symfony\Component\HttpKernel\Kernel->initializeContainer() #9 /home/devel/public_html/app/AppKernel.php(93): Symfony\Component\HttpKernel\Kernel->boot() #10 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/SymfonyAdapter.php(76): AppKernel->boot() #11 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader80.php(44): PrestaShop\Module\AutoUpgrade\UpgradeTools\SymfonyAdapter->initAppKernel() #12 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(87): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader80->initConstants() #13 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(46): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->doUpgrade() #14 /home/devel/public_html/modules/autoupgrade/classes/TaskRunner/Upgrade/UpgradeDb.php(43): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->doUpgrade() #15 /home/devel/public_html/admin3756utwoe9xinaeuvsl/autoupgrade/ajax-upgradetab.php(53): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\UpgradeDb->run() #16 {main}

ChillCode · 2023-06-28T20:26:12Z

If you can upgrade MariaDB I think problem will be solved easily since the default ROW FORMAT is DYNAMIC.

I asked my hosting about upgrading MariaDB version. They said me that it can be done, but it will be done serverwide and the operation is not reversible, so I'm not sure about this because I have dozen of website of the server, and I'm not sure about MariaDB versions compatibility.

My response is only what MySQL/MariaDB docs says about that error you're getting, both with 10.1.38, and I wouldn't do an upgrade on a production server neither.

On a staging site so you can try to upgrade again and then see the results and take a decision.

But PrestaShop may change column definition to solve the issue.

joecoolio66 · 2023-06-29T13:17:06Z

Apparently we use percona... has there been any reported issues with that DB?

ChillCode · 2023-06-30T11:57:36Z

Percona is also a MySQL distribution but you can wait till @mflasquin release the solution and then upgrade.

xga91 · 2023-07-01T14:53:18Z

Im also getting "database" errors at the end of auto-upgrade, doesn't really seem to be database related though

PHP Version 8.1.16 MySQL version: 10.4.30-MariaDB

[INTERNAL] /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php line 180 - Symfony\Component\Config\Exception\LoaderLoadException: There is no extension able to load the configuration for "api_platform" (in "/home/devel/public_html/app/config/config.yml"). Looked for namespace "api_platform", found ""framework", "security", "twig", "monolog", "swiftmailer", "doctrine", "sensio_framework_extra", "prestashop", "translation_tools", "tactician", "fos_js_routing"" in /home/devel/public_html/app/config/config.yml (which is being imported from "/home/devel/public_html/app/config/config_prod.yml"). #0 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php(104): Symfony\Component\Config\Loader\FileLoader->doImport() #1 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/FileLoader.php(66): Symfony\Component\Config\Loader\FileLoader->import() #2 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(197): Symfony\Component\DependencyInjection\Loader\FileLoader->import() #3 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(133): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->parseImports() #4 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/DelegatingLoader.php(40): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->load() #5 /home/devel/public_html/app/AppKernel.php(211): Symfony\Component\Config\Loader\DelegatingLoader->load() #6 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(697): AppKernel->registerContainerConfiguration() #7 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(593): Symfony\Component\HttpKernel\Kernel->buildContainer() #8 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(136): Symfony\Component\HttpKernel\Kernel->initializeContainer() #9 /home/devel/public_html/app/AppKernel.php(93): Symfony\Component\HttpKernel\Kernel->boot() #10 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/SymfonyAdapter.php(76): AppKernel->boot() #11 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader80.php(44): PrestaShop\Module\AutoUpgrade\UpgradeTools\SymfonyAdapter->initAppKernel() #12 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(87): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader80->initConstants() #13 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(46): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->doUpgrade() #14 /home/devel/public_html/modules/autoupgrade/classes/TaskRunner/Upgrade/UpgradeDb.php(43): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->doUpgrade() #15 /home/devel/public_html/admin3756utwoe9xinaeuvsl/autoupgrade/ajax-upgradetab.php(53): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\UpgradeDb->run() #16 {main}

I got same error message as you, did you manage to find anything ?

AureRita · 2023-07-03T13:31:23Z

Hi @PeNov

Thank you for your report, I need to know some things with you :

Did your issue seems like this one ?

Untitled_.Jul.3.2023.12_08.PM.webm

Moreover, did your issue seems like this another issue ; #33041

but at the end, I think this issue is too technical for me, ping @PrestaShop/prestashop-core-developers, can someone please reproduce this issue ?

Thanks

ghost · 2023-07-03T18:24:39Z

Im also getting "database" errors at the end of auto-upgrade, doesn't really seem to be database related though

PHP Version 8.1.16 MySQL version: 10.4.30-MariaDB

[INTERNAL] /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php line 180 - Symfony\Component\Config\Exception\LoaderLoadException: There is no extension able to load the configuration for "api_platform" (in "/home/devel/public_html/app/config/config.yml"). Looked for namespace "api_platform", found ""framework", "security", "twig", "monolog", "swiftmailer", "doctrine", "sensio_framework_extra", "prestashop", "translation_tools", "tactician", "fos_js_routing"" in /home/devel/public_html/app/config/config.yml (which is being imported from "/home/devel/public_html/app/config/config_prod.yml"). #0 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php(104): Symfony\Component\Config\Loader\FileLoader->doImport() #1 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/FileLoader.php(66): Symfony\Component\Config\Loader\FileLoader->import() #2 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(197): Symfony\Component\DependencyInjection\Loader\FileLoader->import() #3 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(133): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->parseImports() #4 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/DelegatingLoader.php(40): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->load() #5 /home/devel/public_html/app/AppKernel.php(211): Symfony\Component\Config\Loader\DelegatingLoader->load() #6 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(697): AppKernel->registerContainerConfiguration() #7 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(593): Symfony\Component\HttpKernel\Kernel->buildContainer() #8 /home/devel/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(136): Symfony\Component\HttpKernel\Kernel->initializeContainer() #9 /home/devel/public_html/app/AppKernel.php(93): Symfony\Component\HttpKernel\Kernel->boot() #10 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/SymfonyAdapter.php(76): AppKernel->boot() #11 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader80.php(44): PrestaShop\Module\AutoUpgrade\UpgradeTools\SymfonyAdapter->initAppKernel() #12 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(87): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader80->initConstants() #13 /home/devel/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(46): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->doUpgrade() #14 /home/devel/public_html/modules/autoupgrade/classes/TaskRunner/Upgrade/UpgradeDb.php(43): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->doUpgrade() #15 /home/devel/public_html/admin3756utwoe9xinaeuvsl/autoupgrade/ajax-upgradetab.php(53): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\UpgradeDb->run() #16 {main}

Same problem with same errors
fresh 8.0.4 intall
8.0.4 to 8.1.0
Updating test with different php versions
Updating test with tow different updating modules
Failed...

PeNov · 2023-07-10T08:26:26Z

Hello @AureRita,

my error is described in the first paragraph of the bug report #33021. I have only Error upgrading Doctrine schema.

Your video showed different behavior. I have not Ajax error. I have only Doctrine schema error.

Bug report #33041 is different too from my report.

Best regards
Petr

darkf3d3 · 2023-07-10T08:34:03Z

I update my situation, updating mariadb version from 10.1 to 10.11 solved the problem.
After doing that I was able to upgrade from PS1.7 to PS8.1 succesfully.

I just have a minor issue with back office left menu show names in English instead of Italian, but I don't think it could be something related to mariadb.

kpodemski · 2023-07-10T08:44:38Z

@darkf3d3 that's great! :)

regarding the back office menu, update your language pack, that should do it - go to International -> Translations and update Italian language :)

darkf3d3 · 2023-07-10T08:57:14Z

@kpodemski Thanks, now it's 100% Italian. I didn't know that I need to do that after upgrade. It's an expecter behaviour that it's not done automatically during the upgrade?

kpodemski · 2023-07-10T08:58:07Z

@darkf3d3 I honestly don't know :) I used to do it manually, not only after the upgrade, etc., but regularly just to get fresh translations from time to time :)

darkf3d3 · 2023-07-10T09:00:20Z

@kpodemski Good to know. I will do this too. Thanks ;)

blvckcoder · 2024-01-25T05:27:58Z

For those encountering this bug, from version 8.0.4 -> 8.1.0 and higher with doctrine database:

Restore your healthy backup
Simply disable the psgdpr module
Proceed with the update using clickupgrade
Done without errors

maxadp · 2024-02-07T08:21:07Z

I got the same problem, I can't update from 8.0.5 to 8.1.3, got everytime: "Error during database upgrade. You may need to restore your database." "Error upgrading Doctrine schema"

I try to use @mflasquin fix but in 8.0.5 I got no AuthorizedApplication.php file
in src/PrestaShopBundle/Entity/ so for me is not useful

I try also to disable psgdpr module, but got same error.

I can't update mysql or mariadb version.

What I can do?

Pele4711 · 2024-02-29T14:43:12Z

Hi there,
same here. Just tried to upgrade from 8.1.1 to 8.1.4. Also the same Doctrine error. The psgdpr module uninstalled.
Any solution?

PeNov added Bug Type: Bug New New issue not yet processed by QA labels Jun 27, 2023

prestashop-issue-bot bot removed the Waiting for author Status: action required, waiting for author feedback label Jun 27, 2023

prestashop-issue-bot bot added the Topwatchers Backlog prioritization: issue reported & followed by +6 people label Jun 28, 2023

MatShir assigned mflasquin Jun 30, 2023

AureRita added Waiting for author Status: action required, waiting for author feedback TBR Status: issue to be reproduced Waiting for dev Status: action required, waiting for tech feedback and removed NMI Status: issue needs more information labels Jul 3, 2023

AureRita mentioned this issue Jul 3, 2023

Error upgrading from 8.0.4 to 8.1.0 with autoupgrade 4.16 #33064

Closed

2 tasks

WahbiPS added this to the 8.1.1 milestone Jul 6, 2023

WahbiPS mentioned this issue Jul 4, 2023

Release 8.1.1 🧑‍✈ #33097

Closed

20 tasks

prestashop-issue-bot bot removed the Waiting for author Status: action required, waiting for author feedback label Jul 10, 2023

mflasquin mentioned this issue Jul 10, 2023

Fix authorized application column length #33164

Merged

prestonBot added the PR available Solution: issue is being addressed label Jul 10, 2023

WahbiPS added the Waiting for QA Status: action required, waiting for test feedback label Jul 13, 2023

WahbiPS closed this as completed Jul 17, 2023

WahbiPS removed Waiting for QA Status: action required, waiting for test feedback Waiting for dev Status: action required, waiting for tech feedback labels Jul 20, 2023

Hlavtox mentioned this issue Jul 25, 2023

Error while updating to 8.1.0 #33364

Closed

2 tasks

hibatallahAouadni added Fixed Resolution: issue closed because fixed and removed TBR Status: issue to be reproduced labels Aug 17, 2023

matks mentioned this issue Sep 7, 2023

In autoupgrade process, Doctrine entities schema updates are managed by Doctrine command prestashop:schema:update and it creates plenty issues #33874

Closed

ChillCode mentioned this issue May 16, 2024

MariaDB Incompatibility #33157

Closed

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Upgrade PS from 8.0.4 to 8.1.0 - Error upgrading Doctrine schema #33021

Upgrade PS from 8.0.4 to 8.1.0 - Error upgrading Doctrine schema #33021

PeNov commented Jun 27, 2023

Hlavtox commented Jun 27, 2023 •

edited

Loading

sallemiines commented Jun 27, 2023

darkf3d3 commented Jun 27, 2023

PeNov commented Jun 27, 2023

mflasquin commented Jun 28, 2023

kpodemski commented Jun 28, 2023 •

edited

Loading

darkf3d3 commented Jun 28, 2023 •

edited

Loading

mflasquin commented Jun 28, 2023

darkf3d3 commented Jun 28, 2023

kpodemski commented Jun 28, 2023

PeNov commented Jun 28, 2023

ChillCode commented Jun 28, 2023 •

edited

Loading

joecoolio66 commented Jun 28, 2023

darkf3d3 commented Jun 28, 2023

ghost commented Jun 28, 2023 •

edited by ghost

Loading

ChillCode commented Jun 28, 2023

joecoolio66 commented Jun 29, 2023

ChillCode commented Jun 30, 2023

xga91 commented Jul 1, 2023

AureRita commented Jul 3, 2023

ghost commented Jul 3, 2023

PeNov commented Jul 10, 2023

darkf3d3 commented Jul 10, 2023

kpodemski commented Jul 10, 2023

darkf3d3 commented Jul 10, 2023

kpodemski commented Jul 10, 2023

darkf3d3 commented Jul 10, 2023

blvckcoder commented Jan 25, 2024

maxadp commented Feb 7, 2024

Pele4711 commented Feb 29, 2024

Upgrade PS from 8.0.4 to 8.1.0 - Error upgrading Doctrine schema #33021

Upgrade PS from 8.0.4 to 8.1.0 - Error upgrading Doctrine schema #33021

Comments

PeNov commented Jun 27, 2023

Prerequisites

Describe the bug and add attachments

Expected behavior

Steps to reproduce

PrestaShop version(s) where the bug happened

PHP version(s) where the bug happened

If your bug is related to a module, specify its name and its version

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

Hlavtox commented Jun 27, 2023 • edited Loading

sallemiines commented Jun 27, 2023

darkf3d3 commented Jun 27, 2023

PeNov commented Jun 27, 2023

mflasquin commented Jun 28, 2023

kpodemski commented Jun 28, 2023 • edited Loading

darkf3d3 commented Jun 28, 2023 • edited Loading

mflasquin commented Jun 28, 2023

darkf3d3 commented Jun 28, 2023

kpodemski commented Jun 28, 2023

PeNov commented Jun 28, 2023

ChillCode commented Jun 28, 2023 • edited Loading

joecoolio66 commented Jun 28, 2023

darkf3d3 commented Jun 28, 2023

ghost commented Jun 28, 2023 • edited by ghost Loading

ChillCode commented Jun 28, 2023

joecoolio66 commented Jun 29, 2023

ChillCode commented Jun 30, 2023

xga91 commented Jul 1, 2023

AureRita commented Jul 3, 2023

ghost commented Jul 3, 2023

PeNov commented Jul 10, 2023

darkf3d3 commented Jul 10, 2023

kpodemski commented Jul 10, 2023

darkf3d3 commented Jul 10, 2023

kpodemski commented Jul 10, 2023

darkf3d3 commented Jul 10, 2023

blvckcoder commented Jan 25, 2024

maxadp commented Feb 7, 2024

Pele4711 commented Feb 29, 2024

Hlavtox commented Jun 27, 2023 •

edited

Loading

kpodemski commented Jun 28, 2023 •

edited

Loading

darkf3d3 commented Jun 28, 2023 •

edited

Loading

ChillCode commented Jun 28, 2023 •

edited

Loading

ghost commented Jun 28, 2023 •

edited by ghost

Loading