I have a use case that led me to this module. I have been using content permissions to keep the editing of fields to a certain role on one content type. But now I have a new content type that I want to allow another role the permission to edit that field (on the new node type only). The problem is, the field is shared between both content types, so content permissions is inadequate. And no other module provides this (that I can find).

So, would you accept per content type field permissions as a feature expansion to this module?

Comments

markus_petrux’s picture

markus_petrux commented
Status: Active » Closed (won't fix)

If the field is shared between several content types, CCK uses the same table for both, therefore access control to the field data cannot be treated differently. For example, there would be no way in Views to control access to data related to the content type the user has access to.

I'm afraid it is not safe to provide this feature.

herve’s picture

herve commented

Hi, i ve tried to plan a specific module to implement per bundle permissions. Currently, i am using a custom table to store bundle permission settings. Could you explain exactly why it could be dangerous to have per bundle permissions markus? It's not really clear for me.

Thanks in advance,

Regards,

herve.

osopolar’s picture

osopolar
Primary language German
Location 🇩🇪 GER 🌐
commented
Status: Closed (won't fix) » Active

Status should be open to get an answer of question #2.

mariacha1’s picture

mariacha1 commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Per-bundle config would take up a lot of extra space in the database, and would cause you to have to update each bundle for field settings instead of just one. These arguments are articulated here:

https://www.drupal.org/node/1221186

From this module's point of view, if you want a field to have different permissions per bundle, you should create two different fields.

Also, this is D6, which I don't believe anyone is maintaining.