Nice start fago. I like what you've got so far. I'd like to add the ability to control access by group so that you can have an admin group of fields that no one else can edit. I'll play around with your module using my previous efforts to group fields to try to create a patch for your module that will do this.

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented

I aggree, that's a really cool and important feature. however, I don't like the implementation of your sandbox module very much - because all data is loaded from the database all the time and you prevent the display just by overwriting the whole node body.

So i would prefer to put this functionality into its own module fieldgroup_access or so, which could be invoked from fieldgroup if necessary and could also be shipped with it. So it's possible to also use fieldgroups without access control.

karens’s picture

karens commented

The module in my sandbox was a *very* rough early attempt to get access control working and I agree it is far from ideal. I hadn't thought about making fieldgroup access control into a separate module, but that makes some sense. Access control works nicely for editing but viewing will be a problem in 4.7 (looks like some changes are coming for 4.8 that will make it much easier by using FAPI).

stanbroughl’s picture

stanbroughl commented
Version: » 4.7.x-1.x-dev

+1 for first rate idea - i would love to see this happen! perhaps get together with simple access for node privacy by role and work something out?

fago’s picture

fago
Primary language German
Location Vienna
commented
Project: Fieldgroup » Content Construction Kit (CCK)
Component: Code » fieldgroup.module
moshe weitzman’s picture

moshe weitzman commented
Status: Active » Closed (duplicate)

lets consolidate this conversation to http://drupal.org/node/63240