Use a tabbed browser like Iceweasel. Install fresh Drupal 6.0. Enable/install some modules. Go to "administer by module". Using the middle mouse button or whatever you use to open a link into a new tab, click on all "permissions" links corresponding to the new modules you enabled. You now have lots of tabs with permissions. You configure the first one and click Save and close the tab. Then you get to the second tab, you configure the permissions for the second module and you click save. But the permissions page was loaded before you clicked Save for the first module. Therefore, any changes you made to the first module's permissions are now gone!

We need a way to make this more compatible with the tabbed browser paradigm. We ought to keep a central permissions page listing all permissions, but we should perhaps have a second way to set permissions only for a specific module.

The obvious answer (not to use tabs) doesn't work for sites that have huge numbers of modules that may have to be enabled and disabled several times. In such cases the admin with little time in their hands wants to know which modules from the whole list displayed in the permissions page were installed lately.

Perhaps another solution would be simply to highlight the newly installed modules in the permissions page.

Comments

pasqualle’s picture

Title: Permissions by module has usability issues with tabbed browsers » Permissions by module
Component: admin.module » user system

don't use tabs. it is absolutely evident that your permissions what you set on the first page will be lost when you save the permissions on the second tab..

possible solution would be to show the permission for one module only. for example when you click "configure permissions" on the module help page..

pasqualle’s picture

Version: 6.0 » 7.x-dev
cyu’s picture

Part of what this module aims to do, http://drupal.org/project/filter_perms would give you what you want. When clicking on the 'Configure Permissions' link from the 'administer by module' page you will get only that module's permissions and it will not overwrite permissions of other modules when that page is saved. Just coded it up yesterday, so still very dev but you might want to give it a try.

Anonymous’s picture

Status: Active » Closed (won't fix)

Since this hasn't received much support in 3+ years, closing.