Subform Functionality
| Project: | Popups: Add and Reference |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I was excited to find and test this module with hopes that it might help end discussions of using Subform here at work. Do you picture this module ever working like that or would it be better for me to put efforts into separate different module that could work alongside Popups Reference? A few things that would be nice (and I can break them into separate issues if you consider any or all of them within the scope of this module).
1. Editing of referenced nodes in a popup. I'm picturing an edit link next to nodereference fields that opens a popup for editing and saving that referenced node with the same sort of interface that you currently have new nodes added.
2. #308589: Autofill base form NodeReference field on popup close
3. A setting to only allow newly added nodes to be referenced. This would remove the initial autocomplete nodereference text field leaving only the "Add New:" link and then lock the nodereference field that was populated with this newly created node.
4. A way of expanding a noderefence field to show not only the title and nid but all display fields for referenced nodes in the view and edit screens of the parent node (maybe already exists in another solution)
If you browse some of the issues on the Subform module you can see that this sort of functionality has a decent demand. I had hoped to see #119102: Combo field - group different fields into one go in a direction where you could set up a repeating fieldset instead of a new content type that gets referenced, but found that it was meant to fit different needs. I'd like to help get functionality in Drupal to solve Subformish situations and what you've put together looks very promising, so if you are interested I can try to put some patches together.
#1
#1 should be pretty easy, and I would accept a patch that did it, as long as it included a setting to turn the behavior off.
#2 If you can do it, fantastic. I don't know of any way that does not involve hacking core or moving big chunks of the FormAPI into the module (like Views2 does, and I bet Asynchronous does as well). But maybe there is something I haven't thought of.
#3 Doesn't this depend on #2?
#4 Should be trivial, and I would happily integrate a patch that did it.
#2
Great, thank you for the prompt response. I will try to get something together for #1 and #4. #3 does depend on #2 but I was hoping meba's idea in that issue was workable. Your take on that, though, makes me slightly less optimistic.
#3
I also need #3.
#4
The good news is that I have funding to work on #308589, and a plan. Fingers crossed.
#5