new server / characters in database code

I migrated to a new server and some old sites that were fine are now showing the "diamond with question mark for apostrophes" or missing spaces. Digging through old issues, I found where line 137 in ck editor 5 had a line replacement. Checking a site that is throwing the errors, I see that site was using that correction. (http://www.webassist.com/forums/posts.php?id=37452)

The database is set to latin / swedish character sets, same as old server.

On page meta is <meta charset=UTF-8>. Seeing another thread I tried a uni-code replacement but it didn't affect anything.

An example page that is throwing errors: https://professional-siding.com/siding.php which was ok on old server. It's an older site so created before I was using the new mysqli, so it is using the original database interface.

Any ideas what to change on new server to correct? Or why a new server would cause this issue?

Thanks

Usually the database, connection, and page should be using the same charset setting to make sure they show characters correctly. You may just need to update your connection and specify the charset as utf8 there.

If you access the database directly with phpmyadmin do the characters show correctly there? The issue could have occurred with the transfer to the new server.

Looking directly to db,

It�s

<meta charset=UTF-8>

So it looks correct when viewing with phpmyadmin?

You could try adding this to the bottom of the connection:

mysql_set_charset('utf8',$prof);

no... in the database it is reflecting

�

instead of an apostrophe.

I will add

mysql_set_charset('utf8',$prof);

to the prof.php in the connection folder

Adding that in removed the diamond and replaced with the characters

There are only 6 sites affected so I'm just going to go change the curly apostrophes to straight. I will test a new page on server this week to see if it is still happening or it was an issue with migration.

I have manually fixed all 6 sites that needed help.

Next week, I will start a new site and see if new server has issues ... I suspect migration was the problem but I will see.