State of the multigroup module

Speaking by myself...

For the moment, I think we cannot consider the 3.x branch anything stable, at least until the nested fieldgroups patch is rolled out, tested, validated, and committed. Once that happens, I'm not sure if there will be releases for the 3.x branch. But, I would say we all need this as stable as possible, and there will be no more additions to this branch. So, when the monster patches get in, I guess the 3.x branch could be considered as stable as the 2.x branch.

Creating stable releases for the 3.x branch may potentially depend on how stable 3.x is, how much time could require to deal with the impact of a more widely known new release of CCK, etc. Note I'm just guessing here. We still have the problem that D7 and Fields in core are getting closer, time passes quickly, CCK maintainers are pretty busy, etc.

All I can say is that I'll try to commit only code that has been tested, so that will trigger a new -dev snapshot, and we should try to not impact too much sites that may be running this branch, even if it is experimental. I think we all need this as stable as possible.

it would be interesting to have some information about users that are using this module on live websites.

You may want to look at the usage statistics for the 6.x-3.x-dev release available in the project usage page for CCK:

http://drupal.org/project/usage/cck

Thanks Markus!

I'll leave this issue open if that is oki with you (if not, just close it :) ). We can report back here our experience during the development of this module/branch.

Cheers !

Sure. No problem. :)

Actually, here's a couple of things we have in the todo list for CCK3 right now:

• #416154: Synchronized deltas Views integration: Filter on equal deltas in multigroups
• #300084: Nested fieldgroup
• #495582: Panels integration for multigroups
• #520956: Add a new storage method for fields in multigroups

Edited to add the 3rd issue to the list. --- Edited again to add the 4th issue to the list. --- and I'll be editing so that we can easily follow the state of the multigroup, and where it is going.

Subscribing

Am testing this module at the moment and it is fantastic! Can't see any problems with the way I am using it at the moment. Great work!!

Would like to use this on a production site within the next few weeks. Is the data structure looking quite solid at the moment? Does it look like there are there any parts of the dev version data structure that might need to change when this goes stable that might make a site built on the dev version incompatible?

Would it be better to use the multigroup module with the stable 2.x? Would that even work?

Thanks :)

@matt.nz #5: Nope. The multigroup module works only with 6.x-3.x. It requires a few changes to CCK core to be able to keep multiple values of fields in sync. In CCK2, an item in multiple valued field is removed when it is left empty. In CCK3, it is removed per user request. There's a new 'remove' button for multiple value fields, that's also used in multigroups.

The multigroup module manages multiple value field in unison, keeping delta values in sync. That means you may have something like:

First values are delta 0, second values are delta 1, third value are delta 2.

Fields a and b are stored in the database with a record for each value, where deltas are 0, 1 and 2. This is the same in CCK2 and CCK3.

But Field_b is different. It contains a second value which is empty. It is its delta 1 and it doesn't exist in the database. For field_b, we have the following in the database:

Note here we have non-consecutive deltas (0 and 2, 1 is not stored in database). Well, this is a particularity of multigroups that needs specialized handling, which is implemented in CCK3 only. That's why the multigroups module is implemented on a separate experimental branch of CCK. More information about this can be found on the issue where this feature was born: #196421: Deleting unwanted multiple values / multiple values delta issues and, of course: #119102: Combo field - group different fields into one

With CCK3 you can move a field in and out a multigroup with no problem. Fields placed in multigroups are the same as outside multigroups. But when placed in multigroups, they inherit the "Number of repeats" option of multigroups.

As per the stability of CCK3... I would refer to my previous comments above. This is an "experimental" branch where there is still a bit more work to do. The data model should not change, though, and we all want this as stable as possible.

While testing this module, initially it worked fine. Later, I clicked "Add more value" button and got the following message:
"warning: Invalid argument supplied for foreach() in C:\wamp\www\F37\sites\all\modules\cck\modules\content_multigroup\content_multigroup.node_form.inc on line 702."

Can you please help me get rid of this?

Thanks

