• Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Highest Highest
    • None
    • 4.2.6
    • None

      PermissionSetter is removed from the Confluence API in 4.2.6. What i can see no deprecation, just removed. This brakes our product RefinedWiki Original Theme for the new confluence versions. 4.2.6+.

      Here it is (4.2.5) http://docs.atlassian.com/atlassian-confluence/4.2.5/com/atlassian/confluence/util/actions/PermissionSetter.html

      And here is it removed: (4.2.6) http://docs.atlassian.com/atlassian-confluence/4.2.6/com/atlassian/confluence/util/actions/PermissionSetter.html

      Is this a mistake or intentionally?

      This cause major problems for us.

          Form Name

            [CONFSERVER-25981] PermissionSetter is removed in Confluence 4.2.6

            The release notes/upgrade guide/plugin dev notes are generally how we communicate such things.

            Jonathan Nolen (Inactive) added a comment - The release notes/upgrade guide/plugin dev notes are generally how we communicate such things.

            SarahA added a comment -

            Thanks for raising this Emil!

            I've added it to the Confluence 4.3 developer notes too: https://developer.atlassian.com/display/CONFDEV/Preparing+for+Confluence+4.3

            SarahA added a comment - Thanks for raising this Emil! I've added it to the Confluence 4.3 developer notes too: https://developer.atlassian.com/display/CONFDEV/Preparing+for+Confluence+4.3

            Hi,
            Thanks for the quick help.

            Yes, we are currently working on a new create space view which is similar to yours but have choose category/subcategory option as well.

            @Sarah thanks for adding a note.

            Cheers

            Emil Sjödin [Refined] added a comment - Hi, Thanks for the quick help. Yes, we are currently working on a new create space view which is similar to yours but have choose category/subcategory option as well. @Sarah thanks for adding a note. Cheers

            SarahA added a comment - - edited

            I have added a note about the problem to the Confluence 4.2.6 – 4.2.9 upgrade notes:
            https://confluence.atlassian.com/display/DOC/Confluence+4.2.6+Upgrade+Notes

            SarahA added a comment - - edited I have added a note about the problem to the Confluence 4.2.6 – 4.2.9 upgrade notes: https://confluence.atlassian.com/display/DOC/Confluence+4.2.6+Upgrade+Notes

            He Emil, this was on oversight on our part. We regret the complications this has caused you. We should have deprecated the class, with a clear explanation as to why.

            That reason is straight forward: while adding the new Space Permission Defaults feature (CONF-2559), we added new methods to the SpaceManager for creating a global Space, one that creates it with no permissions (createPrivateSpace) and modified the existing one to apply the default space permissions configured in the global admin screen (createSpace). There are equivalent methods for creating personal spaces too. By the time you have a reference to the newly created Space, it will already have the relevant permissions applied, making the PermissionSetter obsolete, and downright dangerous to keep using - it has no way of removing permissions that already exist.

            You will need to adjust your code to call the appropriate SpaceManager methods, then modify the space permissions further (should your theme allow it) via calls to the SpacePermissionManager directly. I highly recommend adding support for Space Permission defaults as well, so your users can benefit from the easy administration this provides.

            Richard Atkins added a comment - He Emil, this was on oversight on our part. We regret the complications this has caused you. We should have deprecated the class, with a clear explanation as to why. That reason is straight forward: while adding the new Space Permission Defaults feature ( CONF-2559 ), we added new methods to the SpaceManager for creating a global Space, one that creates it with no permissions (createPrivateSpace) and modified the existing one to apply the default space permissions configured in the global admin screen (createSpace). There are equivalent methods for creating personal spaces too. By the time you have a reference to the newly created Space, it will already have the relevant permissions applied, making the PermissionSetter obsolete, and downright dangerous to keep using - it has no way of removing permissions that already exist. You will need to adjust your code to call the appropriate SpaceManager methods, then modify the space permissions further (should your theme allow it) via calls to the SpacePermissionManager directly. I highly recommend adding support for Space Permission defaults as well, so your users can benefit from the easy administration this provides.

              Unassigned Unassigned
              899018603b05 Emil Sjödin [Refined]
              Affected customers:
              2 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: