ampersand troubles
peterzoe - April 20, 2008 - 22:26
| Project: | Node Type Filter |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | NancyDru |
| Status: | by design |
Jump to:
Description
Hi there,
I have clean url's enable and encounter a lot of trouble with the ampersand in front of 'type=nodetype'. instead of %26 (urlencoding for &) i get %2526 which seems to be coming from the % being translated after the first encoding (compare http://drupal.org/node/119876).
any ideas of how I could get rid of this? would it be possible to get a solution for this into the module?
cheers, Peter.
#1
I'll have to see I can do anything.
#2
I've been looking at this off and on, and it finally dawned on me that this is not the fault on NTF. The problem lies with who ever is using it and producing the URL. And, BTW, all my modules use a question mark ("?") before the "type=", an it is not encoded.
#3
Nancy, I think you're perfectly right, this is not a NTF fault. I was just wondering how others get along with this issue. I found a workaround in using absolute (and not relative) paths calling up NTF but from my point of view this is not really nice.
I also tried to use the '?' (among other trials) upfront, but it didn't help for me (with clean url enabled).
Don't you encouter this problem at all? what do you do differently than me?
#4
I tried it with Taxonomy Browser and no, the = did not get converted -- but the comma between terms did.
BTW, TB invokes it like this:
return array('taxonomy/term/'. $str_tids, 'type='. $node_type);#5
The Drupal powers-that-be seem to think this is not an issue. http://drupal.org/node/272962
#6