Hi,

just looking at CCK and contemplate again and wondering if there's a feature or enhancement already to VIEW certain fields (or groups) just by user-role or enable/disable that via a single custom privilege

I'd need only a simple scheme

- normal users
- admin users (they see all the fields)

Your help is appreciated

Christoph

Comments

iandickson’s picture

You can probably use a variation of this in contemplate...

http://drupal.org/node/86241

Ian Dickson - community specialist.
www.emint.org - Association of Online Community Professionals

Christoph C. Cemper’s picture

great - thanks for the link - will check it

memtkmcc’s picture

there is new module:

http://drupal.org/project/cck_field_perms

HTH
Adam

Christoph C. Cemper’s picture

wow - cool - that was fast!

Christoph C. Cemper’s picture

Adam,

I just tested your 5.x version and found that it only gives us create / update privileges,
but the goal is to HIDE information from anon users as you wrote on the project page
(anon cannot create/update nodes ANYWAY)

did you plan or forget about this one?

thanks & best
christoph

memtkmcc’s picture

Chris,

I'm just user, not developer, the module was submitted by Arthur:
http://drupal.org/user/27259
please re-send this message to Arthur
I will be able to confirm my own results a bit later since I am
still testing this new module

HTH,
Adam

*UPDATE*

yes, it seems module description suggest it gives control over VIEW fields,
but the .info makes it clear:
"description = Allows admin to restrict create and update access on specific cck fields."

there is note:
"Currently this module only supports creating and updating, it does not change the display of the node."

but at the same time it says also:
"Using this module you can allow only registered users to have access to that field."

I feel it is confusing

Christoph C. Cemper’s picture

Thanks, I mailed him and created this issue

http://drupal.org/node/105569

However, as I wrote,
anon ussers cannot create/update nodes ANYWAY (at least in NONE of my systems)
so my major prio is the view priv

cheers,christoph

--- http://www.cemper.com
--- http://weblog.cemper.com
--- http://www.marketingfan.com

arthurf’s picture

My original use case did not require having view restrictions. It seemed like this could be handled on the theming side, however, since it appears to be in demand, I've put it into the 4.7 and 5.0 versions of the module.