Closed (fixed)
Project:
TableField
Version:
6.x-1.0-beta2
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
19 Nov 2009 at 23:51 UTC
Updated:
27 Jun 2017 at 10:35 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedanybody?
Comment #2
bomarmonk commentedI believe the table field offers a collection of text fields in arbitrary rows and columns. CCK 3 and multigroup allows you to essentially treat a group of fields as a single field.
Comment #3
giorgio79 commentedMultigroup was booted as well as CCK3 from the CCK project as it was a hack according to the maintainers and was incompatible with Drupal 7.
Comment #4
bomarmonk commentedAre you serious? CCK3 has been booted? How do you know this? Last I've heard, work is ongoing to get the much more powerful features of CCK 3 updated for Drupal 7.
Comment #5
giorgio79 commentedTake a look at the CCK page, do you see the dev release on the front?
read some of the status discussions in the issues...
Comment #6
bomarmonk commentedThe dev release has never been on the front, so this doesn't mean that work on CCK 3 has ceased or been booted. It does show that the project hasn't gained a more official status, but I hope that doesn't mean it never will. Maybe you do know something I don't, but until I see the actual corpse, I'm going to hold out hope that CCK 3 lives.
Comment #7
giorgio79 commentedRead the status threads :)
Comment #8
bomarmonk commentedI am actively subscribed and reading just about everything in them. Is there a particular one that clearly proclaims the death of CCK 3? The closest I've seen to this is KarenS's comments that CCK3 will need to be accomplished in a very different way for Drupal 7 and that the current method looks more like a hack. Does this necessarily mean that this same functionality won't be ported to Drupal 7 with more refined code for CCK? I hope not. It definitely doesn't mean that you cannot currently download CCK 3 from CVS and that work isn't continuing for Drupal 6 (it may not be, as active development seems to have stopped as of January 26th 2010). More importantly, how does the functionality of your module, which appears to be really quite wonderful (good work), compare to the functionality of CCK 3? I think the question of this original thread might still deserve your attention, as the uncertainty of CCK 3 could lead others to consider your module instead. How do you compare the functionality of CCK Tablefield to the functionality of Multigroup in CCK 3? Would you mind providing more of a response to this question? I don't even know if my understanding, as expressed above, is at all accurate. Thanks for your help here.
Comment #9
bomarmonk commented...and just one more thing to suggest CCK 3 is still alive: Markus, the CCK 3 developer, just stated on April 20th: "I do not think a separate branch for CCK was created (CCK3) for no reason...Please, read this thread: #416154: Synchronized deltas Views integration: Filter on equal deltas in multigroups." This shows that the maintainer/developer has not left CCK 3 to die.
Comment #10
BenK commentedSubscribing....
Comment #12
bomarmonk commentedI am reopening this, as I'm still interested in a more detailed explanation about the differences between this module and multi-group; thanks for any additional information or comparisons.
Comment #13
kevin hankens commentedThink of multigroup as a table row that contains different widgets. For a gallery, the row might contain a title, description, image upload, etc. Then, you could make the multifield contain multiple values. So, essentially, each "row" in the table is a gallery image and meta data.
TableField has a slightly different goal. The module aims to be a lightweight spreadsheet that lets you quickly create tables with an arbitrary number of rows/columns on a per-node basis. With things like Matrix and multigroup, you have to define a certain number of cells for all nodes of a particular type. With tablefield, you can have one or more tables for a node with different rows/columns. Then the next node, can have a totally different combination.
Comment #14
lolandese commentedSeems to be answered.