Posted by KarenS on June 26, 2009 at 3:04pm
| Project: | Permissions API |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | ebeyrent |
| Status: | closed (fixed) |
Issue Summary
I realize this module is intended to be only an API, but one easy way to illustrate how it works would be to include an example. This code creates a fieldset above the User permissions page that allows you to grant all or revoke all permissions by module and role. It's a pretty simple addition, a very useful feature, and a nice illustration.
I have a bit of css that I use to float these boxes next to each other, which you can use or not.
Also, this patch adds in the 'core = 6.x' line in the .info file which is necessary to even be able to enable it.
| Attachment | Size |
|---|---|
| permissions.patch | 3.13 KB |
Comments
#1
And a screenshot.
#2
As you said, this is merely an API, provided specifically to help people avoid the access control page. However, I agree with you there there is a need for this.
Maybe the best thing to do would be to add a contrib module called Permissions UI; something to layer on top of the existing access control page. What do you think?
#3
yep, makes sense to me. Are willing to add it as an extra module within Permissions API? I'm trying to avoid creating and maintaining a new project for such a small thing.
Also, not the missing line in the .info file. I should do a separate patch for that, but didn't have time.
#4
Sounds like a plan. I'll add it as a contrib module within Permissions API.
Permissions UI? Permissions Extra?
#5
Where's the permissions_api.css?
#6
OK, here is a whole package, called Permissions Reset (since that's all it does).
#7
I've committed to cvs, but haven't tried it out yet...
#8
That was fast :)
#9