EvilDragon Posted January 14, 2020 Share Posted January 14, 2020 (edited) Okay, it seems like I'm another one having issues with the upgrade to 1.7.6.2 from 1.7.5.2 I upgraded using the latest (4.10.1) version of the upgrader. No errors during the upgrade. At first look, everything seems to work fine - but the Backoffice has some issues. Whenever I open "Customers", "Brands", "Categories" or some other sites, I get a 500 error. The server log says: ./var/logs/prod.log:[2020-01-14 03:18:23] request.CRITICAL: Uncaught PHP Exception Doctrine\ORM\ORMException: "Unrecognized field: filterId" at /srv/www/vhosts/dragonbox.de/httpdocs/vendor/doctrine/orm/lib/Doctrine/ORM/ORMException.php line 101 {"exception":"[object] (Do ctrine\\ORM\\ORMException(code: 0): Unrecognized field: filterId at /srv/www/vhosts/dragonbox.de/httpdocs/vendor/doctrine/orm/lib/Doctrine/ORM/ORMException.php:101)"} I've followed similar threads here and made sure the filter_id columns are existing in the database. Now the weird thing is: When I enable DEBUG mode, this error does NOT occur! All these pages work fine for some reason, without any error. Any ideas? I hope someone can help me here? Right now, I'm running PHP 7.2.26 (FPM) on my own dedicated server, so I can easily switch to a lower or higher PHP version as well. Thanks in advance! Edited January 14, 2020 by EvilDragon (see edit history) Link to comment Share on other sites More sharing options...
Rhobur Posted January 18, 2020 Share Posted January 18, 2020 I'd say you remove var/cache (or remove var completely and replace it with the one from your PS version archive) and try again. Link to comment Share on other sites More sharing options...
Thiebauld Posted February 5, 2020 Share Posted February 5, 2020 I've got exactly the same problem. I've tried everything reported on github (add missing filter_id attribute in filter_admin table, clear cache ect...). "Customers", "Brands", "Categories" views are working only in debug mode. @EvilDragon Did you manage to resolve your issue ? Thanks, Link to comment Share on other sites More sharing options...
EvilDragon Posted February 5, 2020 Author Share Posted February 5, 2020 (edited) 7 hours ago, Thiebauld said: I've got exactly the same problem. I've tried everything reported on github (add missing filter_id attribute in filter_admin table, clear cache ect...). "Customers", "Brands", "Categories" views are working only in debug mode. @EvilDragon Did you manage to resolve your issue ? Thanks, Unfortunately not. I haven't retried yet, as I tried that a few hours and no new suggestions did appear here (of course I cleared the cache more than once :)) I'll wait for the next version and try again. And if that doesn't work, I'll try upgrading in smaller steps, from one version to the next to find out when it happens. EDIT: Just noticed 1.7.6.3 is out already. Have you tried that version and still have the same issue? Edited February 5, 2020 by EvilDragon (see edit history) Link to comment Share on other sites More sharing options...
Thiebauld Posted February 6, 2020 Share Posted February 6, 2020 17 hours ago, EvilDragon said: Unfortunately not. I haven't retried yet, as I tried that a few hours and no new suggestions did appear here (of course I cleared the cache more than once :)) I'll wait for the next version and try again. And if that doesn't work, I'll try upgrading in smaller steps, from one version to the next to find out when it happens. EDIT: Just noticed 1.7.6.3 is out already. Have you tried that version and still have the same issue? Thank you for your update, we finally resolve the problem by reinstalling the shop on a fresh Prestashop 1.7.6.3 and reimported the database... Everything works fine now but not a solution. Link to comment Share on other sites More sharing options...
EvilDragon Posted February 6, 2020 Author Share Posted February 6, 2020 Oh, did you reinstall it and just switch the database? Or which tables (and how) did you import? 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