1.3.9h to current version upgrade

[DarkAngel]

I just want to confirm (yes I did read the upgrade and keep inof but...) that to do the upgrade from 1.3.9h to the current version I should do it like I did when the host is different from where store was.

1. back files to computer
2. back up database
3. upload new files to server either overwriting or after deleting the old ones
4. install as if new store
5. make sure it works and is accessible
6. reinstall all plugins with updated versions
7. droop tables in new database ( which has been created with the database name/db user and pass as before)
8. import table info from old DB

Then check again.

or should I do all of the above before installing all the plugins again.

[twitchtoo]

3. - please delete the old ones. You'll just get grey hair if you don't.

Be sure to run the DB upgrade from 1.39h to 1.51 with the ZC Installer

[DarkAngel]

Thanks Twitch, I usually delete all old files leaving only the override folders for the templates only but wanted to make sure I was gonna do the update right...have not done an actual update in centuries it seems.

do you think I should install the plugins after the entire other stuff is done?

[mc12345678]

Thanks Twitch, I usually delete all old files leaving only the override folders for the templates only but wanted to make sure I was gonna do the update right...have not done an actual update in centuries it seems.

do you think I should install the plugins after the entire other stuff is done?

Something that I'm not sure I properly read/understood was that your new store (upgrade) should happen all in a different directory/different directory, with functionality verified there before redirecting or moving the files to the old location. As for moving/updating the data, first suggest following the recommended directions: however, believe that the data could be updated in either way. I guess the important thing to note is that some plugins when updated may require different fields in the database than the earlier version. As a result if the tables are dropped after the plugin(s) are installed and the old database is imported (reformatting the tables to the old version(s), and then the plugin(s) are not again updated (SQL statements run as applicable) then the database will not be up-to-date with the most recent version. I thought one of the statements was to either upgrade your site or upgrade your plugins, not both at the same time. This statement leads me to think that your initial process description is incomplete as you may need to "update" your plugins again after the last check.

Regarding template/override files. It's "okay" to keep the override files, but you will want to compare the override file(s) to the base file(s) to update any changes made applicable to the newer version of the cart.

Make sense?

[DarkAngel]

Something that I'm not sure I properly read/understood was that your new store (upgrade) should happen all in a different directory/different directory, with functionality verified there before redirecting or moving the files to the old location. As for moving/updating the data, first suggest following the recommended directions: however, believe that the data could be updated in either way.

Yes that confused me too but I was hoping that I did not need to do that. I was just (since it is root level and not in a folder to begin with) going to make a landing page that said the store was in maintenance. While I demolish it by removing all store core files and leaving the template over-ride ones there.

IF it is essential to create the store in a new directory, then when done undo the config file paths I can do that too but I was just going to install the store as if it had never been installed, then change out the DB with the old one....as is I were moving it from one host to another, as I just did with another persons store.

I guess the important thing to note is that some plugins when updated may require different fields in the database than the earlier version. As a result if the tables are dropped after the plugin(s) are installed and the old database is imported (reformatting the tables to the old version(s), and then the plugin(s) are not again updated (SQL statements run as applicable) then the database will not be up-to-date with the most recent version. I thought one of the statements was to either upgrade your site or upgrade your plugins, not both at the same time. This statement leads me to think that your initial process description is incomplete as you may need to "update" your plugins again after the last check.

AHA that is just what I was trying to figure out....first do the upgrade then when done do the plugins as if it were a complete new store. I knew that ALL the plugins used now would need to be reinstalled with their newer version compatible with 1.5+

Regarding template/override files. It's "okay" to keep the override files, but you will want to compare the override file(s) to the base file(s) to update any changes made applicable to the newer version of the cart.

Make sense?

Totally, I know that this template is probably going to pitch a fit due to it being a template monster one from several years ago. Hoping he would like a new template too, there are many free ones here that can be edited to appear like his...or as close as possible. I did have to butcher it a bit to get somethings to work even in 1.3.9h soooo, I can most likely just add the files that match from the original store files. I shall see.

I am hoping that one of the more experienced helpers here would chime in here too....thanks for doing just that. I can usually follow instructions, especially if I write them down like in my post so I do not mess up---I tend to do things backwards at times, transposing when writing or doing steps plays havoc with ones mind...LOL

[DivaVocals]

I just want to confirm (yes I did read the upgrade and keep inof but...) that to do the upgrade from 1.3.9h to the current version I should do it like I did when the host is different from where store was.

1. back files to computer
2. back up database
3. upload new files to server either overwriting or after deleting the old ones
4. install as if new store
5. make sure it works and is accessible
6. reinstall all plugins with updated versions
7. droop tables in new database ( which has been created with the database name/db user and pass as before)
8. import table info from old DB

Then check again.

or should I do all of the above before installing all the plugins again.

NO NO NO.. none of this..

an upgrade is really a rebuild as DrByte says here: http://www.zen-cart.com/entry.php?3-How-do-I-rebuild-my-site-on-the-new-version-instead-of-upgrading

Well, an upgrade *is* basically a rebuild. At least, that's what I find to be the simplest approach to take when upgrading.

So here's the high level version of what you need to do

1. BACKUP EVERYTHING!!! (DB and files)
2. Create a development/test folder, and copy the Zen Cart v1.5.1 files there. Add to this ONLY your two configure files, along with your images, and downloads folders from your v1.3.9 backup.
3. Create a development database
4. dump your v1.3.9 DB into the development DB
5. Follow the normal UPGRADE install path. (in addition to the DB upgrade, there is an optionwhich will update your configure files to the new 1.5.x format. USE IT!)

Once the install is complete, then re-install all your add-ons.

This is the the most efficient way to do an upgrade, and will work without a hitch.. Folks run into problems because they are trying to find a shortcut.. Trust me when I say.. THIS IS the shortcut..

[frank18]

......This is the the most efficient way to do an upgrade, and will work without a hitch.. Folks run into problems because they are trying to find a shortcut.. Trust me when I say.. THIS IS the shortcut..

Absolutely!

Don't try it any other way, listen to those who have done it as recommended by Dr Byte! If you don't you invariably run into a brickwall

[DivaVocals]

Yes that confused me too but I was hoping that I did not need to do that. I was just (since it is root level and not in a folder to begin with) going to make a landing page that said the store was in maintenance. While I demolish it by removing all store core files and leaving the template over-ride ones there.

IF it is essential to create the store in a new directory, then when done undo the config file paths I can do that too but I was just going to install the store as if it had never been installed, then change out the DB with the old one....as is I were moving it from one host to another, as I just did with another persons store.

Why put the store out of commission while you upgrade?? Customers will go elsewhere and NEVER come back..

Unless there is a URGENT need (ie: site hack) to take the live site down for an upgrade, the RIGHT WAY to do this is to build a development/test store.. this way you can test things while the live store continues to live on.. (which is WHY DrByte and all the other experienced Zenners ADVOCATE for this method of development)

The SMARTEST way to do that is this:

a) keep your live store running, as-is. With its own admin. Its own database. Its own folder of files on the server. Everything as-is.

