50 replies to this topic

[OC2PS]

New version

1. What's new in 1.4.5.1?

A. A lot - check here

2. Will upgrading screw up my modules, themes, etc?

A. If you are running 1.4.x, then your modules, themes, etc should be fine as 1.4.5.1 is based off the same codebase. However, if you have modified any core files, these modifications are likely to be overwritten in the upgrade process.

Upgrade process

3. I am running version 1.3.x or 1.4.x at the moment. How do I upgrade?

A. Upgrading is simple; read instructions here or watch video here

But wait! You don't have to! PrestaShop has now released (thanks Michaël Marinetti) an autoupgrade module which will do all the work for you. You can download the module and check out the instructions here. While it has been released as a module to help legacy installations, from now on, autoupgrade will be a part of the core software.

Upgrading with Autoupgrade module

4. I am unable to install Autoupgrade module. What can I do?

A. First, try changing default language to English. Then uninstall and install the module again.

5. I have installed the module and started step 4 of Mike Kranzler's instructions. Selected “No” under "Shop Desactivated", but can't see “Enable Shop”!!

A. "Shop Desactivated" and “Enable Shop” are actually on 2 different pages. Selecting “No” under "Shop Desactivated" is designed to redirect you to the page where you find “Enable Shop”. If for any reason (e.g. if "Shop Desactivated" was already "No" in your shop) the redirect doesn't work, then go to Preferences tab, and you'll find “Enable Shop” right at the top.

6. I have finished step 5 of Mike's instructions, but do not see the "Upgrade Prestashop Now!" button.

A. That happens sometimes. Click "Click here to refresh" button (you will find it somewhere below "Last version is 1.4.5.1 final (1.4.5.1)").

7. Clicked "Upgrade Prestashop Now!" button, but getting error.

[Server Error] Status message : error

A. If you are using shared hosting like godaddy or 1and1, it is highly likely that this is caused because of a server timeout. In your hosting account root, find the php5.ini file and add/edit max_execution_time line so that it looks like:

max_execution_time = 300

To be sure, do the same in php.ini
You may need to wait up to 24 hours (depending on the time at which the host resets servers) for this to take effect.

If even 24 hours after making the above change, on hitting "Upgrade Prestashop Now!" you still get the same error, then in your PS files, change Line 29 in /config/config.inc.php from

@ini_set('display_errors', 'off');

to

@ini_set('display_errors', 'on');

