warrenm Posted October 25, 2012 Share Posted October 25, 2012 I installed 1.5 a month or so ago and when it came to upgrading to 1.5.1 using the 1-click upgrade, the process started OK, reached the stage that the db and files had been backed up but then the second that the actual upgrade process started after the backup had finished, I received the error: Javascript error (parseJSON) detected for action "upgradeFiles".Starting restoration... I see this error listed in many discussions but no conclusion. I thought that as new versions of the 1-click upgrade module came out and when 1.5.2 was released that the 1-click upgrade would work, but I still get the same error. Any ideas how I can upgrade or what is going wrong? I'm stuck on 1.5.0.17. warren Link to comment Share on other sites More sharing options...
musicmaster Posted October 26, 2012 Share Posted October 26, 2012 When I had a similar error it looked like it might be a timeout. So I disabled the backup of the images and other files (I had a manual backup anyway and the PS restore is not very reliable). It helped me at least further: instead of an error in the midst of the backup I got the same error during the update of database. You might also consider adapting the PHP.INI settings that regulates the timeout. Anyway, take care that you have a good backup both of your files and your database. 1 Link to comment Share on other sites More sharing options...
warrenm Posted October 27, 2012 Author Share Posted October 27, 2012 Thanks so much for your help but its not too encouraging. This is a screenshot of the point that the upgrade stops: https://www.dropbox.com/s/ce5ni83uz3azoy5/2f.png Is there a way I can get more feedback about from the system or the logs about where the problem is? Link to comment Share on other sites More sharing options...
musicmaster Posted October 28, 2012 Share Posted October 28, 2012 It looks like you are upgrading on a server where you have too little rights. You should at least set the rights of all files to 666. And you might try an updates first at home on a localhost situation. Link to comment Share on other sites More sharing options...
warrenm Posted October 29, 2012 Author Share Posted October 29, 2012 Hi, Thanks again for the advice... i already had a 1.5.0.17 test install and when I tried to upgrade to 1.5.2, I received a similar error. When I then went and changed all files to 777 recursively, the upgrade worked fine and the store seems perfect. When I went to change permissions back to 755 though, the store stopped working. So the question is, out of all the files/directories in PS, which need to be 777 because clearly I can't leave my entire site with 777? If I can figure this out, I should be able to change my live site permissions to 777, upgrade and then change permissions back. Warren Link to comment Share on other sites More sharing options...
musicmaster Posted October 29, 2012 Share Posted October 29, 2012 My Prestashop asked me to change the settings for only one file: \config\xml\default_countries_modules_list.xml Link to comment Share on other sites More sharing options...
musicmaster Posted October 30, 2012 Share Posted October 30, 2012 In Tools->configuration settings you can see where you need to change the permissions: Link to comment Share on other sites More sharing options...
warrenm Posted November 3, 2012 Author Share Posted November 3, 2012 Hi, I don't have any problems reported in this section other than magicquotes which i believe is not a critical item. http://o7.no/ntUwJf Any other ideas on how I can progress? Warren Link to comment Share on other sites More sharing options...
Sunder Posted January 2, 2013 Share Posted January 2, 2013 Hi, I had the same problem, Javascript error (parseJSON) detected for action "upgradeFiles".Starting restoration... Solved after i tried with Firefox. Sunder Link to comment Share on other sites More sharing options...
ubergirl Posted July 9, 2013 Share Posted July 9, 2013 Hello everyone. I'm having this parseJSON javascript error on autoupgrade as well, so I'm trying to create a checklist of possible causes. Here is what I understand from this thread on this forum: Potential cause: Timeout Check or try: disabled the backup of the images and other files (make manual backup before) Potential cause: PHP.INI settings Check or try: edit this file to make sure there are no timeout (Hey guys, how do we do that?) Potential cause: upgrading on a server where you have too little rights Check or try: Use phpmyadmin to check that your user has all privileges on your database. also: You should at least set the rights of all files to 666 Potential cause: the type of browser you use Check or try: try with firefox (Really????, can it make a difference) If anyone has any insight on this matter, please reply to this topic... Link to comment Share on other sites More sharing options...
musicmaster Posted July 10, 2013 Share Posted July 10, 2013 I did some search on that parseJSON error on the internet. The only location where I found something that could be a solution is here: http://forge.prestashop.com/browse/PSCFV-7119?page=com.atlassian.streams.streams-jira-plugin%3Aactivity-stream-issue-tab Link to comment Share on other sites More sharing options...
ubergirl Posted July 11, 2013 Share Posted July 11, 2013 As follow-up notes: before updating to 1.5x, I previously updated from 1.4.10 to 1.4.11 with the 1-click upgrade, and it worked fine. It's when I try to go from 1.4.11 to 1.5.x that it bugs... Link to comment Share on other sites More sharing options...
Recommended Posts