Total Posts: 11
4. Only happening with pre-existing content, or will it also happen if you add new content? For simplicity, maybe test with cms page content (no crazy EAV stuff to worry about for starters).
5. Check the encoding for the database, table, and specific columns. More info here:
I’d be kinda interested to see whether the problem existed if you cloned it down to mageupdate.com - should only take you a couple minutes and would be an interesting test case for me.
As for #4, I have been doing some testing today that is relevant: I have multiple languages in my store, each set up as their own store using their own locale. My English, German, French, and Portuguese stores all work fine, but my Spanish store refused to load a all, spewing xml parsing errors into the application log. I traced these errors down to entries in the core_config table, specifically entries for some of the shipping modes. In the Spanish versions of these messages, there were lots of Ã©, Ã, and Ã³. When I inspected them in the database, they appeared correctly (using mysql command line as well as in SequelPro). I also dumped that table into a .csv and opened that in LibreOffice - that worked fine as well. I even went so far as to truncate the table and re-load for a well-formed .csv correctly encoded using UTF-8. The store would still puke. Finally, I replaced all the Ã© with é , Ã with í, etc. Now the Spanish store at least loads and is usable.
I’ve found a number of other odd problems that all seem to be linked to UTF-8 encoded characters on various things in the database. One other one shows up when selecting a state for either a shipping or billing address that is in Germany. Instead of getting a drop-down menu with the states in it, I get a fill-in box AND a dropdown, but the dropdown has display:none; set in its style tag, and only shows 1 of the German states. I suspect that whatever is supposed to be populating that drop down pukes on a state with a double-byte character and bails, which then spews out an entry field instead.
So I’m seeing lots of annoying problems all related to string encoding of data after it has been pulled out of the database.
For #5, I have checked the encoding of the database and table, but not the specific columns. The link you provided with more information seems to just bring me back to this post.... do you have a better link?
I’m interested in tossing it onto mageupdate. I’ll see if I can follow the instructions there.