The simpler media website CMS
At the end of the Month, we're due a major (yes, it's our fault for leaving it so long...) upgrade to a site I'm helping to support.
ZP 1.6.2 (with matching ZPBootstrap) to ZP 1.6.8 (with latest ZPBootstrap, downloaded the day before)
As an ex-software developer - it scares me to make two major software upgrades, at the same time, and then be left wondering "what broke?" (We've done ZP upgrades before, so I'm used to closing the site, backing up the database, deleting then re-copying index.php, zp-core etc)
Best Ideas: -
Thoughts welcome...
Comments
Sorry, I didn't respond as I just noticed. Actually an upgrade from 1.6.x to 1.6.8 should be pretty straightforward. Those are not major updates by any means. We try to not break things unless technically necessary for fixing something wrong. If we really do that on such a smaller release version we note it in the release articles.
Note that a later zpBoostrap may have fixes for the current version that does not work on older ones as well (it should not but it may happen)
Of course since every site (and server) is different we never can say if just you are the one where something really fails. Especially if you do any custom things.
Please consult the release articles for changes. It is strongely recommended to frequently do upgrades because it is most likely less things to consider and fix.
I've since realised I can have both versions of ZpBootstrap running (with different theme names), switch, look, then switch straight back if there's an issue. Including checking customisation.
I'll do that first, then (minutes) later upgrade ZP 1.6.x to 1.6.8...
Yes, you can rename/duplicate the theme's folder. It will even re-use the same options of they are not renamed or otherwise changed.