How to update without breaking what's there

So I'm on 1.5.5e & 1.5.5f just came out & now we can't update :(

This will be our first update since we started with Zencart & with the plugins we've used & a few tweaks we made that we didn't keep track of, updating would mean that everything breaks :(

Can't you guys come out with a way to keep things separate (like with WP) where the plugins are separate & when updates come out, it just updates the core & won't break everything else?

Yes we read that we can use a tool that tells us what the differences are between the 2 versions, but that would be a lot of work, like a whole day of tedious work.

Thanks a ton & Happy New Year :)

Just use the instructions at https://www.zen-cart.com/entry.php?3-How-do-I-rebuild-my-site-on-the-new-version-instead-of-upgrading

It allows you to keep the current going while tweaking the new. There's no a great deal of difference between e and f so, if you are familiar with winmerge or something similar, you might be able to upgrade that way.

With Zen Cart you still have to get your hands dirty.

1. Make a local server. That is more than just essential.

2. Compare the ZC155f files to yours with Beyond Compare (buy it). There probably will not be many differences.
   Once you you grit your teeth and get on with it, it shouldn't take very long, and you will have learnt a lot.

Probably most if not all of your plugins will not require any changes.
The comparison process will show you the plugins, now is the time to document your installed plugins. Download the original version to keep a backup of those install files and make notes with them - scrupulously. Make sure you are subscribed to each support thread.

3. Once it is all working locally, upload all the changed files in one go in a couple of minutes.

Every upgrade includes more stuff to make ZC more plugin-friendly, but it is an old-style codebase and there is a limit what can be done without a massive change to using a framework (which is in development).

I'm afraid I would disagree with the local server is more than essential UNLESS it is the only option. Many times, environments on the server and local are so opposite that hours spent upgrading are only added to hours spent trying to get the remote version work on the server. As long as the OP has a free database, using the folder-on-the-server method keeps everything in house. zc_install is not only able to setup the site to match the current server but, can also warn the user of any incompatibilities prior to loading. Better to know what you're up against before you start.

So... If your server supports a PHP version that will work with the new ZC and you have a database available, the instructions from DrByte that I posted in the #2 in the "How do I do an upgrade and still keep my live store running in the meantime?" section just goes smoother in a folder on your server.

Side effects of off-server -- Can't get there without some fancy program when using a different computer AND can't post link for help on the forum.

Yes, either way will work. I just see more good in the server-folder method.

The title of this thread is extremely relevant to every DIY shop owner, and should be borne in mind.

I approach the management of my site from the point of view of minimising risk. Working locally has zero risk to my production shop.
I also have had to do most of my early development work in isolated locations with no internet access, so that has coloured my outlook.

1. From a practical point of view, I find modifying files and having to upload them every single time to check the result, then look at debug logs etc., to be a pita when done remotely. Far easier and faster on a local machine for this work.

Comparing an old site against an old ZC version then comparing against a new ZC version to figure out differences etc...or quickly installing an old version or vanilla version to check something...doing this remotely...eek what a headache!:wacko:
Uploading everything would be a huge waste of time (and bandwidth).

2. The issue of different environments causing different problems seems common sense, oft repeated.
   But, since upgrading from 1.38 upwards over the years, I have only ever come across one instance where I had a problem remotely that did not occur locally (and that was my stupid mistake).

So, my experience is that the difference in environments is not something that has wasted my development efforts.
Even if something like that does occur, my better productivity from working locally (wherever I am, irrespective of internet connectivity) has proved far more efficient.

To minimise such issues, locally I always use the latest php version, to fix deprecating issues well in advance of the hosting php version catching up.
When all is well locally, yes I test on the remote server on a new db. This is a point of risk, letting a test site potentially affect a production db by mistake. :shocking: Something that I have done, despite trying to be careful!

If someone knows an easier way to work with 1000's of files than on a local pc, I'd love to know about it.

Yes, we were hoping for it NOT to be a PIA like it wouldn't be with WP & their updating.

Hopefully, in the next 2 verions we will see something.

Thanks :)

rapidfinancia1:

Yes, we were hoping for it NOT to be a PIA like it wouldn't be with WP & their updating.Maybe you're comparing apples and oranges. WP started as a blog and keeps trying to evolve to other things while Zen Cart started as a very good e-commerce platform and grew to a PCI certified powerhouse.
From a recent WP review:> A flexible promotions editor lets you add discounts and coupons that apply when certain rules are met. Products can be categorized and have variations. You can choose between Paypal Standard or Stripe as a payments provider. *You are **not *able to customize the emails and receipts that are sent to customers. No digital products. No PayPal Xpress, Square, etc, etc.
Oh, WP has an addon for PCI. Just $100 per year.
You have to remember all that's going on "under the hood" of Zen Cart.