@anonymous-piwik-user opened this Issue on January 14th 2009

Hello, I've encountered a bug: when referer keyword is a of some exotic language (georgian in my case), search by keyword can't find any of those georgian words, while they are displayed correctly in initial list of keywords.

I think the problem is more global, and is caused by incorrect collation of database. The solution, as fas as I can see, is to add an option of selecting db collation in installation procedure of Piwik, or just setting it staticaly to utf8_unicode_ci

Hope this information was helpful :)
Keywords: keyword search database collation

@robocoder commented on January 14th 2009 Contributor

Database collation to be addressed in #310. (Sounds like this may be the cause of #435.)

@mattab commented on January 14th 2009 Owner

_Hitman47, did you try changing the collation of your tables? Did it work better then? Thanks

@anonymous-piwik-user commented on January 14th 2009

hey Matt, I've changed the collation of all tables and fields in piwik db to unicode, but the problem is still there :( so, i'm going to log the queries that piwik sends to mysql server and I'll write here as soon as I get any result.

@robocoder commented on January 14th 2009 Contributor

re-opening.

@anonymous-piwik-user commented on January 14th 2009

Digging up mysql logs didn't gave any result, I couldn't find any query mentioning the word I specified in keyword search, neither english, nor georgian. But while I was browsing piwik database I found that referer_keyword is stored in url format, so, actually, the issue can be even not associated with database collation, more possibly - with php logic behind the search process - maybe someone forgot to apply urlencode to search phrase before using it in sql query?

@mattab commented on January 29th 2009 Owner

duplicate of #435

@mattab commented on January 29th 2009 Owner

hitman, please post a comment in #435 giving example of georgians earch engine for which searching the keywords don't work in piwik. we really want to fix this issue. thanks!

This Issue was closed on January 29th 2009
Powered by GitHub Issue Mirror