Closed (outdated)
Project:
Views Autocomplete Filters
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
27 May 2011 at 11:39 UTC
Updated:
17 Apr 2020 at 17:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
vipin.mytechplay commentedI also find the same issue. I have two different types of nodes and a view with two displays (each display is meant for particular node). Each display exposes node title as view filter.
When auto-complete is enabled on both exposed filters then one stops working and other starts showing nodes of both node types. However, if I disable one filter things do work fine.
regards,
Vipin
Comment #2
vasike1. This module doesn't work with cck with allowed values,
- http://drupal.org/node/1157370 , http://drupal.org/node/1151218
2. I see this is a version 2 of the module. This should not be used.
please try with 6.x-1 versions
http://drupal.org/node/1130370
http://drupal.org/node/1102386
Comment #3
vipin.mytechplay commentedvasike,
In my case, comment 1, both fields are node titles and none of this title is present in default display of the view then why the problem is coming. I am using 6.x-1.2 version of the module.
Vipin
Comment #4
hsimeoni commentedSame here
It doesn't work with multiple exposed filters
Comment #5
MBroberg commentedAre the filters named the same thing? I have issues with filter identifier names. Be sure to make them unique and not "name" or "value" as those have given me trouble.
Comment #6
liquidcms commentedcan't get autocomplete to list anything other than the note that says field needs to exist in fields list (which it does).
setup is a noderef field which i have created a relationship from so that i can use node title as both the field to display and the filed to filter.
have tried 2.x-dev, 1.2
would be a very cool module if i could get it to work.
Comment #7
tuzoo commentedsame for me...
the fields that are displayed on the page are correctly filtered, but the fields in the autocomplete-list are not, if the second field is also exposed. if the second field isn't exposed, the filters are applied to both outputs.
I have tried now all kinds of combinations...this is were I'm right now:
display:page
fields: (overridden)
content: testfield
node: title
filters: (overridden)
this works:
content: testfield (hidden, is equal to = test)
node: title ( exposed, op = contains, optional, auto-complete)
this doesn't works:
content: testfield ( exposed, op = contains, optional)
node: title ( exposed, op = contains, optional, auto-complete)
I would really appreciate help or tipps.
thanks ;)
Comment #8
heydemo commentedAttached a patch that fixes this issue. Basically removes other exposed filters so that the autocomplete is not limited by these exposed filters which it doesn't yet have data for.
Comment #9
mtnmn commentedI'm trying to get this to work. I think my problem is with the last part of the patch.
@@ -58,4 +69,4 @@
$matches[''] = '
';
}
drupal_json($matches);
-}
\ No newline at end of file
+}
What exactly am I doing? removing } then adding it again?
Thank you for your help
Comment #10
drm commentedI've got 3 exposed filters, two of which are auto-completes. One of those is a title, the other a CCK field.
The autocomplete for the CCK field appears to be returning (the dropdown list) the node ids instead of cck field values. Node title works fine.
Comment #11
jerry commentedPatch in #8 worked for me.
Comment #12
jvieille commentedI found the problem.
The worse you would get is then you are using several fields / filters of the same type. You will likely get xxx_1/2/3 fields and filter system IDs that do not match at all, except if you carefully implement them in the exactly same order.
The code made provision for this by trying to match the correct field based on the filter custom id instead of the filter system id, but it did it wrongly. Below the correct code
Comment #13
colan