Grayside.Org - cck

Spaces Integrating a CCK Field

Grayside — Mon, 26 Jul 2010 20:25:09 +0000

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.

/**
 * Implementation of hook_field_access().
 * Allow View/Edit access to 'field_my_cck_field' only when 'feature_name' is enabled.
 */
function custom_field_access($op, $field, $account, $node = NULL) {
  // Be sure not to affect other fields.
  if ($field['field_name'] != 'field_my_cck_field') {
    return TRUE;
  }
  
  switch ($op) {
    case 'edit':
    case 'view':
      // Make access contingent on whether a given feature is enabled in the current space, such as atrium_book.
      return spaces_access_feature('view', 'feature_name');
  }
}

EDIT: Issue posted to the Spaces queue with patch to add this functionality generically for all fields.

Terms:

Remove CCK Fields from the Node Form

Grayside — Thu, 12 Nov 2009 23:05:04 +0000

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:

function _mysnippet_set_denied(&$elements) {
&nbsp;  foreach (element_children($elements) as $key) {
&nbsp;&nbsp;&nbsp;  if (isset($elements[$key]) && $elements[$key]) {
&nbsp;&nbsp;&nbsp;   // Recurse through all children elements.
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;     _mysnippet_set_denied($elements[$key]);
&nbsp;&nbsp;&nbsp;   }
&nbsp; }
&nbsp; $elements['#access'] = FALSE;
}

Terms:

CCK Fields and the Open Atrium Node Form

Grayside — Wed, 11 Nov 2009 00:04:09 +0000

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.
Move your CCK fields under that group.

Voilà! Make it collapsible as you like.

Terms:

Field Permissions Plus

Grayside — Wed, 23 Sep 2009 20:03:39 +0000

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.

Field Permissions Plus makes Field security behave more akin to the rest of the Drupal Permissions world.

Content Permissions Doesn’t Play Nice?!

Well, Content Permissions is fine. But it implements CCK’s hook_field_permissions(), and that function is just looking for an excuse to deny access. By replacing it, it becomes possible to create complex permission schemes with a positive perspective- and a sparse grid of checkboxes.

Different from the Competitors

CCK Private Fields and CCK Field Privacy both operate based on node-by-node approvals, user relationships, and so on. This module provides static permissions.

Why the Name?

This module was partially inspired by #323950 Edit own field permission. In that thread, creating a “Content Permissions Plus” was proposed to solve the problem, because it is too niche a case to integrate into CCK directly. To avoid the confusion of a project specifying Content Permissions, and developer confusion with the CCK’s API, Field Permissions Plus was named. The “plus” is all about the additive nature of the permissions it provides.

{{dp:field_permissions_plus|Field Permissions Plus}}
{{dp:cck|CCK}}

Terms:

field-permissions-plus

Field Permissions Plus: 2.x Already?!

Grayside — Tue, 22 Sep 2009 23:39:48 +0000

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

Tonight, a new release will be packaged that separates the View/Edit Own functionality from the core of FPP, creating a new sub-module dubbed Own Field Access. If you decide to test the development version, be sure to enable this module. If you do not uninstall FPP 1.x, all the permissions will still be there with all the same boxes checked.

The biggest difference in 2.x is the new hook- hook_field_access_plus(). This function should be implemented exactly the same as CCK’s hook_field_access, except anything implemented with the _plus version will be deemed an exclusive, instead of inclusive, means of access.

With Field Permissions Plus installed, you can now write two kinds of Field Access modules to create your complex Field Access scheme.

Terms:

Field Permissions Plus: Complex Access Schemes

Grayside — Wed, 09 Sep 2009 22:09:29 +0000

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.

What does View Own (or Edit Own) mean? Well, CCK fields are attached to nodes. If you own the node, you own the fields. This permission enables an author to see (or edit) all the field content associated with his own nodes.

In the future, FPP will be expanded as a framework so other modules can provide additional permissions to expand on how a field might become editable or visible.

{{dp:field_permissions_plus|Field Permissions Plus}}
{{dp:cck|CCK}}

Terms: