After upgrading multidb to version 3.0.5 which is the latest, the older bug is still existing even though using this newer version. The bug is that weird characters appear right after a period or any punctuation marks if there are two spaces between the punctuation marks and the next letter.
After upgrading multidb to version 3.0.5 which is the latest, the older bug is still existing even though using this newer version. The bug is that weird characters appear right after a period or any punctuation marks if there are two spaces between the punctuation marks and the next letter.
Just to clarify, this only happens on blogs of members that created with older version multi-db. New blogs are unaffected. Unfortunately, the oldest blog which is the main site of everything using buddypress and bp-social theme, and this is affected by strange characters. When a user post something, on the activity page, you can see strange characters appear, but yet on the users' blogs the strange characters aren't there.
10635 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Sales & Support Lead
—
16th February 2011 (1 year ago)
#
Hiya argh,
You can change by selecting your db in phpMyAdmin, click on "Operations" at the top and change the collation.
To check WordPress you will need to make sure your db collation matches what's in your wp-config.php file. It's best to get this all matching at the start...trying to change things in an established blog can get messy.
Hello,
I upgraded from multisite and multi-db 3.0.1 to 3.0.5 and got the black diamond question marks on all my blogs. I just checked as masonjames suggested above. This is what I found,
In my wp-config.php:
define('DB_CHARSET', 'utf8');
define('DB_COLLATE', '');`
In my MySQL localhost:
MySQL connection collation: 'utf8_general_ci'
In my principle database:
All tables show : utf8_general_ci
Except the last summary line says:
10 table(s) Sum 1,456 MyISAM latin1_swedish_ci 2.1 MiB 73.2 KiB
What's up with the latin1_swedish_ci? Is this causing the problem? I can't find a way to change it. None of the tables include it (I exported all the tables to a text file and did a "find" on "swedish").
I noticed on some of my sub-blogs, some plugin tables are set to latin or latin1_swedish_ci. Especially one called "subscription". What would happen if I manually changed all the tables throughout my site to utf8_general_ci?
The latin or latin1_swedish_ci is not consistant with the same tables throughout the blogs.
I also noticed this under the "Variables" tab in PHPMyAdmin:
character set client utf8
(Global value) latin1
character set connection utf8
(Global value) latin1
character set database latin1
character set filesystem binary
character set results utf8
(Global value) latin1
character set server latin1
character set system utf8
character sets dir /usr/share/mysql/charsets/
collation connection utf8_general_ci
(Global value) latin1_swedish_ci
collation database latin1_swedish_ci
collation server latin1_swedish_ci
My provider confirmed that the "Variables" settings (above) are the Standard.
I rolled back the upgrade to 3.0.1. Set all my tables to utf8_general_ci (in the Operations tab for each table in PHPMyAdmin). Still not sure how some tables got changed to "swedish". Did the upgrade to wp 3.0.5. All looked good. Upgraded multi-db to 3.0.5, got the black diamond question characters back. Reverted back to multi-db 3.0.1 and all was restored.
I'm now running mulitsite 3.0.5 with multi-db 3.0.1. Will this create any problems for now?
Just for fun I tried multi-db 3.0.4, and it works fine. I re-downloaded multi-db 3.0.5 thinking I may have a corrupt file, but no go, still gives me the strange characters.
Chuck S.
I'm having this problem as well. I just upgraded to wp 3.1 -- does multi-db 3.0.4 work with WP 3.1? I'd hate to roll back the site upgrade if there's a solution for this character thing on the horizon, or an easy temporary fix.
Yes, multi-db 3.0.4 works with WP 3.1 - but I don't know how stable it's going to be in the long run. Best to get the charset issues sorted and move ahead, but at this point I don't know how to get that done. :(
Hi guys. Thanks for your patience! I'll go ahead and ping Barry. But just to get a bit more info in the meantime, is everyone having the same trouble as the original poster, where the newly created blogs don't have character issues but only older ones created using the previous version?
Can't speak for new blogs. I saw it before any new subscriptions, but all my existing blogs displayed the characters on upgrade. I'm now running Multisite 3.0.5 with Multi-DB 3.0.4.
Thank you for looking into it!
Chuck S.
Hi,
I've been running Multisite 3.0.5 with Multi-DB 3.0.4 and I'm getting ready to upgrade to 3.1.2. I'm somewhat concerned having read some of the problems on other posts in the forums. Did anyone resolve the character issues after upgrading older blogs?
Thanks for checking in. No, not related. I resolved the issue by editing ever post and page on every blog. Tedious, but worked. I've since updated to wp 3.2.1 and no problems. But, let's see what happens when you update the Multi-db 3.0.6 and I install it. :) .
Don't get me wrong. You guys are great! WordPress is just frustrating at times.
I just upgraded to Multi-db 3.0.6 on a WordPress 3.2.1 install, and all hosted blogs (all in french) are messed up. I have a black diamond question marks fort every accentued charter !
This affected old posts, new posts are not affected.
Note – It's the second problems with UTF-8 occured with an upgrade of Multi-db this year (precedence with version 3.0).
My database config for UTF-8 is correctly configured, and my datas are this time untouched in MySQL : the problem is in WordPress and created by the Multi-db upgrade...
I proved to downgrade to Multi-db 3.0.5 : same punition...
Responses (29)
Member — 8th February 2011 (1 year ago) #
Just to clarify, this only happens on blogs of members that created with older version multi-db. New blogs are unaffected. Unfortunately, the oldest blog which is the main site of everything using buddypress and bp-social theme, and this is affected by strange characters. When a user post something, on the activity page, you can see strange characters appear, but yet on the users' blogs the strange characters aren't there.
Developer — 8th February 2011 (1 year ago) #
What encoding do you have in your database? Have you set the WordPress install to use the same encoding?
Member — 9th February 2011 (1 year ago) #
encoding in database is utf-8, i don't remember if i had set wordpress install as utf-8 or not, how to find this out?
Sales & Support Lead — 16th February 2011 (1 year ago) #
Hiya argh,
You can change by selecting your db in phpMyAdmin, click on "Operations" at the top and change the collation.
To check WordPress you will need to make sure your db collation matches what's in your wp-config.php file. It's best to get this all matching at the start...trying to change things in an established blog can get messy.
Hope this helps!
Member — 19th February 2011 (1 year ago) #
Hello,
I upgraded from multisite and multi-db 3.0.1 to 3.0.5 and got the black diamond question marks on all my blogs. I just checked as masonjames suggested above. This is what I found,
In db.php 3.0.5:
In my wp-config.php:
define('DB_CHARSET', 'utf8');
define('DB_COLLATE', '');`
In my MySQL localhost:
MySQL connection collation: 'utf8_general_ci'
In my principle database:
All tables show : utf8_general_ci
Except the last summary line says:
10 table(s) Sum 1,456 MyISAM latin1_swedish_ci 2.1 MiB 73.2 KiB
What's up with the latin1_swedish_ci? Is this causing the problem? I can't find a way to change it. None of the tables include it (I exported all the tables to a text file and did a "find" on "swedish").
Member — 19th February 2011 (1 year ago) #
I noticed on some of my sub-blogs, some plugin tables are set to latin or latin1_swedish_ci. Especially one called "subscription". What would happen if I manually changed all the tables throughout my site to utf8_general_ci?
Member — 19th February 2011 (1 year ago) #
The latin or latin1_swedish_ci is not consistant with the same tables throughout the blogs.
I also noticed this under the "Variables" tab in PHPMyAdmin:
character set client utf8
(Global value) latin1
character set connection utf8
(Global value) latin1
character set database latin1
character set filesystem binary
character set results utf8
(Global value) latin1
character set server latin1
character set system utf8
character sets dir /usr/share/mysql/charsets/
collation connection utf8_general_ci
(Global value) latin1_swedish_ci
collation database latin1_swedish_ci
collation server latin1_swedish_ci
Any suggestions?
Member — 19th February 2011 (1 year ago) #
To re-open.
Member — 20th February 2011 (1 year ago) #
FYI. Update...
My provider confirmed that the "Variables" settings (above) are the Standard.
I rolled back the upgrade to 3.0.1. Set all my tables to utf8_general_ci (in the Operations tab for each table in PHPMyAdmin). Still not sure how some tables got changed to "swedish". Did the upgrade to wp 3.0.5. All looked good. Upgraded multi-db to 3.0.5, got the black diamond question characters back. Reverted back to multi-db 3.0.1 and all was restored.
I'm now running mulitsite 3.0.5 with multi-db 3.0.1. Will this create any problems for now?
Chuck S.
Member — 21st February 2011 (1 year ago) #
Just for fun I tried multi-db 3.0.4, and it works fine. I re-downloaded multi-db 3.0.5 thinking I may have a corrupt file, but no go, still gives me the strange characters.
Chuck S.
Sales & Support Lead — 21st February 2011 (1 year ago) #
Hiya Chuck,
Thanks for your continued feedback. Please use 3.0.4 - you should be fine with this and WP 3.0.5.
We'll have Barry take a look at the plugin (he's been out for a couple days - thus a bit of a delay here).
Thanks again!
Member — 21st February 2011 (1 year ago) #
Mahalo!
Member — 28th February 2011 (1 year ago) #
I'm having this problem as well. I just upgraded to wp 3.1 -- does multi-db 3.0.4 work with WP 3.1? I'd hate to roll back the site upgrade if there's a solution for this character thing on the horizon, or an easy temporary fix.
Member — 28th February 2011 (1 year ago) #
Yes, multi-db 3.0.4 works with WP 3.1 - but I don't know how stable it's going to be in the long run. Best to get the charset issues sorted and move ahead, but at this point I don't know how to get that done. :(
WPMU DEV Fanatic — 5th March 2011 (1 year ago) #
Hi guys. Thanks for your patience! I'll go ahead and ping Barry. But just to get a bit more info in the meantime, is everyone having the same trouble as the original poster, where the newly created blogs don't have character issues but only older ones created using the previous version?
Cheers,
David
Member — 5th March 2011 (1 year ago) #
Can't speak for new blogs. I saw it before any new subscriptions, but all my existing blogs displayed the characters on upgrade. I'm now running Multisite 3.0.5 with Multi-DB 3.0.4.
Thank you for looking into it!
Chuck S.
Member — 11th March 2011 (1 year ago) #
I'm not seeing the problem with new posts and pages since the upgrade. It's only on pages and posts that existed before the upgrade.
Sales & Support Lead — 30th March 2011 (1 year ago) #
Hiya guys,
Just noticed this one's been about 2 weeks since any response. Anyone have an update? Were you able to get these sorted?
Please let us know/feel free to re-open if we need to continue troubleshooting here.
Thanks!
Member — 22nd May 2011 (1 year ago) #
Hi,
I've been running Multisite 3.0.5 with Multi-DB 3.0.4 and I'm getting ready to upgrade to 3.1.2. I'm somewhat concerned having read some of the problems on other posts in the forums. Did anyone resolve the character issues after upgrading older blogs?
Member — 30th May 2011 (11 months ago) #
OK.
I just upgraded from Multisite 3.0.5 with Multi-DB 3.0.4 to 3.1.3 and 3.0.6. The characters are back.
Please help.
Member — 4th June 2011 (11 months ago) #
Anyone with an idea? Would sure appreciate it. Right now I'm going through blog by blog editing out the characters. Very tedious.
Sales & Support Lead — 11th July 2011 (10 months ago) #
Hiya,
Wondering if it's related to this:
http://core.trac.wordpress.org/ticket/17998
Is this still going on for you? Let us know. Thanks!
Member — 20th July 2011 (10 months ago) #
Thanks for checking in. No, not related. I resolved the issue by editing ever post and page on every blog. Tedious, but worked. I've since updated to wp 3.2.1 and no problems. But, let's see what happens when you update the Multi-db 3.0.6 and I install it. :) .
Don't get me wrong. You guys are great! WordPress is just frustrating at times.
Sales & Support Lead — 20th July 2011 (10 months ago) #
Hiya Chuck,
Agreed... can be very tedious and frustrating. Do keep us updated with how things are going and we'll support ya as best we're able :)
Thanks!
Member — 15th August 2011 (9 months ago) #
Same problem as ChuckS
I just upgraded to Multi-db 3.0.6 on a WordPress 3.2.1 install, and all hosted blogs (all in french) are messed up. I have a black diamond question marks fort every accentued charter !
This affected old posts, new posts are not affected.
Note – It's the second problems with UTF-8 occured with an upgrade of Multi-db this year (precedence with version 3.0).
My database config for UTF-8 is correctly configured, and my datas are this time untouched in MySQL : the problem is in WordPress and created by the Multi-db upgrade...
I proved to downgrade to Multi-db 3.0.5 : same punition...
After I downgraded to Multi-db 3.0.4 and it solved the problem, but with old posts... for the new ones, and the edited ones, every accentued charter produce a weid garbage like this : “é” (for “é”), etc.
Guy, I trusted you when you write in the changelog : “Fixed character set issue”. It's mu fault.
Sales & Support Lead — 19th August 2011 (9 months ago) #
Hiya Aris,
Did you upgrade from 3.0.5?
I'll ask the developer to drop back by here and take a look with us as well.
Thanks!
Member — 24th August 2011 (9 months ago) #
This solved the character issue for me
http://premium.wpmudev.org/forums/topic/critical-character-issue-bug-report
Member — 24th August 2011 (9 months ago) #
Good find troykd! Good to know someone found the problem and a solution. I'm good for now, already edited all my posts and pages.
Lifetime Member — 24th August 2011 (9 months ago) #
Did your problem solved?
I marked resolved.If not solved,please let me know.
Cheers
Become a member