You are here:  » Problem with encoding


Problem with encoding

Submitted by lecolet on Mon, 2012-02-27 07:52 in

Hi, David,

I bought the script recently and I am trying to install it now, but have the problem with encoding. My Russian WordPress site encoding is utf-8, and WP posts show fine. XML feeds are in windows-1251, and all Russian characters in products names and descriptions don't show correctly. I've tried setting config.php to windows-1251, I've tried leaving it with utf-8 and using the utf8 encode filter, I've tried changing the fields' encoding in phpmyadmin...

Imported Russian text displays incorrectly in the mysql table, too. I've tried to type the text directly to the table in phpmyadmin (fields set to utf8-general-ci), and then it displays correctly both in the table and on the site, but importing still makes all text unreadable. So, right now the config.php is set to utf-8, all table fields in mysql are set to utf-8-general-ci, feeds are in windows-1251, utf-8 encode filters for name and description are set. And it's not working. When I open the site, it's in utf-8, and even when I try to change the encoding in the browser, I can't get the products names to be readable with any of the encoding. So, it looks like the utf-8 encode filter doesn't encode windows-1251 to utf-8 correctly. Is there a way to make it work? Thanks!

Submitted by support on Mon, 2012-02-27 09:32

Hello lecolet,

I will email you an alternative version of the database Price Tapestry library which fixes the character set of the MySQL connection to utf8 which as helped other users in situations where datafeed imported content is not showing correctly within WordPress. This is in addition to existing character set configuration values.

I've not yet any experience of this solution under windows-1251 encoding but if this version doesn't solve the problem I will investigate further with you - please check your email in a few minutes...

Cheers,
David.
--
PriceTapestry.com

Submitted by lecolet on Mon, 2012-02-27 09:54

Thanks, David! It works correctly now.