@masudfz77: Please, open a separate issue with as much information as possible. We need to be able to reproduce the problem, otherwise it may be quite impossible to guess. Thanks

subscribing

Subscribing with enormous gusto.

My status:
Currently, I'm using this on production site. However, I have to bend my design as it doesn't support multivalues per field. Up to now, no issues.

Hi guys

Thank you for this awesome component.. It saved me a whole lot of custom code.

I have a quick feature request and I apologize in advance if this has already been discussed.... Rather than display all of the rows in the field, I would like to add some JQuery to dynamically add/delete the rows of the grouping similar to this jQuery plugin example.

http://www.datatables.net/examples/example_add_row.html

Any suggestions or feedback?

Thanks,
Greg

@gsvitak: Please, read #8 above.

Most of my projects involve using the multigroup module. Makes it easier than to write and maintain widgets written as modules. I'm using this on four production sites already.

It would have been great if this feature could have been part of the stable branch quite a while ago.

Keep up the good work.

Just was interested in a quick summary from Markus as to where things are at. My understanding was that the last big hurdle was getting nested fieldgroups into multigroups: it sounds like the nesting is pretty much working now, so is this coming soon? Once that's ready to go, is this ready for alpha or even beta versions? I'd like to start using this on a client's site, but I just wanted to make sure that it was ok to do that for a production site. I know you've stated that since many are using this on production sites, you don't want to make changes that will break those sites... just wanted a little extra reassurance before I take the plunge.

Thanks much for all your work. It is really and truly appreciated.

Subscribe

Hi,

Uhm, it is my understanding that to use this feature one would have to get cck 3 from cvs. Am I correct?
If so, I was reading here that I would have to execute a cvs command something like this:

I would have to subtitute moduleName for cck. But I am not sure what I should put as version tag...

Any help would be greatly appreciated.
(I have never used drupal cvs before.)

THANKS!

@zeno129: goto the CCK project page, and follow the link to all releases. You'll find one that is 6.x-3.x-dev. This is a development snapshot that's built automagically twice a day or so.

@zeno129: or use the handy CVS Instructions. You'll see that the command is cvs -z6 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal-contrib checkout -d cck-DRUPAL-6--3 -r DRUPAL-6--3 contributions/modules/cck/

Or if you use drush, simply type:

drush dl cck-3.x-dev

from your command line.

Anyway, I'm planning to test this feature extensively in a project. It seems to me the best way to go. Will open any related issues (seperately) and link them here.

@askibinski: There's no need to link issues here. The CCK queue can be used to filter by version and/or component, and we added the multigroup as an issues component.

I think this issue where we are now is mostly a placeholder to host information about the big things that are already pending to do. Once these things are fixed, I think it will be time to close this issue and live with the features of the issues queue.

Thanks to everyone who replied so promptly! :)

I was able to do what I needed with markus_petrus' instructions. (...so I didn't use cvs in the end)

subscribing with gratitude

Just wanted to mention that we have a problem with Date fields, and there's a patch that needs testing:

- #522558: Date field jumps delta when date field is emptied or fieldset is deleted

Another issue that needs testing and feedback:

- #416154: Synchronized deltas Views integration: Filter on equal deltas in multigroups

Any input is much appreciated. Thanks :)

Subscribing

Subscribing.

Subscribing

Subscribing

+1 subscribing-thanx for the great work

Subscribing...

subscribe

subscribe

subscribing

subscribing

subscribing

subscribing.
It looks really good!
Thanks!!

subscribing

Subscribing and testing with enthusiasm!

Is multigroup available in 7.x-2.x-dev release?

I'm currently focussed on D6 because this is what the project I'm working is based on.

Subscribing

Subscribing

Subscribing

subscribing

Minor change, enhancement for themers: #580156: Wrap multigroups with unique CSS classes in node view

Sub

Subscribing!

Subscribing

subscribing

Subscribing

I depend on the content_multigroup module and I'm quite upset that it was removed from the 2.x branch. This now means that on any of those sites I have built with that module, CCK can't be updated.

