Manual Upgrade Error 34 From V1.4.10.0 To V1.6.1.4

[darvidc]

Hi,

 

I'm testing an manuall upgrade from v1.4.10.0 to v1.6.1.4 (because I want a cleaner install afterwards) by following the recommended upgrade instructions given in PSs documentation.

 

The upgrade script (upgrade.php) works fine, with the except of 1 error (indicated by an error 34 at the top of the returned XML text). Ive isolated the error in the returned XML text, se below (in red).

 

It seems to be a SQL call to ALTER and DROP a KEY "id_shop_group" in the newly created table "shop" that gives the error, that it can't be found ???

 

The strange thing also is that the next call the very same table is adressed again, this time to ADD the same KEY, without an error (in green)   ?

<request result="fail" sqlfile="1.6.1.0">
<sqlQuery>
<![CDATA[ ALTER TABLE `amu_shop` DROP KEY `id_shop_group` ]]>
</sqlQuery>
<sqlMsgError>
<![CDATA[
Can't DROP 'id_shop_group'; check that column/key exists]]>
</sqlMsgError>
<sqlNumberError>
<![CDATA[ 1091 ]]>
</sqlNumberError>
</request>

<request result="ok" sqlfile="1.6.1.0">
<sqlQuery>
<![CDATA[
ALTER TABLE `amu_shop` ADD KEY `id_shop_group` (`id_shop_group`, `deleted`)]]>
</sqlQuery>
</request>

 

I should say the shop seem to work perfectly after the upgrade ...

Any ideas anybody? Is this a bug? Can this be found and corrected in the script somewhere?

Do I even need to worry about it?

 

Thanks in advance.

David C
 

[El Patron]

often times when I do upgrade on 1.4, I' ve found upgrading to latest 1.4.1.11 then upgrading to 1.6 to be easier path with less or no errors along the way.  This can be done by clicking advanced settings in one click upgrade.

[darvidc]

Ok, thanks for your reply.

 

Where aiming to upgrade the "live" shop soon, so "downtime" is important and I would like to avoid adding more downtime by waiting for an extra step to complete but as you say maybe to get a clean upgrade I would have to upgrade to 1.4.1.11 first.

 

This is why I asked if the error above is significant, as is seems to overwrite/correct itself and we aren't using multi-shops anyway, which I presume is what that particular DB table is for. Correct me if I'm wrong but I've a feeling, as the shops seems to work correctly after the manual upgrade, I think I can ignore the error, or am I wrong?

 

BTW. Why is 1.4.1.11 so much better than 1.4.1.10, I've heard this from some where before? Can an "1-click Upgrade" to 1.4.1.11 be done with the minimal of worry then?

 

David C

[El Patron]

David, yes 1.4.1.11 rocked (in the day) lol

 

My opinion?   1.6.09 and 1.6.1.0 rock, 1.6.1.4 would  be goal to achieve or at min. 1.6.1.0.

 

as for down time, you should be doing this to a test copy,  them move that to production,  hardly any downtime at all.  You really only need then to sync the new cust/orders since db capture.  The time is not so much spent on upgrade but modules (getting upgraded modules if you have any 3rd party and configuring compliant theme)...

[darvidc]

El,

 

The situation is that we have a live site, with around 3000 articles (inc. variations) and over 20,000 customers registered, so as you understand I have to get this right :-) .

 

I'm doing all of my testing on a VPS, in fact the server will most properly be the server we move to when it's time (by re-pointing the DNS to their name servers etc.) so your suggestions of using a test server before are really what I am doing all the time now ;-)

 

What I will do tomorrow, is try, on the test server to upgrade from 10 to 11 and if it looks good, to save time, (I'll do backups first) do the same minor upgrade on the Live site! If it works on the test site, can you see any risk in that? (I have done minor upgrades before and they seem to have worked Ok)

 

If that then works I'm left with a 11 ready for the major upgrade to 1.6.x. when its time. :-)

 

The main thing here is to get a so clean major upgrade as possible (free from all the accumulated custom changes that have been made and modules that will no longer be used) that's why I've chosen the manual upgrade over the automatic "1-click Upgrade" I can keep it cleaner and then later remove unnecessary tables from the database.

 

I must admit I'm still indecisive about whether to use an upgrade or a clean install of v1.6.x and then csv. import all the necessary order, product, customer info. etc? The only reason I haven't tested that yet is because I haven't found any good modules or good instructions to do that way! If you know of such a solution I would appreciate it, if you could point me in the right direction too.

 

Thanks

David C

 

 

[El Patron]

Use one click upgrade whenever possible for best results.