Need help to do an upgrade from 1.5.0 to 1.5.5

ie: you already have an /includes/ directory.
I usually copy the new one in as includes_new
and then once it's all uploaded, I rename /includes to /includes_old, and then /includes_new to /includes
Won't I lose custom files/folders that way? Like the French language folders? or other images i might have customized?

CaroleAs:

Won't I lose custom files/folders that way? Like the French language folders? or other images i might have customized?

If your "new" folder has everything in it to provide what you want, then no you won't lose any of your customizations.... That's the point of having built a functional version of the site under the new version, it will self-contain everything needed for the site to be live, it's just that it is not in the correct location and doesn't have the latest visitor information..... While working on the new version, users are navigating your site, even while copying files (if the store is not in maintenance mode) then they are "changing" the database...

This was where I was talking about store fileset version matching the zc_install folder version and database being "old", then zc_install is expected to bring the database up to the same level of the files and away the store can go.

Remember to refer back to the instructions: https://www.zen-cart.com/entry.php?3-How-do-I-rebuild-my-site-on-the-new-version-instead-of-upgrading

CaroleAs:

I didn't know about that. Thanks.

Yeah, that is what i meant. I learned a lot though!

Probably what i'll do. Now that i "understand" more about database, I can see that i can make a copy of my live site (on a subdomain), clone the database (to not touch the live one), adjust the configure.php files, and then, go through the upgrade process again. Is that what you are talking about?
A fully functional store with all of the programming properly written to handle the expected data and to sanitize any wrong/malicious data, should provide no additional mydebug logs during operation other than those that may be created as a part of debugging or logging for a particular purpose. That does not mean in "means-to-an-end" solution one is to disable any form of logging, but instead should correct the code so that such an error, warning, or notice is not generated to require a log or onscreen notification.

While the discussion is ongoing to come back full circle on what all is involved in the upgrade process, as far as additional testing, I mainly was referring to doing whatever is needed to be done on your site for you to believe that you have successfully worked with a customer. See, some people their intent is to pass out a bunch of free information or have things on display, others to sell a product, or to make an option available, etc.. I mean it is an e**Commerce** application, so one would think that it would be used to sell/buy things... So primarily suggesting that you try to go through that process as a customer. Verify that you have copied over all the things, statements, descriptions, etc. that you expected and that it all actually works.

For various payment modules, they often make it possible to use test credentials so that you can "fake" purchase items rather than actually getting a bank involved. This should work the same in test mode as live mode and normal site traffic may play a factor in how much/in what way that is tested... I mean if orders seem to fly in usually, can watch the customer action and see if they are getting stuck at checkout or error logs are generated and then quickly resolve the situation as needed... In a less busy site, well, may be good to just buy that 1 cent image of your favorite place that you posted to support the operation. :)

When I was doing the upgrade on the challengemehq site (the first test), I had a bit of a hard time with the admin login password. When I tried with the cloned site test, same thing. Today, on another test site, same thing.

In which file is that password "stored"? Is it part of the DB? I am just wondering why the password that works on the live site, does not seem to work on the test stores while i am using a copy of the live site database. And when doing the upgrade, I am also asked for that PW which does not seem to match the login pw I have for the live store admin. I am just puzzled what pw it is using.

From post 162:

mc12345678:

Good, so hopefully though (and it was stated earlier that you had learned how to do a database "transfer") you now know how to do that because the database is your "life-line" the files can be easily put back/found, reconstructed, but the data is your business.

Anyways, yes the only place(s) your database is referenced is in the two configure.php files.

As for the admin... if you notice in any/all upgrade instructions login to the admin does not occur until the end of the update. There's actually reason for that which may or may not be an issue with ZC 1.5.5, but has been in previous versions. Attempting to login will update the password "complexity" which may or may not be equivalently compared when providing credentials during the upgrade. I haven't recently tested this aspect because of previously being bit. :P

Additionally, if you think about it, until it was suggested to try to login to this recent upgrade, you hadn't. So, why do something different unless you want to either redo this database move or run the "I forgot my password" script?

CaroleAs:

When I was doing the upgrade on the challengemehq site (the first test), I had a bit of a hard time with the admin login password. When I tried with the cloned site test, same thing. Today, on another test site, same thing.

