I installed module, added the permission for admin for cck_field-perms, and to the specific cck field (which is a select list/text type), I wanted the field available for admin and not authenticated users. This specific field is linked to a filter that sends the
specific content to a special block. However when logging in as a regular "authenticated user" I can still see
the field and use it, its as if the cck field permissions module doesnt exist...

Comments

Gidgidonihah’s picture

I'll second this. I just installed the most recent version and set it so that a certain section couldn't be edited by anyone but the superuser. It simply didn't change anything.

dkoffler’s picture

I also thought this module was broken. I enabled perms for the field, setup my ACL and all users still saw my restricted fields. I finally figured out the issue. It appears to be a bug in the "create" permission. When users have create permission they can see the field.

The problem with removing "create" permission is that default values don't get populated. so for instance if you want to have a status field on a node that's hidden from anonymous users and has a default value of "unprocessed", you're out of luck. The only default value you can get is null if the user can't see the field.

liquidcms’s picture

I have all fields enabled for this module and for my limited role i have no permissions (create, edit, own) set for any of the fields for this type and i see only one of the fields not showing - the rest are there and editable.

Something is interfering with something. (my rev is latest 5.x-1.10)

jgoldfeder’s picture

It would appear that the module hasn't kept up with CCK. I would gamble that if someone did a fresh install of CCK that was out at the time this was last updated, it would work. However, that really isn't a solution.

Per author: This module is currently in need of a new maintainer. I don't have time for it these days and it seems many people want it.

I would suggest that this module be marked as not being updated (over 8 months without an update) and no longer operates as intended (which is a shame since I could use this).

diegohermes’s picture

Hope someone could update this module to become compatible with latest version of CCK.

bsherwood’s picture

I could really use this module. To bad it doesn't work.

It just seems to me, this module tackles a pretty big issue. Shouldn't something like this belong in CCK core?

richard.e.morton’s picture

Title: Simply does not work » Does work but has bugs
Component: Miscellaneous » Code
Priority: Normal » Critical

It does work for me, but I am only restricting the viewing of fields that are private (such as an events location)

However there are two bugs I have found
1. Hide entire group doesn't work - there is a single checkbox in teh cck field permissions to add access control to the gorup as a whole. but this doesn't work at all
2. I get the following error on my home page, althought stangely, other than looking ugly it does not seem to cause any problems

* warning: Invalid argument supplied for foreach() in /var/www/vhosts/plusgroups.org.uk/httpdocs/b/modules/cck_field_perms/cck_field_perms.module on line 77.
* warning: Invalid argument supplied for foreach() in /var/www/vhosts/plusgroups.org.uk/httpdocs/b/modules/cck_field_perms/cck_field_perms.module on line 77.

despite the code version box above, I am using 1.10 for Druapl 5 and I am using the latest drupal 5 (5.6)

Rich

antipix’s picture

Version: 5.x-1.5 » 5.x-1.10

It does work for me too !!!
But i confirm that hide entire group doesn't work at all.

antipix’s picture

any idea how we could fix the "hide entire group" bug ?

asugene’s picture

Component: Code » Miscellaneous
Category: support » task
Priority: Critical » Normal

Since I could not get this to work either with the updated version of CCK, I looked elsewhere. I found out that the new version of Workflow supports the function of this module. http://drupal.org/project/workflow

mennonot’s picture

Asugene,

Can you say more about how you got the workflow module to do field based permissions? I looked in the readme.txt and the closest I found was the Workflow Access module which is described thusly:

The workflow package contains an additional module, workflow access. This module allows workflow administrators to set which roles can access nodes based on their state. You can also set edit and delete permissions by state.

This doesn't appear to include permissions for individual fields. Am I missing something? For my purposes, any way to have notes for a given node that are viewable by admin only would work. Is there a way Workflow Access can provide this?