Steps to reproduce:

  1. Clean install with 'Standard' profile.
  2. Enable Views-7.x-3.0-rc3 and its dependencies.
  3. Create a view with a page showing nodes of type 'Article'.
  4. Add the Tags field ('field_tags').
  5. Add a filter on the Tags field ('field_tags').
  6. Choose 'dropdown' and see what comes next...

Comments

mesr01’s picture

mesr01 CreditAttribution: mesr01 commented

Some more info:
Adding the filter before adding the field makes it work correctly if the bug hasn't been triggered yet. Removing the field and the filter does not make the filter settings work again if the bug was triggered before, but saving the view does.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Title: Clicking on taxonomy filter 'setting' link displays wrong setting form » Clicking on taxonomy filter 'setting' link displays the field settings form

Wow i can reproduce that.

Just to summarize you see the settings form of the field, not the settings form of the filter.
Currently i can just guess that this problem is caused by the #ajax binding the event. Maybe this #ajax
behavior isn't detached correctly.

joachim’s picture

joachim CreditAttribution: joachim commented
Version: 7.x-3.0-rc3 » 7.x-3.1

> Just to summarize you see the settings form of the field, not the settings form of the filter.

Yes, that's correct.

1. open the 'settings' for the filter. The modal dialog title is 'Configure extra settings for filter criterion Content: Manufacturer (field_ref_term_brand)'
2. Click on 'dropdown'.
3. It IMMEDIATELY is replaced with modal dialog 'Configure field: Content: Manufacturer'.

Hence I've been switched over to the config for the field handler on the same Field API field (and thus which presumably share an item in hook_view_data()).

joachim’s picture

joachim CreditAttribution: joachim commented

If I remove the field handler and keep the filter then:

a) prior to saving the view, I get taken to an empty modal in step 3
b) after saving the view, things work correctly.

arkz’s picture

arkz CreditAttribution: arkz commented

I'm also encountering this bug. Some more details:

  • It seems that just accessing the field configuration for any taxonomy reference field causes the bug to start occuring (even if you close the modal window without applying).
  • Refreshing the page 'fixes' the bug, until you access a taxonomy field again. (I think this is why saving appears to fix it - because it refreshes the page)
  • If you access any taxonomy field, the bug will occur on all taxonomy filters.
  • The field configuration window that it redirects to (after changing the selection type) is always the taxonomy field that you accessed last.
  • The bug is triggered by changing the selection type, not just dropdown. (e.g. if the selection type is already dropdown and you change to autocomplete, the bug still triggers)
wxman’s picture

wxman CreditAttribution: wxman commented

Just adding mine as well. I had got to the point that I was just about to chuck my laptop out the window, then I found this thread. Mine is a filter to sort a group of writers names, with the filter being a drop down selecting the writing type. Every time I set it to drop down, it either went to a blank window, or just ignored the setting. After I read this thread I saved it, and now it works. This was for a content pane by the way.

Kristen Pol’s picture

Kristen Pol
she/her
Primary language English
Location Santa Cruz, CA, USA
CreditAttribution: Kristen Pol commented

Many thanks to @mesr01 and @joachim for explaining the workaround for this issue!!! Just to confirm:

1) I encountered the bug... tried different things... scratched head... found this issue report

2) Saved the view

3) Immediately click on the *filter* *settings* (before clicking anything else)

4) Choose "dropdown" (no weird behavior!)

5) Saved

Phew! I'm very happy there is a workaround for now until this is fixed :)

idcm’s picture

idcm CreditAttribution: idcm commented
Issue summary: View changes

Thank you so much for the steps to get around this.

codemode01’s picture

codemode01 CreditAttribution: codemode01 commented

Have had this issue for a while now and it's directly related to using taxonomy fields with the 'dropdown' option selected. Nice to find this thread and confirm it's not just me. The only option that I've found is to do what was described above...

  • let it do its thing and take you to another field, or a blank window, and cancel it
  • save the view (whether it registers as saved, or not)
  • hit 'settings' on the taxonomy related field that failed to finish
  • select 'dropdown' and save

Wondering whether it's Taxonomy, Views, or the last time that I upgraded core...

ericwenger’s picture

ericwenger CreditAttribution: ericwenger commented

This issue continues - wonder what the problem is?

grossmann’s picture

grossmann CreditAttribution: grossmann commented

Same problem here. Have to save the view first and can then change to "dropdown".
Maybe this is reintroduced in views 3.16? I am pretty sure this worked before.

grossmann’s picture

grossmann CreditAttribution: grossmann commented
Version: 7.x-3.1 » 7.x-3.16