I have switched to using 3.x for a site I'm currently working on but I read that it shouldn't be considered stable. Maybe I should rip out the old content_multigroup module and keep it as a separate module, but then I wouldn't benefit from the ongoing work.

Is there any solution to my woes?

@psynaptic: When a commit is made to CCK3 branch, the development snapshot will be rebuilt during the next pick of the Drupal packaging crons. Since the .info files are updated with a new timestamp, this should be noticed by update status module. So you have a method to know when to update.

You can compare the new CHANGELOG.txt file with your current version of that file to see what's been changed/fixed. I may also advice to run update.php next to the changes that need it, but still, it is always a good idea to make back ups before and running update.php after updating any package in your Drupal installation.

I do my best in trying to keep this process as smooth as possible. That's all I can say. For more details, please read the first comments above, and follow the original threads where the multigroup module was born.

Subscribing. To everyone working on this: Thank you! I consider this one of the most important developments in drupal.

I agree. The multigroup is a wonderful CCK addition. :-)

I also agree. I am using this on a site that should go in production soon. It was either this or writing a whole lotta code myself. This code, although alpha, is probably better than what I would write. I sure do hope that D7 will have *some* kind of a solution for this (/me whispers: "and an upgrade path??")

Subscribing.

Subscribe

@markus_petrux: Thanks. A couple of specific questions, if I may:

1. Is CCK 3.x safe to use in production?
2. When a feature or fix gets added to 2.x will it be added to 3.x too?
3. Will 3.x eventually supersede 2.x?
4. Do you recommend that I update production sites using CCK 2.x to CCK 3.x. Is this considered safe?

1. and 4. Please, refer to comment #1
2. All commits to CCK2 are also applied to CCK3.
3. I don't think so. Official stable releases of CCK will probbaly jump from CCK2 to Fields in D7.

5. Will multigroup module be ported to D7? Sure, but I cannot tell when it will be ported at this moment (I'm too busy now, still with D6 stuff). I don't think it will be in D7 core. It will probbaly live in contrib.

Thanks. :)

Subscribing

Subscribing

So, when the monster patches get in, I guess the 3.x branch could be considered as stable as the 2.x branch.

Its seems from a comment above that the monster patch (mentioned in comment #1, which was referring to fieldgroups) has been resolved. Is this the case, can i feel a bit more confident about this module now than back in June.

I know you can't say its stable - this is totally understandable.
Rather can you say exactly how unstable is it, perhaps on a scale of House of cards to Place you keep horses in

BTW amazing work on this and I/we massively appreciate it.

Having been using this module for few months, I would say its very close to being stable that is as long as you don't use node_save to update any nodes.
I have submitted a patch to solve the node_save issue: #596242: Content Multigroup node_save mixes up the delta's

If you are simply using the form to submit things etc i haven't noticed any issues with it.
Don't know if that helps you.

Subscribing

subscribing...

I'm just installed this on a test environment (although I had to take the module code from v2.3 as it's removed in 2.5).

subscribe

subscribing

subscribing

installed multigroups and it works ok. looking forward to stable version as this is an important component to custom node forms.

subscribed

subscribing

subscribing

Subscribing. This has potential to be added to Drupal 8 core, once a stable D7 contrib release is out.

Hi
Please, can somebody of you explain to me, what exactly will be multigroup cck (sub)module, and how it will be working?
how it could helps, what it will be doing better as current CCK?

thanks a lot
Igor

^igorik, currently cck allows grouping of fields (fieldgroup) as well as multiple values for a field. However it does not by default allow a group of fields to have multiple sets. The difference can be illustrated for example:

A person may have multiple addresses (home, office, etc.). You may then have the fields "street_address", "city", "country", "zip code" as a fieldgroup. Without multigroups the multiple setting for each field will yield something like:

street_address1, street_address2, ....
city1, city2, ....
country1, country2....
zip code1, zip code2....

It disregards the intended grouping. Multigroups on the other hand allows multiple instances of the same fieldgroup such that the meaningful grouping of the data set is preserved:

