1st time user - Confused on upgrade process

I was asked to upgrade a V1.3.9h website to the latest version. I am confused as to which folders/files need upgraded? The live website has several years of files and folders and they do not match the downloaded upgrade files. What folders and files are required for the upgrade?

I am familiar with WinMerge but because of the mass of files and different folder structures on the live site I haven't been able to figure out what needs changed as it relates to customization's, etc.

There will be a file change list in the docs folder of the new version, and you can search the FAQs here for upgrade for instructions.

stevesh:

There will be a file change list in the docs folder of the new version, and you can search the FAQs here for upgrade for instructions.

Thanks for the quick reply... but in the file change list is says: "**/admin/**some_file_name.php" yet there is NO /admin/ folder on the live site... or at the least I cannot find it. The folder names and structure are not identical.

RonThePartsGuy:

I am familiar with WinMerge but because of the mass of files and different folder structures on the live site I haven't been able to figure out what needs changed as it relates to customization's, etc.
Do a 3-way compare.
But ...
Since WinMerge can't do a 3-way comparison directly, start with a 2-way compare of the OLD ORIGINAL ZC files against your current files.
ie: original v1.3.9h files on one side, and your current site on the other side.
That'll show you all the changes made to your site. So now you know exactly what things you need to recreate in the new version.

You can then also optionally do another 2-way compare between original v1.3.9h files and the latest version files ... in both cases without any customizations. Just so you can see all the changes made to official code. That way you have a frame of reference if there's a customization that happens to clash somehow with core code changes.

If you had a 3-way compare program then you could do all of that at one time. http://www.zen-cart.com/wiki/index.php/Useful_Tools

RonThePartsGuy:

in the file change list is says: "**/admin/**some_file_name.php" yet there is NO /admin/ folder on the live site... or at the least I cannot find it. The folder names and structure are not identical.
Also, there shouldn't be an admin folder on the live site. You are required to change the name of that folder after installation.

stevesh:

Also, there shouldn't be an admin folder on the live site. You are required to change the name of that folder after installation.

This is helpful. Are there other folders/files that are supposed to be renamed on the live site after installation?

No, but he zc_install folder has to be deleted.

Using phpMyAdmin - Trying to restore the current database into the new database for the demo site and I get this error: /*!40000 ALTER TABLE 'XXX_orders_total` DISABLE KEYS */;

Trying to restore the current database into the new database for the demo site and I get this error: /*!40000 ALTER TABLE
Did you follow this for making the db backup?

http://www.zen-cart.com/content.php?144-how-can-i-do-a-site-backup-or-use-phpmyadmin-for-database-backup

kobra:

Did you follow this for making the db backup?

http://www.zen-cart.com/content.php?144-how-can-i-do-a-site-backup-or-use-phpmyadmin-for-database-backup

There are several databases on this server. How do I know which one is the currently used one? Is there a certain file on the live server that will tell me which database is being used?

RonThePartsGuy:

There are several databases on this server. How do I know which one is the currently used one? Is there a certain file on the live server that will tell me which database is being used?

I figured out which database was being used. I installed the latest version of ZenCart to my "demo" directory and it all works except I see the test data and not the real data. I told the setup process to use the live (backed up) version of the real sites database yet it still shows the demo data and the demo site layout/templates.

Look at the /includes/configure.php in the old site ... Find the DB_PREFIX value.
Then put that same DB_PREFIX value into both of the configure.php files on your test site.

DrByte:

Look at the /includes/configure.php in the old site ... Find the DB_PREFIX value.
Then put that same DB_PREFIX value into both of the configure.php files on your test site.I GOT AN ERROR: "WARNING: An Error occurred, please refresh the page and try again."

DrByte:

Look at the /includes/configure.php in the old site ... Find the DB_PREFIX value.
Then put that same DB_PREFIX value into both of the configure.php files on your test site.
You say "both of the configure.php files" - where are they?

root directory/ includes/ configure.php
root directory/ your_admin_name/ includes/ configure.php

Ok... starting day 2 on this upgrade. Why are there 2 configure.php files? What does each one do exactly?

RonThePartsGuy:

Ok... starting day 2 on this upgrade. Why are there 2 configure.php files? What does each one do exactly?

They are similar, but one is for the admin side, and one is for the storefront side.

DrByte:

They are similar, but one is for the admin side, and one is for the storefront side.
Since they are both named exactly the same and they weren't included in the upgrade zip file I assume they are created when setting up the site via the zc_install folder?

How do I tell which is which? I have them both open in my text editor and now I don't know which one goes where?

I figured out the configure.php issue.

Now the demo site says I need to upgrade the database and I follow the process to do such, but the Database Information -- Upgrade Sniffer is incorrectly sniffing the wrong database.

It says that the info is pulled from the configure.php settings but they are not what the configure.php settings say.

Where is the Database Information -- Upgrade Sniffer getting the database info from? More importantly how do I get it to upgrade the correct database and not the one is thinks it should upgrade?

zc_install reads the /includes/configure.php file, and pulls the DB_XXXXXX settings from there when responding to your request to attempt a db upgrade