Elaboration please for ugrade procedure

[shags38]

Hello - I am about to upgrade from v1.3.9h to v1.5.4 and have been reading the article by Dr Byte, "How do I rebuild my site on the new version, instead of upgrading?" (http://www.zen-cart.com/entry.php?3-...d-of-upgrading) and am OK with steps A & B but being a dummy I am uncertain about step C.

The 'new' v1.5.4 site has a database created for it as part of the installation process which will have data from the core ZC files, and the plugins I will load as per step B. So step C below - I would be upgrading the database to the 'new' version from the 'old' (existing) version I take it? So I use the zc_install script on the 'new' site, right? How does it locate the database from the 'old' site to be able to import it? I tried this a few weeks back when attempting my first upgrade and there was nowhere for me to select 'add this database' or similar, just a selection of upgrading from 1.3.2 to 1.3.5 etc, etc. - totally confused.

I thought maybe this step was done on the 'old' (existing) site after the 'new' site files were copied into it but data like products etc would need to be in the 'new' site to be able to test it, right?

cheers, Mike


c) upgrade the database to the new version
The zc_install script is used to do this in an automated way. Just a couple clicks to take care of keeping all your data intact and bringing its data structure up-to-date to work with the new version.

And of course, doing all of this in a TEST COPY of your site first, not on your live site directly, lets you ensure that everything is working and nothing is missed, before putting it all onto the live site. This way, when it comes time to actually touch your live site, you can do it in just a few minutes instead of potentially having your store down for much longer while testing/checking addons and customizations, etc.

[DrByte]

Preface: The following comments assume the reader is following the process I outlined at http://www.zen-cart.com/entry.php?3-...d-of-upgrading
(just pointing that out so that my comments about "upgrade the live site" in the next paragraphs are not taken out of context)

To be clear: This is assuming you have FIRST made a TEST SITE using the new version and imported the old database to it for testing .... all in a temporary testing/staging area someplace separate from your live site.
That's the only "database import" you do.

Then to "go live", you don't have to import any database data, because your "go live" steps will be done ON THE LIVE SITE, because at this point it is assumed you've already tested all the PHP code changes, etc on your TEST SITE.

Summary:
- first, backup the live site, for safekeeping
- make a temporary test site, and test all your mods, changes, merges, customizations, plugins, etc ... TAKING NOTES OF EVERY STEP REQUIRED TO RE-DO THEM ALL ON THE LIVE SITE
- then go to the live site and update all the PHP files, upgrade the database using zc_install, reconfigure all mods/plugins as per your detailed handwritten notes (and be sure to delete any obsolete files from your server too)

[shags38]

Preface: The following comments assume the reader is following the process I outlined at http://www.zen-cart.com/entry.php?3-...d-of-upgrading
(just pointing that out so that my comments about "upgrade the live site" in the next paragraphs are not taken out of context)

To be clear: This is assuming you have FIRST made a TEST SITE using the new version and imported the old database to it for testing .... all in a temporary testing/staging area someplace separate from your live site.
That's the only "database import" you do.

Then to "go live", you don't have to import any database data, because your "go live" steps will be done ON THE LIVE SITE, because at this point it is assumed you've already tested all the PHP code changes, etc on your TEST SITE.

Summary:
- first, backup the live site, for safekeeping
- make a temporary test site, and test all your mods, changes, merges, customizations, plugins, etc ... TAKING NOTES OF EVERY STEP REQUIRED TO RE-DO THEM ALL ON THE LIVE SITE
- then go to the live site and update all the PHP files, upgrade the database using zc_install, reconfigure all mods/plugins as per your detailed handwritten notes (and be sure to delete any obsolete files from your server too)

Hi Doc, this was the part that was missing from the article "and import(ed) the old database to it for testing" "That's the only "database import" you do." Probably goes without saying but didn't want to assume anything - import via phpMyAdmin.

many thanks, Mike

[mc12345678]

Hello - I am about to upgrade from v1.3.9h to v1.5.4 and have been reading the article by Dr Byte, "How do I rebuild my site on the new version, instead of upgrading?" (http://www.zen-cart.com/entry.php?3-...d-of-upgrading) and am OK with steps A & B but being a dummy I am uncertain about step C.

The 'new' v1.5.4 site has a database created for it as part of the installation process which will have data from the core ZC files, and the plugins I will load as per step B. So step C below - I would be upgrading the database to the 'new' version from the 'old' (existing) version I take it? So I use the zc_install script on the 'new' site, right? How does it locate the database from the 'old' site to be able to import it? I tried this a few weeks back when attempting my first upgrade and there was nowhere for me to select 'add this database' or similar, just a selection of upgrading from 1.3.2 to 1.3.5 etc, etc. - totally confused.

I thought maybe this step was done on the 'old' (existing) site after the 'new' site files were copied into it but data like products etc would need to be in the 'new' site to be able to test it, right?

cheers, Mike


c) upgrade the database to the new version
The zc_install script is used to do this in an automated way. Just a couple clicks to take care of keeping all your data intact and bringing its data structure up-to-date to work with the new version.

And of course, doing all of this in a TEST COPY of your site first, not on your live site directly, lets you ensure that everything is working and nothing is missed, before putting it all onto the live site. This way, when it comes time to actually touch your live site, you can do it in just a few minutes instead of potentially having your store down for much longer while testing/checking addons and customizations, etc.

