With CCK multigroup, fields are not shown, just one ajax drag/drop area for each instance in the multigroup. See attached screenshot.
| Comment | File | Size | Author |
|---|---|---|---|
| cck3_multigroup.png | 19.88 KB | obrienmd |
With CCK multigroup, fields are not shown, just one ajax drag/drop area for each instance in the multigroup. See attached screenshot.
| Comment | File | Size | Author |
|---|---|---|---|
| cck3_multigroup.png | 19.88 KB | obrienmd |
Comments
Comment #1
arhak commentedwhere 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..
Comment #2
arhak commentedI'm seeing some drag & drop
is that a multiple field?
that needs clarification whenever reporting issues, they are tougher
Comment #3
arhak commenteddo you think it worth to try compatibility with 3.x so soon?
from their project's page
Comment #4
obrienmd commentedFrom 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).
Comment #5
arhak commentedwow, what a way to persuade me :-)
I can't make any time-promises, but its seems feasible
just that I will have to detect them to fix the driven properties' path, but keep the path the usual way on validation/submission
Comment #6
arhak commentedI thought they weren't working, since I expected them to be D7-related
Comment #7
obrienmd commentedArhak, do you need more information from me on this?
Comment #8
arhak commentedno, thanks
just wait a little longer, we are getting there..
Comment #9
arhak commentedthis 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
Comment #10
arhak commentedthis 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)
Comment #11
obrienmd commentedTested, works great w/ latest CCK3, D6.16, and latest dev of comment_driven and driven API.
Comment #12
arhak commented1st half considered fixed as per #11
pending 2nd half #773962: CCK 3.x multigroup as a whole