Then open your Prestashop backoffice in Firefox.
Start Firebug (you'll need to have it already installed).
In Firebug, click Console Tab, then Errors subtab
Then in your PS backoffice, hit "Upgrade Prestashop Now!" again.
Take a screenshot of the errors (e.g. with Windows 7 Snipping Tool) and save the image
Send this screenshot to US Community Manager Mike Kranzler - he will be happy to help

8. I am getting an error during backup.

error during backupDB

A. If you have cache (memcache or filesystem cache) enabled (BackOffice > Preferences > Performace), please disable it and try again.

9. I am having problems with blocklayered module after completing upgrade!

A. Go to BackOffice > Preferences > Performace
Disable cache (at the bottom of the page)
Disable Force Compile (at top of the page)

10. I installed the Autoupdate module fine, but I don't see the Tools > Upgrade tab that I am supposed to go to.

You are probably using an old version of PS...there was a bug with displaying tabs. In the URL, next to your PS base, add /admin/index.php?tab=AdminSelfUpgrade (replace /admin/ with whatever you have renamed admin folder to). This should take you directly to the upgrade page.


If you are running 1.4.x then it's probably a permission issue. To fix this:
Go in Employee > Tabs and check if the tab "Upgrade" is created. If yes, then delete it. Then, create a new employee:
name : Upgrade
class : AdminSelfUpgrade
module : autoupgrade
parent: Tools

The tab should now appear when you go on tab Tools

11. The process stop when "backupFiles" immediately. How to fix that ?

Your php configuration does not have the "ZipArchive" extension, and the module need it for backup files. This will be fixed in a future release of that module.

12. The process stop when "unzip". How to fix that ?

This can be a write permission problem. Please check the user which runs apache has proper rights to all your admin/autoupgrade/ directory.

[Michaël Marinetti]

Thanks you very much OC2PS !

We will probably edit it when new question and answers cames

[Carl Favre]

Really great post OC2PS.

I pinned it.

Thanks.

[Mike Kranzler]

Thanks OC2PS!

-Mike

[soroosh]

I have problem with auto update:
I face with suspended "Currently processing : I'm waiting for your command, sir" message.
After updating the AdminUpgrade.php file (with commenting line:1117) I faced with suspended :
Currently processing :

All sample files removed. Now backup files.
message!

[Mike Kranzler]

Hi soroosh,
Can you please post a screenshot of the error you're encountering?

-Mike

[soroosh]

Hi Mike
Actually this is not an error.
But is an stop point for the upgrade progress.
Screen shot attached.

Attached Files

•  Untitled-1.jpg   191.23K   123 downloads

[Mike Kranzler]

Hi soroosh,
Do you get any message or warning, or anything that would tell you that the upgrade has failed?

-Mike

[soroosh]

Mike Kranzler, on 18 October 2011 - 07:51 PM, said:

Hi soroosh,
Do you get any message or warning, or anything that would tell you that the upgrade has failed?

-Mike

No, I don't get any message or warning. Just freeze with this message:

Currently processing :

All sample files removed. Now backup files.

[Mike Kranzler]

Hi soroosh,
It is possible that this is an issue with your server speed and timeout settings. If you have access to the file php5.ini in your root directory, please try changing max_execution_time from 30 to 300 and see if that solves it for you. If you don't have access to this, please ask your hosting provider to do this for you.

I hope this helps.

-Mike

[soroosh]

I asked from hosting support about the max_execution_time and they said that it sets on 300 but the problem exists.

Is there anyway to upgrade 1.4.4.1 to 1.4.5.1 manually without losing data and customizations?

[OC2PS]

[trendbutiker.se]

Hi. Just want to say thanks for this upgrade module. It worked like a charm for me:-).. Just upgraded from 1.4.4.1 to 1.4.5.1

//Daniel

[soroosh]

But for unknown reasons I had to upgrade it manually

[Mike Kranzler]

soroosh, on 21 October 2011 - 11:01 AM, said:

But for unknown reasons I had to upgrade it manually

Hi soroosh,
I'm sorry to hear that the autoupgrade module didn't work properly for you, but can you confirm that you were successful in upgrading manually?

-Mike

[soroosh]

Hi Mike
Yes, I could successfully upgrade it manually!

[Mike Kranzler]

soroosh, on 21 October 2011 - 03:19 PM, said:

Hi Mike
Yes, I could successfully upgrade it manually!

Great! I'm glad that you were able to upgrade. Enjoy 1.4.5!!

-Mike

[Crisplant]

After upgrade, i found that error:


The following module(s) couldn't be loaded:

• All modules cannot be loaded due to memory limit restriction reason, please increase your memory_limit value on your server configuration

What it could be?

[Mike Kranzler]

Hi Crisplant,
In this situation, you will want to call your hosting provider and ask them to increase your memory limit. Just explain this situation to them and they should be able to take care of that for you pretty easily.

-Mike

[David @ gfe.]

Hi, I am getting the following error/warning after auto upgrade on payment tab options page (Back End) after installation:

The following module(s) couldn't be loaded:

• All modules cannot be loaded due to memory limit restriction reason, please increase your memory_limit value on your server configuration

I am alos unable to access translations.

I have "SetEnv PHPRC /home/gamesfro/public_html" in my htaccess and I have a php.ini file (permission 644) which reads:

upload_max_filesize = 128M
post_max_size = 128M
memory_limit = 128M
suhosin.post.max_vars = 6400
suhosin.request.max_vars = 6400

What else do I need to do?