This is a very small problem and I don't mind since I just need to change the taxonomy term, but this is what is happening:
I have a taxonomy term named "Eco-Friendly" which applies to a Product type.
I have a view set up that makes a page of each product, using the taxonomy term as an argument.
I have the option "Transform spaces to dashes in URL" checked on.
The MySQL query is the following: WHERE (node.type in ('product')) AND (node.status <> 0) AND (term_data__term_data.name = 'eco friendly')
I'm pretty sure views is removing the dashes when it searches for the taxonomy term because I have the url dashes turned to on. It's a small bug, but could be annoying if someone desperately wants dashes in their taxonomy terms, and didn't catch the error like I did.
I'm attaching the live preview to the view.
| Comment | File | Size | Author |
|---|---|---|---|
| Picture 1.png | 66.68 KB | misterZ |
Comments
Comment #1
RoboPhred commentedI have the same issue, and it seems its the transformation acting the opposite as it usually does.
In the past I have used this successfully, where a url "view/this is a test" is transformed into "view/this-is-a-test" in the displayed url, but remains "this is a test" to the argument. However, with the newer views it seems the opposite is happening now; the url remains "views/this is a test" and the argument becomes "this-is-a-test".
Comment #2
sk33lz commentedThis just seems to be broken in general. I am trying to get a taxonomy term that is 3 words long to come together as /word1-word2-word3 in my panel url, and this is not working at all. It doesn't matter if it is checked or unchecked. I have to type /word1 word2 word3 and end up with the very ugly path of /word1%20word2%20word3%20
I really don't want to have to use 1 word taxonomy terms, but will for the time being until this is fixed.
Comment #3
esmerel commentedadding tag
Comment #4
Letharion commentedI can verify "the problem", and the OP's question is reasonable, but I'm not entirely sure what the intention is with the feature. Until "Transform spaces to dashes in URL" has it's behaviour documented, it could might as well be undefined. Therefore I'm moving this to documentation.
If we still have a problem when we're sure what's supposed to happen, we'll take it from there.
Comment #5
Letharion commentedI tested with 2.11
Comment #6
esmerel commentedWhat is the intended function? I'd imagine "all spaces should be transformed to dashes, and everything is treated as one argument"
Comment #7
merlinofchaos commentedThere's really not much you can do about that. There's no way for Views to know that some dashes should be spaces and some shouldn't be.