Nappipatteri Posted July 13, 2019 Share Posted July 13, 2019 After upgrading Prestashop 1.7.5.2 to 1.7.6 many Backoffice features just show empty, some work, but mostly whole Backoffice is now unusable !!! Shop is in maintenance mode, and if I go to visit shop, everthing is showing in Frontend like before upgrafe, also checked in database that values are in tables....but Prestashop Backend has problems to show things. Link to comment Share on other sites More sharing options...
Nappipatteri Posted July 13, 2019 Author Share Posted July 13, 2019 (edited) When looking the browser developer tools, it looks that those few working BO parts has "...index.php?controller=...." in url, and those that load properly look like this: ..../index.php?controller=AdminAttributesGroups&token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ..../index.php?controller=AdminOrders&token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx and all those BO parts that fails and just show empty page, are missing it, also otherwise the url structure looks different ??? Like all the failing BO parts look like this: ..../index.php/sell/catalog/products?_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ..../index.php/sell/catalog/categories?_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ..../index.php/configure/advanced/system-information/?_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Has there been some change on this between 1.7.5.2 -> 1.7.6 ? Edited July 13, 2019 by Nappipatteri (see edit history) Link to comment Share on other sites More sharing options...
Nappipatteri Posted July 13, 2019 Author Share Posted July 13, 2019 https://github.com/PrestaShop/PrestaShop/issues/14624 Link to comment Share on other sites More sharing options...
selectshop.at Posted July 13, 2019 Share Posted July 13, 2019 Check as well your min requirements to the server for prestashop 1.7. that are described here: https://www.prestashop.com/forums/topic/884856-best-server-settings-for-prestashop-17-tested-in-production/ This problem could be a too short set memory_limit or max_input_vars on your server. Link to comment Share on other sites More sharing options...
Nappipatteri Posted July 13, 2019 Author Share Posted July 13, 2019 (edited) Most of the min requirements mentioned are for Prestashop version 1.7.4 or below, or higher than that. My shop was already 1.7.5.2 and working, so I would assume change from 1.7.5.2 to 1.7.6 would not have meaning, at least what comes to listed rquirements. But I modified some values more like that in php.ini. I also run "apt update" and "apt upgrade", to update few mentioned items. But I see so far no change, those parts that worked in BO, still work, and those that did not work after update, still dont work. Every item that uses index.php?controller in url, are fine, others not, this is still only most clearly visible difference between parts that work or not work. Edited July 13, 2019 by Nappipatteri (see edit history) Link to comment Share on other sites More sharing options...
Rhobur Posted July 13, 2019 Share Posted July 13, 2019 You sure the files ownership and the permissions are correct? Usually this is a cause. Link to comment Share on other sites More sharing options...
Mostafa.J Posted July 15, 2019 Share Posted July 15, 2019 exactly the same here Link to comment Share on other sites More sharing options...
Nappipatteri Posted July 15, 2019 Author Share Posted July 15, 2019 This seems to be known issue, reply to my ticket in Prestashop github: ------------------------------------------- This issue is caused by a old version of the autoupgrade module. There is currently a conflict between the twig versions included by the core and the module. As you cannot upgrade the module, you can instead safely remove it by deleting the folder modules/autoupgrade. You will recover your BO immediately. Link to comment Share on other sites More sharing options...
Mostafa.J Posted July 20, 2019 Share Posted July 20, 2019 On 7/15/2019 at 11:59 PM, Nappipatteri said: This seems to be known issue, reply to my ticket in Prestashop github: ------------------------------------------- This issue is caused by a old version of the autoupgrade module. There is currently a conflict between the twig versions included by the core and the module. As you cannot upgrade the module, you can instead safely remove it by deleting the folder modules/autoupgrade. You will recover your BO immediately. it worked! thanks! 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