I'm creating a view and filtering by 'has taxonomy term, type, published' and have run into some very odd little quirks that I have never seen before. I'm using one custom image field in the 'fields' and sorting by 'post date'. The content type has the custom image field and the taxonomy vocabulary as fields.
steps im taking are:
1) create view as a block
2) add the image field to fields
3) configure the field for image field
4) add filter criteria, 'has taxonomy term' and 'type'. 'Published' is there by default.
5) the configuration window for 'has taxonomy term' comes up. My vocabulary is selected by default. In selection type, I click on drop down. Before i can hit apply and continue, I am automatically redirected to
6) ... the configuration window for the image field
7) Click apply
8) taken back to the main window with a x no valid values found on filter content: type
9) select my content type in the configuration window for that filter
10) back to the main window which shows: content has taxonomy term (or unknown) | Settings
11) click on settings and the configuration window for content has taxonomy term reads: An invalid vocabulary is selected. Please change it in the options.
NOW
If i do the same thing, but change the order of the steps, I get the desired results:
1) Create view as a block
2) create filter criteria with taxonomy and type
3) configure taxonomy and type
4) add image field to fields
5) configure image field
6) done
OK after just writing this all out I decided to do some more messing around with this and something interesting happened.
Doing the second set of steps I laid out works perfect, no errors. If after going through the first set of steps, you save the view, you will get an error message that taxonomy has no valid terms selected. If you go back, to the settings options and select drop down, you can continue without being redirected to the image field configuration window. Now you can click on the extra configuration options and select the taxonomy term.
I'm not sure if this is an issue with views or an issue with core, but I thought I would start here.
thanks
leaf
Comments
Comment #1
mustanggb commentedClosing this as outdated, feel free to re-open with updated details if it's still a problem in the latest release.