JBarros Posted January 7, 2015 Share Posted January 7, 2015 (edited) Hi, after upgrade from 1.6.0.9 to 1.6.0.11 cant login at administration , give me http error 500 someone can help? Edited January 8, 2015 by barros77 (see edit history) Link to comment Share on other sites More sharing options...
mytheory. Posted January 8, 2015 Share Posted January 8, 2015 Hi, How is your front office? Have you tried clearing cache (CTRL + F5)? Or try to access it using incognito mode in chrome. HTH! Link to comment Share on other sites More sharing options...
JBarros Posted January 8, 2015 Author Share Posted January 8, 2015 hi, the front office is in mantenance , when i upgrade i never access more at backoffice . i have clear the cache but dont solve Link to comment Share on other sites More sharing options...
Eolia Posted January 8, 2015 Share Posted January 8, 2015 rename your .htaccess at the root of your directory shop to .htaccess1 and retry Link to comment Share on other sites More sharing options...
JBarros Posted January 8, 2015 Author Share Posted January 8, 2015 dont solve Eolia Link to comment Share on other sites More sharing options...
Eolia Posted January 8, 2015 Share Posted January 8, 2015 Ok display errors on in config/defines.inc.php ? Could you look into your error.log (if you have access to) ? Link to comment Share on other sites More sharing options...
guilleogallar Posted January 8, 2015 Share Posted January 8, 2015 Hello, I've got the following error after upgrade to prestashop 1.6.0.11 in Front Office: Fatal error: Call to undefined method mysqli_result::fetch_all() in xxxx/classes/db/DbMySQLi.php on line 112 It appears in FrontOffice. Thanks everyone! Link to comment Share on other sites More sharing options...
guilleogallar Posted January 8, 2015 Share Posted January 8, 2015 Hello again, in other store that I've tried to upgrade, I have the same error in frontoffice and backoffice too. Thanks. Link to comment Share on other sites More sharing options...
shacker Posted January 8, 2015 Share Posted January 8, 2015 maybe mysqli is not installed on your server. need to check with your host , or in the control panel, in php config check if you have mysqli installed Link to comment Share on other sites More sharing options...
mytheory. Posted January 8, 2015 Share Posted January 8, 2015 HI, Are you sure your upgrade completed successfully? How did you upgrade - manually or automatic option? I think you might want to use a backup and upgrade again, or make a second copy and test the upgrade on that one. Link to comment Share on other sites More sharing options...
JBarros Posted January 8, 2015 Author Share Posted January 8, 2015 hi, the upgrade is completed successfully without errors , automatic upgrade i install prestashop again in subdomain and upgrade good Link to comment Share on other sites More sharing options...
shacker Posted January 8, 2015 Share Posted January 8, 2015 i upgraded 3 sites in automatic, and have issues in all. must check Link to comment Share on other sites More sharing options...
guilleogallar Posted January 9, 2015 Share Posted January 9, 2015 Hello, I have reviewed all sql queries and autoupgrade module says that all is ok. Sql is runnig fine in the server, I have a wordpressw installed and it is working fine. Thanks. Link to comment Share on other sites More sharing options...
aknobody Posted January 9, 2015 Share Posted January 9, 2015 When I initially installed prestashop 1.6 the installer said msqli was ok, everything installed fine. When trying to upgrade today from 1.6.0.9 to 1.6.0.11 using 1-click. The upgrade got no errors (exept the geolite database-file was not backed up.) And when going to the front page og backend: Server error 500 After enabling dev-mode. Fatal error: Call to undefined method mysqli_result::fetch_all() in /home/usernamehere/public_html/classes/db/DbMySQLi.php on line 112 The back end worked for a while, then I got the same error on front and back. Glad I backed up the whole site manually. Link to comment Share on other sites More sharing options...
JBarros Posted January 9, 2015 Author Share Posted January 9, 2015 (edited) hi, i have backup the important things and remove all installation , after i install one new prestashop 1.6.0.11 and work good , after this i change the tables in database and some folders via ftp , working good 10 minuts and appear the same error Edited January 9, 2015 by barros77 (see edit history) Link to comment Share on other sites More sharing options...
guilleogallar Posted January 9, 2015 Share Posted January 9, 2015 Hello, try this, i works for me: https://github.com/PrestaShop/PrestaShop/commit/20d880cd0c4720afeb2a95fc49e787e92d663881 Regards. 2 Link to comment Share on other sites More sharing options...
Dreamtheme Posted January 9, 2015 Share Posted January 9, 2015 Hello, try this, i works for me: https://github.com/PrestaShop/PrestaShop/commit/20d880cd0c4720afeb2a95fc49e787e92d663881 Regards. Yes this is the fix if your hosting don't have Mysql ND installed. You can follow the bug report here. Link to comment Share on other sites More sharing options...
JBarros Posted January 9, 2015 Author Share Posted January 9, 2015 i have change the files and now gime this error Fatal error: Class 'Db' not found in /home/probike/public_html/config/alias.php on line 64 Link to comment Share on other sites More sharing options...
guilleogallar Posted January 9, 2015 Share Posted January 9, 2015 Hello, you must have a misteke doing the fix. It works fine for me. Link to comment Share on other sites More sharing options...
JBarros Posted January 9, 2015 Author Share Posted January 9, 2015 no, i confirm all Link to comment Share on other sites More sharing options...
bellini13 Posted January 9, 2015 Share Posted January 9, 2015 The patch posted above does not effect code line 64. you must have made a mistake in applying the change Link to comment Share on other sites More sharing options...
RockyS Posted January 10, 2015 Share Posted January 10, 2015 Hello, try this, i works for me: https://github.com/PrestaShop/PrestaShop/commit/20d880cd0c4720afeb2a95fc49e787e92d663881 Regards. I can confirm this fix works. But I didn't have to change db.php file. Link to comment Share on other sites More sharing options...
Recommended Posts