[support] CCK field permission

[Joel Willers]

Worked perfectly, although it confused me that the list wasn’t already in Permissions.  Since I have about thirty content types, it took me a while to go through each field and set the permissions settings, just to go into the Permissions area and then actually SET the permissions settings.

 

From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On Behalf Of Ted
Sent: Thursday, February 24, 2011 2:58 PM
To: support at drupal.org
Subject: Re: [support] CCK field permission

 


http://drupal.org/project/field_permissions

Allows you to separate editing permissions for a given field on new and existing nodes.

This won't work if you need to work only with existing nodes.

Ted

On 2/24/2011 3:51 PM, Joel Willers wrote: 

Drupal 6.20 – I want a user to be able to select a node reference for a Content Type, but, once set, they can’t go back and edit it again.  I’m actually using URL Node Reference, which works great, but if I don’t allow editing of that field, it doesn’t save the Node reference, but if I allow editing of the field, adding works fine, but when they go back and edit the Content, the Node reference comes up.  

I have the Content Type set to 404 if Argument isn’t present, and the same behavior on editing, but it doesn’t seem to matter on editing.

Any ideas how I might prevent my users from changing that node reference?

Joel

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20110224/1682bdd5/attachment-0001.html