When running zc_install appears not to have upgraded

I am currently running ZenCart version 1.3.8 and am upgrading to 1.5.3, I have downloaded the latest (w/hotfix) and am following the instructions here: http://www.zen-cart.com/content.php?140
The problem is when I got to step #9. Choose the Upgrade Database option - There was nothing that told be to upgrade or offered a link to upgrade. At first it said my configure files were missing, then after going into the dist-configure.php at admin/includes/ & includes/ and filling out the data accuratley in both files, then I removed the "dist-" from configure leaving it configure.php, uploading to the appropriate folders and setting permissions (for now) at 744.
I went back refreshed the zc_install/index.php page and now I have this :( http://www.shimmys.net/shopping2/
My original database is in folder shopping/ new database is in folder shopping2/ I added the line date.timezone = "America/Los_Angeles" in my global php.ini and made a .htaccess file with the following line added: SetEnv TZ
I also have a redirect set up in my Cpanel to shopping2/
Yikes! Any help will be apprciated!
Robert

If the stepsin that link were followed and the zc_install could not find configure.php files, then thatmeans they didn't exist to begin with and that step 5 wasn't followed (because if it was followed, then the files would have been modified to point to the new location.) Also, it indicates that step 7 wasn't followed as written which is to simply cover over the "old"/existing files with the new files. New install files do not include a configure.php that. Wouldoverwrite an existing version, so the files that should have been modified in step 5 would still be there after performing step 7...

Beyond that, I don't see what the issue is.

It's good that you've found and are using some of the posted instructions to finally get away from 1.3.8. There's another set that seem to help do this from Dr. Byte: http://www.zen-cart.com/entry.php?3-How-do-I-rebuild-my-site-on-the-new-version-instead-of-upgrading

I have followed ALL the steps, when it didn't find the config, I put one in the appropriate spot, didn't I already say this? I filled it out and NO UPGRADE... this was supposed to be a simple cut and dry upgrade why why hwywhwywhw!

Step 7 says: Now load the "new" version files to your new temp directory (from latest downloaded ZIP) it says nothing about overwriting files that were old, in fact that would make mute the whole point of creating a new database so you don't screw up the OLD one. All steps were followed, how do I fix the store, It can't be in this state Monday!!!

RAD1964:

Step 7 says: Now load the "new" version files to your new temp directory (from latest downloaded ZIP) it says nothing about overwriting files that were old, in fact that would make mute the whole point of creating a new database so you don't screw up the OLD one. All steps were followed, how do I fix the store, It can't be in this state Monday!!!

Correct, it says in step 7 to load the new files in the new directory. In step 3 a new directory was created that has the old files, therefore the directions say to load the new files over the old files that are in the new directory.

Also, step 5 says to modify the configure.php files to point to the new database, so again, if in step 7 the files in thenewdirectory were overwritten with the new files, then the configure.php files would still be there and the database upgrade option would have been presented.

Now, what the instructions don't identify is that even when overwriting sommetimes some files also haveto be deleted, and while they will be "discovered" during operation, the files to be deleted are pretty well covered in the documentation as well.

If thats the case you all need to re-write the instructions to be CLEARER. I am a web developer, doing this stuff for over 14 years and if its not clear to me, then it certainly won't be clear to the newbie.
Is there somewhere where their are clear and precise directions with every step laid out?

What about these: http://www.zen-cart.com/entry.php?3-How-do-I-rebuild-my-site-on-the-new-version-instead-of-upgrading

So I notice there is no mention of an addition to the php.ini file or any htacces files, no changes are needed there? Or was I misinformed from yet a different set of instructions?

Not misinformed... There is no "here is how to upgrade directly from version 1.3.8.(a-f) to 1.5.3" instructions. All of the instructions have an air of generic guidance to them. Each particular version has it's own requirements. The need for identifying say the timezone is more of a php requirement though it is covered in the forum as well and if the question is asked again, there is likely to be someone that will respond rather promptly with some guidance or instruction.

Overall though as long as ZC is able to kick in there is an error trapping system that guides users to their solution. There are base requirements for each version on which the software is expected to function with no issues straight out of the box, although that also assumes that the host has properly setup the service.

Anyways, ZC is designed to not require an .htaccess in the store's root. The other directories include an .htaccess as applicable for the content being provided and is considered to be hosted on an apache server. So a base install does not need a .htaccess file modification. The php.ini file may need a modification depending on what the host has established as the default/users modification. Again though there is help available when a problem arises. Most problems though come from an action performed. While not all instructions are so detailed to be able to perform blindly, they generally guide users down the right path.

Now there are some plugins that require .htaccess modifications,but most of those are uri rewriters. I don't know of any that specifically need .htaccess mods. Okay there are those things that will need a different type of file to be accessible such as .csv files in certain directories, some sort of multimedia upload/download. But most of those extra facts are covered in the applicable installation instructions or in a FAQ or the wiki. Then of course in the forum thread for that application, etc...

Anyways, the instructions do leave details to be determined and are written to provide a more grand overview. Many have asked the question of upgrade details, and many have responded, typically each with a little of this or a little of that different, but generally coming back to the same base instruction. While version 1.3.8 may not have been as "portable" as the later versions, if the site was originally built under the current philsophy of change as little of the default code provided and use the override system as much as possible, then upgrades are far easier/quicker and less buggy. It's when holding onto what was and may no longer work with the current code (more secure) that issues begin to crop up.

Appreciate your time.

RAD1964:

Appreciate your time.

Hope there was something useful in the information.

You questioned the accuracy of some other instruction. Mind if I ask what instruction that was? It may have been correct for the right reasons. :)

