When you have added a filter of the type "Content: Has taxonomy terms (with depth)" and you want to change the settings of this filter, the default value for the selected vocabulary is wrong. Possibly to a non existent or wrong #default_value of the radio form element for choosing the vocabulary.
Always the first vocabulary is selected, when you open the configuration form, that is confusing at best or leads to wrong settings, if you don't notice and save the form.
Had this problem with the last version and it persists after updating to 3.0
I will look into this some more and try to provide more info
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | views_taxonomy_filter_form-1396376-1.patch | 703 bytes | pixelmord |
Comments
Comment #1
pixelmord commentedLooking further into this issue I found:
The condition, that checks for the absence of a selected vocabulary ist always TRUE. That causes the default value to be reset to the first available vocabulary.
Attached I provided a path that fixes this by checking against empty() not against "== 0"
Comment #2
dawehnerEven i still don't get why this check doesn't help your patch improves all other kind of situations on which vocabulary might be empty.
Thanks for providing the patch. Committed it to 7.x-3.x