In which file is that password "stored"? Is it part of the DB? I am just wondering why the password that works on the live site, does not seem to work on the test stores while i am using a copy of the live site database. And when doing the upgrade, I am also asked for that PW which does not seem to match the login pw I have for the live store admin. I am just puzzled what pw it is using.
Password is stored encrypted in the database. Username and password to be used in the zc_install process when asked for "super user" credentials is that of an admin that logs into the admin screen of the store. Specifically the credentials to be used to log into the "old" store.

Trying to access the admin using the new files and a database that has not yet been upgraded could cause the issue you have been seeing.

Don't try to log into the admin during the upgrade until the database has been upgraded to the software version that is installed. (The database upgrade is done using zc_install)

I think I had a 100% successful test this time around (yeah, the 4th time around!)

• created a new DB
• cloned my live site DB into this new DB
• copied the whole live site into a sub-domain
  So I worked on a site that was identical to my live site (of course, I adjusted the configure.php files)
  And when running the zc_install, it went smoothly, upgraded the db, and everything is ok (except the sideboxes, but it takes less than 5 minutes to adjust). So it looks like I finally did it correctly, without any mistake this time.

Breathing now.
Taking a break too.

http://creationcassel(dot)com/test3store/ (if you want to poke around :) )

CaroleAs:

I think I had a 100% successful test this time around (yeah, the 4th time around!)

• created a new DB
• cloned my live site DB into this new DB
• copied the whole live site into a sub-domain
  So I worked on a site that was identical to my live site (of course, I adjusted the configure.php files)
  And when running the zc_install, it went smoothly, upgraded the db, and everything is ok (except the sideboxes, but it takes less than 5 minutes to adjust). So it looks like I finally did it correctly, without any mistake this time.

Breathing now.
Taking a break too.

http://creationcassel(dot)com/test3store/ (if you want to poke around :) )

You know what's both interesting and concerning? There is no discussion about how the new ZC version files got integrated, placed, replaced, or otherwise used to "successfully" upgrade...

Interesting because an upgrade process was identified as being followed "exactly" but no reference to its instruction, the significant questioning about file placement, etc... and as for "poking around" the thing is that other than possibly a few "known" problems with earlier versions of ZC, the possibilities of identifying the exact ZC version with complete certainty can be low. Remember we all see the template... a template for a new version could more than likely be used on an older version of ZC, much like an older template could be used on a newer version. But, there are some 10 things known to be a characteristic of a version and a majority of those are again seen, then playing the odds that one would expect that to be the version in question. :)

Btw, and another reason of doubt, was recently approached by someone that said: I personally upgraded this site to the next higher version, but for some reason now when I try to skip several versions (years later right), there now appear to be indications that I haven't done that upgrade. When the site was checked, the database in fact had not been updated to the next version and a few other issues that caused the upgrade to not be able to go through. Anyways, the omission of pertinent facts can lead one to either assume that the action was taken or cause questions to be asked. Generally as almost any that have seen my posts would claim, I ask a lot and also offer many alternative reasons or possibilities. Some have stepped in to swat me, some have just gone on to ignore what is written and anywhere in between. You seem like you are really trying to get 'er done and correctly, I don't like to see someone that tries so hard and is being successful to run into a problem because of some miscommunication/misunderstanding and it would seem that any other person posting suggestions/guidance are trying to see the same success. We all have our backgrounds and methods, but like I said, just concerned that there is/was something bigger missed. :)

Like I had mentioned earlier, it happened that lat9 sent me steps to upgrade, that were even more detailed than what was on the blog post from DrByte. She happened to PM me for something unrelated to the upgrade and I guess she noticed my questions here. Here is what she shared as detailed steps:

