Closed (fixed)
Project:
CCK Field Permissions
Version:
5.x-1.10
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
22 Jul 2007 at 10:39 UTC
Updated:
3 Mar 2008 at 23:42 UTC
I want to use CCK Field Permissions to allow my registered users to edit one (and only one) cck field in a CCK-built node. However, it seems the only way to allow my users access to that node is to make the entire node editable for registered users. When this happens the ONLY fields I can "lock down" are CCK-specific fields -- in other words, the title, taxonomy and body fields, which are default fields to every CCK node, will be editable.
Is there a way to lock down these non-CCK fields as well?
Comments
Comment #1
Grammarian commentedI have a CCK type which should always have the same title. I'd also like to know how to make the title of thit content type uneditable by the user, just to keep it simple.
Comment #2
Vidarls commentedThere are a hole host of modules to help you achieve this.
On the top of my head:
- There is an autotitle module
- There are at least two modules that tries to limit who can add categories
- Use cck fields for everything else (including body) to allow cck_field_perms to limit access
Comment #3
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.