Radek101 Posted May 6, 2021 Share Posted May 6, 2021 (edited) Hello, I tried to update Prestashop 1.7.7.3 (which was a clean installation with custom theme and some extra modules) to the 1.7.7.4 with Prestashop 1-click upgrade module v4.12.0. I got this message at the end: [2021-05-07 10:36:21] Database upgrade OK [2021-05-07 10:36:27] Warning detected during upgrade. [2021-05-07 10:36:27] Database upgraded. Now upgrading your Addons modules... [2021-05-07 10:36:29] 68 modules will be upgraded. [2021-05-07 10:36:30] [INTERNAL] /hosting/www/domain.com/www/classes/controller/FrontController.php line 359 - Trying to get property 'logged' of non-object There was no information "upgrade complete" but I saw Prestashop 1.7.7.4 at the top left corner in the administration. I can Log in into administration without problem. Realized that if I disable all modules then I got succesful upgrade and it finish. Now if I want to know which module this cause how can I find it? I revert back previous backup so I can find it during upgrade. But If I checked autoupgrade/tmp/log.txt there is no mention which module has the problem. Have anyone experience with this? please approve @Prestashop Admin my first post Thank you Edited May 7, 2021 by Radek101 (see edit history) Link to comment Share on other sites More sharing options...
SharmPRO Posted June 12, 2021 Share Posted June 12, 2021 same problem here. tried to update to 1.7.6.5 tried to update to 1.7.7.0 tried to update to 1.7.7.4 same problem Only solution found: updated to 1.7.6.5 with usual error, then launched update to 1.7.7.4 than complete without error. Seems to work Link to comment Share on other sites More sharing options...
Radek101 Posted June 22, 2021 Author Share Posted June 22, 2021 Hi, I found my problem with with this carrier module https://github.com/Zasilkovna/prestashop/issues/88. Unfortunatelly it doesn't help to just only unistall the module to succesful upgrade. But it needs to delete module completely from modules. The new version of the module is already ok and have fixed this issue. Best regards Radek 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