General question about when to upgrade

eyates

This is probably a pretty basic question but I had a disastrous experience when I upgraded recently and wanted to be clear on how to go about doing so in the future.

I basically recreated my site using a fresh install of 1.4.0.2 - I see that the latest version is now 1.4.0.3 and I'm wondering if in order to upgrade to that, if I'm supposed to follow the whole process of removing the zp-core folder, theme folders, and files in the home directory and then uploading the latest version to my server or if I don't need to do all that each time.

Again, the only reason I ask is that I messed something up big time the last time I did this. My guess is that I was upgrading to the latest version from something other than the immediately previous release in which case it was completely my fault. So basically my question is: do I follow the whole upgrading instructions when going from something like 1.4.0.2 to 1.4.0.3 or are those instructions only for going from something like bigger like 1.4.0.2 to 1.4.1 or even 1.4 to 1.5?

Thanks for your help!

sbillard

Well, you will certainly need to upload the complete version of Zenphoto each time. While there may be files that have not changed, unless you are skilled at detecting which ones and have the time to do so you will certainly "brick" your installation if you do not do so.

It should no longer be necessary to remove the prior version of Zenphoto. Instead Setup will tell you what files do not belong and allow you to remove just them. This is a feature introduced with the 1.4 series of Zenphoto. We have not yet changed the upgrading instructions as they still work (even if removing the files is not needed) and they apply to earlier versions of Zenphoto.

I am not sure what happened to you on your previous upgrade. But if you did "jump" a large span of releases that is probably the culpret, not removing the existing files before uploading the new ones.

We do try to make upgrades work across all releases. Unfortunately we have no where near the resources to test these permutations. So, a bug can creep in where release X has a dependency on some migration that occured in release Y but is no longer being perfomed. If you somehow skip over release Y you may encounter that bug. Of course, if you report the problem we can make sure that it will not occur in release X+1.

BTW, this "release skipping" issue will not apply to the bug fix releases (e.g. 1.4.0.1, 1.4.0.2, etc.) You can safely skip them if you do not care about the bugs they fix.

eyates

Ok great, thanks for your help! So it sounds like I don't have to worry about upgrading from 1.4.0.2 to 1.4.0.3 if I don't have any issues with bugs as this is just a bug fix release and not a new version release. Perfect! I just wanted to be sure I wouldn't be skipping versions again if I didn't upgrade for each and every change in version number.