Yes.
Browsers want it one way, and databases want it the other way. Irritating, but true.
Printable View
I thought that might be the case, thanks.
But... neither of the zc139h configure files contain:
define('DB_CHARSET', 'xxxx');
Should I just add that line?
Correct. Prior to v1.5.0 it was always assumed that things used latin1.
If you're using the latest version of Zen Cart, it will auto-define DB_CHARSET for you if you don't. And upgrading will put the define into configure.php for you if relevant.
So, yes, if you're still stuck with using the obsolete v1.3.9 then yes you'll have to add it if you're doing conversions. Very few good reasons to stay with 2010 version though.
@DrByte, I tried to talk the client into updating but they declined. So my project is just adding new products (20k+, not to mention 2k categories).
@lat9, the reason I am doing this is because my uploads are triggering the "Â" problem all over the place. Are you saying that changing the site to UTF8 won't help me? Won't resolve the  issue?
What I'm saying is that the v1.3.9h core code isn't going to "understand" what a DB_CHARSET means. I don't know if modifying the database to be utf8 is going to correct your problem or introduce additional issues.
If you're converting to UTF8 then there's a ton of value in actually upgrading.
It's very possible that you've got language files using non-utf8 characters in them, so will get undesired symbols.
There could also be a lot of PHP files that have old latin1 symbols in them. The upgrade replaces all those core files with "clean" ones, so avoids those issues.
The FAQ article about converting to utf8 is based on the dependency of you also running Zen Cart v1.5.x or higher. If you're trying to bolt stuff onto the old version, you'll have to do additional coding to retrofit it.
Hmmm. Ok. Maybe I need to go a different direction then.
The problem only occurs with Easy Populate 4. When I export, the data contains the funny characters. When I import, the funny chars are created and inserted. But if I directly edit the mySQL table, no problems.
And the same data that looks fine on the Live site contains garbage when exporting from EP4. But it looks fine on the site.
I'm off to figure out where in the EP4 files a CHARSET gets specified and just change it there.
Thank you so much for the info!!!
Since you mentioned EP4, consider that using it could contribute to your problem as it is made for the later versions of ZC - thus it may be auto-converting to the later charset.
What about a 1.39 version of Ep? https://www.zen-cart.com/downloads.php?do=file&id=1103
Just a wag. Upgrade is best, of course.