Percent sign % breaks ga tracking

[pykler]

The line of code:

_t._gaq.push(['_trackPageview', decodeURI(value)]);

decodeURI does not work if the value had a lone % sign, as far as I can see, value was not previously encoded and therefore should not be decoded

[flablog]

Hi !

same issue for me. In firefox for example, from a link in a gmail email I click and the #/# becomes #/%23 and jquery.address won't work.
Same issue in a OSX Safari from a Thunderbird client. So It may be useful to catch that inside the jquery plugin directly as different browser have the same issue.
And I cant figure out how to change the hash before .address triggers... and it would be pointless right?

Thanks for that plug by the way. Easy to use and deploy.

[flablog]

Pykler, did you find any solution for that issue ? :S

[joksnet]

Same problem here with crawable activate.

When I send the URL by mail, some webmails will encode the URL. Instead of http://example.com/#!/page will be http://example.com/#%21/page.

The plugin doesn't decode the ! character and the ajax request is not correct.

[kimhallberg]

same issue here I get http://example.com/#!/%2Fsomething instead of http://example.com/#!/something
Linking works on a static/dynamic tags, but not the ones generated by the data.xml, and I haven't changed anything, downloaded it just a few days ago, and not working.

[kimhallberg]

Anyone found a solution yet?

[flablog]

Nop :(

[kimhallberg]

Anyone tested if it works on 1.5? I haven't had the time to test it out yet, so I don't know if it's fixed.

[joksnet]

A quick workaround is set location.hash = decodeURIComponent(location.hash) before the plugin include.

[flablog]

Hey, that work well for me !
Not so clean (it can be nice to include it in the plugin directly)... but working
Thanks ! :)

[nbergseng]

Along the same lines of this, adding a space in the path will break the uri on some browsers. I don't want to fully encode the entire string, because then you lose things like slashes. The solution for me has been to regex into uri encoded form spaces and one or two other chars, rather than to use encode/decode uri component.

I'd like to see better encoding on the next version of this.