dtgmaze Posted August 29, 2018 Share Posted August 29, 2018 (edited) Hi, After updating the "1 click upgrade" module the following issue occurs on the backend. Frontend is working normally. Oops! An Error Occurred The server returned a "500 Internal Server Error". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused. I have enabled debug mode and get the following message. Check the screenshot! This happens when I update the module from v4.0.0 arrow_forward v4.1.0 Also when I try to delete the module the same thing happens. So now I cannot upgrade or remove the module "1 click upgrade" For now I reverted back to a backup, but I need to be able to upgrade in the future. Who can help? Edited August 29, 2018 by dtgmaze (see edit history) Link to comment Share on other sites More sharing options...
Rolige Posted August 29, 2018 Share Posted August 29, 2018 Hello, In the upgrade is very recommended to enable the options to disable non native modules and override files, otherwise, if you have errors there you could have troubles in the process. Regards! Link to comment Share on other sites More sharing options...
dtgmaze Posted August 29, 2018 Author Share Posted August 29, 2018 1 minute ago, Rolige said: Hello, In the upgrade is very recommended to enable the options to disable non native modules and override files, otherwise, if you have errors there you could have troubles in the process. Regards! I am not updating prestashop ! I am only updating the module "1 click upgrade" Link to comment Share on other sites More sharing options...
Rolige Posted August 29, 2018 Share Posted August 29, 2018 Ok, then you can try downloading it directly from addons and upload, instead to upgrade directly in the BO. Link to comment Share on other sites More sharing options...
dtgmaze Posted August 29, 2018 Author Share Posted August 29, 2018 Everyone hear has the same issue after updating or removing the 1 click upgrade https://github.com/PrestaShop/PrestaShop/issues/9516 Link to comment Share on other sites More sharing options...
dtgmaze Posted August 29, 2018 Author Share Posted August 29, 2018 (edited) Hi there, Who can help me further! The solution for as for I can find on https://github.com/PrestaShop/PrestaShop/issues/9516 This solution works, but what does it break? Removing the /modules/ps_facetedsearch/vendor folder stops the eror 500 and I can login to backend again! like @VictorVSa said, to solve the problem we can also remove or rename the folder: /modules/ps_facetedsearch/vendor I checked again and he’s right, this folder and others was not there before this bug, as you can see on this screenshot: I have further pinpointed it to /httpdocs/modules/ps_facetedsearch/vendor/symfony/yaml renaming the yaml , brings up the backend again. BUT IS THIS SAFE ???? Edited August 29, 2018 by dtgmaze (see edit history) Link to comment Share on other sites More sharing options...
jetx Posted August 30, 2018 Share Posted August 30, 2018 My own installation (1.7.4.2 and autoupgrade 4.0.1) does not have a vendors folder in ps_facetedsearch, it totally doesn't belong. So delete that module manually and replace it with your backed up version. Link to comment Share on other sites More sharing options...
Seppe Posted December 1, 2020 Share Posted December 1, 2020 When I used 1-click upgrade to update my shop from version to 1.7.6.5 to 1.7.6.9, my backend is messed up. I can't even add products in a normal way Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now