1- Create a copy of your test site's /includes directory (i.e. /testsite/includes) into a directory accessible from your main site (/includes2)
2- Copy your live site's /includes/configure.php to the /includes2 directory (remember that it might be read-only).
3- Create a copy of your test site's /YOUR_ADMIN directory (i.e. /testsite/YOUR_ADMIN) into a directory accessible from your main site (/YOUR_ADMIN2).
4- Copy your live site's /YOUR_ADMIN/includes/configure.php to the /YOUR_ADMIN2/includes directory.
5- Download all files from your main site's root directory to a directory on your local system; I usually name this root1.
6- Download all files from your test site's root directory to a directory on your local system; I usually name this root2.
7- Place the main site in Maintenance Mode, making sure that your current IP address is listed in the Admin IP's OK for maintenance. Make sure that you remember the Username and Password that you used to sign into the admin; you'll need it for the zc_install database conversion step!
8- Make a backup copy (using your webhost's cPanel's phpMyAdmin) of your current (older ZC) database ... important!
9- Copy the Zen Cart installation directory (/zc_install) to the root directory of your live site (/zc_install).
10- Take a deep breath.
11- Rename your live site's /includes directory to something like /includes_xxx (where xxx is the previous Zen Cart version).
12- Rename your live site's /includes2 directory to /includes
13- Rename your live site's /YOUR_ADMIN directory to something like /YOUR_ADMIN_xxx (xxx is the previous Zen Cart version).
14- Rename your live site's /YOUR_ADMIN2 directory to /YOUR_ADMIN (your current admin-folder name)
15- Copy all the files from your local /root2 to your live store's root directory
16- Point a browser to https://www.yourstore.com/zc_install and follow the upgrade instructions. That processing will convert your older configure.php files to match the current (ZC1.5.5) formatting as the first step and then go through the database upgrade process.
17- Once the upgrade step is finished, you'll need to rename/remove the /zc_install directory before you can access the admin.
18- Log into your updated Zen Cart admin. Poke around a bit to make sure that stuff still works.
19- Go to your updates storefront (your IP address needs to be in the maintenance-mode allowed list). Poke around a bit to make sure that everything's still OK.
20- Take the site out of maintenance mode, have a glass of wine and pat yourself on the back.

CaroleAs:

Like I had mentioned earlier, it happened that lat9 sent me steps to upgrade, that were even more detailed than what was on the blog post from DrByte. She happened to PM me for something unrelated to the upgrade and I guess she noticed my questions here. Here is what she shared as detailed steps:

That at least gives an understanding of the likely status of things. Note that in the installation process "earlier" there was discussion of issues with the htaccess file(s) as pertains to nginx. The above process does not fully address that, though it would care for the includes and admin directories. Also other things like if the copyright image has been modified (assuming that it has been maintained as a part of the template) then that also isn't included.

It's a great start and will accomplish like 95%+ of what is truly needed, but does leave a few things to still be addressed.

mc12345678:

That at least gives an understanding of the likely status of things. Note that in the installation process "earlier" there was discussion of issues with the htaccess file(s) as pertains to nginx. The above process does not fully address that, though it would care for the includes and admin directories. Also other things like if the copyright image has been modified (assuming that it has been maintained as a part of the template) then that also isn't included.

It's a great start and will accomplish like 95%+ of what is truly needed, but does leave a few things to still be addressed.

If I remember, the .htaccess issue was when I was dealing with the cloned site that had a redirect in the .htaccess file. In the last two "tests", I was not using the "cloned" store as I copied the store itself so I didn't deal with that file at all.

Now, what about the copyright image? I never saw that mentioned anywhere. What image? or which template? I am cloning the responsive template using the cloning mod. Is that what you are referring to?

CaroleAs:

If I remember, the .htaccess issue was when I was dealing with the cloned site that had a redirect in the .htaccess file. In the last two "tests", I was not using the "cloned" store as I copied the store itself so I didn't deal with that file at all.

Now, what about the copyright image? I never saw that mentioned anywhere. What image? or which template? I am cloning the responsive template using the cloning mod. Is that what you are referring to?
At the core of it, I'm speaking metaphysically. See, the ZenCart logo if not mistaken has changed since at least ZC 1.5.0. So, if it is still used on your site at any point/location then it would be considered prudent to also update it.

Again, basically encouraging engagement of one's noodle rather than blindly following instruction.

As for the other things related to the htaccess, again there is the issue of inheritance where if a parent directory was updated, child directories would be "protected" by the same rule(s) as the parent and therefore no further action in the child directories would be necessary.

Ok, I'm just babbling now. Back to what I was doing.

mc12345678:

