Order of updates

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: -

  • Close the site down, update everything, hope for the best
  • Update ZP 1.6.2 to 1.6.8, bring it back up (knowing there will be issues with the Theme), then update ZPBootstrap
  • Update ZPBootstrap, check things are generally OK, then update ZP 1.6.2 to 1.6.8

Thoughts welcome...

Comments

  • acrylian Administrator, Developer
    edited July 12

    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...

  • acrylian Administrator, Developer
    edited July 12

    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.

  • 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

    Minor point (unless I've misunderstood you, in which case, apologies) - Admin/Theme/Duplicate only seems to be available for the stock themes; "Basic", "Garland" etc, not for Themes I've added such as ZpBootstrap.

    Not a showstopper - wish me luck tomorrow morning with ZP 1.6.8 and the latest ZpBoostrap!

  • acrylian Administrator, Developer
    edited July 26

    Seems you are right. I was indeed not aware of that. No idea why that is so. But you can always do that via FTP directly.

  • Seems you are right. I was indeed not aware of that. No idea why that is so. But you can always do that via FTP directly.

    Many thanks (as always) - I'll keep you posted (once I've done the upgrade, had coffee and calmed down...)

  • Update completed without incident - five minutes for the update, 63 minutes to make an (off site) FTP copy of everything including albums in case it went wrong!

  • acrylian Administrator, Developer

    Great all worked out!

  • Update completed without incident

    Spoke too soon (and happy to start a new Discussion...)

    Upgrading appears to have lost the ability for an Admin to be in multiple User Groups, documented as a change in 1.6.6

    I've no right to ask, but what was the reason for the change? It was really handy to have a small number of groups and then "Tony is in both 'Album Manager (Rail)' and 'Album Manager (Road)'"

  • acrylian Administrator, Developer
    edited July 27

    If I recall right the idea was that to us it didn't make sense to have a user in several groups as the group rights could theoretically go against each other. Especially albums can already assign to each users.

    I openly admit that we rarely to never use groups ourselves so maybe were to quick here… I always understood them as kind of "user roles" which they apparently are not really. We happily revert that if it really was a bad idea! Should be pretty easy as - if I recall right - only changed checkboxes to radioboxe. All other code is still in place so current assignments should still work as before.

  • Thanks (as always)

    Should be pretty easy as - if I recall right - only changed checkboxes to radioboxe. All other code is still in place so current assignments should still work as before.

    Job for tomorrow - on the development site (where, of course, we never use groups... Install, yes but we only have two users and they both have full admin)

  • Still playing...

    I always understood them as kind of "user roles" which they apparently are not really.

    That's how we are using them; a "user" can have multiple roles in a smallish organisation, hence the desire that "X" can be a member of both "Album Manager (Canal)" and "Album Manager (Rail)" [and maybe "News Manager" as well]

    Should be pretty easy as - if I recall right - only changed checkboxes to radioboxe. All other code is still in place so current assignments should still work as before.

    I've changed these back - I've also removed a subtle piece of code which converted an array of groups into an array with only one entry; that of the first group. It now seems to function as I wish, but (annoyingly) if a user is in more than one group all the usual tickboxes are enabled - if only one group they are greyed out... It doesn't matter as, on saving, they are ignored; but I like "tidy". Now delving into the /user_group/user_groups-tab.php...

  • acrylian Administrator, Developer

    Okay, I understand the use case. I will look into reverting the changes for the next release. I don't remember all places involved offhand. I'll post here when it is up in the master on GitHub (currently that can direclty be used as there are not many changes although that might become version 1.7 later on).

  • (as always) Many Thanks

  • acrylian Administrator, Developer

    The support build has the multiple groups assignment restored now. The extension should be directly usable with 1.6.8 as there are not yet any that should be related. Please try.

  • The support build has the multiple groups assignment restored now. The extension should be directly usable with 1.6.8 as there are not yet any that should be related. Please try.

    Will do - and thanks (again)

Sign In or Register to comment.