If i have multigroup with multiple fields, i would like to be able to set privacy options for each field separately, right now if I change settings for one field, it changes settings for all fields.

Comments

markus_petrux’s picture

markus_petrux commented
Status: Active » Closed (works as designed)

Sorry, this is not supported because the module would have to store and manage delta values in multiple value fields and multigroups. Too complex.

henrijs.seso’s picture

henrijs.seso commented
Category: bug » feature
Status: Closed (works as designed) » Active

I understand, but it's a must feature. Typical usage of field privacy is contact information - multigroup where user can enter multiple phone numbers - home, office, mobile etc. User would like home number shown to friends, office and mobile number to followers or business partners.

markus_petrux’s picture

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

As a feature request this would be "won't fix" unless someone can come up with a patch and we can start a review process.

Setting the issue as such to reduce noise in the queue, but it can be re-opened when a patch is posted. Thanks

henrijs.seso’s picture

henrijs.seso commented
Title: multigroup - privacy options for one field applies to all, must be a way to set options seperatly » cck3 multigroup issues
Status: Closed (won't fix) » Active

Please dont close, I am working on this issue, cannot promise results, but Ill try

issues:

1) multigroup field settings are not saved because they have delta values and stuff
2) js conflict between multigroup and private fields - loading new group resets icons to default 'public' (just icons, not settings) and icons are not shown for new fields

UPDATE: I am starting to understand scope of problem - module sets privacy for field, it just loads all fields in content type, but multigroup fields has multiple values and those are not supported at all

henrijs.seso’s picture

henrijs.seso commented
Title: cck3 multigroup issues » cck3 multigroup support

I am not skilled enough to do such massive rewrite :(

henrijs.seso’s picture

henrijs.seso commented

#881860: Content permission for CCK3, call to join forces

markus, see this issue over at content permissions, maybe instead of rewrite, CCK team with a little help from their friends would update content_permission module to some kind of simple API state, that you and others could use?

markus_petrux’s picture

markus_petrux commented
Status: Active » Postponed

I have marked the issue for CCK as won't fix. Reason is that any change would affect the core of CCK, function content_access(), however next generation of Fieldable stuff is being done in Drupal core itself. Drupal 7 is feature frozen, so such a change would have to be approached for Drupal 8. Note that it makes no sense to provide a feature for CCK D6 that is not going to be ported to Fields in Drupal 7 core.

The above makes me think that it is not a valid solution for your current need, sadly. So, I would suggest to think around an alternative approach to implement your request.

I'm going to leave this issue as "postponed", so that it is more visible, and maybe that helps you better than being marked in a status that is not visible in the queue by default... though, if there's no patch for review in a few weeks, I'll revert the status to "won't fix".