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

BO - An error when upgrade from 1.7 to 1.7.8 or to 8.0 when the zip and the xml are erased #29929

Closed
2 tasks done
Tracked by #25648
HanaRebaiQA opened this issue Oct 7, 2022 · 2 comments
Closed
2 tasks done
Tracked by #25648
Labels
1.7.7.8 Affects versions Autoupgrade Module: autoupgrade Backlog SUE Added to the SUE backlog BO Category: Back Office Bug Type: Bug Minor Severity: minor bug > https://build.prestashop.com/news/severity-classification Module Module Regression Type: regression Verified The issue has been reproduced

Comments

@HanaRebaiQA
Copy link

HanaRebaiQA commented Oct 7, 2022

Prerequisites

Describe the bug and add screenshots

An error when upgrade from 1.7.7.8 to 1.7.8 or to 8.0 when the zip and the xml are erased after being used and save it

image

upgrade.error.with.N_A.2.mp4

Expected behavior

The upgrade button shouldn't be displayed (Proposition) and an alert to block the upgrade

Steps to reproduce

  1. Install PS1778 OR PS1787
  2. Use the release of autoupgrade.zip (v4.15)
  3. Go to 1-click upgrade > Configure
  4. Enable the Disable non-native module option
  5. Do not uninstall the problematic modules
  6. Under auto-upgrade > Download > Use the .zip and the xml for the 8.0.0 RC
  7. Go to 1-click upgrade > Configure
  8. Choose local archive
  9. Fill the fields with the zip and the xml and the version
  10. Click on Save
  11. Check that the button Upgrade Prestashop now is displayed
  12. Refresh the page
  13. Under auto-upgrade > Download > Erase the zip and the xml
  14. Choose local archive
  15. There is no field to put
  16. Click on Save and Click on Upgrade PrestaShop now
  17. See error ==> An error is displayed when running the upgrade

PrestaShop version(s) where the bug happened

1.7.8.7, 8.0.0

PHP version(s) where the bug happened

7.4

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

autoupgrade v4.15.0 (Release) & autoupgrade v4.14.2

@HanaRebaiQA HanaRebaiQA added Bug Type: Bug New New issue not yet processed by QA Minor Severity: minor bug > https://build.prestashop.com/news/severity-classification BO Category: Back Office Autoupgrade Module: autoupgrade 1.7.7.8 Affects versions Module Module labels Oct 7, 2022
@hibatallahAouadni
Copy link
Contributor

Hello @HanaRebaiQA

I reproduce the issue only with 1-Click autoupgrade v4.15.0, with v4.14.2 I didn't manage to reproduce the issue, see the attached screenshot below:

image

So, it's a regression on the module! I will add to the Backlog to be fixed.

Thanks!

@hibatallahAouadni hibatallahAouadni added Needs Specs Status: issue needs to be specified Regression Type: regression Verified The issue has been reproduced and removed New New issue not yet processed by QA labels Oct 10, 2022
@florine2623 florine2623 mentioned this issue Oct 10, 2022
8 tasks
@gericfo gericfo added the Backlog SUE Added to the SUE backlog label Apr 22, 2024
@gericfo
Copy link

gericfo commented May 7, 2024

@HanaRebaiQA Thanks for this feedback. We close this issue as we will redesign the autoupgrade module (including this part, we will avoid this situation).

@gericfo gericfo closed this as completed May 7, 2024
@prestashop-issue-bot prestashop-issue-bot bot removed the Needs Specs Status: issue needs to be specified label May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.7.7.8 Affects versions Autoupgrade Module: autoupgrade Backlog SUE Added to the SUE backlog BO Category: Back Office Bug Type: Bug Minor Severity: minor bug > https://build.prestashop.com/news/severity-classification Module Module Regression Type: regression Verified The issue has been reproduced
Projects
None yet
Development

No branches or pull requests

3 participants