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.

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}}