jamesharding Posted September 16, 2013 Share Posted September 16, 2013 Hi all. I have just updated one of my websites from 1.4.1 to the latest version 1.5.5.0 I did the upgrade through the Upgrade Module. The back office works perfectly however the front end does not. When you go to the front end all you get is index.php with a small rectangler box with links to , Home New Products Price Drops and Contact Us for which none of the links works. I have tried changing to the default theme, changing cache and updating htaccess file but get the same. Running out of ideas, anyone able to help? I have attached a picture of what I get. Link to comment Share on other sites More sharing options...
NemoPS Posted September 16, 2013 Share Posted September 16, 2013 Hi, and welcome to the forums! First, try turning on errors, as suggested in my signature. See if any error occur. If nothing ahppens, clear your browser's cache and try again. If nothing happens yet, replace all the files in the main directory (such as index.php) with new files taken from a fresh 1.5.5 package you can download from prestashop.com Let us know Link to comment Share on other sites More sharing options...
jamesharding Posted September 16, 2013 Author Share Posted September 16, 2013 Hi Nemo Thanks for the warm welcome and help. I have tried to do both of these but still no luck. I have noticed in the back office the image url's are also wrong and not working. But it is mainly the front of house. Also if I copy and paste the product urls from the back office and paste directly into the browser, these do not work either? Any further suggestions? Link to comment Share on other sites More sharing options...
NemoPS Posted September 16, 2013 Share Posted September 16, 2013 Really weird. CHeck that your base url is correctly set in preferences->seo&urls as well Link to comment Share on other sites More sharing options...
triplei Posted December 28, 2013 Share Posted December 28, 2013 if your index.php is NOT working and the rest of the website is working then you need to go into the backend and turn down the settings under your featured products or whatever you are featuring. You shouldn't feature 1000 products on your homepage because you will run up the ram on the server causing a memory error, your website to run extra slow, or your index.php page not to load at all. minimize your featured products or other modules that allow products and you should be good to go! Link to comment Share on other sites More sharing options...
dirknerkle Posted December 31, 2013 Share Posted December 31, 2013 I have the same problem -- tried upgrading and index.php went nowhere. I get nothing. Cleared browser cache -- even cleared browser history. Administration works fine but when the store is enabled, it won't display the store's home page. On the front page there are only 2 small pictures so it can't possibly be a memory issue on the server. So I restored it to the old version -- good news there -- the restore worked fine, although I did have to rebuild thumbnails. Not satisfied, I thought I'd try the upgrade again. Same problem. Restored again, all is working with the old version. Link to comment Share on other sites More sharing options...
NemoPS Posted December 31, 2013 Share Posted December 31, 2013 With the new one, you can get a free package and simply put the missing files where they should be Have you tried this? Link to comment Share on other sites More sharing options...
dirknerkle Posted December 31, 2013 Share Posted December 31, 2013 With the new one, you can get a free package and simply put the missing files where they should be Have you tried this? So essentially you're saying, "run the upgrade and then replace all the directories with files from a blank package so that it'll work again?" If that's the case, if so many things have to be replaced, why bother with the upgrade at all? I'm thinking that the software update ought to be much, much smarter than that and the end user shouldn't have to mess with it. And, I'm thinking that following a software update, the system should at least run. Is that too much to expect? Link to comment Share on other sites More sharing options...
dirknerkle Posted January 1, 2014 Share Posted January 1, 2014 Tried the upgrade again. This time after the upgrade, I copied all the "root" files from the Prestashop zip archive (installer) to the root of the store, thinking that if anything was missing, it would catch it. Then I tried to "view my shop." Nada. Zippo. No runnee store. I activated it, just to see whether that might trigger something. More nothing. Blank screen. Waited about 3 minutes, thinking that some updating was still happening. Nope. Gooseegg. Tried regenerating thumbnails, thinking that might be it. Nope. still nada. Zippo. Not wanting to waste any more time on this project, I did a rollback to my older version, 1.4.10.0. I had to rebuild the thumbnails again but hey, at least it fires up. I'm disappointed... Link to comment Share on other sites More sharing options...
NemoPS Posted January 3, 2014 Share Posted January 3, 2014 You don't have to copy everything. the config folder must not be overwritten Link to comment Share on other sites More sharing options...
JeffV Posted March 22, 2014 Share Posted March 22, 2014 So, how did you resolve this? I just upgraded from 1.5.6.1 to 1.5.6.2 and now get the same blank screen as described above. Link to comment Share on other sites More sharing options...
aduarte Posted March 23, 2014 Share Posted March 23, 2014 Hello everyone , does anyone know how to fix this? any help would be appreciated Fatal error: Uncaught Unknown column 'module_shop.enable_device' in 'on clause' SELECT h.`name` as hook, m.`id_module`, h.`id_hook`, m.`name` as module, h.`live_edit`FROM `ps_module` mINNER JOIN ps_module_shop module_shop ON (module_shop.id_module = m.id_module AND module_shop.id_shop = 1 AND module_shop.enable_device & 1)INNER JOIN `ps_module_shop` ms ON ms.`id_module` = m.`id_module`INNER JOIN `ps_hook_module` hm ON hm.`id_module` = m.`id_module`INNER JOIN `ps_hook` h ON hm.`id_hook` = h.`id_hook`WHERE (h.name != "displayPayment") AND (hm.id_shop = 1)GROUP BY hm.id_hook, hm.id_moduleORDER BY hm.`position`thrown in /mnt/codebase/datab/public_html/classes/db/Db.php on line 623 Link to comment Share on other sites More sharing options...
NemoPS Posted March 24, 2014 Share Posted March 24, 2014 You have to add that column to module_shop as TINYINT in the database Link to comment Share on other sites More sharing options...
dirknerkle Posted March 25, 2014 Share Posted March 25, 2014 You don't have to copy everything. the config folder must not be overwritten Shouldn't the upgrade have taken care of that? Is there a new upgrade that fixes this problem leftover from the last upgrade? Link to comment Share on other sites More sharing options...
NemoPS Posted March 26, 2014 Share Posted March 26, 2014 It should, but it doesn't do that, sometimes, so it's also worth trying that if some things are still broken Link to comment Share on other sites More sharing options...
sampeter Posted April 15, 2014 Share Posted April 15, 2014 I have installed the prestashop environment in my localsystem, i have successfully completed the installation but the thing is that its always going towards maintainence mode even i tried to make changes from administrator but it doesnt work. please help me........................!! 1 Link to comment Share on other sites More sharing options...
NemoPS Posted April 16, 2014 Share Posted April 16, 2014 So what happens if you toggle off maintenance mode from the back office and the page refreshes? Link to comment Share on other sites More sharing options...
Kanary Posted April 20, 2014 Share Posted April 20, 2014 Dear Nemo1, I upgraded from 1.4.9 to 1.6 and turned the error on. Now please check the error and advise: http://www.kanaryluxurywatches.com/2013Test/en/ Thanks. Link to comment Share on other sites More sharing options...
NemoPS Posted April 21, 2014 Share Posted April 21, 2014 The database is all screwed up. Login to the database and use a single collation for all tables (utf8_general_ci) Link to comment Share on other sites More sharing options...
Kanary Posted April 21, 2014 Share Posted April 21, 2014 The database is all screwed up. Login to the database and use a single collation for all tables (utf8_general_ci) Thank you very much dear. Regards, 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