1.5.5a to 1.5.5b patch

[rued]

Attached is a patch, containing the changed files between 1.5.5a and 1.5.5b

It's easily created from GitHub by cloning the repo, then by running the following in the v1.5.5 branch:

git diff-tree -r --no-commit-id --name-only 1898b97 3c6e497 | xargs tar -rf zen-cart-v1.5.5a-05052016-zen-cart-v1.5.5b-11022016-patch.tar

Where 1898b97 is the last commit in 1.5.5a and 3c6e497 the last in 1.5.5b, as displayed on https://github.com/zencart/zencart/releases

The Zen Cart team would help their less techy users a lot if official patches was released for each new version, and maybe encourage more to update. I'm sure the hole release process can be automated with some cool scripts to. ;)

Anyhow, I hope this tip will help some make their life easier.

- Uhm ... sorry ... the forum doesn't allow me to add the patch (tar not allowed, zip to big), so you folks will need to do your own.

[HeleneWallis]

It would even help the more techy users who have heavily modified their installations, and will have to go through their mods one by one to make changes to individual files.

Thanks much for this!

[mc12345678]

Also as somewhat pointed out there are/were different points in the process of "release" of 1.5.5.a or any other such 1.5.5 version. Using the last change applied to ZC 1.5.5.a would only be good for those that had installed 1.5.5.a based on that last change because the first version of 1.5.5.a was different than the last...

The most accurate diff is the one between your new download and your old download... even then one or more files may be partially patched on the live store with one or more of the fixes identified along the way.

There are plenty of software comparison tools (free or commercial) available that can identify changes and permit application of the changed code.

[Design75]

And also !! READ !! the manual in the docs folder there is a list in there with all the files that have changed, added and or removed.

[rued]

OMG! You can make the patch from any version to any version, and if they where published officially, anyone could easily unzip them to the same folder (starting with the oldest), to get all changed files.

Also, quite many other projects managed this perfectly well. Releasing patches / upgrade packages, for any version.

Still, this was just a tip for those who understand and can use it. The hard headed ones living in the dark ages, well, continue to do as you like ... :)

Btw! It happens quite often there is missing file changes in the docs, and there is a Git command to get all changed files equally easy as making the patch, it can even be combined.

[swguy]

It happens quite often there is missing file changes in the docs ...

This is true. Senior members of the community: you can help everyone by posting tips, corrections and bug reports.
Thanks @Rued for posting this piece of advice.

[carlwhat]

Still, this was just a tip for those who understand and can use it. The hard headed ones living in the dark ages, well, continue to do as you like ... :)

Btw! It happens quite often there is missing file changes in the docs, and there is a Git command to get all changed files equally easy as making the patch, it can even be combined.

i agree with swguy....

nice little tip, and one that i plan on using! thanks!