I seem to be running into this issue everywhere lately. I've been working on a greasemonkey script the last few days that adds a check all and a uncheck all option to the user permissions page. I'll share this when its complete if anyone else would find it useful. At my office we usually maintain an admin role on the sites we work on so that the developers don't do all of their work as user 1. I have used admin role before, and didn't like the fact that it took the decision process away from me, sometimes you want to limit access even for the administrator. I agree that a check all button is extremely dangerous in the wrong hands, and shouldn't be available to everyone. For anyone looking for a quick workaround I was listening to the recent Lullabot 50 tips podcast this morning, and they mentioned using the web developer extension for Firefox and selecting forms -> populate forms, to check all of the boxes if you are on the roles individual permissions page. Mark On Nov 29, 2007, at 4:40 PM, Steven Peck wrote:
I cannot possibly conceive of a situation where I would use this 'feature/configuration accident waiting to happen' on a production site. Looks very nice as a contributed module.
Your point (not 'the point), desired feature... My point, unacceptable risk.
Nice contributed module.
-Steven
On Nov 29, 2007 1:22 PM, blogdiva@culturekitchen.com <blogdiva@culturekitchen.com> wrote:
The point is that it should NOT be a module but a default feature of the system.
/ liza
On 29.Nov.2007, at 03:42 PM, Simon Roberts wrote:
Agree. If someone really wants an "admin role" they can use (ta-da)