Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I have nothing to do with multireference, but I have made a module that does the same thing for Drupal 6. I have worked extensively with Drupal 6 version of nodereference and userreference, I have contributed a D6 port for revisionreference, and I have also created blockreference and viewreference for Drupal 6.
The method by which my Drupal 6 module works is by being made aware of various drupal 'objects' such as 'node', 'user', 'comment', 'view', 'block', 'revision', etc.. etc... and then it looks for a module called xxxxreference.module and uses the functionality from that to create the appropriate widget.
It also gives options for how and where to display the referenced object, including support for tabs.module and I also plan to be able to have insertion into content via token.
I have attached a screenshot to prove I'm not full of it. As you can see it has support for multiples, drag n drop, and autocomplete.
If you like I can contribute this module to the multireference project and we can work on it from there.
If you'd rather just do a simple port of the existing module, then that's fine - I can create this as a separate module. But I thought I should ask since the 'purpose' of my module appears to be the same as yours, it may be a good idea to join.
There are a few things missing from my module which may affect your decision
- Descriptive text fields aren't there - could be added as an optional extra?
- Currently Autocomplete is the only type of widget (select list is implemented but still buggy)
- Only 'unlimited' multiples are supported (for now) and you can't really set up a 'default' value for the field
I will probably not be contributing to this project, however I am working on a new module which should allow you to combine user reference and node reference together, though it will work in a very different way to multireference I've used some things I've learnt from trying to do a multireference type module for 6. I'll try to remember to update this thread if I have anything to show - at this stage I am not even certain this is going to work!
Flexifield lets you create combinations of fields and then use that combination as items within a larger field. You define a field combination by creating a node type and adding fields to it. On a different node type, you can add a flexifield, and then on its configuration form, specify which node types to use as items within the field.
Flexifield is handy for getting complex grouped fields into Drupal, but has some serious limitations with customizing the presentation, in that it simply doesn't work with Views. Alternatively, there is currently some serious work being done on a separate notion of a combo field here: #119102: Combo field - group different fields into one
I have given up development on my 'any reference' module I described earlier. I found myself rewriting half of the content.module to achieve this ability, and it was still crap.
Now even though it doesn't say so, I have been told the creators of this intend to leverage existing CCK fields, and allow you to choose how to format/output them in your content. If that is indeed the case, this would solve a lot of our problems.
The ultimate idea would be that there could be a button in your wysiwyg to insert a particular field, and it brings up a popup where you fill in the field and choose how to display it, which would insert the correct macro to do it. At least we could keep an eye on it and push for that feature soon.
For reference, here's another possible approach. We're using it in our project.
- Try out CCK3, which is somehow a *experimental* branch that includes the content multigroup module.
- You can create a multigroup with unlimited values, but you can also limit it to 1. Therefore, it becomes like a customizable combo that supports almost all kind of fields.
- In "Display fields" for the multigroup you can configure the field in a myriad of ways: fieldset one field after the other, table with single or multiple columns, etc.
Comments
Comment #1
danielb commentedHI I thought I'd just chime in here.
I have nothing to do with multireference, but I have made a module that does the same thing for Drupal 6. I have worked extensively with Drupal 6 version of nodereference and userreference, I have contributed a D6 port for revisionreference, and I have also created blockreference and viewreference for Drupal 6.
The method by which my Drupal 6 module works is by being made aware of various drupal 'objects' such as 'node', 'user', 'comment', 'view', 'block', 'revision', etc.. etc... and then it looks for a module called xxxxreference.module and uses the functionality from that to create the appropriate widget.
It also gives options for how and where to display the referenced object, including support for tabs.module and I also plan to be able to have insertion into content via token.
I have attached a screenshot to prove I'm not full of it. As you can see it has support for multiples, drag n drop, and autocomplete.
If you like I can contribute this module to the multireference project and we can work on it from there.
If you'd rather just do a simple port of the existing module, then that's fine - I can create this as a separate module. But I thought I should ask since the 'purpose' of my module appears to be the same as yours, it may be a good idea to join.
There are a few things missing from my module which may affect your decision
- Descriptive text fields aren't there - could be added as an optional extra?
- Currently Autocomplete is the only type of widget (select list is implemented but still buggy)
- Only 'unlimited' multiples are supported (for now) and you can't really set up a 'default' value for the field
Comment #2
wuf31 commentedsubscribe
Comment #3
mgiffordI'd be interested in seeing the code danielb.. Thanks for the offer to share what you've already developed.
Comment #4
danielb commentedUnfortunatly with the latest CCK updates, my module's functionality has become very buggy and I will have to do some massive changes :(
Comment #5
Anonymous (not verified) commented+1 to Danielb
Any updates?
Comment #6
danielb commentedI will probably not be contributing to this project, however I am working on a new module which should allow you to combine user reference and node reference together, though it will work in a very different way to multireference I've used some things I've learnt from trying to do a multireference type module for 6. I'll try to remember to update this thread if I have anything to show - at this stage I am not even certain this is going to work!
Comment #7
reinholdlange commenteddanielb - thank you so much! I, too, would be interested to hear about the progress on the D6/standalone module progress!
Again, thank you!
Comment #8
giorgosk@danielb
which module does the same thing that "multireference" does ?
Comment #9
Rosamunda commentedditto:
which module does the same thing that "multireference" does ?
Thanks! :)
Comment #10
Rosamunda commentedComment #11
Village Internet commentedFlexifield lets you create combinations of fields and then use that combination as items within a larger field. You define a field combination by creating a node type and adding fields to it. On a different node type, you can add a flexifield, and then on its configuration form, specify which node types to use as items within the field.
http://drupal.org/project/flexifield
Comment #12
jwilson3Flexifield is handy for getting complex grouped fields into Drupal, but has some serious limitations with customizing the presentation, in that it simply doesn't work with Views. Alternatively, there is currently some serious work being done on a separate notion of a combo field here: #119102: Combo field - group different fields into one
Comment #13
danielb commentedI have given up development on my 'any reference' module I described earlier. I found myself rewriting half of the content.module to achieve this ability, and it was still crap.
Check this out though:
http://drupal.org/project/inline
Now even though it doesn't say so, I have been told the creators of this intend to leverage existing CCK fields, and allow you to choose how to format/output them in your content. If that is indeed the case, this would solve a lot of our problems.
The ultimate idea would be that there could be a button in your wysiwyg to insert a particular field, and it brings up a popup where you fill in the field and choose how to display it, which would insert the correct macro to do it. At least we could keep an eye on it and push for that feature soon.
Comment #14
koala098 commentedsubscribe
Comment #15
markus_petrux commentedFor reference, here's another possible approach. We're using it in our project.
- Try out CCK3, which is somehow a *experimental* branch that includes the content multigroup module.
- You can create a multigroup with unlimited values, but you can also limit it to 1. Therefore, it becomes like a customizable combo that supports almost all kind of fields.
- In "Display fields" for the multigroup you can configure the field in a myriad of ways: fieldset one field after the other, table with single or multiple columns, etc.
See: #494100: State of the multigroup module
Cheers