Hello,

I want to select some of the nodes in an autocomplete nodereference field with the help of a View. Everything works ok. For example if I use dropdown, the nodes listed are correct. But when I use autocomplete, only at most one result is shown. For example.

If the desired results are:
- Amsterdam
- America
- Amethist
- Bombay

When I type in "A", only Amsterdam is shown.
If I type "Ame", then only America is shown.

Why the dropdown of autocomplete doesn't show all the matched results?

My Views version is 6.x - 3.0 - alpha 3

Thanks...

Comments

Sinan Erdem’s picture

Sorry, I thought the select list, or radio button widgets were working but they don't... They don't show any results...

Dries Arnolds’s picture

Have you found a solution to this? I'm having the same issue after upgrading from views 2 to views 3.

edit: adding nid to the view fixes this (but thus still behaves different from views 2)

slybud’s picture

@Pixelstyle : you made my day with your edit !

Samer probleme noticed here with Views3 + CCK3 latest versions on D6.
After adding another field in the view (in my case, an image CCK), I got more than 1 element in the autocomplete.
Also works with adding nid field.

This is a real issue, and it looks that we have a solid scenario to reproduce it.

pisco23’s picture

Hi,

I am using cck-6.x-3.x-dev.tar but have the same issue. Although I don't have a solid case for this I can add an observation.

I am using the filtered Node Title as the item to display in my filtered list (via views). When I set the display of the Fields in the VIEWS and include 'Link this field to its node' by clicking the check box ant the end of the page, the corresponding autocomplete field shows me the complete list when I start typing (as it should, I type "a" and it filters all titles with "a" in them.

If however, I set (in Views) the field to not be a link (what I need.. since in autocomplete if its a link when you select it doesn't select but takes you to the linked node :-( ), then I don't get the list - but as noted in a post above, you can get to your desired answer by continuing the input typing - not ideal.

So MAYBE this is a views issue?