Preparing to go from 139d to 139h - Advice please?

Hi,

I am preparing to go from 139d to 139h. I'm still a newby and I've never done a multistage upgrade... so I'm very nervous!

I wonder if this approach is good:
Each version after 139d has a changelog. Each changelog has 4 sections (Changed; Deleted; New; Moved). My thought was to compile all the changlelog lists into a single master list, then work that list.

Once I have the list together outlining everything between d and h, then I would begin merging, deleting, adding, or moving files.

With regard to mods, my plan was to handle the transition from d-to-h first, then go down my list checking for mod upgrades.

Does this sound right?

Thanks in advance for your thoughts!

Create your list....

Hope you are using the template override system

If so then only those files need to be check against the list for a new version, and then only those files that have a new version need to be merged

If there is not a mod update then the mod files can be handled the same way

Hi Kobra,

I don't think I understand about the template override system. I've heard people talk about it... but I don't know about it. I guess that means I am not using it?

But thanks for the reassuring words, I'm reasonably confident I will be able to muddle through now.

I don't think I understand about the template override system.
https://www.zen-cart.com/tutorials/index.php?article=36

Aaah cool man, thanks!

I have kind of a mixed bag right now. That was the first time I've seen it explained.

I wonder how hard it would be to transition over? I am very, very heavily modified. But considering the a new ZC version rolls out every 5 minutes, it might be worth the effort to go backwards and sort that out. :D

Everywhere there is a classic folder, the files that exist there are overridable.

To do this at this point get a fresh cdistribution of the version that your live shop is - expand it locally

Download all your files to your local

Get a comparison tool like winmerge and run a comparison and make a note of every file that you have edited that is not in an over ride folder

Move all these files to a folder structure on your local naming the folders for your template and maintaining the default structure

Almost all will exist under the /includes folder

When done you can upload this /includes structure that contains only your overrides folders and their files

Now you have a list of override files to see if there are new versions

Sounds harder than it is....