While dopry's work http://drupal.org/node/60756 is good indeed for the itch he has, mine is different. I do not want a nodereferrer field, I want a seemless experience of nondirected references. I have uploaded a backreference.module there but that hard wired in database information. That's not nice. I have tried using CCK functions to do the same -- it survived some basic testing.

Comments

markusH’s picture

This sounds like something I was looking for for a long time. However, I'm stuck with the code you provided (I'm not yet a real programmer). Can you please give me a hint how to use the patch?

rickvug’s picture

subscribing

rickvug’s picture

Subscribing

Bevan’s picture

@markusH: Learn how to apply patches, then apply chx's path to nodereference.module v 5.x-1.3. Here are some links to get you started:
http://drupal.org/patch/apply
http://drupal.org/node/34422
http://www.google.com/search?q=how%20to%20apply%20patch%20files&sitesear...

moshe weitzman’s picture

looks pretty useful.

theruslan’s picture

Subscribing.

jody lynn’s picture

Version: 5.x-1.3 » 6.x-2.x-dev
StatusFileSize
new2.78 KB

Here's a version updated to work in D6. You'd probably want to limit it to work on only certain fields (if it tries to work on a single-value nodereference field it will fail) instead of generically across the board.

chx’s picture

_bjeny_backreference_insert ?

also the comment about the race conditions misses a "have".

Edit: I realize my terse code reviews style might not come across as nice to those not accustomed to it in the core queue. So: thanks porting the module, I do appreciate it.

jody lynn’s picture

StatusFileSize
new2.78 KB

Fixed my bad function name and your bad comment grammar. :)

nickbn’s picture

Question regarding using/installing:

This doesn't look like a patch or a complete module to me.... do I add it to nodereference.module?

Thanks!

markus_petrux’s picture

Status: Needs review » Closed (won't fix)

There are no options to enable/disable this feature per field. And it lacks a few snippets to become a true module.

IMHO, the approach here is inefficient, however. It is already possible to get back references from the node reference field table to the referenced node. See the Node Relationships module for an example of this.

I would suggest to create a separate project for this. As I don't think it will happen in CCK2 for D6, and then we have Fields in core, so this may be something to work on that context, if it needs to be...

..or let it be as a contrib module for D6, which is a real option today for those that need "this way to do it", that might be a bit more useful than an issue lost in the CCK queue.