I was directed to this module by someone who thought it might be able to easily do what I need. I've got some fields on some custom content that are view references, with set default values and arguments that I do not want anyone else to change. When the new content is created, I want those default values to be entered for that view reference field, and I don't want the user to be able to see or affect it at the time of creation and editing of the node.

I tried this module, but after a bit of trial-and-error experimentation, I don't think it can currently do this. When I disable "create" permissions, the user doesn't see the field at the time of node creation, but when they save the node, I later see that the default values were completely left out.

Is there a veroin of tis that allows default values to remain while restricting permission to see and change them?

CommentFileSizeAuthor
#2 cckdisable.zip2.01 KBdagmar

Comments

hillaryneaf’s picture

hillaryneaf commented

I'm looking for the same thing. Have you found anything to do this??

dagmar’s picture

dagmar
Primary language Spanish
Location Argentina
commented
StatusFileSize
new cckdisable.zip2.01 KB

Hello:

I have developed a module called disable cck. It allows to define witch roles can edit the content of the each cck field in a content type.
The module works fine.

However the final result is very unsafe.

Webdeveloper and Firebug (Firefox extensions) can modify the "disable state" of a field.
Then, though you can alter the node form to disable some field, the users will can skip this restriction through webbrowser extensions.

Possible solution...
I think the ideal solution is, hide the cck field like cck permision does, but save the default values of the cck using drupal_execute()

There is an example in: http://civicactions.com/blog/cck_import_and_update

Caution: Cck Disable module is not for production use

Sorry for my english
Mariano

Vidarls’s picture

Vidarls commented
Status: Active » Closed (duplicate)

http://drupal.org/node/118513