@Starker3 opened this Issue on January 4th 2022 Contributor

A user that has a non-utf8 locale set in their PHP configuration, for example:

export LC_ALL=fr_FR

export LANG=fr_FR

Can result in reports or tracking requests with non-utf8 character encoding being generated/inserted. For example:

This was fixed for this user by setting the following in the PHP configuration:

export LC_ALL=fr_FR.utf8

export LANG=fr_FR.utf8

Not sure if this is something that we could add a system check for or prevent in some other way?

Edit: This is the PHP configuration for the Matomo server, not the website being tracked.

@Starker3 commented on January 9th 2022 Contributor

Further clarification from the user, this can result in a Fatal Error when trying to show reports in the UI:

It seems that this is now happening when after switching to the following PHP configuration:

export LC_ALL=fr_FR.utf8

export LANG=fr_FR.utf8

Will ask for further clarification to confirm this.

@Starker3 commented on January 17th 2022 Contributor

FYI the character that likely caused this was:

@sgiehl commented on January 18th 2022 Member

@Starker3 do you know if the user is using utf8mb4 for database tables?

Powered by GitHub Issue Mirror