As for the other things related to the htaccess, again there is the issue of inheritance where if a parent directory was updated, child directories would be "protected" by the same rule(s) as the parent and therefore no further action in the child directories would be necessary.

The one file that was redirecting was the /storetest/ while the live store was /store/. They weren't parent-child, but "siblings", so if i understand correctly, it won't affect the live store in any shape or form, especially since i am not even going to use the files from the "storetest" installation, but the "challengemehw" one. So should i still worry about something?

At the core of it, I'm speaking metaphysically. See, the ZenCart logo if not mistaken has changed since at least ZC 1.5.0. So, if it is still used on your site at any point/location then it would be considered prudent to also update it.
I am not sure what the difference is between the two logos, but i have no plan to use the ZenCart logo; i want to replace it by my own anyways. And since i don't have the ZenCart logo on my current live store, how do i know that i am using the correct one before even replacing it?

Now, I am just more unsure if i should/can go ahead. After 4 test installation/upgrade, what else should i test?

CaroleAs:

The one file that was redirecting was the /storetest/ while the live store was /store/. They weren't parent-child, but "siblings", so if i understand correctly, it won't affect the live store in any shape or form, especially since i am not even going to use the files from the "storetest" installation, but the "challengemehw" one. So should i still worry about something?

I am not sure what the difference is between the two logos, but i have no plan to use the ZenCart logo; i want to replace it by my own anyways. And since i don't have the ZenCart logo on my current live store, how do i know that i am using the correct one before even replacing it?

Now, I am just more unsure if i should/can go ahead. After 4 test installation/upgrade, what else should i test?
Don't let me shake you like that...

I've asked twice, have you verified that you can do with your store what it is constructed to do? Ie. If you sell things, have you tried to purchase something? If you have downloads, have you tried to download it? That's part of that "poking around your site" perspective.

As for differences and validating configurations, do you have some form of comparison software? The "simplest" of these is say WinMerge, though there are other open source and commercial product that are a bit better and offer some more/better features. :)

Don't let me shake you like that...
Well, I am heavily relying on your guidance so yeah, it is shaking me!

I've asked twice, have you verified that you can do with your store what it is constructed to do? Ie. If you sell things, have you tried to purchase something? If you have downloads, have you tried to download it? That's part of that "poking around your site" perspective.
Darn it! I was not able to complete a transaction as it gives me (it was working when I did the very first install, on the challengemehq test site):

This page isn’t working
creationcassel.com is currently unable to handle this request.
HTTP ERROR 500

as soon as i click on the Checkout button to complete the transaction. What did I miss? Anything I forgot to enable somewhere?

As for differences and validating configurations, do you have some form of comparison software? The "simplest" of these is say WinMerge, though there are other open source and commercial product that are a bit better and offer some more/better features. :)
Yes I know about WinMerge but then, since the zencart is different, I am not sure where to look/compare to not end up comparing things that are obviously different due to an upgrade or which files should be compared because they should be identical.

CaroleAs:

Well, I am heavily relying on your guidance so yeah, it is shaking me!

Darn it! I was not able to complete a transaction as it gives me (it was working when I did the very first install, on the challengemehq test site):

This page isn’t working
creationcassel.com is currently unable to handle this request.
HTTP ERROR 500

as soon as i click on the Checkout button to complete the transaction. What did I miss? Anything I forgot to enable somewhere?

Yes I know about WinMerge but then, since the zencart is different, I am not sure where to look/compare to not end up comparing things that are obviously different due to an upgrade or which files should be compared because they should be identical.

Don't know how strong a tree is until it is shaken a bit, keep growing roots and understanding the "why"...

Errors: always check first for ZC logs. There might be one directly related.
Could be a temporary issue with host, could be a missed "change", is SSL a part of the domain/sub-domain to allow it's continued use? includes/configure.php file data entry: does it look right for secure communication?

Comparison software for an upgrade: new out-of-the-box version to your upgraded fileset. Only differences in files existing in both should be those associated to your manual manipulations and those identified as necessary to support a plugin. Ideally, the only files that should exist in the out-of-the-box (vanilla) version should be those associated with demo product (some of the images in the images folder), the zc_install directory, the docs directory and the other files/folders that are recommended to either be removed or renamed as part of maintaining security (there are steps after the install/upgrade suggested to be performed to lock things down again).

