I have two node types (event and 'story from event', which reference event).
In event I have node referrer to 'story from event'.
The referring links in event doesn't appear after creating 'story from event', but only after I edit 'story from event' again and save it again. :-(

Comments

Leefmc’s picture

I can confirm this aswell, i've been having this trouble off and on. Not sure why i sometimes have it, and why othertimes it seems like it does not need this type of "manual update"

nicholasthompson’s picture

Have you tried emptying the cache (using the devel tool, for example)? I wonder if the cache needs refreshing in the 'cache_content' table...

asb’s picture

Hi,

I just installed this module, hoping it would give me some kind of automatic "Backlinks" feature for my site. However, nodes linking between each other do not appear in the attached CCK field, even not after editing them. Too bad, this would have been a great extension for CCK users ;-(

Probably I'm missing something; maybe this module does handle solely references created by CCK's nodereference field, not those embedded in the node's body? If so, a notice pointing this out would be nice in the module's description.

Greetings, -asb

nicholasthompson’s picture

asb - have you configured it on the content type display settings?

This module does work - checkout http://challenges.dbp-site.com/

http://challenges.dbp-site.com/challenges/overhead-shooter -- A Challenge CCK Node Type. Entries is a Node Referrer field type.
http://challenges.dbp-site.com/challenges/overhead-shooter/wendox -- Snippet CCK Node Type. Has a Node Reference to the challenge Node above.

Nick

asb’s picture

Hi Nicholas,

thank you for the hint; yes, the module is enabled, the CCK field is attached to a content type, and the display settings are configured as follows:

* Field: Backlinks; Type: Node Referrers; Label: (hidden); Teaser (Default); Full (Default)
* Group: Backlinks; Label: Above; Teaser: (hidden); Full: fieldset (collapsible)

This is supposed to display a fieldset called "Backlinks" below the node's body that displays those "Backlinks" (or CCK node referrers).

Most probably I'm doing something else wrong, or I simply want the module to do somthing that it is not intended for.

Greetings, -asb

nicholasthompson’s picture

That should be fine - you should get a fieldset containing links to all the nodes which refer to that node...

gp.mazzola’s picture

Hi I am also experiencing the same problem. I was hoping to get, installing this module, something like a 2-ways relationship.
I have 2 content types, People and Events. In every event there can be more than one persone referenced from people, so in my Event content type I have & nodereference type fields,and everyone has multiple values enabled:

Event                                                    People
 |
 |--field_performer--> nodereference,multiple values -->
 |
 |--field_presenter--> nodereference,multiple values -->
 |
 |--field_introduce--> nodereference,multiple values -->
 |
...

Now I have installed nodereferrer, and I have created in the people content type a nodereferrer field:

field_backlinks, type:nodereferrer

and in the widget settings I chose as referring nodes, the Event node type.

When now I show a people node, the links to referring events do not appear.
Caching is disabled.
If I add a print_r($node) in the node.tpl, the field for nodereferrer is an empty array.

I can't find out where I am wrong. And I do not understand if this module would be meant to act "dinamically", that is, if i change a relation in parent object, should it update automatically in the nodereferrer field in the child object?
So could somebody help?
GP

asb’s picture

Hi,

at least for my issue I came a bit closer to the truth. NodeReferrer simply does *not* provide Backlinks (like in MediaWiki), it's just a counterpart of the CCK node reference field, and nothing else. It does *not* display anything but relations created with node reference, it does *not* display "normal" hyperlinks (that's what the backlinks module is trying). The description of the NodeReferrer module is a bit misleading regarding this.

That said, if you have enabled (a) CCK, (b) node reference, and (c) node referrer, you'll find some new entries in admin/content/types; go to admin/content/types/{type}/fields, then to admin/content/types/{type}/fields/field_{node_referrer}. There you'll find a new entry "Referring Fields", AS SOON as working node reference fields are establishing relations (and not before). In this settings page, you can also enable "Referring Node Types". The matching content type have to be checked, as well as the "Referring Fields".

Within these limitations, the NodeReferrer module seems to work fine at the moment. However, depending on what you really need, the "Backlinks" and/or the "Node relativity" modules might be an alternative.

Greetings, -asb

dopry’s picture

Status: Active » Postponed (maintainer needs more info)

@asb, gb.mazzola:
thanks for going on a documentation tangent and totally ignoring the caching issue people are experience.
Get your own issues for you own problems stop hijacking other people's issues. If you have a problem with the documentation submit it in another issue as a patch or recommended text for the project description.

@zbyna, Leefmc, do you have the caching issue with the latest dev release?

gp.mazzola’s picture

@dopry
I was not hijacking nor ignoring anything. Just reporting the SAME issue EVEN with cache disabled.
Having said this, I can't do without appreciating your kindness.

Zbyna’s picture

I test latest dev release and it seems OK. Now it works much better. Thank you very very much.

dopry’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

@gp.mazzola: I appreciate that you were reporting the same issue, but I would much rather you get your own Issue... I or someone with debugging skills who is triaging can decide if it's a duplicate.

@Zbyna: I'm glad to hear your issue is fixed... I did a lot of cache clearing clean up earlier I believe. :)