When using the 'Taxonomy: Term' argument there is a problem with
the Validator options part of the UI when using the 'Taxonomy term' validator.
For the 'Argument type' option if you select 'Term name/synonym converted to node ID'
you get an option to 'Transform dashes in URL to spaces in term name arguments'.
When using the Argument type 'Term name or synonym' option you don't get
the 'Transform dashes in URL to spaces in term name arguments' option, even
though it honors that hidden setting.
So if you select 'Term name/synonym converted to node ID' and check the
'Transform dashes in URL to spaces in term name arguments' option and then
select 'Term name or synonym' you can enable that functionality even though
the UI field is hidden.
The 'Transform dashes in URL to spaces in term name arguments' should be
visible for both options.
(wow that was a bit long winded for such a simple bug:)
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | views-term_validator_transform-777072-2.patch | 933 bytes | agileware |
| #2 | views-test_term_validator_transform_export.txt | 2.56 KB | agileware |
Comments
Comment #1
Letharion commentedIn case this old bug report is still relevant here is my comment:
I'm not familiar with this functionality in views, so please provide an exported feature with terms that allows the bug squad to reproduce the error, in the most recent version of views, and we will have it assigned to a maintainer.
However, based on the age of this request I'm going to close this. Please re-open as necessary.
Comment #2
agileware commentedI have attached a view that reproduces this issue but it won't work unless your taxonomy vocabularies are set up to match the view.
Basically all you should need is a vocabulary with the vid 4.
Otherwise just edit the view and go to the term argument and in the "Validator options" fieldset, for the "Vocabularies" option, select one of your vocabularies.
Basically if you create any view with a "Taxonomy: Term" argument set up as outlined in the original post you can see the issue.
For the sake of a potentially easier explanation, I have also attached a patch that fixes the problem for me.
Comment #3
dawehnerLooks find and make sense. Sadly this patch has to be rerolled for views3
Comment #4
agileware commentedHad a look at 6.x-3.x-dev and it doesn't seem to have the same problem.
Transform doesn't have a dependency any more so is visible all the time.
Comment #5
merlinofchaos commentedCommitted to the 2.x branch.