I when we were going to upgrade from Conf 5.1.5 -> 5.2.5 we were lucky to recieve a very critical bug warning from Atlassian on the same day regarding problems with restrictions. The fix was to upgrade to 5.2.4 then to 5.2.5. We ended up holding off on the upgrade.
Just wondering, is this still the case if I wanted to go from 5.1.5 -> 5.3? Or have those bugs been fixed so that I can upgrade directly without any view restrictions going missing?
Thanks
Looks like you were mentioning about this bug/issue: https://confluence.atlassian.com/display/CONFKB/User+specific+page+restrictions+are+removed+during+upgrade+to+Confluence+5.2.4
Actually, this bug only affects customers who upgraded directly from version 5.1.5 or earlier to 5.2.4. The fix was NOT to upgrade to 5.2.4 and then to 5.2.5 but instead to rollback to the previous/pre-upgrade Confluence version or follow through the next steps mentioned in the documentation.
You can upgrade 5.1.5 directly to 5.3 and you shouldn't be encountering the same problem doing so. The bug has been fixed in 5.2.5 and 5.3.
I meant 5.2.3
The fix (workaround) was to install 5.2.3 first then 5.2.4.
I don't see how you won't classify it as a workaround/fix. Because it is.
But thanks for the info. We should be fine going right to 5.3.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the discussion on interview best practices and common pitfalls. Share your experiences and learn from others in the Atlassian Community.
Share you experiences!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.