thefridgemagnetshop Posted January 19, 2017 Share Posted January 19, 2017 Hi there, We can't seem to access our website after upgrading, I've attached a screen shot of what is happening when we try to access our front office - clearing cache and cookies seems to help occasionally but then it reverts back to this. A2 Hosting say they can't help because apparently it's working all over the world, it's an issue only on our end, but as well as it not working through our factory here, it will also not load on my mobile (which is not connected to the same server as the factory).As well as this, we can't log in to our back office. We deleted the install folder as specified, and the login in screen appears, but when we go to log in the input boxes disappear and we can't go any further. Also attaching screenshots with this.Any help would be much appreciated as we've been trying to figure this out all morning and it's been down since last night now. Front Office Error: Login Page Error: Link to comment Share on other sites More sharing options...
razaro Posted January 19, 2017 Share Posted January 19, 2017 You should try to enably debug mode and see what actual error says. Check this guide https://www.prestashop.com/forums/topic/224525-how-to-turn-on-error-reporting-for-debug-information-blank-page-500-internal-server-error/ Link to comment Share on other sites More sharing options...
thefridgemagnetshop Posted January 19, 2017 Author Share Posted January 19, 2017 We've tried this, it doesn't come up with any underlying error message? Link to comment Share on other sites More sharing options...
razaro Posted January 19, 2017 Share Posted January 19, 2017 Not even on Front office ? Then did you check error logs in hosting cPanel/Plesk ? What PHP version do you have ? Link to comment Share on other sites More sharing options...
thefridgemagnetshop Posted January 19, 2017 Author Share Posted January 19, 2017 Ok, I found the debug messagesFront Office:Back Office:And this is our error log? I'm not really sure what PHP version we have? Link to comment Share on other sites More sharing options...
razaro Posted January 19, 2017 Share Posted January 19, 2017 OK I see your site is back with just few error messages Warning/home/thefridg/public_html/modules/lengow/models/lengow.file.class.php on line 91Warning: fopen(http://kml.lengow.com/mp.xml): failed to open stream: no suitable wrapper could be found in /home/thefridg/public_html/modules/lengow/models/lengow.file.class.php on line 91Warning/home/thefridg/public_html/modules/lengow/models/lengow.file.class.php on line 91Warning: fopen(http://kml.lengow.com/plugins.xml): failed to open stream: no suitable wrapper could be found in /home/thefridg/public_html/modules/lengow/models/lengow.file.class.php on line 91 Try to disable that module, contact developer. Check this "wrapper is disabled in the server configuration by allow_url_fopen=0 " with your hosting. And do not forget to disable debug mode. Those worrnigs will be hidden. But this could be from something else but better to have fully working module too. Link to comment Share on other sites More sharing options...
thefridgemagnetshop Posted January 19, 2017 Author Share Posted January 19, 2017 How can I disable the module from my cpanel? As I can't get in to my back office at the moment Link to comment Share on other sites More sharing options...
razaro Posted January 19, 2017 Share Posted January 19, 2017 Oh I tought because front is working you fixed back office too. Well it could not be that module error that preventing login to back office. Try in incognite/private window maybe. Also try to get some detailed error message when you are loggin in. Turn PrestaShop debug mode on again. Then open developer tools and follor Network tab. Try to log in. Check on left side ajax-tab.php call and another tab Response. Hopefully some eror will be there . Also later do not forget to rename your admin folder, security wise. Link to comment Share on other sites More sharing options...
thefridgemagnetshop Posted January 19, 2017 Author Share Posted January 19, 2017 My front office still isn't working, it comes up with the same error?This is what the ajax-tab.php is saying, same error as the front office: Link to comment Share on other sites More sharing options...
razaro Posted January 19, 2017 Share Posted January 19, 2017 Was working few moments ago, strange. First make sure debug mode is enabled, sorry, It should display similar messages like in your cPanel. Do you have some A2 specific caching or Cloudflare ? Disable it you do. Link to comment Share on other sites More sharing options...
thefridgemagnetshop Posted January 19, 2017 Author Share Posted January 19, 2017 Yeah, it keeps doing it, it's worked a few times when we've cleared our cache/cookies but then it'll break again.Got the front office to work, not sure how long for, but this is what is showing:Just disabled the Cloudflare too but it still won't let me log in. Link to comment Share on other sites More sharing options...
thefridgemagnetshop Posted January 19, 2017 Author Share Posted January 19, 2017 I've now restored it to a back up from Tuesday before we upgraded but it's still not working at all -_-' Link to comment Share on other sites More sharing options...
thefridgemagnetshop Posted January 23, 2017 Author Share Posted January 23, 2017 hey razaro ! Sorry to be a pain, but don't suppose you're able to shed any more light on this at all ? Link to comment Share on other sites More sharing options...
razaro Posted January 24, 2017 Share Posted January 24, 2017 Sorry but I can not think of anything else. You did not post error from back office when you trying to log in. So full message. Steps: disable Cloudlfare, durn debug mode on, go to admin log in. Follow steps from previous post #8. Hope something new come up, more descriptive error. Link to comment Share on other sites More sharing options...
thefridgemagnetshop Posted January 24, 2017 Author Share Posted January 24, 2017 The error we are getting is:[Tue Jan 24 10:53:03 2017] [error] [client 81.137.251.134] PHP Warning: fopen(http://kml.lengow.com/plugins.xml): failed to open stream: no suitable wrapper could be found in /home/thefridg/public_html/modules/lengow/models/lengow.file.class.php on line 91, referer: http://thefridgemagnetshop.co.uk/admin869/index.php?controller=AdminLogin&token=144f1055b452f64479e84f96858765bemodules/lengow/models/lengow.file.class.php on line 91, referer: http://thefridgemagnetshop.co.uk/admin869/index.php?controller=AdminLogin&token=144f1055b452f64479e84f96858765beI've looked on line 91 but I can't really see anything obvious to me, but I'm not an expert in CSS or coding so I'm not really sure what I should be looking for anyway. I've attached a screenshot of this area of coding.Any help you can give would be great! thank u so much Link to comment Share on other sites More sharing options...
bellini13 Posted January 24, 2017 Share Posted January 24, 2017 Well at least you know it is a custom module causing the issue. Remove the module from the file system and then try to login again. Then contact the author of the module Link to comment Share on other sites More sharing options...
thefridgemagnetshop Posted January 24, 2017 Author Share Posted January 24, 2017 We've tried to remove from our A2 hosting account cpanel and have tried to rename it, tried to delete it and it's still showing us this warning error. So we're a bit confused , what do you suggest? I really appreciate all this help Link to comment Share on other sites More sharing options...
bellini13 Posted January 24, 2017 Share Posted January 24, 2017 if you physically remove the module from the file system, then you cannot be receiving that same warning. Link to comment Share on other sites More sharing options...
thefridgemagnetshop Posted January 24, 2017 Author Share Posted January 24, 2017 (edited) All Lengow files have been deleted, we still can't log in and our images for all our products have disappeared. In error log we are now getting: [Tue Jan 24 16:35:34 2017] [error] [client 109.121.61.202] PHP Warning: phpinfo(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/thefridg/public_html/phpinfo.php on line 8 [Tue Jan 24 16:35:34 2017] [error] [client 109.121.61.202] PHP Warning: phpinfo(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/thefridg/public_html/phpinfo.php on line 4 [Tue Jan 24 16:22:58 2017] [error] [client 86.166.109.183] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 77 bytes) in /home/thefridg/public_html/classes/Tools.php on line 366, referer: https://www.bing.com/ This is what the phpinfo.php code looks like.Our login is also coming up with a 404 error now. Edited January 24, 2017 by thefridgemagnetshop (see edit history) Link to comment Share on other sites More sharing options...
bellini13 Posted January 24, 2017 Share Posted January 24, 2017 [Tue Jan 24 16:35:34 2017] [error] [client 109.121.61.202] PHP Warning: phpinfo(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/thefridg/public_html/phpinfo.php on line 8 For this you should contact your hosting provider so they can properly configure PHP [Tue Jan 24 16:22:58 2017] [error] [client 86.166.109.183] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 77 bytes) in /home/thefridg/public_html/classes/Tools.php on line 366, referer: https://www.bing.com/ For this you have simply run out of memory. You should try to increase the memory available 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