tdr170 Posted January 2, 2013 Share Posted January 2, 2013 (edited) Just updated a 1.4.9.1 site to 1.5.3.1 (test site not live) made a few changes then thought I should probably turn force compile on while testing. So I turned on and saved got a 500 internal server error hit back saved again same result then I did a F5 refresh and all I get is 500 internal server error can not get into admin or front office. This is the log report: 20130102T170438: mysite.com/shop3/administrator/index.php PHP Fatal error: Call to undefined method Shop::initialize() in /hermes/bosweb26d/b1447/ipg.mysite/shop3/config/config.inc.php on line 88 Have not figured this out yet, I am going to see if I can switch off Force Compile in the DB. if you Edited January 2, 2013 by tdr170 (see edit history) Link to comment Share on other sites More sharing options...
Site Posted January 3, 2013 Share Posted January 3, 2013 Hi, Have a look under "ps_configuration" "PS_SMARTY_FORCE_COMPILE" mine is set to "2" for force compile "0" is for Never recompile template files I'm guessing it may try and continue to regenerate the templates Link to comment Share on other sites More sharing options...
Audrius Posted January 3, 2013 Share Posted January 3, 2013 Just updated a 1.4.9.1 site to 1.5.3.1 (test site not live) made a few changes then thought I should probably turn force compile on while testing. So I turned on and saved got a 500 internal server error hit back saved again same result then I did a F5 refresh and all I get is 500 internal server error can not get into admin or front office. This is the log report: 20130102T170438: mysite.com/shop3/administrator/index.php PHP Fatal error: Call to undefined method Shop::initialize() in /hermes/bosweb26d/b1447/ipg.mysite/shop3/config/config.inc.php on line 88 Have not figured this out yet, I am going to see if I can switch off Force Compile in the DB. if you Is it really a force compile problem? Maybe you got it on making second test order? Link to comment Share on other sites More sharing options...
tdr170 Posted January 3, 2013 Author Share Posted January 3, 2013 Hi, Have a look under "ps_configuration" "PS_SMARTY_FORCE_COMPILE" mine is set to "2" for force compile "0" is for Never recompile template files I'm guessing it may try and continue to regenerate the templates Yes I changed to 0 to turn it off and still can not enter BO or FO still 500 error. Is it really a force compile problem? Maybe you got it on making second test order? Never got a chance to do any test orders was a fresh install and upgrade. Link to comment Share on other sites More sharing options...
tdr170 Posted January 3, 2013 Author Share Posted January 3, 2013 (edited) I have not been able to log in to the forum so I have deleted and will start over and try again will post here if issue is same on next install. Edited January 6, 2013 by tdr170 (see edit history) Link to comment Share on other sites More sharing options...
tdr170 Posted January 6, 2013 Author Share Posted January 6, 2013 Well I finally had the time to upload the 1.4.9.1 site and upgrade to 1.5.3.1 again and yep once again the minute I try to turn on force compile I loose the Admin and FO to http 500 error. The funny one here is just for kicks I uploaded the classes, config, controllers, css and I could get back in the minute I clicked on force compile, save, back to http 500 error. Upload the same folders back in this time I deleted all modules that were from 1.4 just in case set all other settings, so iwas was working in the back office for some time I decided to change the theme to 1.5 before trying force compile this time as soon as I clicked on Preferences/themes back to http 500 error and this time nothing helps. Not sure If I should bother posteing on the forge they will just say its my 1.4.9 or ignore it all together like they do with any other serios issues that I have had. (I know but I am starting to get a little annoyed) This same site I had updated to 1.5.2 without any issues so it must be something with the update to 1.5.3.1 Its a test site and was originally a 1.4.6 updated to 1.4.7 then 1.4.9. now trying 1.5.3 but if this is it I guess I will not be updating to 1.5. I have 800 products in my site and am not going to start from scratch just to use 1.5, I also have a 1.5.3.1 test site and there I have no issues at this time. Just some FYI Link to comment Share on other sites More sharing options...
Site Posted January 6, 2013 Share Posted January 6, 2013 Hi, Have you tried a fresh install of 1.5.3.1 on your server? Link to comment Share on other sites More sharing options...
tdr170 Posted January 6, 2013 Author Share Posted January 6, 2013 Yea Last line of my post above works great,. I have 4 sites: 1 - 1.4.7 Live site 2 - 1.4.9 test site upgraded from site above and used to test new ideas without effecting live site. 3 - 1.4.9 site upgraded to 1.5.3.1 used to test upgrades to 1.5 (problem site) 4 - 1.5.3.1 test site I did not have this issue with site 3 untill 1.5.31. this site has been upgraded to 1.5.01, 1.5.017, 1.5.2. Think I will try a manual upgrade the crappy part is the time it takes to delete the site and re-upload 1.4, drop tables from database and upload backup for 1.4. Link to comment Share on other sites More sharing options...
Site Posted January 7, 2013 Share Posted January 7, 2013 Have you tried a non live upgrade to the shop 4 1.5.3.1 test site? So all 800 products are on the latest release? Link to comment Share on other sites More sharing options...
tdr170 Posted January 7, 2013 Author Share Posted January 7, 2013 As I stated in my post above (last line) I am going to try a manual upgrade as one thing I notice is that sometimes the URL in the address bar seems to point to autoupgrade or something like that but makes me think that during upgrade something is not deleted or is left in database that should not be there. In the original release of 1.5.3 there were tables missing from the database, makes me think that there is more to that then what has been fixed at this point. Stay tuned uploading now. Link to comment Share on other sites More sharing options...
tdr170 Posted January 9, 2013 Author Share Posted January 9, 2013 Well seems you can not use the manual update for 1.4 to 1.5 I get the message you can not use upgrade as you already have the latest version, then the page redirects to the install. Link to comment Share on other sites More sharing options...
tdr170 Posted January 10, 2013 Author Share Posted January 10, 2013 So I gave up on upgrading 1.4.9 site as it just does not work, Unbelievable!!! I uploaded a backup of my 1.4.7 actual online store just encase the upgrade I originally did to the 1.4.9 site was not an issue. Uploaded the shop created the database upgraded the One click upgrade only to get this error message. Javascript error (parsejson) detected for action "upgradenow". Starting restoration Onve again UNBELIEVABLE!!! Starting to get very disappointed with Prestashop as a whole. Link to comment Share on other sites More sharing options...
.png.022b5452a8f28f552bc9430097a16da2.png)
Recommended Posts