If you are able to access either the .htaccess file or create/edit php.ini files then it would be worth doing a comparison of these files between the two sites, as the default encoding can be controlled by these files. There could be more than one php.ini file.
What did you use to export the database, and was it the same tool you used to import to the new server?
Is the character encoding correct in the SQL you exported?
In re SiteCheck:
Quote from: quarterloop at Mar 05, 2018, 08:01 AMThanks for your reply. I just don't see how that should help me? My site's integrity is alright. As I said, all works perfectly well so far, I just see the wrong characters and am not able to some characters from foreign languages (I tried to manually fix some of the broken Texts and wasnt able to enter /copy&paste the texts from the old website).
FWIW, SiteCheck does extensive tests on the database character encoding. It checks the database itself, all tables, and all text fields within the tables for compatibility with what's set in the MODX config.inc.php file. Given the symptoms, it's almost certainly a character set problem.
BTW, it's very unusual to use a Latin1 collation with a utf8 character set. I've never seen a setup where the collation wasn't in the same family as the character set. Do you have a special reason for not having them match?
If I am not mistaken, collation issues with a new copied site can come not only from SQL settings but also phpmyadmin settings...I feel strongly there is at least two aspects you have to watch for, because this happened to me some time ago
Thanks for your replies! I was away for a couple of days so I couldn't investigate any further. I will report back as soon as I have more information.
