I thought the permissions screen might make more sense grouped by module and it wouldn't be too much code to change.

CommentFileSizeAuthor
#12 perms.patch2.53 KBSteven
#1 newperm3.png31.53 KBdrumm
user.module_0.diff1.85 KBdrumm
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

drumm’s picture

FileSize
31.53 KB

And this is what it looks like.

ccourtne’s picture

-1

I don't think grouping by module helps admin a site... as a matter of fact it makes it less intuitive because all of my create * permission are now spread all over the place. Maybe make a module column and allow me to sort either by permission name or module.

Zack Rosen’s picture

+1

This makes identifying the permissions to toggle much clearer. Different modules vary greatly in the number of permissions they need and the semantics used to describe them. This makes it hard to identify which permission are associated with which module / functionality. Think of how many times you have installed a module and then found its permissions by looking for gaps in your "administrator" checkbox column. That is an unnecessary and silly interface crutch.

pfaocle’s picture

+1

I'd have to agree with this one: this layout makes it a darn sight clearer what the permissions are for, and is a great help when installing/testing new modules.

matt westgate’s picture

+1

1. It is easier to find new permissions after enabling a module (i.e., look for the module name)

2. Permissions now have context, making the list less daunting to look at. It also is easier to understand how permissions interact with one another, when one knows what module is creating them.

adrian’s picture

+1

This should make it simpler to test out modules.

Gábor Hojtsy’s picture

+1

It is much easier to adjust permissions this way.

Jhef.Vicedo’s picture

+1

Great! With you, administrators will know what are these permissions for, what they do. And the developers, will have a better understanding on where these permissions come from.

Jhef.Vicedo’s picture

+1

Great! With this, administrators will know what are these permissions for. And the developers will have better understanding on where these permissions came from.

Anonymous’s picture

i prefer to add a column for module at the end. then enable optional table sort sorting on that column. that is, keep the current sort by default

Steven’s picture

I'm ambivalent on this patch. For one thing, it spreads the various types of permissions out (administer, access, ...). On the other hand, these types were unofficial.
This patch does make it a lot easier to set up additional modules on an existing site: you no longer have to hunt for the right permissions (and worry that might've missed one). With the patch, it's easy to see what a particular module offers.

So +1 for that.

Steven’s picture

FileSize
2.53 KB

Here's an improved patch, after some discussion. It uses misc/drupal.css for the style rather than inline style. It also changes the table header back to "permission", and says "<module name> module" instead of "<module name>".

Steven’s picture

Applied a cleaned up version to CVS/HEAD.

Anonymous’s picture