[Trac-tickets] Re: [The Trac Project] #2546: Cannot remove default permissions when the module defining the action is disabled

[The Trac Project]

#2546: Cannot remove default permissions when the module defining the action is
disabled
------------------------+---------------------------------------------------
 Reporter:  eblot       |        Owner:  daniel
     Type:  defect      |       Status:  new   
 Priority:  normal      |    Milestone:        
Component:  trac-admin  |      Version:  devel 
 Severity:  minor       |   Resolution:        
 Keywords:              |  
------------------------+---------------------------------------------------
Old description:

> When a new project ("''environment''") is created, a set of default
> permissions is automatically granted.
>
> If the project administrator edits the project config file (`trac.ini`)
> to disable some module(s), following the
> [wiki:TracDev/PluginDevelopment#Disablingbuiltincomponents
> documentation], the project ends up in a dead-lock situation:
>
> `trac-admin` refuses to revoke '''existing''' permissions if the action
> is defined in the disabled component. This permission for this action has
> not been set by the administrator, but by the `trac-admin` script at
> project creation time.
>
> This situation is quite confusing for the administrator: with the current
> implementation, he/she should ''first' remove unwanted permissions for a
> module he/she does not want to use. If it fails to do so, he/she gets the
> infamous error message:
> {{{
> Command failed: <action> is not a valid action.
> }}}
>
> ==== Notes ====
>  1. if `repository_dir` is not set in `trac.ini`, ''versioncontrol''
> actions are automatically disabled, and the administrator cannot remove
> the following permissions: `BROWSER_VIEW`, `CHANGESET_VIEW`, `FILE_VIEW`,
> `LOG_VIEW`
>  1. I think #2307 is the expression of this general issue, specialized
> for TracReports.

New description:

 When a new project ("''environment''") is created, a set of default
 permissions is automatically granted.

 If the project administrator edits the project config file (`trac.ini`) to
 disable some module(s), following the
 [wiki:TracDev/PluginDevelopment#Disablingbuiltincomponents documentation],
 the project ends up in a dead-lock situation:

 `trac-admin` refuses to revoke '''existing''' permissions if the action is
 defined in the disabled component. This permission for this action has not
 been set by the administrator, but by the `trac-admin` script at project
 creation time.

 This situation is quite confusing for the administrator: with the current
 implementation, he/she should ''first'' remove unwanted permissions for a
 module he/she does not want to use. If it fails to do so, he/she gets the
 infamous error message:
 {{{
 Command failed: <action> is not a valid action.
 }}}

 ==== Notes ====
  1. if `repository_dir` is not set in `trac.ini`, ''versioncontrol''
 actions are automatically disabled, and the administrator cannot remove
 the following permissions: `BROWSER_VIEW`, `CHANGESET_VIEW`, `FILE_VIEW`,
 `LOG_VIEW`
  1. I think #2307 is the expression of this general issue, specialized for
 TracReports.

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/2546>
The Trac Project <http://trac.edgewall.com/>