I created a NODE REFERENCE field, with AUTOCOMPLETE TEXT FIELDS (the user has the option of choosing 5 reference).

When I go to edit the article, and start to type in the name of other articles on my site ... nothing happens. If I submit the page with an incomplete title, I get...

Related Content: found no valid post with that title.

So, the fields aren't autocompleting. And, if the user doesn't know the exact title ... then it will be hard for them to know what to put in those fields.

I thought it might be a browser issue, so I tried it in IE8, FireFox and Chrome. All the same.

Please help.

CommentFileSizeAuthor
#7 error messages.txt1.28 KBkbi

Comments

tomcatuk’s picture

Dang...I'm getting this failure of autocomplete to work as well. It was working when I was on core release 7.7 though, and appeared to stop after updating to 7.8.

tomcatuk’s picture

OK, updated to 7.9. Still not working. On a whim, changed the field widget type, then back. Still no dice. Something's gone squiffy, just not sure where to look.

tvilms’s picture

I'm on 7.7. I was having the same problem. No matter what View Reference Display I selected in a Node Reference field, it didn't bring back the nodes that the view should've been showing. No matter what widget. However... I just updated to the 10/10/11 7.x-2.x-dev release and the problem disappeared. Try that.

1kenthomas’s picture

Status: Active » Closed (cannot reproduce)

Works for most people. Closing because of age. Reopen if you still have an issue.

kbi’s picture

Status: Closed (cannot reproduce) » Active

I am using Drupal 7.14 with references module version 7.x-2.0. Autocomplete does not work if user is not assigned to administrator role, but works fine for administrator.

holtzermann17’s picture

I'm on 7.12 and it doesn't work as administrator. Furthermore, the references fields (both user and node variants) are not passing validation, even when they are unchanged (as they come out of the database, where they were stored by Migrate).

kbi’s picture

Category: support » bug
Priority: Normal » Critical
StatusFileSize
new1.28 KB
  • I updated from Version 7.x-2.0 to 7.x-2.0-8-dev (2012-Feb-11). Same bizarre behavior.
  • After running update-script and re-enabeling the module, i got a bundle of error messages - see appended file.
  • Changed category an priority to critical because of this bug (not autocompleting for normal user) make this module useless to me.
kbi’s picture

Category: bug » support
Priority: Critical » Normal

Using another browser I found autocomplete indeed working as expected!

The crazy facts:

  • With Opera 12.00 administrator get a list to chose from, but normal user get no list.
  • With Firefox 13.01 both administrator and normal user get a list, but these lists are on different positions with respect to the field.

This problem does not concern module code but presentation only, so changing category and priority back to normal.

holtzermann17’s picture

Component: Code: node_reference » Documentation

In my case I resolved the "non-autocompleting" issue in my case by making sure to select some roles in the field settings for my user_reference field.

If this fixes the issue for everyone, could someone please propose some language for documentation purposes? (Assuming that the issue is just confusion!)

BTW, I can break or repair both node_reference and user_reference fields by adding/removing roles and content types. So, the relevant documentation might be:

"Make sure that at least one content type (in the case of node_reference) or role (in the case of user_reference) is selected, otherwise autocompletion features will not work."