b) build your new store in a temporary location. THIS IS ONLY FOR TESTING AND PREPARING FOR LIVE DEPLOYMENT.
This separate testing area will use a complete copy of your live site, in another subdirectory of your site, AND another database.
This is done following the main upgrade procedure as described in steps a), b), c) above, and in more detail at this FAQ article: http://www.zen-cart.com/content.php?...-zen-cart-site

Hoping he would like a new template too, there are many free ones here that can be edited to appear like his...or as close as possible. I did have to butcher it a bit to get somethings to work even in 1.3.9h soooo, I can most likely just add the files that match from the original store files. I shall see.

So why not just build a NEW template that looks like the old one.. WHY keep messing with a template YOU KNOW to be problematic.. I can create a template that looks like ANY TEMPLATE from the Template Monstrosity folks.. I have said repeatedly that there is NOTHING special about their templates that cannot be recreated.. So if you know how, then DO IT..

I am hoping that one of the more experienced helpers here would chime in here too...

DING!!

[mc12345678]

Yes that confused me too but I was hoping that I did not need to do that. I was just (since it is root level and not in a folder to begin with) going to make a landing page that said the store was in maintenance. While I demolish it by removing all store core files and leaving the template over-ride ones there.

IF it is essential to create the store in a new directory, then when done undo the config file paths I can do that too but I was just going to install the store as if it had never been installed, then change out the DB with the old one....as is I were moving it from one host to another, as I just did with another persons store.





AHA that is just what I was trying to figure out....first do the upgrade then when done do the plugins as if it were a complete new store. I knew that ALL the plugins used now would need to be reinstalled with their newer version compatible with 1.5+






Totally, I know that this template is probably going to pitch a fit due to it being a template monster one from several years ago. Hoping he would like a new template too, there are many free ones here that can be edited to appear like his...or as close as possible. I did have to butcher it a bit to get somethings to work even in 1.3.9h soooo, I can most likely just add the files that match from the original store files. I shall see.

I am hoping that one of the more experienced helpers here would chime in here too....thanks for doing just that. I can usually follow instructions, especially if I write them down like in my post so I do not mess up---I tend to do things backwards at times, transposing when writing or doing steps plays havoc with ones mind...LOL

Only thing that jumps out at me in the moment is the plan to disassemble a functioning shop while the shop is being rebuilt and tested. That is time of lost reviews, sales, contacting, page checks by crawlers, etc... If lucky down for a few hours. If however, the site is built elsewhere (including offline) then the downtime can be reduced to a 15 mins or so while the files are being uploaded and verified in place. Naturally to also prepost that the site will be down for a designated period some point before (and while) the site is offline and being refreshed.

Better yet is to have both up, and simply. Redirect to the new site, then restore the old location to be. The new database and files, and thenundo the redirection. If done atright time, nearly seemless.

[DarkAngel]

NO NO NO.. none of this..

an upgrade is really a rebuild as DrByte says here: http://www.zen-cart.com/entry.php?3-How-do-I-rebuild-my-site-on-the-new-version-instead-of-upgrading



So here's the high level version of what you need to do

1. BACKUP EVERYTHING!!! (DB and files)
2. Create a development/test folder, and copy the Zen Cart v1.5.1 files there. Add to this ONLY your two configure files, along with your images, and downloads folders from your v1.3.9 backup.
3. Create a development database
4. dump your v1.3.9 DB into the development DB
5. Follow the normal UPGRADE install path. (in addition to the DB upgrade, there is an optionwhich will update your configure files to the new 1.5.x format. USE IT!)

Once the install is complete, then re-install all your add-ons.

This is the the most efficient way to do an upgrade, and will work without a hitch.. Folks run into problems because they are trying to find a shortcut.. Trust me when I say.. THIS IS the shortcut..

IN red: use the old store config files ? nothing downloads since his are physical deliveries

development database? not same name as old? but a totally new one. then just use the old DB without installing new store.

then use upgrade path in installer


so when I get all this done and it works like it should do I then change the path in the config files? since basically I will be removing all his old files --- which I will put the store in maintenance mode first so no sales while I get the other ready --- then do I do the update db again.

sorry flu meds make one feel and sound stoopid...LOL