Upgrading from 1.4.7 to 1.6

[NNGNews]

Hello,
Soon we are going to do an upgrade to version 1.6
Currently we are on an old version (1.4.7.0) and we would like to move to the more recent (hopefully stable) 1.6.xx version
We know that we will lose any our customization, but the real question is, it could be done with the Autoupgrade module or it will be a mess ?
And what shall we do to avoid losing the data?
If we make a back-up of the Database, then it would be restorable on the new DB 1.6 or is it a massacre  ?
If someone has already gone through this "adventure" can help us?
 
thank you

PS

Sorry for english gramma mistakes

 

___________________________

http://www.kissene.com/en

[bellini13]

Do not attempt to perform an upgrade to your live production store...

 

You should first make a copy of your store, either on your local computer using WAMP, or in a subfolder on your web host.  Make sure this test store works properly, and then perform the upgrade only to this test store, using either auto or manual method.

 

Then test the hell out of the test store, be sure to test things your customers would do to ensure that everything is working properly.  Make sure you document all the steps you performed, any changes you had to make.

 

Only after you are satisfied that it works properly, take FULL BACKUPS of your live production store (web and database), and then proceed to upgrade the store following the exact same steps that you documented above.

 

And if you are looking for a professional to perform the upgrade for you, feel free to send me a PM

[asgllccb]

Still going through the "adventure". I am using a backup and testing on a wamp server.  You will loose connection with images but there is good information around in the forums to fix this.  I also made a copy of my images folder after the backup and before moving them so I could replace them when I had errors.  I put instructions in the forums for this too.  Just search the forums for fixing image problems when you get there.  I also lost my sign in option in the front end and lost some hooks and customer account module functioning and have found really no help thus far on resolving those problems for my test yet with upgrade to any of the 1.6 versions yet.  In your test update, make sure you are taking notes and copying links to any solutions you find for your test so you can easily repeat when you update your live.

[NNGNews]

What a mess ... all of you are scaring me 

[bellini13]

What a mess ... all of you are scaring me 

thats a good thing, upgrading a store is not a 'simple' process, and I don't recommend performing an upgrade unless you have experience and can successfully repeat the upgrade process on test sites. 

 

It's a 'mess' because inexperienced people perform complex processes, and things go wrong and they do not have the experience to correct it.

[asgllccb]

While I get what and agree with your very valid point bellini13.  It is a realistic fact of using prestashop.  However, from a consumer standpoint...prestashop markets it self with and like programs that require very little experience, which is why so many inexperienced people decide to try it and then get frustrated and leave, because too often users feel like it is not living up to how it is marketed.  However, I do agree that prestashop has provided plenty of warnings, cautions and instructions about key things to help reduce inexperienced user errors, which too many people overlook or ignore.  Even then though, there are too many errors.  I have never used anything but original prestashop software with no adaptations, including no non-native themes or modules, etc and my updates, operating exactly as instructed, have never worked straight up.  Most explanations for errors in updates are written off as associated with modifications, non native modules or themes, etc.  The only things that has ever worked straight up as instructed has been a fresh install.  I would love to be a tester for the upgrade but that hasn't ever seemed to be an option.  But that is also another topic.  I think everyone wants to be a happy prestashop updater.  

[asgllccb]

Helpful hint: Aside from the regular backup and do tests on a copy of the backup first (you will likely deal repeatedly with problems with some resolution and others with none and messing things up, so having to take notes on what works and restore the backup copy and rework things with the copy to resolution of all problems, again taking notes along the way) until you know how to resolve problems you face.  Then you will probably be more ok with updating your system and using your notes to get everything set right.

 

Though you can deal with images after the update, I found it makes things easier to move images and turn off legacy before you update, though it is not necessary to regenerate images if you do not change the size or settings.  

 

I lost the sign in function after update but later an update for the module showed up.  I did the update, then reset it, cleared cache and set prestashop to force recompile to get the sign in to work.

 

Though I am not done testing yet (1.5 months), so far I have been able to go straight from 1.4.4.1 to 1.6.0.8 on my tests.  Fingers crossed.

 

Hope this helps.

[NNGNews]

Thanks, you are very kind, all yours tips are useful, although it seems a very hard work to go through.

We have more doubts than before after these posts

 

 

_______________________

http://www.kissene.com/en/

[NNGNews]

Here we are, after some months we are ready to upgrade.

Two questions :

Is the 1.6 available in download a stable version or it's better 1.5 ?

The upgrade from 1.4.7 to 1.6 (or 1.5) could be done with the Autoupgrade module or it's better do it "manually" ?

 

Any other suggestion is welcome 

 

______________________________

http://www.kissene.com/en

[NNGNews]

We're starting upgrade in test.

First of all, we have this problem.

When the 1click-upgrade module does the checklist we have

"The mobile theme is disabled" with the red X

we don't know what to do.

The 1.4.7 version doesn't have a mobile theme by default , we have only installed recently the "Mobile template v0.5.3" but it seems ok.

What we must do to erase the red X ?

Thank you

 

____________________________

http://www.kissene.com/en

[NNGNews]

It's a bloody mess !

Hope someone could give us some tips.

 

We are trying to upgrading from 1.4.7 to 1.6 on local servere (wamp)

After some corrections, and after the procedure have done the DB and folders backup, we saw that the files update seems done but as soon as it tries to update the Database we have this error in the file mysql.log :

 [ERROR] wampmysqld: Can't find file: '.\dbname\ps__module@000a@0009@0009where@0020name@003d@[email protected]' (errno: 22)

 

what does it mean ?

We understand that a file is not find, but which file and why ?

 

Thanks

[mattheoh]

Trying to upgrade from 1.4.11 to 1.6.0.14 (also with in local with WAMP).

And I have exactly the same error as you !

2015-03-20 10:56:14 336 [ERROR] wampmysqld64: Can't find file: '.\dbpresta16014\ps__module@000a@0009@0009where@0020name@003d@[email protected]' (errno: 22 - Invalid argument)

This error makes that the db upgrade always fails (Time Out cause of max execution time, despite it is very huge at 120000 seconds).

I m not an expert but I think it's about the field "name" in the table ps_module, with the value blockcms.

I m going to try to disable this module before upgrading.

Edited March 21, 2015 by mattheoh (see edit history)

[mattheoh]

Tried by disabling the module.Still the same result :-(

I think this error is generated by this php file : install/upgrade/upgrade_cms_15.php (line 44)

Edited March 22, 2015 by mattheoh (see edit history)

[mattheoh]

Managed to do it by modifying AdminSelfUpgrade.php.

In fact the Ajax request timeout was too short... (3600 sec)

I had to increase it to avoid max execution time message.

[dviprod]

Managed to do it by modifying AdminSelfUpgrade.php.

In fact the Ajax request timeout was too short... (3600 sec)

I had to increase it to avoid max execution time message.

Hi,

I have the exact same error :

2015-08-25 14:37:14 7288 [ERROR] wampmysqld: Can't find file: '.\shop\_module@000a@0009@0009where@0020name@003d@[email protected]' (errno: 22 - Invalid argument)

 

I changed max_execution_time in php.ini to a very large value 120000, but I still get the same error.

 

Can you tell me how you modified AdminSelfUpgrade.php to get it right?

Thanks!