Opened 18 months ago

Closed 17 months ago

Last modified 17 months ago

#3450 closed Bug (fixed)

umlauts in sitesearch keywords

Reported by: megadroid Owned by: matt
Priority: major Milestone: 1.10 - Piwik 1.10
Component: Core Keywords: piwik charset sitesearch
Cc: Sensitive: no

Description

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?

Attachments (1)

suchbegriffe.JPG (22.6 KB) - added by megadroid 18 months ago.

Download all attachments as: .zip

Change History (14)

comment:1 Changed 18 months ago by pebosi

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.

Changed 18 months ago by megadroid

comment:2 Changed 18 months ago by megadroid

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

comment:3 Changed 18 months ago by megadroid

Url-Parameter of the piwik request:
"...search_result.php?keywords=t%FCte&search_count=21"

Should be tracked as "Tüte".

comment:4 Changed 18 months ago by matt (mattab)

  • Milestone set to 1.9.1 - Piwik 1.9.1

Thanks for the report. We should urldecode the keyword twice

comment:5 Changed 18 months ago by matt (mattab)

  • Owner set to capedfuzz

comment:6 Changed 18 months ago by Rlyeh

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...

http://www.abload.de/img/untitledgojge.jpg

comment:7 Changed 18 months ago by capedfuzz (diosmosis)

  • Resolution set to fixed
  • Status changed from new to closed

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

comment:8 Changed 17 months ago by dywtglt

  • Resolution fixed deleted
  • Status changed from closed to reopened

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

comment:9 Changed 17 months ago by megadroid

Agreed, problem show up again with 1.9.2.

comment:10 Changed 17 months ago by dywtglt

Hello,

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

comment:11 Changed 17 months ago by matt (mattab)

  • Milestone changed from 1.9.1 - Piwik 1.9.1 to 1.9.3 - Piwik 1.9.3
  • Owner changed from capedfuzz to matt
  • Priority changed from normal to major
  • Status changed from reopened to new

comment:12 Changed 17 months ago by matt (mattab)

  • Resolution set to fixed
  • Status changed from new to closed

(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

comment:13 Changed 17 months ago by matt (mattab)

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

Note: See TracTickets for help on using tickets.