Okay, so questions similar to this get asked time and again...

One thing about all of the instructions provided is that there is a bit of an expectation of some "basic" (not necessarily basic/everyone knows kind of thing, but let's say that there are aspects about site setup that are not considered the responsibility of the core ZenCart instruction) internet/website/database operations. That said, there are plenty of people that are willing to help when asked... (This includes those of the core ZC team which I am not a part of, but I certainly do not wish it to seem that help is not available.)

So, the guide in general is not detailed to cover every caveat and aspect of how to perform the upgrade/process; however, provides enough guidance to identify the type of action to be performed. Take a look at the expanded instruction (FAQ) that follows in section 3. (http://www.zen-cart.com/content.php?...-zen-cart-site) When preparing the temporary/development site to contain recently live data, the data must be pushed into the new database after the new database/applicable table(s) have been cleared (dropped). Be sure that the temporary site when "installed" uses the same DB_PREFIX as your existing site. (Simply makes the full process easier if that is done up front.)

The zc_install process will upgrade (attempt to upgrade) the database that is referenced in the includes/configure.php file where the includes folder is in the same folder as the zc_install folder. The database upgrade action portion of the instruction does not require modification of any file(s) so there is no reason to make/force any files to be writeable. When presented, simply select the upgrade database only option and if the database has a need to be upgraded (ie older database) then, allow it to do its thing.

Help any? Regardless keep the question(s) coming as necessary.

[shags38]

Okay, so questions similar to this get asked time and again...

One thing about all of the instructions provided is that there is a bit of an expectation of some "basic" (not necessarily basic/everyone knows kind of thing, but let's say that there are aspects about site setup that are not considered the responsibility of the core ZenCart instruction) internet/website/database operations. That said, there are plenty of people that are willing to help when asked... (This includes those of the core ZC team which I am not a part of, but I certainly do not wish it to seem that help is not available.)

So, the guide in general is not detailed to cover every caveat and aspect of how to perform the upgrade/process; however, provides enough guidance to identify the type of action to be performed. Take a look at the expanded instruction (FAQ) that follows in section 3. (http://www.zen-cart.com/content.php?...-zen-cart-site) When preparing the temporary/development site to contain recently live data, the data must be pushed into the new database after the new database/applicable table(s) have been cleared (dropped). Be sure that the temporary site when "installed" uses the same DB_PREFIX as your existing site. (Simply makes the full process easier if that is done up front.)

The zc_install process will upgrade (attempt to upgrade) the database that is referenced in the includes/configure.php file where the includes folder is in the same folder as the zc_install folder. The database upgrade action portion of the instruction does not require modification of any file(s) so there is no reason to make/force any files to be writeable. When presented, simply select the upgrade database only option and if the database has a need to be upgraded (ie older database) then, allow it to do its thing.

Help any? Regardless keep the question(s) coming as necessary.

Thanks for the information - helps a lot in the understanding of processes.

cheer, Mike

[frank18]

After many upgrades (starting back with 1.3.7.1) over the years I have developed my own upgrade prodecure.

I have identical copies of all my live sites (fully operational) on my local dev server (using the Linux LAMP stack).

My first step is to download another copy of the live file system which I am zipping up for safe keeping. At this stage I am not backing up the live DB as I am keeping the live site operational taking orders.

Then I am upgrading/merging the local file system - including addition of new files, plugins and deletion of obsolete files. I am using Beyond Compare for this. The only tedious part is to add any changes in the template_default files into the corresponding my_template files.

When I am done with this I add the zc-install folder into the upgraded local file system, make the 2 configure.php files writeable and then run mystore.com/zc_install and select DB upgrade. Let it run it's course..... set the 2 configure.php files back to 444 and rename the admin folder back to my_secret_admin, delete the zc_install folder and attempt to log into admin. If all went well I can now test the upgraded clone store including all installed plugins. Sometimes it will be necessary to make changes to the installed plugins files..... so note taking is necessary to apply these changes later to the live site. The local logs folder is closely watched.

Once I am happy that all is well locally, the live site goes into maintenance mode and I download a backup of the live DB and add it to my zipped backup I made earlier. If anything goes wrong I have a fully intact backup of the live site and can roll back (never needed it).

That just leaves me with uploading all local files to the live server, delete obsolete files and then run zc_install on the live site to upgrade the DB (ofc the 2 configure.php files are set to writeable at this stage and the secret_admin folder is renamed to admin). Then delete the zc_install folder, rename the admin and set the 2 configure.php files back to 444. Test and apply the plugins changes (if necessary), test again including doing a test order as customer. If all goes well then the live site is back up and running in no time. At this stage I also completely clear the logs folder so I have a fresh start for monitoring the functionality of the live site. I check the logs daily for a few days and make corrections to affected files if necessary.

Principally this is the same procedure as recommended here - just a few short cuts. The method has never failed me on all the sites I upgraded in the past.

Cheers / Frank

[shags38]

Thanks Frank - I will try the standard procedure first on one site then I will try your method on another site.
Cheers, Mike

[mc12345678]

Btw, although it may be "routine" to do, a database upgrade only does not require renaming the admin nor making the configure.php files writeable. If anything it makes it easier to accidentally wipe the database if the upgrade only option is not selected. But basically it is non-essential as there is no file modification necessary for a database only upgrade.