Upgrading 1.4.7 To Anything?

[tdr170]

What a nightmare this day has been.

 

First my online shop is still a 1.4.7 version for many reason but I want to upgrade to 1.5 as I have solved the issues I had with upgrading mainly taxes.

So today I tried the upgrade to 1.5.6 and had errors with modules not updating here is a snippet of the error massage.

 

(note: I uploaded to a test folder not my actual store)

 

[ERROR] error on extract using pclzip : PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature

[WARNING] error when trying to upgrade module canadapost.

using class ZipArchive ...

 

However the modules mentioned were not ones I really used to left the upgrade alone and started looking through the BO and FO.

None of the images in the FO showed and regenerating did not help, I then moved the images to the new file storage and changed the legacy option regenerated again and now the images show.

I then tried to log in and authentication did not work, when you filled in your info and clicked login nothing happened. I did some research and found no solution so I started over deleted the install and cleared the database.

 

So now I decide to update to 1.4.11.0 first to see if that would help but kept getting this error.

 

 Ajax / Server Error] textStatus: "error" errorThrown:"" jqXHR: ""

 

After many attempts and having to upload files and folders again that the upgrade had deleted I decided to try a different approach and uploaded the 1.4.11.0 file to the Admin/autoupgrade/dowmload folder and chose local archive this time the error was that the file could not be unzipped I unzipped the file on my pc no issues.

 

So once again I decided to try the upgrade to 1.5.6 and that went through with issues with the exception of the module upgrades noted above but the same issue exist in that you can not login to the FO.

 

So it seems as the latest ONE CLICK UPGRADE MODULE does not work for upgrading 1.4xx to 1.4xxx.

 

I am not sure how to fix the Authentication issue if anyone has an idea or has seen these errors please post something.

 

Next I am going to do a manual upgrade to 1.4.11.0 and see if that helps.

 

One other option I am toying with is to do a fresh 1.5.6 install and then use the database tables from the database I backed up before clearing it, for customers, products and so on to populate the database then upload all my images to the install and hope that authentication will work.

 

 

 

[PascalVG]

Hi Tdr,

 

About the login, try this:

http://www.inmotionhosting.com/support/edu/prestashop-15/308-password-change-via-database

 

This may get you back into the BO of your shop, I hope.

 

About the last problem you describe, the database you use to 'recover' your customers, products etc is probably not version 1.5.6, so I expect the tables not to be identical as your old version, so replacing the 1.5.6 ones for these is for these table not always an option. You might try to insert them into the new ones, by copying the correct fields to the matching fields in the new tables

for example:

Say a table ps_products has field

id_product, oldfield1,oldfield2, newfield1

Where newfield1 is a new field for this table, which wasn't there in the old table version

 

replacing them with the old table directly:

id, oldfield1, oldfield2 table will give problems as newfield1 is being used in the new PS version and wouldn't be there when replaced with the old one.

 

Inserting them using SQL could help you here:

 

1) Create a table pd_products_old in the new database and add all fields from the old table in here.

then use some SQL statement like this

INSERT INTO PS_products  (id_product, oldfield1, oldfield2,newfield1) VALUES (`ps_products_old`.id_product, `ps_products_old`.oldfield1, `ps_products_old`.oldfield2, `ps_products_old`.newfield1, null) WHERE 1

 

or so. Maybe null should be replaced by 0 or another fitting default value.

It's just an example, the real fields should be checked in the tables themselves...

(Always make a backup of your database before using SQL on it. An error is easily made!

 

About error:

 Ajax / Server Error] textStatus: "error" errorThrown:"" jqXHR: ""

 

I've seen this one a few times and always could fix it by cleaning cache and cookies for your domain.

 

Hope this helps a little,

pascal

[tdr170]

Thanks for the reply, the problem is not the BO login but the customer login in the Shop.

For the database I backed up the 1.5.6 upgrade database before deleting the install so the tables should work to populate customers products, images and so on.

I am trying the fresh install of 1.5.6 with the tables from the backed up database from the upgraded 1.5.6 and see if the FO log in will work.

There were other issues with the upgrade in the FO, the authentication page had some strange css, the left block create account looked okay with the exception of the button being out of place was against the border to the right and bottom (no padding) and the right block had the same issue and the header had no background. (not terrible as I was able to fix with css).

[doekia]

Providing a link to your shop and activating debug mode can dramatically helps figuring out what goes wrong.

I have done numerous migration using 1 clic upgrade w/o any error

When error surface this is usually caused by a module (even a Prestashop certified one) that does not properly upgrade or is not compatable (ex: mailalerts)

[tdr170]

 I to have vast numbers of installs and upgrades usually without issue, that is why I poted this here to get other opinions as sometimes we don't think of everything.

No need to give link as this is only a test site and not a live site.

I tried the upgrade many times and with different scenarios, with all modules from 1.4, removing all added modules before upgrade, the upgrade would fail every time when trying to upgrade to 1.4.11 first but would upgrade every time when going to 1.5.6, some times with errors on upgrading modules, when modules removed upgrade was OK but still the FO login issue remained. 

Edited December 7, 2013 by tdr170 (see edit history)

[doekia]

Firebug on the ajax call during login might point out the culprit.

Amongst possible cause it could be dos encoded files, BOM marker on files ... etc (those also are the cause of cookie/cart misbehaviour)

[tdr170]

Now have a working 1.5.6 test shop, the only way I was able to achieve this was to do a fresh install then and use the back up database from the upgrade so as to not have to input all 800+ products again.

I then uploaded all the my images and regenerated them and they all appear in FO.

The Log In works as expected and at this point all seems fine.

[PascalVG]

Hmm, that wasn't as easy as 1-click indeed...

Just for completeness sake, how and to where exactly did you upload your images to make it work?

 

Thanks,

pascal

[tdr170]

I uploaded the images to the standard img folder, I only uploaded the folders within that I had images in, /c, /m, /p, I did not load the /s (shipping) as I started from fresh with that.

As far as the Theme images go I just loaded them fresh from the Themes page.

I then changed the option for Images to use the legacy image storage and then regenerated all the images and all was well.

Seems as the newer versions have changed to the new image storage filesystem and regenerating images with the option set to NO for use legacy does not regenerate the images.

You can move the images then regenerate and that also seems to work.

 

I have been modifying the template to a 2 column and changing options in the BO and at this point all seems to be working well.

 

I still wonder about the One Click compatibility with older versions upgrading to something other then the latest version.

As I stated did not seem to work for upgrading 1.4.7 to 1.4.11, someone suggested that I upgrade to that before 1.5.6 but that does not seem possible at least not automatically.