We have site in russian language in windows-1251 codepage and all working fine except internal site serch keywords.
E.g. when I try to find ‘окрб’ this keyword turns to url encoded ‘q=%EE%EA%F0%E1’ and then in database it turns to some wierd encoded string ’ Г®ГЄГ°ГЎ’.
There is small 2-HTML page site (windows-1251) where the problem can be reproduced:
I've just checked that one. For me it seems to work as expected. Maybe that is meanwhile fixed with utf8mb4 support.
Hi @tsteur Just tested my test.zip with the freshly installed Matomo 4.0.5 and the problem remains.
This problem has nothing to do with the database, because the GET request to the tracker passes already corrupted keyword, i.e. the problem is in matomo.js, namely in the call "locationHrefAlias = safeDecodeWrapper(locationArray)". safeDecodeWrapper("%EE%EA%F0%E1") returns "îêðá", but it "must" return "окрб". When I remove "safeDecodeWrapper" and leave "locationHrefAlias = locationArray", the problem goes away, but it is not a solution as far as I understand.
But for more than a year I solve the problem this way, with each patch I have to mess with yuicompressor-2.4.8.jar, etc.)
@KALLIAK Which browser are you using? I had tried your example, and as long as the encoding of the file is
windows-1252 and served as such it worked at least in Chrome. When you are viewing the page in your browser is the page title displayed correctly?
We have windows-1251 encoding. We tried all famous browsers.
When I try to find "тест", I get this url: "matomotest/find.html?q=%F2%E5%F1%F2"
And then it turn to this request:
Checked that again and now I was able to reproduce.