Inherit exposed filters is enabled, but attachment won't display when using autocomplete widget.

Same problem here...

Thanks for support!

Greetings
Filburt

Same here, exposed filter with autocomplete field breaks the attachment.

Same problem. Autocomplete exposed filter makes attachment view disappear.
Subscribe.

tnx geraud :)

Please i have the same issue.

I confirm that when you choose autocomplete for a taxonomy field, you can't inherit filters from a page to an attached block.

Need help on that !

Thanks a lot

Stumbled on this too, and it's very annoying. Also changing the title to reflect the infos provided.

Changing Version to dev.

Also see : http://drupal.org/node/1026436

Possibly useful info :

- The preview seems to work well, so it's probably not SQL related.
- Setting a value for the exposed Taoxnomy term or not doesn't change anything : even an empty value breaks the attachment.
- To be more precise, the attachment DOES show, but returns No Result.
- The behaviour of autocomplete fields seems to be OK otherwise, in exposed filters or elsewhere.

Hope it can help to debug this.

** edit ** nevermind ...

Here is the solution that helped me:
You should remove the autocomplete exposed filter in the attachment and make a contextual filter instead of it. For example, in the main view there is an exposed filter called "has taxonomy term with depth" provided with "term_node_tid_depth" variable.
Add contextual filter to the attachment: "has taxonomy term with depth". Set the same depth as on the main view. Choose "provide default value" as php-code:

$name = isset($_GET['term_node_tid_depth']) && !empty($_GET['term_node_tid_depth']) ? $_GET['term_node_tid_depth'] : 'all';
$name = preg_replace('/^"(.*)"$/', '$1', $name);
$name = str_replace('""', '"', $name);
return $name;

Then specify validation criteria: taxonomy term, your vocabulary and term id converted from name.

PROFIT

As noted in https://www.drupal.org/node/1026436, I had this problem in views-7.x-3.10. I think these two bug reports are about the same issue. I'm not sure of the procedure for updating/closing a duplicate or marking the version from dev (noted two years ago) or 7.x-3.10 noted today.

Hi guys,

Here is the patch for this mysterious bug. Spend a while for investigating until I see the cloned views in wrong.
Not sure where it is wrong so it's better to get a fresh new views.

Patch for bypass test

I had the exact same bug (attachment not displaying because of a taxonomy exposed filter with autocomplete), and this patch fixed it… Thanks a lot!
I'm changing the status just to move things along about it.

Had this exact issue with drupal 7.59 and views 7.x-3.20. Couldn't apply the patch but changed it manually and it all works fine now. Would be great to get this in a release.

Thank you for this patch! I have a complicated view (that does *NOT* have an autocomplete field, but does have many inherited filters) and my attachment was getting 0 results. After the patch things work correctly. I'm using Drupal 7.65 and Views 7.x-3.22.

@seattlehimay @tisteegz Could you please check, if #3040497: [Regression] Missing JOIN in attached display with taxonomy filter and inherited exposed filter fixes your issue as well? It's already in the 7.x-3.x-dev version, so you could either try that or apply the patch from the issue. This is especially likely to fix the issue, if you don't have an autocomplete and are using 7.x-3.22 like @seattlehimay.

If the patch won't fix it, we're probably missing another property in views_clone(), that we should unset, but don't. In that case it would really help us, if you could export your view and attach it here so that we can look into it more closely. Thank you for your help.

Sorry, linked to the wrong issue... Should have been #3040497: [Regression] Missing JOIN in attached display with taxonomy filter and inherited exposed filter.

@FeyP - I just tried the dev version of views on my test site, and it *DID* indeed fix the problem (complicated view, attachment with inherited filters that was previously displaying only in preview but not live on site). Thank you!!

@seattlehimay Thank you for testing the dev release and for confirming that it works in the latest dev. That's great!

@all It would still be helpful to know, whether the latest dev release or the patch I posted earlier resolves the problem for someone, who has the original problem with the autocomplete. If it doesn't work, we need an export of a broken view to investigate further. If any of you could give it a shot, that would be appreciated.