With CCK multigroup, fields are not shown, just one ajax drag/drop area for each instance in the multigroup. See attached screenshot.

CommentFileSizeAuthor
cck3_multigroup.png19.88 KBobrienmd

Comments

arhak’s picture

where is cck 3.x?
http://ftp.drupal.org/files/projects/cck-6.x-3.x-dev.tar.gz
I can't even see its snapshot, it is hidden, you're killing me
lets see what I can do..

arhak’s picture

I'm seeing some drag & drop
is that a multiple field?
that needs clarification whenever reporting issues, they are tougher

arhak’s picture

do you think it worth to try compatibility with 3.x so soon?
from their project's page

Most of CCK has moved to core in the Drupal 7 version. The D7 version of CCK contains nodereference and userreference (mostly working), fieldgroup (not working yet), some upgrade code if it is not in core (not written yet), and some miscellaneous helpers to do things that core will not do, like maintain the php code snippets some fields may have been using to define allowed values (not yet working). The future of Content Copy and Content Permissions has not been decided and nothing has been done with them. Everything else is in core.

obrienmd’s picture

From what I understand, 3.x is simply 2.x with multigroup.
http://drupal.org/node/484068

It is a multiple field (there is a multigroup w/ a text field, another text field, and a radio yes/no field, and there are 5 pieces of this data in this particular node).

Drag and drop works (I guess), but comment_driven is not showing the actual data in each piece of data.

I think it's very useful to work on this, but that's just me :) However, multigroup is a "killer feature", and is going to be in core D7 eventually, and CCK-6.x-3.x is fairly widely used (look at the CCK issue queue).

arhak’s picture

wow, what a way to persuade me :-)
I can't make any time-promises, but its seems feasible

On the node form, the group is rearranged to keep the delta
values for each field in a single drag 'n drop group, by transposing the
normal array(group_name => field_name => delta => value) into
array(group_name => delta => field_name => value).

just that I will have to detect them to fix the driven properties' path, but keep the path the usual way on validation/submission

arhak’s picture

I thought they weren't working, since I expected them to be D7-related

obrienmd’s picture

Arhak, do you need more information from me on this?

arhak’s picture

Status: Active » Needs work

no, thanks
just wait a little longer, we are getting there..

arhak’s picture

Status: Needs work » Needs review

this is "ready for review"
but not completely finished

keep in mind than a multigroup is expected to act as a whole field, therefore, enabling part of its contained fields is not reasonable, but admin UI doesn't constraints this yet

the unfinished part is only that one
when enabling fields within a multigroup you'll have to enabled them all or none

pending: admin UI restricting this, and having unified settings for the whole set of fields within a multigroup instead of each field having its own

arhak’s picture

Version: 6.x-1.x-dev » 6.x-1.0-unstable9

this got into alpha1
nevertheless, enforcing multigroup's settings as a whole is still pending
in the meantime, manually ensure you enable/disable all the properties within a multigroup and assign to them the same policies (e.g. ACP or NEP)

obrienmd’s picture

Status: Needs review » Reviewed & tested by the community

Tested, works great w/ latest CCK3, D6.16, and latest dev of comment_driven and driven API.

arhak’s picture

Status: Reviewed & tested by the community » Fixed

1st half considered fixed as per #11
pending 2nd half #773962: CCK 3.x multigroup as a whole

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.