I have seen that there is an issue marked as Won't Fix here #413330: views integration, in order to no hijack issues I'm opening one new.

Since Views 3 is not ready yet, use this code is not recomended for productions sites, even for tests either. At least until views 3 alpha 2 be released.

So, why Views 3 integration. Views 3 comes with a new kind of plugin called Exposed Forms. This plugin allows modules to override the functionality of exposed forms without implement hook_form_alter in a custom module.

This patch provides a plugin based on exposed form basic, it is very small and provides an UI to select wich exposed filters (only text or numeric autocomplete widgets cck fields) should be used as autocompletable widgets.

I'm leaving this issue as postponed works in order to wait until views alpha 2 be ready.

If you insist to test this patch before Views-6--3-alpha-2 be released :), you need to apply this patch to the last views 3 development version in order to can expose filters:

#652716: Default Exposed Filters does not affect query.

CommentFileSizeAuthor
autocomplete_widget_views_integration.patch4.17 KBdagmar
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

markus_petrux’s picture

markus_petrux CreditAttribution: markus_petrux commented

Sure, Views 3 looks like it will come with a lot great stuff. Thanks for this patch!

Unfortunately, I'm tied to Views 2 at this moment, so aside from waiting to Views 3 with all the stuff already in place (alpha or beta, etc.), I would appreciate feedback from testing.

dagmar’s picture

dagmar
Primary language Spanish
Location Argentina
CreditAttribution: dagmar commented
Status: Postponed » Active

Now that views 3 alpha-2 was released we can start to test this patch

dagmar’s picture

dagmar
Primary language Spanish
Location Argentina
CreditAttribution: dagmar commented
Status: Active » Needs review
gilcpd’s picture

gilcpd CreditAttribution: gilcpd commented
Version: 6.x-1.x-dev » 6.x-1.3

I installed the patch and enabled "Auto complete widget" on Views form exposed. How do I add the view to the field now? :S

dagmar’s picture

dagmar
Primary language Spanish
Location Argentina
CreditAttribution: dagmar commented
Version: 6.x-1.3 » 6.x-1.x-dev

@glicpd: this patch doesn't do that. This patch only enables you to use an exposed filter with autocomplete capabilities. You cannot use a view as the source for an autocomplete field, sorry.

markus_petrux’s picture

markus_petrux CreditAttribution: markus_petrux commented
Status: Needs review » Fixed

@dagmar: Thanks again for the patch. I have committed a slight variation, with a few doxygen comments, and also an attempt to fix something that seemed to me it was missing in the plugin handler: initialization of the $relationships array, which I think it comes from the $this->view->relationship array.

Also, I have moved Views stuff to its own subdirectory.

You may want to check out from CVS, or wait for the next nightly built of the dev package.

I'm marking this fixed, but it could be re-opened in case there's anything missing or not working properly. I'm going to create a new "Component" for the issues queue as "Views integration" too.

I decided to go ahead and commit because this is the first change after the latest stable release, and there's no other stuff planned in the short term, so people can easily test this feature using the atest dev package.

markus_petrux’s picture

markus_petrux CreditAttribution: markus_petrux commented
Component: Code » Views integration

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Beatle88’s picture

Beatle88 CreditAttribution: Beatle88 commented
Status: Closed (fixed) » Active

Hi,

I have a slight problem - I can see the Autocomplete widgets option on the exposed form, however, when I update the display (after selecting the autocomplete option) the exposed form reverts back to the previous option I had selected. Any ideas about why this might happen?

Thanks

sketman’s picture

sketman CreditAttribution: sketman commented

The same problem here...

george.plescan’s picture

george.plescan CreditAttribution: george.plescan commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
Priority: Normal » Major

I have the same problem on Drupal 7. For the Exposed form style settings it doesn't change to Autocomplete.

I use Views 3 dev.

off: I tried using another autocomplete module Views Autocomplete Filters. After I adapted it to Drupal 7 it had a checkbox for autocompletion which also didn't stay activated...

markus_petrux’s picture

markus_petrux CreditAttribution: markus_petrux commented
Version: 7.x-1.x-dev » 6.x-1.x-dev
Priority: Major » Normal
Status: Active » Closed (fixed)

The original request was already addressed.

Please, open a separate issue for each different problem. Thanks.

george.plescan’s picture

george.plescan CreditAttribution: george.plescan commented

I have tested both the 6 and 7 version of the module to see if the views integration is working.

So far none of them save the autocomplete option. Please can anyone specify if the integration works and in what configuration.

I have tested both on drupal core fields and cck fields with the widget enabled in the content type structure.

SchwebDesign’s picture

SchwebDesign CreditAttribution: SchwebDesign commented

subscribing. any updates on this? I very much need this to work for views 3 as well. I'll likely be testing the patch above, but from what #13 says that's not working. I'd be willing to pay someone to implement this (and share with community) if any one is interested!