Grayside.Org

I wanted to make a CCK Field available only when a given feature was enabled. It turns out it’s really easy.

CCK comes with a hook_field_access() hook (see content_access()). Any implementation of this function that returns FALSE for a given field results in that field being denied to the user.

By implementing this function with a Spaces API call instead of the content_permissions module approach of a new, field-specific permission, all kinds of magic becomes possible.

Read on for demonstration code.

There is a fine tutorial on drupal.org describing How to set the disabled attribute of a CCK field on your node add/edit form. All that does is deactivate the input widget without removing the clutter. Let’s get rid of the form elements entirely.

OpenAtrium has some pretty slick styling of it’s node add/edit form. Unfortunately, when you add a CCK field to it, you get something comparatively under-styled and in the main column of the form.

If you want to get that slick styling and move the CCK fields to the right, try the following:

1. Go to admin/build/modules and enable the Fieldgroup module under CCK.
2. Go to the Manage Fields page for your content type. Create a new group, the machine name starting as group_sidebar.

This Drupal module provides a more flexible framework from granting and restricting access to the content of CCK fields.

Field Permissions Plus has barely been released, but FPP 6.x-2.x-dev is already making progress.

This post refers to Field Permissions Plus 1.x

This Drupal module provides View Own and Edit Own permissions for CCK fields. As a necessary step, Field Permissions Plus supercedes CCK’s Content Permissions module so the View/Edit [all] permissions it provides play nice. With this module, if you give a role the ability to View a field, or to View Own a field, they will be able to see it.