yebberdog Posted November 2, 2009 Share Posted November 2, 2009 I have spent a number of weeks learning and creating a website using Prestashop. All seems to have been fine and the site has been live after extensive testing and recently took three orders. Today I have hit major problems, when I go to the ADMIN/MODULES section, I am seeing Parse error(s) in module(s) for all standard modules, only custom modules are not affected. This has also resulted in the cart not working in the front end, so when I try and add a product to the cart I also get a parse error. The strange thing is that I have not made any changed to the site, either by adding new products or changes.I am running Prestashop Version 1.2.4.0 from a fresh install. I have added a screen shot below so if anyone can add any help as to the problem I will be very grateful. This is my first Prestashop site have completed many Zen Cart shops and the thought of re-installing and starting again is more than I can take.So please please any ideas would be very welcome.Kind regards Link to comment Share on other sites More sharing options...
lionelbernier Posted November 3, 2009 Share Posted November 3, 2009 hi,i ve had the same error....is someone know what to do to correct this problem.thanks a lot.Lionel Link to comment Share on other sites More sharing options...
ningu Posted November 3, 2009 Share Posted November 3, 2009 Have you checked your php_error logs ? Link to comment Share on other sites More sharing options...
lionelbernier Posted November 3, 2009 Share Posted November 3, 2009 Thanks for the answer.In fact i'm really new on prestashop.I didn't know where to find the error log.phpCould you tell me where to find it.lionel Link to comment Share on other sites More sharing options...
lionelbernier Posted November 3, 2009 Share Posted November 3, 2009 In fact i've found a log folder compressed where i've found an erro log filehe says :[Mon Nov 02 23:40:20 2009] [error] [client 213.58.133.66] File does not exist: /home/perlashop1/domains/perlasensua-shop.com/public_html/img/abc.jpg, referer: http://www.perlasensua.com/[Mon Nov 02 23:40:20 2009] [error] [client 213.58.133.66] File does not exist: /home/perlashop1/domains/perlasensua-shop.com/public_html/404.shtml, referer: http://www.perlasensua.com/[Tue Nov 03 00:08:39 2009] [error] [client 80.133.248.143] File does not exist: /home/perlashop1/domains/perlasensua-shop.com/public_html/img/ban.jpg, referer: http://www.care4babygallery.net/c4toplist/[Tue Nov 03 00:08:39 2009] [error] [client 80.133.248.143] File does not exist: /home/perlashop1/domains/perlasensua-shop.com/public_html/404.shtml, referer: http://www.care4babygallery.net/c4toplist/in fact a lot of lines, but it crashes this morning due to an error certainly...Does images can cause this kind of crashes? Link to comment Share on other sites More sharing options...
yebberdog Posted November 6, 2009 Author Share Posted November 6, 2009 Out of interest I did resolve this issue, however I am not closing this thread as I still have no idea why the problem happened in the first place. When I checked any php file associated with any of the modules where the parse error existed, there was what I can only describe as a large block of random numbers at the top of the file. The only legible content was base64?To overcome the problem I simply deleted all standard modules and FTP the original module from my computer to my server. Link to comment Share on other sites More sharing options...
lionelbernier Posted November 8, 2009 Share Posted November 8, 2009 Problème résolu, problem solvedIn fact my provider changed us the from hosted server because Mysql 5.0.37 seems to bug with prestashop.en fait notre fournisseur nous a changé de serveur car le mysql 5.0.37 semble ne pas etre compatible avec prestashop. Link to comment Share on other sites More sharing options...
yebberdog Posted November 19, 2009 Author Share Posted November 19, 2009 The route cause which I have now found relating to the parse error was a virus which infected many php files, in particular index.php and all the standard modules. Transfering the backup modules from a clean version only resolved the problem for a short time, the key was removing all the infected files that showed a base64 code line in many php files. 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