Ticket #449 (assigned defect)

Opened 4 years ago

Last modified 3 years ago

mergedLocalRolesWithPath should know about blocking roles

Reported by: fguillaume Assigned to: fguillaume (accepted)
Priority: P2 Milestone: CPS 3.5.0
Component: CPSUserFolder Version: CPS 3.2
Severity: normal Keywords:
Cc:

Description (Last modified by fguillaume)

mergedLocalRolesWithPath should know about blocking roles. Currently it does not take them into account, so misleading information is presented to the user.

This must be changed in all user folders implementing blocking.

Change History

12/09/04 15:24:18 changed by fguillaume

  • status changed from new to assigned.

03/07/05 12:37:05 changed by atchertchian

This bugfix is needed for Messager since we extensively use role blockings.

04/12/05 12:05:32 changed by fguillaume

  • milestone set to CPS 3.3.3.

04/13/05 16:31:51 changed by fguillaume

  • milestone changed from CPS 3.3.3 to CPS 3.3.4.

05/30/05 12:41:27 changed by fguillaume

  • description changed.
  • milestone changed from CPS 3.3.4 to CPS 3.3.5.

08/04/05 20:05:43 changed by fguillaume

  • milestone changed from CPS 3.3.5 to CPS 3.3.6.

09/15/05 20:06:06 changed by fguillaume

  • milestone changed from CPS 3.3.6 to CPS 3.4.0.

10/27/05 14:27:06 changed by atchertchian

Note that CPSDefault localroles management pages needs to know if roles are blocked at current level. This is currently done by looking if the group role:anonymous has '-' in its list of roles at current level. So either mergedLocalRolesWithPath should keep that information (maybe not what it's supposed to do...) either there should be another way to get that kind of information.

10/27/05 17:21:49 changed by fguillaume

Note that the whole and unique point of mergedLocalRolesWithPath is to provide an underlying function for the UI display of local roles.

If it has to be modified, go ahead.

02/22/06 17:59:19 changed by janguenot

  • milestone changed from CPS 3.4.0 to CPS 3.5.0.