cck

Jul

2010

Grayside

Add new comment

Spaces Integrating a CCK Field

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.

Terms:

Nov

2009

Grayside

Add new comment

Remove CCK Fields from the Node Form

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.

To actually remove the field from the input form, change the _mysnippet_fix_disabled() function to the following:

Terms:

Nov

2009

Grayside

CCK Fields and the Open Atrium Node Form

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:

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

Terms:

Sep

2009

Grayside

Add new comment

Field Permissions Plus

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

It provides a simple framework by which you can create multiple modules which cooperate in finding some method of granting access to site users, as opposed to CCK’s core permission scheme in which field access modules are effectively looking for ways to deny access.

Terms:

field-permissions-plus