@ryrun opened this Issue on October 17th 2012

I love the new features of 1.9, you are great guys. Good work.
I've only a small problem with tracked keywords from sitesearch. Umlauts wont be displayed correctly. I saw that all urls with umlaut keywords are also not displayed correctly in the page urls view.
how does piwik detect the charset of a page?
Keywords: piwik charset sitesearch

@ryrun commented on October 17th 2012


@pebosi commented on October 17th 2012 Contributor

Can't confirm this on my installation of Piwik 1.9. Please provide more information about your site (charset, php, etc.). Maybe provide a screenshot.

@ryrun commented on October 17th 2012

Site is using charset "iso-8859-15".

@ryrun commented on October 17th 2012

Url-Parameter of the piwik request:

Should be tracked as "Tte".

@mattab commented on October 18th 2012 Member

Thanks for the report. We should urldecode the keyword twice

@anonymous-matomo-user commented on October 22nd 2012

Iam not sure if i have the same problem as megadroid. its also with the "umlauts" but i dont see the squared question marks instead my search words just end (they get cut off) when an umlaut comes up...


@diosmosis commented on October 23rd 2012 Member

(In [7289]) Fixes #3450, handle non-utf-8 character encoding in query parameters of tracked URLs.

@anonymous-matomo-user commented on November 13th 2012

In 1.9.2 the problem occurs again. Please see changes in reencodeParameters-function.

@ryrun commented on November 16th 2012

Agreed, problem show up again with 1.9.2.

@anonymous-matomo-user commented on November 19th 2012


is there maybe a fix for this or can we revert to a previous version of function that works in 1.9.2?

@mattab commented on November 22nd 2012 Member

(In [7521]) Site search improvements

  • Support &kwd[]= notation fixes #3454
  • Support random text case fixes #3539
  • Fixes umlauts regression with non utf8 encoding: Fixes #3450
  • Adding setPageCharset() method to Tracking API FIxes #3565
@mattab commented on November 22nd 2012 Member

(In [7523]) Refs #3450 Fix regression in the Javascript tracker

This Issue was closed on November 22nd 2012
Powered by GitHub Issue Mirror