Opened 6 years ago

Closed 6 years ago

#2023 closed defect (fixed)

Using the "MultiPermissions" class to set permissions on new items prevents default sharing to project

Reported by: Nicklas Nordborg Owned by: everyone
Priority: major Milestone: BASE 3.9.1
Component: core Version:
Keywords: Cc:

Description

The MultiPermissions class is useful for setting multiple permissions to multiple items in one go and also supports preserving existing permissions.

When used with new items there is a flaw. If permissions is only set for groups (and/or users) but not projects one would expect that the default project permissions are set. This is not the case.

The flaw is that the implementation always call both setItemKey() and setProjectKey() methods even if there is no change. The fix is to only call the setter method if the new keys are different from the old keys.

Change History (1)

comment:1 Changed 6 years ago by Nicklas Nordborg

Resolution: fixed
Status: newclosed

(In [7182]) Fixes #2023: Using the "MultiPermissions?" class to set permissions on new items prevents default sharing to project

Note: See TracTickets for help on using tickets.