street_address1, city1, country1, zip code1
street_address2, city2, country2, zip code2
.
.
.

subscribing

any aproximation on a RC or BETA relase date ? I'm very interested in thie multigroup feature. Thanks!

Very useful features offered by multigroup and I look forward to following/testing the development of this module.

subscribe

Would like to note that I have now been using this module on a production site since June and have found it to be very solid. There was a small issue with the date module, but that has long been sorted and have had no major problems.

I have an old version of content_multigroup with
// $Id: content_multigroup.module,v 1.1.2.4 2008/10/22 11:02:41 yched Exp $

Now, everything was working fine till i realized i need to patch it to make it work for panels3.

Reading more onto multigroup3, i see that the development has been completely migrated to cck 6-3 and the content_multigroup for cck 2 does not have anything in it.

So
1. can i use the CCK3-dev's content_multigroup with cck 2?
if no
2. How do i get the last version of content_multigroup for cck-2 and apply the patch as mentioned in #495582: Panels integration for multigroups ?

Hi all,

I would like to mention that I'm planning to spend the next week in fixing a few pending issues with the multigroup.

Here's a couple of issues that have already been committed to CVS:
- #618910: Multigroup filter fails when using relationship
- #544542: Allow subgroup fieldsets in a multigroup to be collapsible

Here's one that needs review: #577580: Multigroup fields with empty values loose their ordering when saved via node_save <-- Please, help testing.

Note that CCK3 is being used by more than 4000 sites already (see usage stats), so help on testing this is much appreciatted.

Once that one is reviewed and committed, then I plan to spend some time on the following:

- #538458: Do not allow to change the widget type for fields in multigroups when the change is not compatible
- #577590: Multigroup 'Required' status confusion
- #522564: Ignore empty groups on node submit

I hope that multigroup will not be a problem for sites using CCK3 when updating to D7.

Re: "I hope that multigroup will not be a problem for sites using CCK3 when updating to D7."

Honestly, I haven't had the time to check, so I cannot really tell if D7 is ready for the multigroup. I hope, but I'm not 100% sure either. I'm also 100% focussed on D6, so I haven't had the time to follow Fields in core. I cannot do it all. I guess help is needed in one way or another to ensure that's not just a wish we all have.

I believe the best to do is ask in the Drupal queue, Fields component, about it.

~~~~~~~~~~
Needs testing: #577580: Multigroup fields with empty values loose their ordering when saved via node_save

I have a Drupal 6.12 site, and I'm usuing a highly modified blackout theme. I have CCK 3.x from November 4 and View 3.x from November 2.
On the 28th of October I upgraded the Devel module to latest stable, Panel to panels 3, Finder, Link, ImageCache, Fivestar. All my modules are up to date for stable releases. Since the Oct. 28 update, now when I try to add entry to a multigroup, the box area disappears (although you can see the code in source view). If I click to save when this happens, all the values are deleted. Just wondering what might be causing this.

Otherwise, this module since I've been using it in July has worked great, and I've had no issues at all until now. Great work, and I cannot thank the developers enough.

@irishblood55 Please post a new issue for this in the queue. This is a meta issue about the state of the content_multigroup module.

Thank you

subscribing

sub...

Multigroup is exactly what I wished for when I first used CCK/Drupal. Thank you!

With more than 5000 installations running already I wonder how many it would be if it wasn't hidden so well.
I really wonder why there is no direct link to 6.x-3.x-dev in the "Development snapshots" section of the CCK module page...?

Subscribing.

Subscribing

voelklflo +1, I think 3.x branch should be shown on project frontpage

Subscribing

subscribing

subscribing

I need a module like this. Looking forward to future developments.

@wombat: maybe you can use this one if you are in a hurry http://drupal.org/project/content_multigroup

Ugh, I didn't know a separate fork of Content Multigroup was published. That's too bad, IMHO. That's going to cause a lot of confusion.

Also, please monitor this issue: #644646: Module name is not nice