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
Add force removing system for some files #609
Add force removing system for some files #609
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's a good idea.
Even though the file is supposed to be deleted by the module, we know sometimes it fails. We know the deletion failure can happen if no XML file is provided, but it could also happen if a I/O fails at this moment.
So this workaround is OK 👍 . I think it's a good thing to force deletion of files we know are problematic if they stay around
I'm working on testing this. |
Related to PrestaShop/PrestaShop#33520 |
It's all good for me. Upgraded from 1.7.8.10 to 8.1.0. Everything went well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @boherm
Thank you for your PR, I tested it with florine and :
1.7.8.9 -> 8.1.1 ✔️
8.0.4 -> 8.1.1 ✔️
1.7.8.10 -> 8.1.1 ✔️
8.0.5 -> 8.1.1 ✔️
8.1.0 -> 8.1.1 ✔️
1.7.8.8 -> 8.1.1 ✔️
So it's a QA ✔️
Thank you
Thank you @boherm! |
when we upgrade from < 1.7.8.X to 8.X.
This anomaly come when a
news.yml
file stay in filesystem.(on 8.X versions, we have delete this file)
Maybe PrestaShop/PrestaShop#30761
2. Upgrade to 8.1.1 version.
3. The upgrade must be done with success.