Suggestion for User Permissions
the page Users Permissions can be *verry* long. Borring click so much checkboxes I suggest add a nice Global Checkbox in each role header, and using jQuery should be that simple: $(function() { $('#check_all_role1').Click(function() { $('.check_role1').val(this.value); } } How can I help with that, to add in Drupal 6 final release? Its time yet? What PHP file, in core, should I change it? any hook? Sorry for so much noob questions, this is probably documented in Drupal.org, but I didnt find. regards Feijó
Yes PLEASE add this! Alessandro Feijó wrote:
the page Users Permissions can be *verry* long. Borring click so much checkboxes
I suggest add a nice Global Checkbox in each role header, and using jQuery should be that simple:
$(function() { $('#check_all_role1').Click(function() { $('.check_role1').val(this.value); } }
How can I help with that, to add in Drupal 6 final release?
Its time yet?
What PHP file, in core, should I change it? any hook?
Sorry for so much noob questions, this is probably documented in Drupal.org, but I didnt find.
regards Feijó
-- Sean Robertson Web Developer NGP Software, Inc. seanr@ngpsoftware.com (202) 686-9330 http://www.ngpsoftware.com
I will, eventually :) jQuery made my life soooooooo much easy!!! damm :)) Feijó ----- Original Message ----- From: "Sean Robertson" <seanr@ngpsoftware.com> To: <development@drupal.org> Sent: Wednesday, November 28, 2007 6:45 PM Subject: Re: [development] Suggestion for User Permissions Yes PLEASE add this! Alessandro Feijó wrote:
the page Users Permissions can be *verry* long. Borring click so much checkboxes I suggest add a nice Global Checkbox in each role header, and using jQuery should be that simple: $(function() { $('#check_all_role1').Click(function() { $('.check_role1').val(this.value); } } How can I help with that, to add in Drupal 6 final release? Its time yet? What PHP file, in core, should I change it? any hook? Sorry for so much noob questions, this is probably documented in Drupal.org, but I didnt find. regards Feijó
-- Sean Robertson Web Developer NGP Software, Inc. seanr@ngpsoftware.com (202) 686-9330 http://www.ngpsoftware.com
On Nov 28, 2007 5:48 PM, Alessandro Feijó <patrao@legendas.feijo.info> wrote:
I will, eventually :)
You might want to take a look at the issue where these check-all boxes were added: http://drupal.org/node/84961#comment-449568 I'm not saying that should be set in stone, but when those select-all boxes were added they were purposefully not added to the permissions page because of the potential for accidentally doing a lot of damage on that form. In general, there's no need to ask whether something should be added. Just make a patch and create an issue. Regards, Greg -- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
There is more than one way to look at it though. Even if you did do a check all box and accidentally checked the wrong column, you could just refresh the page without saving it. How about instead modifying jTooltips to give a nice permissions page specific description when you mouseover each checkbox. Greg Knaddison wrote:
On Nov 28, 2007 5:48 PM, Alessandro Feijó <patrao@legendas.feijo.info> wrote:
I will, eventually :)
You might want to take a look at the issue where these check-all boxes were added: http://drupal.org/node/84961#comment-449568
I'm not saying that should be set in stone, but when those select-all boxes were added they were purposefully not added to the permissions page because of the potential for accidentally doing a lot of damage on that form.
In general, there's no need to ask whether something should be added. Just make a patch and create an issue.
Regards, Greg
Giving a permission to the authenticated user and the anonymous users gives it to all roles. If you are speaking of giving a single role all permissions, I would be careful. It would be better for modules to set defaults for their permissions and then change each permission individually. On Nov 28, 2007, at 4:41 PM, Greg Knaddison wrote:
On Nov 28, 2007 5:48 PM, Alessandro Feijó <patrao@legendas.feijo.info> wrote:
I will, eventually :)
You might want to take a look at the issue where these check-all boxes were added: http://drupal.org/node/84961#comment-449568
I'm not saying that should be set in stone, but when those select-all boxes were added they were purposefully not added to the permissions page because of the potential for accidentally doing a lot of damage on that form.
In general, there's no need to ask whether something should be added. Just make a patch and create an issue.
Regards, Greg
We really need this feature from a usability standpoint. When we set up new sites, we create an Admin role that is assigned to someone at our client's office. They should have permissions to do nearly everything on the site. Pretty much the only thing I don't give them is access to the devel module. Checking all of those damned permissions is a freaking pain in the ass. It'd be much better to be able to click check all (maybe you get a warning alert here?) and then uncheck the one or two I don't want them to have, rather than being forced to click a hundred fifty times as I currently am. Darren Oh wrote:
Giving a permission to the authenticated user and the anonymous users gives it to all roles. If you are speaking of giving a single role all permissions, I would be careful. It would be better for modules to set defaults for their permissions and then change each permission individually.
On Nov 28, 2007, at 4:41 PM, Greg Knaddison wrote:
On Nov 28, 2007 5:48 PM, Alessandro Feijó <patrao@legendas.feijo.info> wrote:
I will, eventually :) You might want to take a look at the issue where these check-all boxes were added: http://drupal.org/node/84961#comment-449568
I'm not saying that should be set in stone, but when those select-all boxes were added they were purposefully not added to the permissions page because of the potential for accidentally doing a lot of damage on that form.
In general, there's no need to ask whether something should be added. Just make a patch and create an issue.
Regards, Greg
-- Sean Robertson Web Developer NGP Software, Inc. seanr@ngpsoftware.com (202) 686-9330 http://www.ngpsoftware.com
On Nov 28, 2007 1:55 PM, Sean Robertson <seanr@ngpsoftware.com> wrote:
We really need this feature from a usability standpoint. When we set up new sites, we create an Admin role that is assigned to someone at our client's office. They should have permissions to do nearly everything on the site. Pretty much the only thing I don't give them is access to the devel module. Checking all of those damned permissions is a freaking pain in the ass.
In that case, it seems like the best place to deal with this issue is an install profile with an "admin" role which gets every permissions by default.
On 28.Nov.2007, at 07:43 PM, Florian Loretan wrote:
In that case, it seems like the best place to deal with this issue is an install profile with an "admin" role which gets every permissions by default.
OMFG! These are the "little things" that Drupal should be adopting from a usability standpoint. Why assume that only person will be admin? Why assume that #1 is the only one to get to the site while it's offline? I have a friend, John Simon, who is a software artist and he has described coding as creative writing. If it is, I have a whole dissertation to write about Drupal's #1 user. The fact that it remains "god-like" and without a role .... we're slipping into Lacanian territory here. Here's a good interview by John http://www.numeral.com/articles/atkins/decodingdigitalart/ decodingdigitalart.html Here's an example of software art, btw (the patriarchy at home is Mark Napier) http://artport.whitney.org/commissions/codedoc/ OK, back to lurking, liza Liza Sabater, Publisher www.culturekitchen.com www.dailygotham.com
Quoting "blogdiva@culturekitchen.com" <blogdiva@culturekitchen.com>:
On 28.Nov.2007, at 07:43 PM, Florian Loretan wrote:
In that case, it seems like the best place to deal with this issue is an install profile with an "admin" role which gets every permissions by default.
OMFG!
These are the "little things" that Drupal should be adopting from a usability standpoint. Why assume that only person will be admin? Why assume that #1 is the only one to get to the site while it's offline?
Let's fix it; see http://drupal.org/node/196296 Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
You might check out the Admin Role module http://drupal.org/project/adminrole cheers, -tao Sean Robertson wrote:
We really need this feature from a usability standpoint. When we set up new sites, we create an Admin role that is assigned to someone at our client's office. They should have permissions to do nearly everything on the site. Pretty much the only thing I don't give them is access to the devel module. Checking all of those damned permissions is a freaking pain in the ass. It'd be much better to be able to click check all (maybe you get a warning alert here?) and then uncheck the one or two I don't want them to have, rather than being forced to click a hundred fifty times as I currently am.
Darren Oh wrote:
Giving a permission to the authenticated user and the anonymous users gives it to all roles. If you are speaking of giving a single role all permissions, I would be careful. It would be better for modules to set defaults for their permissions and then change each permission individually.
On Nov 28, 2007, at 4:41 PM, Greg Knaddison wrote:
On Nov 28, 2007 5:48 PM, Alessandro Feijó <patrao@legendas.feijo.info> wrote:
I will, eventually :) You might want to take a look at the issue where these check-all boxes were added: http://drupal.org/node/84961#comment-449568
I'm not saying that should be set in stone, but when those select-all boxes were added they were purposefully not added to the permissions page because of the potential for accidentally doing a lot of damage on that form.
In general, there's no need to ask whether something should be added. Just make a patch and create an issue.
Regards, Greg
Quoting Darren Oh <darrenoh@sidepotsinternational.com>:
Giving a permission to the authenticated user and the anonymous users gives it to all roles. If you are speaking of giving a single role all permissions, I would be careful. It would be better for modules to set defaults for their permissions and then change each permission individually.
IMO, the set/unset all function should be applied to created roles at the time of creation only. This solves the issues being discussed. Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
When creating a site admin role, there are several items I do not turn on for the users, nor do I want them on for those sites. Creating roles is generally a one time deal per role. It is something that 'even it is a 'pain' or 'inconvenient' should not be 'globally allowed turn on'. This comes to a security issue in that you should determine your permission model. It is not an 'OMFG usability issue'. It is a security issue. I have always liked the default 'everything is off' model because I then have to turn on things. It may be inconvenient but it doesn't seem to be something to go into hysterics over or claim usability as an overarching trump card. If we are going to do this, then allowing it only once per role 'at time of creation' seems the least harmful approach to easily allowing people to shoot themselves in the foot to solve some users 'inconvenience'. Steven Peck :: www.blkmtn.org On Nov 29, 2007 5:14 AM, Earnie Boyd <earnie@users.sourceforge.net> wrote:
Quoting Darren Oh <darrenoh@sidepotsinternational.com>:
Giving a permission to the authenticated user and the anonymous users gives it to all roles. If you are speaking of giving a single role all permissions, I would be careful. It would be better for modules to set defaults for their permissions and then change each permission individually.
IMO, the set/unset all function should be applied to created roles at the time of creation only. This solves the issues being discussed.
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
----- Original Message ----- From: "Greg Knaddison" <greg@pingvox.com> To: <development@drupal.org> Sent: Wednesday, November 28, 2007 7:41 PM Subject: Re: [development] Suggestion for User Permissions On Nov 28, 2007 5:48 PM, Alessandro Feijó <patrao@legendas.feijo.info> wrote:
I will, eventually :)
You might want to take a look at the issue where these check-all boxes were added: http://drupal.org/node/84961#comment-449568 I'm not saying that should be set in stone, but when those select-all boxes were added they were purposefully not added to the permissions page because of the potential for accidentally doing a lot of damage on that form. --- I see... In my point of view, who administer a site must have good understand of the metter, or dont touch it at all :)) In general, there's no need to ask whether something should be added. Just make a patch and create an issue. --- I'm new on that, there is a tutorial to help who never helped before? Feijó
On Nov 28, 2007 8:15 PM, Alessandro Feijó <patrao@legendas.feijo.info> wrote:
I'm new on that, there is a tutorial to help who never helped before?
In that case, welcome! There is a whole handbook section dedicated to this at http://drupal.org/patch If you look at the structure and dig in based on which parts seem most applicable you should be able to answer any questions. If you can't find what you need there, feel free to email me back off-list. Regards, Greg -- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
On the surface adding a checkbox to set/unset all permissions for a given role seems questionable. While it makes it easy to set/unset all permissions for a given role I am not sure that is a wise thing to do. From my perspective it is better to make people consider what they are allowing a given role to do. Allowing someone to select all at once is likely to lead to problems as unexperienced users select all and save without relizing they have just granted some users an open pass to their web site. Nevets
participants (11)
-
Alessandro Feijó -
blogdiva＠culturekitchen.com -
Darren Oh -
David Norman -
Earnie Boyd -
Florian Loretan -
Greg Knaddison -
Sean Robertson -
Steve Ringwood -
Steven Peck -
Tao Starbow