What would happen if (1.3.8a to 89h)

What would happen if I simply ran the /zc_install/index.php and chose "update".

Assumng the only changes were added products and some features turned off on the layout would everything still work (like the UPS APIs)?

I have the "How do I upgrade" from the tutorial but I'm wondering how much of the instructions are to preserve customizations.

zc_install only upgrades the database content.
But that doesn't deal with all the programming changes contained in the .php files and templating/etc changes to .css and .js and .html, etc files.

Follow the documented upgrade instructions.

I guess I'm confused. If nothing was changed from the initial install except adding inventory why doesn't an "upgrade" upgrade the associated program files? Why don't aren't they simply overlaid (I realize I'm asking why you made a programming decision)?

It sounds like it would be easier to export the DB and do a clean install then import the data. But then I'm helping a friend after the fact and I didn't do the initial install, thus my confusion.

And I guess one last question, in addition to the cart what else needs to be "maintained". The host should be applying security patches and what not to their server right?

Thanks for the reply and advice

The "upgrade" selection is for the database; it is not intended to refer to the files. What you think it ought to mean does not change what it does mean.

You say "nothing" was changed from the initial install. Does that mean it still has the stock green Classic template with the Zen Cart logo, and the boilerplate text in various places like "Congratulations, you have installed Zen Cart..."?

If not, you have some changes to files. If those were done in /classic/ folders, you need to follow the "creating a template" instructions in the tutorials to copy all /classic/ files to new /custom/ folders. If they were done in /custom/ folders (whatever the name is), and you have NO changes that are not in /custom/ folders, you could theoretically just upload the new fileset over the existing set and your changes would be safe (except for the /includes/configure.php and /your_admin_name/includes/configure.php).

Hosting server security maintenance has nothing to do with Zen Cart file security upgrades.

Zen Cart's current architecture goes way back to the days before applications were designed to allow plugins to be nicely encapsulated outside of code code.

This means that many Zen Cart add-ons change the core code, and so when upgrades are done, these changes need to be merged into any updated files.

Clearly that's not very satisfactory in this day and age, and one of the reasons why Zen Cart 2.0 is being built around a different architecture. But the moment, it is what it is.

Yes, web hosts should apply security patches to the server OS. Doesn't mean that they do.

However, security patches and updates to application software, such as Zen Cart, would be beyond their remit, unless there's a special agreement with them to do so (which would be rare).

gjh42:

The "upgrade" selection is for the database; it is not intended to refer to the files. What you think it ought to mean does not change what it does mean.

I didn't post to argue simple English. The file is a "Zencart" update, not a "Zencart database" update. If you're upgrading the cart that implies the entire product not a piece of it leaving you to have to edit multiple files and certainly merits asking a forum of experts for clarification. Judging by the number of posts about upgrading, I'm not the only one who thought upgrade referred to the entire product and not just the database.

gjh42:

You say "nothing" was changed from the initial install. Does that mean it still has the stock green Classic template with the Zen Cart logo, and the boilerplate text in various places like "Congratulations, you have installed Zen Cart..."?

If not, you have some changes to files. If those were done in /classic/ folders, you need to follow the "creating a template" instructions in the tutorials to copy all /classic/ files to new /custom/ folders. If they were done in /custom/ folders (whatever the name is), and you have NO changes that are not in /custom/ folders, you could theoretically just upload the new fileset over the existing set and your changes would be safe (except for the /includes/configure.php and /your_admin_name/includes/configure.php).

Hosting server security maintenance has nothing to do with Zen Cart file security upgrades.

Clearly the upgrade process is more involved than I initially thought. The "3 easy steps" I find to be a gross oversimplification of the upgrade process (and this is only my opinion). Particularly when I'm not the person who did the initial install but coming along after the fact to try to help out. I have to rely on what the guy that did the setup says when he states that all he did was input inventory when in actuality he installed UPS api's and added a facebook link to the first page. Probably more than that.

Also, as upgrade implies files that need to be modified should simply have what was changed/added/removed handled programatically. In a perfect world.

I understand now, this is not the case here. Which is fine, I'll deal with it.

Like Kuroi says, it is what it is. My post was just an attempt at trying to get up to speed (put my interpretation of "upgrade" in the appropriate context), and look for any shortcuts or tips the community might have to offer.

Thanks for the reply, I'm off to file compare hell.