| 1 | | When a new project ("''environment''") is created, a set of defaultpermissions is automatically granted.If the project administrator edits the project config file (`trac.ini`)to disable some module(s), following the[wiki:TracDev/PluginDevelopment#Disablingbuiltincomponentsdocumentation], the project ends up in a dead-lock situation:`trac-admin` refuses to revoke '''existing''' permissions if the actionis defined in the disabled component. This permission for this action hasnot been set by the administrator, but by the `trac-admin` script atproject creation time.This situation is quite confusing for the administrator: with the currentimplementation, he/she should ''first' remove unwanted permissions for amodule he/she does not want to use. If it fails to do so, he/she gets theinfamous 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 removethe following permissions: `BROWSER_VIEW`, `CHANGESET_VIEW`, `FILE_VIEW`,`LOG_VIEW` 1. I think #2307 is the expression of this general issue, specializedfor TracReports. |
| | 1 | When a new project ("''environment''") is created, a set of defaultpermissions is automatically granted.If the project administrator edits the project config file (`trac.ini`) todisable 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 isdefined in the disabled component. This permission for this action has notbeen set by the administrator, but by the `trac-admin` script at projectcreation time.This situation is quite confusing for the administrator: with the currentimplementation, he/she should ''first'' remove unwanted permissions for amodule he/she does not want to use. If it fails to do so, he/she gets theinfamous 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 removethe following permissions: `BROWSER_VIEW`, `CHANGESET_VIEW`, `FILE_VIEW`,`LOG_VIEW` 1. I think #2307 is the expression of this general issue, specialized forTracReports. |
