Closed (duplicate)
Project:
CCK Field Permissions
Version:
5.x-1.8
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
26 Mar 2007 at 09:20 UTC
Updated:
17 Jul 2008 at 06:00 UTC
Hey, great module.
I was wondering if it would be possible to add a 'disabled' attribute to inputs that have view permissions set to true, but edit permissions set to false. That way, the user could see the content on the edit form, but not change it. This would, I believe, enhance usability.
Comments
Comment #1
arthurf commentedthis is an interesting idea, though might require a fairly complex interface to make it work- the admin/user/access listing is already quite large, this might double it. Or are you thinking that instead of removing the field, it is just set as disabled?
Comment #2
gollyg commentedI wasn't thinking of any interface changes. If the user can view the information and edit the form this would indicate that they had the necessary priveleges. In this case, rather than removing the component from the edit form, it could be presented to them in a disabled format. That way they could see information that may be relevant to their other options but not change it. In the case where they did not have edit or view permissions the input box would be hidden as is currently the case.
Perhaps there could be a setting that specified the general behaviour for the module so that you could toggle between behaviours.
Just a thought.
Comment #3
arthurf commentedI can see where this would be useful. The problem that I see is that I think it would require an additional permission (something like 'edit, see but not change content') for each field, which gets really messy. However, it is implementable. I'll consider doing it for the next release
Comment #4
gollyg commentedJust to let you know the use case that I encountered - I had a CCK node that was acting as a booking for an event I was setting up. Only the manager could assign a stand number and a few other details, but the rest were editable by the user. It was important that the user knew which stand and other details had been set when they were changing other details, but they were not able to modify them. Disabling the fields provided this ability.
I guess I thought that if the field was set up to be viewed but not edited by the user, this was in itself enough to display the field on the edit form, but I can see how it would not suit everyone so perhaps an extra permission per field would be necessary.
Thanks for considering it.
Comment #5
mrtoner commented+1
This would be similar to my issue at http://drupal.org/node/118404
Comment #6
arthurf commentedThere is code to do this now in cvs. Please grab the latest and let me know if it's what you're looking for.
Comment #7
Vidarls commentedTidying up a bit http://drupal.org/node/173126, same request
Comment #8
designanddraft commenteddrupal 6.x, v6 transparent admin
I am looking for transparent administration, open, visible and sometimes editable admin settings with security. based on permissions, locked individually (as a node?), password protected, view and/or edit choice for admin inserted at the top or bottom of all admin/settings pages. even better, password or radio button next to every settings choice as viewable and/or editable similar to form field protect. a prominent notification to the user, “you can view this page of administration settings, if they require edit, please email administration with your request link”. Possibly even attached comment or site note section, ability to insert instruction or voting widget.
I gather this is the approach taken by adding access control to the core and maybe it is similar to drupal core building. I have been looking at everything I can find and I’m not a programmer yet, so I need to pass what I’ve found on to someone else here. If someone can put these pieces together or have experience with something similar with any version 4,5,6,7. i'm listing this at all of these locations aswell. Rsvp, elisa
http://drupal.org/node/109157 access control
http://drupal.org/node/131101#comment-735943 Add disabled attribute to protected fields
http://drupal.org/node/245900 How to Protect Nodes From Editing on Demand
http://drupal.org/node/31143#comment-796152 Node Privacy by Role not working
http://drupal.org/project/nodeaccess nodeaccess
http://drupal.org/node/126129#comment-703933 password protect a page
http://drupal.org/node/222263#comment-902378 Port of Content access for D6
http://drupal.org/node/29991#comment-51352 Protected content
http://drupal.org/node/13266 Show block to certain users or roles only- Drupal 4.6
http://drupal.org/project/simple_access simple access
http://drupal.org/node/118404#comment-735895 View, but not edit, field at node/xxx/edit
Comment #9
mrtoner commentedPlease post in the forums any requests for custom module development.