Originally Posted by
schoolboy
I'm trying to make sense out of your descriptions of what you have done, but I can't seem to follow exactly what you've done.
It looks like you are trying to do two things:
1. UPGRADE your site.
2. MOVE your site.
UPGRADING should be done before a MOVE (if possible).
UPGRADING involves two fundamental processes:
i) Upgrading FILES
ii) Upgrading the DATABASE
On the FILES side of this procedure, you will have what are known as CORE FILES, and (if you have set up your zencart correctly) some CUSTOM FILES.
CORE FILES are the set of DEFAULT files that make a standard installation of zencart operative.
The CUSTOM FILES will be those that apply to your specific template, and in a lot of cases, will be customised files that relate to certain add-ons that you may have installed. Such CUSTOM FILES can be EXTRA FILES... or they can be MODIFICATIONS OF CORE FILES.
Regardless of whether they are EXTRA or EDITED COPIES OF CORE files, every one of these CUSTOM files should be checked for compatibility with their CORE COUNTERPART(s) in the upgrade version.
Let me give you an example, assuming your site is in English...
Your MAIN LANGUAGE FILE is called "english.php"
When you install zencart for the first time, it will load this file into the following location:
public_html/includes/languages/english.php
But you decide that there are some things in that language file that need changing, so you make a COPY of it, then EDIT that copy, and then send that copy to its OVER-RIDE folder:
public_html/includes/languages/THE_CUSTOM-FOLDER/english.php
The CORE file remains where it is, and is NEVER EDITED.
Now... you have TWO main language files:
(CORE) public_html/includes/languages/english.php
(CUSTOM) public_html/includes/languages/THE_CUSTOM-FOLDER/english.php
Zencart always looks for a CUSTOM FILE first. if it finds the custom file, it uses that one.
If it does NOT find a custom file, it uses the CORE file.
NOW... WHEN YOU UPGRADE...
You need to make sure that all the upgraded CORE FILES for the new version are loaded into the default areas (folders).
You then need to CHECK your CUSTOM files to see which of these need alterations. Remember... you made custom files out of COPIES of the previous version's core files...
... so, your CUSTOM files will still be the OLD VERSION, while your CORE FILES will be the NEW VERSION.
You can't just overwrite your original custom files with their new version counterparts... you will effectively LOSE your customisations!
So you have to manually make edits to affected original custom files.
How do you know WHAT original custom files are affected by the upgrade?
You check the CHANGE_LOG that accompanies every upgrade software set.
The CHANGE_LOG lists what files have been altered from the previous version.
If any files listed in the CHANGELOG are also files in your over-ride system, then these need to be manually edited to bring in any programming changes. So you make these changes, as well as keep your customisations.
When your CUSTOM FILES have been altered (where necessary) to bring them up to the upgrade's standards, you can FTP them to the server.
ONLY NOW is it possible to run the UPGRADE PROGRAM... a process that will upgrade your DATABASE.
Bookmarks