The only additional files that should exist on the new site are those related to plugins (which you should know which file(s) were added), product images (should really confirm that these are your unaltered images), and anything that you've personally placed on the server and need/expect to remain on the server (extra unnecessary software just offers another way for someone to try something undesirable).

Errors: always check first for ZC logs. There might be one directly related.
Could be a temporary issue with host, could be a missed "change", is SSL a part of the domain/sub-domain to allow it's continued use? includes/configure.php file data entry: does it look right for secure communication?
Well I do have an SSL, but not "enabled" so to speak. It is not enabled on the live site either (I am not taking CC payments) so it should not be different than on the live site. A transaction works well on the live site, however, the checkout is different since the mod I use in the 1.5.0 is not compatible with 1.5.5 so I need a different one (which works in the first test installation).

The only additional files that should exist on the new site are those related to plugins (which you should know which file(s) were added), product images (should really confirm that these are your unaltered images), and anything that you've personally placed on the server and need/expect to remain on the server (extra unnecessary software just offers another way for someone to try something undesirable).
Speaking of images, on the live store, I have edited most of the buttons (in English and French). They were created for the "classic" template that I had duplicated and renamed. Since it was not a responsive template, can I still use those in a responsive template in 1.5.5?

CaroleAs:

Well I do have an SSL, but not "enabled" so to speak. It is not enabled on the live site either (I am not taking CC payments) so it should not be different than on the live site. A transaction works well on the live site, however, the checkout is different since the mod I use in the 1.5.0 is not compatible with 1.5.5 so I need a different one (which works in the first test installation).

Speaking of images, on the live store, I have edited most of the buttons (in English and French). They were created for the "classic" template that I had duplicated and renamed. Since it was not a responsive template, can I still use those in a responsive template in 1.5.5?
Remember, you're practicing an upgrade. That means everything about it. Recently it was practicing the database part, but that's just half of the store, besides that, your "first" test store where "everything" works should be your basis for upgrading the files to your new site. So would look at your process to see how this latest upgraded clone didn't get the file(s) that worked in your original build/rebuild. If it happened this time, you don't want it to happen again with the live site.

As to the images: well, let's see. You have what, three ZC 1.5.5 sites now? Think there's the possibility of testing it out to discover the answer? There's a number of factors potentially involved of which I do not know the history on your site. Ie. Was css modified to accompany any width or height changes? Perhaps some other change to a file was made that hasn't been carried over: (comparison of 1.5.0 to your current live site would show the differences made to make your site yours.), etc... if those things are desired to remain a part of your site, then you definitely want to at some time verify that they work. It could be after you do the upgrade of the live site if there is an "immediate" need to get it up or could be done before doing that so that it is a smooth transition.

Remember, you're out to make money, so... whatever needs to be done to support that continued effort.

Now I am stumped. The check out only works on the initial test store, but that was a fresh install, where I didn't carry over all the download files or all the product image files.

Now, on all of the following tests where I had a complete copy of my site (including the initial clone that had a partial copy of the store and all the files), the checkout does not work :( . It fails at the same place and keeps giving the same error.

So I know it means there is something different between the first test install (and the live store) and the later 3 tests. Where to look first? Any specific area? Since I don't know what I would be looking for, can you send me to a general direction?

So first is to identify what error is really being reported: /logs/.
If nothing recent related to that, then possibly server logs if you have access to them and/or can get them relatively quickly.
Then, what has been installed in the original upgrade site to support that check-out process and what from that install hasn't been done to any of the follow on sites? Did you have to disable and/or remove some feature to then re-enable and/or reinstall some feature?

After that, considering/assuming that the files used for these additional upgrade tests, would do a full compare of files having checkout_ in them. They are smattered about in the includes folder. But... there is also another aspect of consideration... the upgrade process... there is a file in more recent ZC versions that is used by more recent plugins that is outside the includes folder... namely ajax.php which is in the root of the store and was not a part of the original ZC 1.5.0 build... it could be that which is missing and causing your 500 error if you have followed the instructions that were posted a little while ago that do not touch the root directory in that way...

Thanks. That is good enough to get me started on checking.
Have to be out for a few hours, but will be back at it later today, for sure!