Closed (won't fix)
Project:
Views (for Drupal 7)
Version:
6.x-2.12
Component:
Views Data
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Feb 2009 at 08:44 UTC
Updated:
25 Aug 2017 at 10:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Anonymous (not verified) commentedI confirm this bug, not working. It replaces the spaces to dashes in URL but the content disappears.
In my opinion this is a very important feature not implemented properly.
Comment #2
liliplanet commentedSame here unfortunately. So the argument directs to a taxonomy term without the-dash ... therefor a blank result.
Is there perhaps a work around this please, very close to launch and this is important.
Thank you for any reply.
Lilian
Comment #3
liliplanet commentedI have been looking in the sql database and do not see where (if even if had to do it manually one-by-one) to convert the url for terms with dashes-please-this-is-important .. :)
Comment #4
damienmckennaIs still an issue with v6.x-2.3.
Comment #5
merlinofchaos commentedI can't duplicate this. On my test system this is working exactly perfectly.
Can you please maybe paste a view and a query from the Views preview that demonstrates this failing?
Comment #6
merlinofchaos commentedComment #7
liliplanet commentedThank you MerlinofChaos,
This problem actually has me running in circles .. because if I use a Content Taxonomy field, cannot override the url ..
and if I just select taxonomy the link to override url in the view works, but without the d-a-s-h-e-s in the argument, although 'Transform spaces to dashes in URL' is selected.
Look forward to your reply, and thank you so much.
Lilian
Comment #8
merlinofchaos commentedCan you also paste the query from the preview?
Comment #9
liliplanet commentedThank you so much MerlinofChaos,
Preview as follows:
Comment #10
liliplanet commentedHi MerlinofChaos,
Pretty stuck here, as I cannot launch until this is fixed.
When you click on a term for instance in the profile pages of a user, it has the d-a-s-h-e-s in the path, so basically no content for the view appears.
That is because the dashes are not created in the argument of the view, although it is selected.
Please is it possible to make the 'Transform spaces to dashes in URL' work in Views?
Look so forward to your reply, and thank you so much!
Lilian
Comment #11
merlinofchaos commentedI don't know what to tell you, Lili. In all of my tests, it works. I've tried it as many ways as I can think of and it has worked flawlessly for me. I do not understand why it doesn't work for you.
FYI that query you pasted? I don't see anything in it that even uses the transform argument.
Comment #12
merlinofchaos commentedOk, I'm playing with your site. And I'm seeing something.
When I visit the URL
http://www.yoursite.com/directory/Focus-Pullersit actually redirects me tohttp://www.yoursite.com/directory/focus-pullers.I bet you have some kind of aliasing that is actually taking over and Views never even sees it.
For grins, try changing the path of your view from 'directory' to 'directoryx' and then trying to visit
http://www.yoursite.com/directoryx/focus-pullers.(Note: I've munged the URL so as to avoid providing unnecessary actual links to your site).
Comment #13
merlinofchaos commentedOk, now I'm sure it's right. Entering an actual term you have produces a URL with no exposed filter but does have the correct title.
However, entering a garbage value produces the title as expected...and the exposed filter.
You have aliases intercepting this, and the view is not being served. This is not a Views problem, which explains why I've never gotten it to break.
Comment #14
liliplanet commentedDear MerlinofChaos,
Yes! one tiny step forward .. As per your suggestion, now I changed url of the view ..
The view outputs the focus pullers.
The problem is that the taxonomy term in the view does not submit the term with d-a-s-h-e-s although my url aliases are correct (see attached)
Please MerlinofChaos, here are 3 screenshots of my views setup for the directory.. (attached)
Honestly, been going in circles here, have tried every option and still just don't seem to get it right. Perhaps have set up the argument incorrectly?
Look so forward to hearing from you, and most most appreciate your help.
Lilian
Comment #15
liliplanet commentedsorry, one more screenshot, the exposed term (attached)
Comment #16
liliplanet commentedPlease how can I contact for paid support or perhaps donate to your services?
Most happy to pay .. to make the directory view work with dashed in the terms, and for exposed view to reset when a search was done.
Look so forward to making this work. Cannot import 11 800 users until I know the directory will work, so so stuck ...
Please contact via my contact form ..
=========
UPDATE: I deleted the whole view and started again.
Discovered that if you use the 'Output this field as a link' (which I definitely need) ... and in my case created link to directory/[tid] the term changes to no dashes.
Still not any closer to making this work, but at least found what causes no dashes.
Comment #17
merlinofchaos commentedI do not do paid support, I never have, and I resent being contacted about it. I resent the amount of time that I've *already* put into this issue for what was YOUR FUCKING ERROR. Now you're still bugging me about it?
Comment #18
merlinofchaos commentedThe bug report you initially opened here is FIXED. The screenshots you show are unrelated to the initial bug report, and are a support request. Also, the view isn't what you submitted earlier, and now you're basically just handing me stuff and saying FIX IT.
If you have another issue, please open a separate issue. And please be clear what your issue is. If you just want me to do your work for you, the answer is no.
Comment #19
michaelfavia commented@Liliplanet - It is important to realise that these issue queues are handled on a volunteer basis and are done to fix issues with the *module* not issues with your site (which would be overwhelming if everyone did this). Thank you for trying to participate in the improvement of this very important module but please make sure that your "bugs" are actually bugs in the module and keep it too one bug per issue. Good luck. -mf
Comment #20
merlinofchaos commentedFYI Validators don't interact with the summary generation, so using the validator to transform spaces to dashes and a summary together will never work.
Comment #21
liliplanet commentedThank you Michael for confirming that this is a bug, and just asked for support and now trying to understand what this means:
"FYI Validators don't interact with the summary generation, so using the validator to transform spaces to dashes and a summary together will never work."
Obviously a bad day from the developer with YFE syndrome. Never knew that offering payment or donations was an insult.
Comment #23
korayal commentedI have the latest dev version, and I'm thinking that this problem is back.
Here are the test samples;
http://www.yerelfutbol.com/test/sultanbeyli-belediyespor
http://www.yerelfutbol.com/test/sultanbeyli%20belediyespor
Merlin could you confirm if it's really a bug or my problem?
Comment #24
korayal commentedI did something wrong on the validator section. It's working OK.
Comment #25
korayal commentedsorry again, when I choose "Basic Validation" it works OK. But when I want that argument to work only if that term is in a specific vocabulary (so "Taxonomy validation"), the "Transform spaces to dashes in URL" option doesn't work.
Check:
http://www.yerelfutbol.com/test2/sultanbeyli-belediyespor
here is the output of my view;
I don't know if it is a workaround or an actual way to do this. But I created a filter to view nodes only for that specific taxonomy. And kept the results the way I wanted.
So when I tested it with a term on a different taxonomy, the preview query for both of the pages became like this;
test:
No query was runtest2:
They both present empty results, but on the first one it doesn't make any query since the validation failed.
Comment #26
techgirlgeek commentedI have stumbled on this bug also.
I didn't notice if anyone had spotted the actual issue, but what I found was in the query the taxonomy term converts the dash to a space, therefore the query doesn't resolve.
For instance:
Taxonomy term: sports-play
Query With 'Transform spaces to dashes'
* WHERE (node.status <> 0) AND (node.type not in ('page', 'profile_information')) AND (term_data.name = 'sports play')
Query Without 'Transform spaces to dashes'
* WHERE (node.status <> 0) AND (node.type not in ('page', 'profile_information')) AND (term_data.name = 'sports-play')
therefore no result, because that taxonomy term does not exist.
Hope this helps.
Thank you,
Karyn
Comment #28
merlinofchaos commentedIt is a known and unsolvable issue that transform spaces to dashes does not work if your actual term has dashes.
Also, this isn't critical.
Comment #29
lesliewu commentedThe option Transform spaces to dashes in URL does not work for me either. I don't have any dashes in my terms and spaces are not transformed in to dashes.
When I set the "case in path" to lower case, it does not work either.
So when I pass my "Term Name" as argument such as
view/Term Name
What I want in the url is view/term-name but it shows view/Term Name
Comment #30
nivelula commentedI'm experiencing the same bug.
I have tried disabling every aliasing module and even emptied the url_alias table, but it is still not converting the spaces in the taxonomy terms to dashes.
It would be nice to hunt down what could be causing the problem.
Comment #31
briinums commentedsame problem here.
I had validation set to taxonomy -> specific vocabulary. changed to "Basic Validation" and it works ok. also added a filter to view for the vocabulary. thanks to hecatomber> comment #25
Comment #33
kram316 commentedGot the same issue.
My transform spaces to dashes in URL option is not working.
Comment #34
Anonymous (not verified) commentedYes, same problem here.
Comment #35
merlinofchaos commentedPretty much every comment in this issue after #29 are useless.
"Some problem here" with little to no detail will go ignored. If you can't be bothered to explain what you're doing in detail, please do not expect anyone else to be bothered trying to understand what you're doing wrong.
Look, please read the issue. I tested multiple times. The option works, but most of the posters earlier have been using it wrong. Either the are fundamentally not understanding what the option does, or they are having trouble with aliases or something else interfering.
If you can demonstrate that you're using the option correctly and it still doesn't work (and you'd best provide *exact* steps to make this happen) then I'll pay attention. Otherwise you're wasting people's time and causing frustration.
Comment #36
Anonymous (not verified) commentedMy apologies, I approached it with a fresh mind this morning and it worked perfectly. Obviously I had something misconfigured.
If you use Taxonomy:Term as the argument, and tick "Transform spaces to dashes in URL" then I can confirm it works fine.
e.g. for the taxonomy term "Black Widgets" you should be able to use the URL widgets/black-widgets using this method.
Comment #37
lhugg commentedThis comment(#36) and #26 by techgeekgirl pretty much describe what is happening here. If no validation is selected, then "Transform spaces to dashes in URL" works as one would expect, and a search for "widgets/black-widgets" will find anything with a taxonomy of "black widgets". But, and I think this is the problem people are having here, as soon as a form of validation is selected in the pull down, this feature ceases to work, i.e. a search for "black-widgets" turns up nothing.
Hope that clarifies, because I was having the same problem. I haven't fully explored yet the implications of not using the validation, but wanted to confirm this behavior while I'm here.
Comment #38
xjmConfirming #25, #36, #37: This option does not work properly if a validator is used. Since the validation happens before the argument is added, the transformed spaces do not match.
EDIT: see #277412: Taxonomy Argument Ignores "Transform Spaces for Dashes" when a validator is used. It is not a duplicate of the "terms containing dashes" cause here, but of the "validator used" cause. (Both are discussed above.)
Comment #39
xjmReverting back to original title since this issue was marked "won't fix" for one particular cause and #277412: Taxonomy Argument Ignores "Transform Spaces for Dashes" when a validator is used addresses the other.
Comment #41
field4000 commentedRemember to flush all caches to see the changes.
Comment #42
SRampley commentedI have also came across a issue with the 'Transform spaces to dashes' tick box, with the node:title filter instead of terms. This was affecting the search query by replacing the dashes with spaces.
Since I am using the view though code, un-checking this option fixed my problems. But I though I should mention it.
Comment #43
rickmanelius commentedThe problem I faced (drupal 7.4, views 3.x) is the interface between panels+ctools validating a term from the URL and then passing to views as a context filter.
Simple example. A panel at site.com/test/%term where %term is a Taxonomy term: ID set to Term name.
Panels+ctools will validate correctly on site.com/test/my%20term but not site.com/test/my-term
Views as a content pane display will only correctly validate with my-term but not "my term" or "my%20term"
For now, I'm simply switching over to term ID's. But if there is a way to get ctools+panels and views to have a common way to validate spaces, that would be cool. If not (because it's either a known but impossible to fully correct issue), I can totally get by with term id's with aliases for now.
Comment #44
merlinofchaos commentedAt the moment, Page Manager still lacks a good way to do automated translations of this nature. It's a frustrating problem. The correct solution, IMO, is to use some kind of field to create additional unique identifiers that can then be used, but such a solution has not yet materialized in the years that I've been hoping someone would contribute one.
You can use a string context and pass that through to Views as a string, rather than a taxonomy term, and that will work. But otherwise, there is not yet a good solution. :/
Comment #45
sockah commentedSubscribing.
Comment #46
nvakenExperiencing same issue. Using "taxonomy term" validator breaks the "Transform spaces to dashes in url" option on terms with a dash in the name. Which sounds as a "major" bug to me as it would not be unusual to have dashes in term names and this breaks functionality of term validation per vocabulary basis and having pretty URL's.
Ofcourse, about this priority change, feel free to change this back if I might be wrong at this judgement. If I am so, please accept my humble apology in advance. ;-) (I think the frustration level in this issue report are already a bit high, so I step on my toes here. ;-) )
Comment #47
nvakenI am sorry, I was a bit hasty on my contribution above. I just read this post:
http://pixelclever.com/how-remove-spaces-when-using-term-names-or-node-t...
Which describes why the combo does not work. Still this post does not explain to me why the combination of Basic validation actually does work and the Taxonomy term validation does not. But if that workaround is a valid fix, I'd think this bug isn't that major. So changing the priority back.
Though I strongly suggest this bug being fixed, one way or the other. Since the current state of views suggests that dashes should be working in URL's, while it clearly does not. So this is a case of "does not work as designed". Maybe removing the dashes option is a better option if this is non-fixable, still I think this should be fixed, maybe in conjunction with core modules, but it's a true shame if this would not work.
Comment #48
mustanggb commented