By loveland on

Hi there,

I ran into an issue with use of the Reference module. Here is the details:

1. First I installed the 7.x-2.0-beta3 release. Then I created a content type A, and created another content type B which has a field as node reference of A. After I saved the field settings, I got a warning message of this: "Notice: Undefined index: args in _node_reference_view_settings_validate() (line 161 of /sites/site1/www/sites/all/modules/references/node_reference/node_reference.module)."

I then add a few contents of As, and also added a new content of B, and I was able to set the node reference to one of the contents of As. However when I look at the updated content B, the node reference of A (set as title link) got strange behavior - in a different color than the rest of the B's fields and the field name & title link are also messed up. However I can still click the title link which takes me to the referenced content A. Note this is done when I logged in as the admin user.

Then I switched to a normal authenticated user. I added a few new contents of As, and also added a new content of B, and I was able to set the node reference to one of the contents of As. However when I look at the updated content B, the node reference of A (set as title link) as well as the field name did not show up at all!!

2. I changed to the dev release 7.x-2.x-dev (updated on 2011-Oct-10). This time I did the similar exercise like I did previously. Here is what I have experienced

(1) I created a content type A, and created another content type B which has a field as node reference of A. I was able to save the field settings, and did not got any warning message.
(2) when I logged in either as admin or a normal authenticated user, although I can set the node reference when creating new content. However, the node reference's title link as well as the field name did not show up when I looked at the updated content.

Is this a known bug of the reference module? Has anyone experienced the similar issue?

Thanks!!!

⋅ Categories: Drupal 7.x

Comments

WorldFallz’s picture

WorldFallz commented

First, check the 'manage display' tab on the content type to make sure the display settings for the nodereference field are set the way you want (ie the field name comes from the label setting).

Then check the module's issue queue. I'm using the current dev without any problems, but when you encounter a bug the first stop should always be the module's issue queue.

loveland’s picture

loveland commented

Thanks.

I checked the "manage display" tab on the content type and it is correctly chosen for label setting.

I am on the current dev release now, but the problem still exists. Neither the field label nor the title link shows when I look at the content. And the fonts of other fields seem not uniform as well. I suspect that this is somehow affected by the issue as well.

Any other suggestion?

loveland’s picture

loveland commented

I did some test and found that if the referenced node is marked as published, then the title link and field label work fine. So I was wondering if this is required for node reference to work properly?

WorldFallz’s picture

WorldFallz commented

yes, lol. i should have thought to mention that ;-)

loveland’s picture

loveland commented

The requirement I have is that user can only see his own unpublished content. The content and referenced content are both his unpublished content. If we make the referenced content published, then other users may see it as well. This could be an issue.

Any idea to solve this?

Thanks

WorldFallz’s picture

WorldFallz commented

Actually it seems this should have been fixed: #1094406: Handle the 'view own unpublished content' perm when displaying referenced nodes -- so I'm not sure what the problem is. Maybe post a new bug report?

loveland’s picture

loveland commented

Thanks.

I have re-activated that bug node. http://drupal.org/node/1094406