I finally realized what CCK node reference does and that it would be quite useful. There are two options that would really be interesting for CRC to leverage with its template system.
1. The ability for the new node to have a node reference field filled with the value from the CRC'd node.
2. The ability for a new node to have the same node reference value as the CRC'd node.
The first would be useful for creating content that has a direct reference to a parent node from that parent node.
The second would be to create a reference to a parent node from a child node.
I suppose the best option would be to choose one or the other or "none" for each content type template.
Hopefully, now that I'm back to using my previously abandoned drupal site I can come up with more suggestions, though between this feature, the permission issue, and the hope that the custom links module will add the feature for each link to be exposed as a block like views does, I really can't see anything that would be necessary to add for robust content creation.
Comments
Comment #1
Trunkhorn commentedHey Alan, I sent you a message about this a couple of days ago and was hoping it didn't end up in your spam folder?
Comment #2
alan d. commentedHi Fred
Sorry. I just been supa busy. I've got a refactored version that handles all standard and cck fields, but no upgrade path and I've still got to refactor the interface / forms as they are just not right yet. I may just skip the first and look at the second, but this is very low down on my list of things to do sorry. Just no time...
Hopefully soon
Cheers
Alan
Comment #3
Trunkhorn commentedThat actually sounds great. I'm not concerned about an upgrade path at all so I think you're making the right decision there.
I made an attempt to move some of the code around to fix the permission issue we talked about in the other issue, but obviously have no clue what I'm doing.
I'm very excited to hear you have a cck version. I really don't mind the way things are laid out now in the interface, any chance you could release it as is before refactoring?
Hope I'm not being too much of a pain, I definitely know what it is like to be crazy busy.
Comment #4
alan d. commentedI could, but the refactored version has no form_alters yet, lol. It does have a nice admin interface if you have vertical tabs though!
Comment #5
Trunkhorn commentedI don't really know that it could qualify as a Drupal module without form_alters!!! You've definitely piqued my curiosity nonetheless!
Comment #6
alan d. commentedThe magic word was yet. :)
Comment #7
Trunkhorn commentedHello again Alan, I saw that there is a new dev version from last month and it seems to be different from the latest stable. Was this node reference capability added into that? Just curious as I was upgrading my site today and thought I'd see where CRC is at.
Comment #8
Trunkhorn commentedPlease don't hate me for asking again, but any info on this module? Will this make it for 7?
Comment #9
alan d. commentedMaybe. I may just dump the standard approach and create a new extendable version. It is very difficult when I'm on the road on motocycles in Central America, but maybe by the time there is a stable D7 release, I can have a look. (May - July 2011 maybe!?)
Comment #10
alan d. commentedIf anyone wants to pick this up and run with it, please feel free too. If continued, I would totally renormalise all of my original crazy settings and redo it with a clean state. Since this is just a helper function, I do not think that it would be a huge issue to make people redo their existing templates and it would clean up the code by a massive factor.
Comment #11
Trunkhorn commentedHey Alan,
Earlier in this thread you mentioned you had a refactored version, could you possibly upload that for us to use the code for on new versions?
And definitely have an awesome time down there. Very cool thing to be doing!
Comment #12
alan d. commentedIt is a bit hard to get onto my old box that is in storage in Australia, otherwise I would :)
Comment #13
alan d. commentedAs per the project page, I am stopping development of this module.
Note that I am not marking it abandoned as this triggers update warnings and I will address any security issues should they raise.