Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1 click upgrade from Prestashop 8.0.4 to 8.1.0 fails #33513

Closed
2 tasks done
musaffarpatel opened this issue Jul 31, 2023 · 13 comments
Closed
2 tasks done

1 click upgrade from Prestashop 8.0.4 to 8.1.0 fails #33513

musaffarpatel opened this issue Jul 31, 2023 · 13 comments
Labels
Bug Type: Bug Duplicate Resolution: issue closed because already reported Invalid Resolution: issue closed because invalid

Comments

@musaffarpatel
Copy link

Prerequisites

Describe the bug and add attachments

1 click upgrade from Prestaashop 8.0.3 to 8.1.0 produces the following error:

One CLick upgrade fails from Pres
23:09:20 CRITICAL [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "There is no active transaction" ["exception" => PDOException { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => "There is no active transaction"]
In Connection.php line 1854:
There is no active transaction
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]] [--]

Expected behavior

No response

Steps to reproduce

Use the 1 click upgrade module to update a Prestashop 8.0.3 install to Prestashop 8.1.0

PrestaShop version(s) where the bug happened

8.0.4

PHP version(s) where the bug happened

No response

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

No response

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

No response

@musaffarpatel musaffarpatel added Bug Type: Bug New New issue not yet processed by QA labels Jul 31, 2023
@musaffarpatel
Copy link
Author

The same error occurs both locally and on my live host, therefore not an isolated issue

@kpodemski
Copy link
Contributor

I confirm this issue. It is a duplicate, but you're not the first person reporting it.

cc @Hlavtox

QA: no need to re-test it, it is not easily reproducible.

@musaffarpatel
Copy link
Author

@kpodemski Thanks, do you think there will be a fix to this anytime soon? We need to decide whether to hold fire on our project or not depending on whether or not we can upgrade

@kpodemski
Copy link
Contributor

@musaffarpatel hard to tell, we couldn't reproduce this issue - it is not a global issue, it is related to the environment configuration

@Hlavtox had more details, so let's wait for him to share more infos

@musaffarpatel
Copy link
Author

@kpodemski if it helps I can give @Hlavtox access to my hosting where the error occurs

@kpodemski
Copy link
Contributor

@musaffarpatel, no need, it won't guarantee any faster fix, etc.

@sallemiines
Copy link
Contributor

Hello,

We are aware of this issue, it is already in our debug backlog. This issue is a duplicate of #32547.
To be informed when it's fixed, please subscribe to the issue mentioned above.

Thank you

@sallemiines sallemiines added Duplicate Resolution: issue closed because already reported Invalid Resolution: issue closed because invalid and removed New New issue not yet processed by QA labels Aug 1, 2023
@rbuelund
Copy link

rbuelund commented Sep 7, 2023

I get the same error when trying to update with the 1-click module from 8.0.2 to 8.05 - is this the same problem ?

@musaffarpatel
Copy link
Author

@rbuelund You can try disabling / removing the GPDR module before upgrading, which is what worked for me.

@rbuelund
Copy link

rbuelund commented Sep 7, 2023

Is it then possible to add/activate it afterwards again ?

@rbuelund
Copy link

Is there a fix on the way for this problem ??

@matks
Copy link
Contributor

matks commented Sep 18, 2023

Is it then possible to add/activate it afterwards again ?

Yes. You can do this

  1. Disable the GDPR module
  2. Process to the upgrade of your shop
  3. Open your shop after upgrade, re-enable the GDPR module

Is there a fix on the way for this problem ??

The root cause is this #33874

Yes it will be fixed but it will take quite a lot of time as the problem has huge impacts.

But a small fix, just for GDPR module, has been submitted and merged PrestaShop/psgdpr#214 and will be released this week with GDPR module 2.0.2

@rbuelund
Copy link

rbuelund commented Oct 5, 2023

My GDPR module is still 1.4.2 - has this fix been released ??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Type: Bug Duplicate Resolution: issue closed because already reported Invalid Resolution: issue closed because invalid
Projects
None yet
Development

No branches or pull requests

5 participants