Error upgrading to v1.7.1

[gray]

[Ajax / Server Error for action upgradeDb] textStatus: "error " errorThrown:"Internal Server Error " jqXHR: " "

 

It seems to have downloaded all the files, but gets stuck when upgrading the database.

 

Any ideas plz

[prestagas]

me too !

[delboy01]

happened to me from 1.7.0.5 to 1.7.0.6

 

Mucked my database right up thankfully my host backs up the database now and again so rolled back

and didnt have that much work to do.

 

ill stick to 1.7.0.5 for now until people have luck upgrading

[gray]

I must admit I had errors upgrading to 1.7.0.6

 

But I cannot remember what they were.

 

I thought 1.7.1 would have ironed out these sort of problems.

[gray]

Done a roll back and that finally crashed with a blank screen. So i now cannot get into admin

[delboy01]

Done a roll back and that finally crashed with a blank screen. So i now cannot get into admin

you will have to go on your hosts website and see if you got a back up of the database and files im guessing

again same happened to me its like wrecking peoples websites

come on prestashop your mucking with peoples livelihood here !

Edited April 3, 2017 by delboy01 (see edit history)

[gray]

Just deleted the whole of my wamp server and copied over yesterdays copy. So back up and running again.

Edited April 3, 2017 by gray (see edit history)

[x2daz]

last time that happened - when upgrading from 1.7.0.4 to 0.5

it was then caused by 1 click upgrade

 

i did not upgrade from 1.7.0 to 1.7.1 yet, but make sure you use the latest version of 1 click upgrade.

[rl_lucian]

Same here..

 

Tryed with major release and with local directory, same results: error, and needed to put back the 1.7.0.5 backup. 

Our clients are not very happy..

[nortom]

Here also this problem. I had this with 1.7.0.5 tot 1.7.0.6

What's the fix

[rl_lucian]

I had succeded upgrade on one of our developing shops, from 1.7.0.6 to 1.7.1.0.

 

90% of the customisation we made on homepage are gone, and the custom theme was reseted on demo state.

 

The theme developers said that they will have to update the theme first, and only after that we shoud make the upgrade.

[nortom]

Template related?

[rl_lucian]

Template related?

 

They said if we make the update to Presta core, before doing the update to template, problems will appear,

because of the fact that 1.7.1.0 has significant modifications from 1.7.0.5.

[gray]

This is another major balls up with prestashop, when the rollback crashes.

 

They must do better testing before issuing a an update.

[breda_Mcg]

i tried the one click upgrade but I get an error saying:

PrestaShop Original version:
Error Unable to check md5 files

 

Trying to upgrade to 1.7.1.0

thanks

[folkifoon]

i get this error during uipdate:

[Ajax / Server Error for action upgradeFiles] textStatus: "error " errorThrown:"Internal Server Error " jqXHR: " "

help please

[omine]

This error is caused by PHP execution time limit.

 

Increase the time limit

 

On php.ini (sample)

max_execution_time = 600

^{(10 minutes)}

 

I also recommend to change others settings:
 

max_input_time = 180
memory_limit = 300M
max_input_vars = 20000

Of course, adjust the values according to your environment.

 

If you are running under FCGI, checkout this topic: https://www.prestashop.com/forums/topic/498947-backoffice-displays-php-code/

Edited April 5, 2017 by omine (see edit history)

[breda_Mcg]

Thanks I will try this.

B

[MaSTeRMinD]

I got the same error after upgrading from 1.7.0.6. Then i had to manually delete the cache folder because BO was giving error 500. As it seems the rest is OK but the database is not upgraded. In this state if you try to add new product you will be redirected to dashboard. You also can't edit existing products.

 

I managed to fix it by going to admin folder autoupgrade/latest/install/upgrade/sql/

Then open 1.7.1.0.sql . Then search and replace PREFIX_ with your prefix. Then copy the sql and execute it with phpmyadmin. 

[Antoine F]

Hello everyone,
Could you please make a new ticket on the forge to transmit the issue to the team? Here is the dedicated link of the forge

Thank you. 

[gray]

http://forge.prestashop.com/browse/BOOM-2777

[giesse]

Hello

I tried to upgrade from version 1.7.0.5 to 1.7.1 and give me that error.

I saw this old topic https://www.prestashop.com/forums/topic/271134-solved-upgrade-fatal-error-internal-server-error-jqxhr/

and I tried uploading files via ftp and enabling in "clik-upgrade" channel "local directory." The files have been updated but then there is error: "error during database upgrade. You may need to restore your database."

[aphilipp]

The same problem... But I downloaded the new version of 1-Click from the site and MANUALLY install it.

Successfuly upgraded from 1.7.0.5 to 1.7.1 ))

Edited April 11, 2017 by aphilipp (see edit history)

[gray]

Hi aphilipp - How did you go about manually installing it ? Its something I have never done successfully.

[gray]

It does not look like there is any urgent upgrade for this problem, or way of solving this.

 

So I have installed  1.7.1 with no problems.

 

The problem now is how do I best go about exporting data (products and categories) from v1.7.0.5 into v1.7.1

 

I have something like 500 products and v1.7.0.5 does not have an export facility direct from admin, only Advanced Parameters / Database / SQL Manager

[breda_Mcg]

 

The same problem... But I downloaded the new version of 1-Click from the site and MANUALLY install it.

Successfuly upgraded from 1.7.0.5 to 1.7.1 ))

 

 

Hi APhilipp

Can you give any info on how to you manually upgraded? I see where I can download the files, but what next?

I tried the latest version of 1 click and its not working.

thanks,

Breda

[breda_Mcg]

Hi Everyone,

I found the solution to my upgrade problem here:

https://www.prestashop.com/forums/topic/575178-ps-1702-one-click-upgrade-error-unable-to-check-md5-files/?p=2513375

It was a permissions problem with the autoupgrade.

Regards

Breda

[prestagas]

hi - i have installed the latest 1-clickupgrade 3.00 and the upgrade went OK. but now i cant see the module page.... maybe a module is corrupted.... les see it...