Search the Community

Initially I upgraded my Prestashop version from 1.5.4.1 to the latest version 1.7.2.2 but post upgrade I got a lot of errors and issues hence I simply removed that version folder from my hosting server and re-uploaded back the 1.5.4.1 version that I had backed-up before the upgrade. I also had to delete the complete DB as that also got upgraded and had to restore the DB from the backup so that the 1.5.4.1 version that I re-uploaded works fine. As of now everything else seems to be working fine in Back-office except for the 'Modules' tab. The moment I click on the modules tab I get the following message: 'The controller adminnotfound is missing or invalid.' I would appreciate if someone could help me find a solution/fix for this issue. I have checked the ../controllers/admin/ folder to make sure all the files are there. There is no file missing in that folder.

Hi everyone! I'm new to Prestashop and just had Prestashop 1.4.7 freshly installed. I haven't installed any other version previously. I haven't even entered a single product nor modified anything, and yet I've already found myself an error. Every time when I click on the Modules Tab in the Back Office, an error message pops up: TECHNICAL ERROR [object XMLHttpRequest]. I've attached a screenshot so that you guys can see what I mean. I saw a few other people who had the same error solve theirs by replacing the Tools.php file in "your shop/classes/Tools.php" with another: http://forge.prestas...tream-issue-tab. I tried this and it didn't work for me. Anyone else that had this problem solved it other than replacing the "Tools.php" file? Or anyone have any ideas on how to solve this error? Please share! Thanks a lot! TECHNICAL ERRORobject XMLHttpRequest.bmp

When i uploaded my prestashop 1.4.4.0 shop to my hosting i had a problem: All the back office tabs worked perfectly except the modules tab. I was having a silent blank page and an error 500 in the response headers. The problem was the memory_limit value of my hosting configuration, and it was being a silent error because error_reporting was set to "Off" in the config file. The modules admin tab is the most memory consuming part of the back office and perhaps that requires a minimum of 32MB of ram to work properly. Hope that helps.