Not sure if this is the same issue as #1244072: Use of tokens in external URL redirect locations not allowed in some cases and not URL Encoded (which appears to have been fixed before version 7.x-4.4?), but I still seem to be having an issue with special characters in the redirect URL, specifically commas.
I am trying to put two tokens in the URL, separated by a comma, so that these can feed into a View as a multiple value contextual filter. Essentially, I would like /[submission:values:schedule:key],[submission:values:period:key]
to become, for example, /1,2
, as opposed to /1%2C2
Is there any sort of fix or workaround for this? Any guidance would be much appreciated
Comments
Comment #1
DanChadwick CreditAttribution: DanChadwick commentedComma must be URL encoded. http://stackoverflow.com/questions/8828702/why-is-the-comma-url-encoded
If you are seeing a comma in your browser, it may well be the browser that is decoding and re-encoding it.