New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal site search decoding bug #15060
Comments
@mattab moved this to 4.1.0 as it's not a regression. |
I've just checked that one. For me it seems to work as expected. Maybe that is meanwhile fixed with utf8mb4 support. |
Hi @KALLIAK it looks like this might be fixed. If you can still reproduce this using Matomo 4 after migrating the DB to UTF8MB4 then please comment here and we will be happy to reopen the issue and investigate again. |
Hi @tsteur Just tested my test.zip with the freshly installed Matomo 4.0.5 and the problem remains. |
@KALLIAK Which browser are you using? I had tried your example, and as long as the encoding of the file is |
Checked that again and now I was able to reproduce. |
this would actually be solved with #16628 |
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:
test.zip
Matomo 3.11.0
Thanks!
The text was updated successfully, but these errors were encountered: