content hiding with CCK (or any other module)
navinjathan - December 29, 2008 - 13:47
i want to profile the professors in my univ. I understand i could use CCK to create the "professor profile" page.
Among the details i would be entering include:
Name, Address, tel. no., picture, biography, book listing, audio/video, email ID etc.
But i do not want all the info that is entered by me to be seen by everyone... e.g. telephone. contact, postal address, etc. should be seen by only those in the "admin" group. Is there a way to achieve this?
Content Permissions
I would suggest trying out the Content Permissions module, which is packaged with CCK (it comes with CCK and can be found in the CCK group of modules on the modules page).
I haven't used it yet, but it looks like it will allow you to set field-level permissions for CCK fields, which is just what you need.
Best of luck!
Depending on how exactly you
Depending on how exactly you want that to work, there are:
- content_permissions module, included in cck (previously http://drupal.org/project/cck_field_perms in D5)
- http://drupal.org/project/workflow_fields
- http://drupal.org/project/cck_field_privacy
"CCK Field Permissions"
"CCK Field Permissions" doesn't look to be available for D6.8
Looks like "CCK Field Privacy" tells there's-a-field-but-you-are-not-supposed-to-see-it.... Hmm... if it is so.. thats not really what i want.. the user should not know in the first place that such a field existed!
I will try "Workflow Fields"
include
cck field permission alrady include on D6.8
This module has been rewritten from scratch and is now distributed with the Drupal6 version of CCK as content_permissions module. I extended the functionality so that Views respects the specified permissions.
As mentioned in its project
As mentioned in its project page, cck field perms has become content_permissions and is included in cck.
user management -> permissions
BTW i just found out a possible work-around. I cannot say yet what would be the drawback of adopting this approach... Someone please point out the gaps in this...
Administer -> user management -> permissions
allows me to define "view field_*" permissions for the fields. Can that be used? Consider there's only one group of users - "Anonymous" - that i need to control access to the fields.
This is not a workaround,
This is not a workaround, this is how you set permissions. Those permissions were added by some of the mentioned modules.
err.. okay.. Thanks a lot
err.. okay..
Thanks a lot for the support :-)