Autocomplete returns unexpected results [#1677652]

Searching for "h" returns nodes without without "h" in their titles, and similar other nonsense results.

Can't figure out why though, as the EFQ looks good.

function entity_collection_content_form_autocomplete in entity_collection.admin.inc

http://drupalcode.org/project/entity_collection.git/blob/refs/heads/mast...

Comment	File	Size	Author
	autocompletewtf.png	8 KB	Letharion

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Letharion CreditAttribution: Letharion commented 10 July 2012 at 09:04

Problem appears to be that the $string never get's passed on to the autocompleter.

Comment #2

naught101 CreditAttribution: naught101 commented 13 August 2013 at 21:23

Version:		» 7.x-1.x-dev
Priority:	Normal	» Major

Major, since this is currently the only way to add nodes to a collection via a UI, and it's not possible to add nodes that aren't at the top of the list.

I'm wondering if it might be possible to just re-use the autocomplete from relation_add? It shows about 12 entities, at least one of each of the entity types selected. So if the relation allows nodes and users, it'll show 6 nodes and 6 users that match the search string. Because it's pre-defined for each relation type, it doesn't need custom javascript, it can use the built in formAPI autocomplete. This should be able to work the same for entity_collection (and allows the "type" selector to be removed from the add existing content form). The code is at http://drupalcode.org/project/relation_add.git/blob/refs/heads/7.x-1.x:/... . I can try to provide a patch, if this is sounds like a good idea.