Multidb 3.0.3 breaks just like 3.0.2 for strange characters.

Just download multidb 3.0.3 version, and I’m still experiencing the strange characters! This time, it gets worse as more strange character appears than before. It seems double space right after punctuation creates the problem!

I’m using mac to write posts and create page in wordpress, I wonder is this the problem? Also, I’m using wordpress 3.0.2 (the latest). Please help me fix this problem immediately as I have been waiting for it to be fix since a month ago?

Thank You!

  • argh2xxx
    • The Incredible Code Injector

    It seems create new test users, and adding new blogs, the strange characters are disappear. Unfortunately for blog users who already have created blogs before the update to multidb 3.0.2 and 3.0.3, these blog users are experiencing the strange characters problem — these characters appear right after all punctuation marks as long there is double space between the punctuation marks and the very next letter.

    Even the main site (administrator site) is experiencing strange character problem, and this is a big problem for me since I cannot make my website looks professionally when posting a new update blog posts to all blog members of my website (blog network using buddypress).

  • argh2xxx
    • The Incredible Code Injector

    Hi Barry,

    Did you mean the Collation which shows up inside phpmyadmin? I see it’s saying utf8_general_ci for db_global

    Other databases that are part of multidb, the tables’ collation shows utf8_general_ci in phpmyadmin, but the default is latin1_swedish_ci listed at the very end where the total tables shown and the sum collumn shown in phpmyadmin. Nonetheless, utf8_general_ci is listed in the collumn next to all tables except for the last row which I’m talking about as if the last row is telling me that the default of the database is in latin1_swedish_ci, but the tables are using utf8_general_ci.

    Can that create a problem? How to switch the database’s default to utf8_general_ci, and how to do that safely for 4096 databases? Nonetheless, should it be OK since all tables are already using utf8_general_ci type even the default of the db is in latin1_swedish_ci?

    Thanks…