Argh, Ok attempt number failed, I got 500 error.

Can I asume that (with no changed files/plugins) I copy the version 1.3.8 that is the current working version of my zencart site, I copy and put that in a new empty folder, called: shopping2.

Now I take the new version of the site and I paste that site into the same folder: shopping2, this time overwriting files with a newer date.

I had an admin in v1.3.8 that I renamed, now there is my renamed admin and the new admin. What do I do there?

This upgrading zencart needs a one button install which I know doesn't exist but boy oh boy does it need it!

YEH! I finally got the upgrade option... it appears 4 files were skipped:

SKIPPED: Cannot drop index page_accessed on table admin_activity_log because it does not exist.
SKIPPED: Cannot drop index access_date on table admin_activity_log because it does not exist.
SKIPPED: Cannot add index idx_page_accessed_zen to table admin_activity_log because it already exists.
SKIPPED: Cannot add index idx_access_date_zen to table admin_activity_log because it already exists.

Should I do something or ignore?!

RAD1964:

YEH! I finally got the upgrade option... it appears 4 files were skipped:

SKIPPED: Cannot drop index page_accessed on table admin_activity_log because it does not exist.
SKIPPED: Cannot drop index access_date on table admin_activity_log because it does not exist.
SKIPPED: Cannot add index idx_page_accessed_zen to table admin_activity_log because it already exists.
SKIPPED: Cannot add index idx_access_date_zen to table admin_activity_log because it already exists.

Should I do something or ignore?!

The way those "error" messages are written, they are more a notification than an error. Ie. Skip and be merry. :)

Now. One thing you will want to do with the template files of your non-classic template(s) is to compare those files to the "core" version of them and incorporate changes that are applicable. Like, I think it is html_specialchars (I could be way off on the function name, but) may now need four "variables" to be included where in the past one was sufficient. Those types of things will somewhat stand out when the files are compared.

Also realize that this method of upgrade may leave behind files that could interfere with operation if the "extra" files that may have existed in 1.3.8 but not in 1.5.x were not one for one replaced when the ZC team created the next version.

As to your earlier admin question, you can have any number of admin directories each with some sort of variation. At the moment there is no "override" system on the admin side like there is on the store side. That said though, the new admin directory would still need a functional configure.php file for this store... Also, if in fact all you did was update the files around the configure.php files, there are new "features" created in the newer configure.php files that did not exist in the older versions. Ie. No longer is the admin directory revealed in the file as it is determined by the location being accessed and the placement of the configure.php file in relation to that... But I don't want to make things harder than they already have been. Congratulations on getting it to work, perhaps though you can now see how some of the other directions fit in and how you can streamline the process a little for what works for you.

Don't know what your geometry skills are like but it's like a vector where you can first solve for the direction and then find the distance or you can first find the distance and then the direction. Either way gets you to the final result, but you can take the path that makes sense to you first. :)

rut ro..
The requested URL /admin/FILENAME_ALERT_PAGE.php was not found on this server.
This is when I try and access the admin. admin/alert_page.php is on the server!

FILENAME_ALERT_PAGE is defined in my includes/filenames.php

RAD1964:

rut ro..
The requested URL /admin/FILENAME_ALERT_PAGE.php was not found on this server.
This is when I try and access the admin. admin/alert_page.php is on the server!

There is a define action somewherre (or it is not there) that is supposed to bridge the gap between the constant FILENAAME_ALERT_PAGE and the actual file. It may not have been fully uploaded (filetransfers sometimes don't fully take) hopefully such a file wouldn't move much from one version to the next. You could possibly use the developers toolkit under tools of the old functional version to see where the file should be/should have been. As for where it is on a 1.5.1 site?

Wait a minute so which is the issue? That the alert message is presented or the fact that the constant is used instead of the file? Where is/was this "information" identified? On screen?
If defined in the store side includes folder, does the admin panel have a correct path to the store side from the configure.php file?
Which admin panel was attempted? :) there was some discussion earlier about which directory the admin files should be in.

So I am using the new admin folder because it may contain updated files, I made sure in both config files to point the paths to the new shopping folder and the paths to the admin without it being renamed.

I am now getting an Internal Server Error 500 when I try to connect to the store and the admin.