OK even more bizarre. A forum I hadn't touched at all yet had 126 rows in it with an empty post_body. Looking at post_body_default it appears those had unicode characters in them. The posts table is still at its default latin1-default collation and MyISAM setting. So it can't have anything to do with touching the table. So maybe this happened during the MySQL upgrade? When I try to add a post to it with curly quotes in this state the post_body stays blank but the post_default_body fills in properly.
I have verified this. On the other forum all I did was change the ubbt_posts table to be UTF8 default for both the whole table and the body row in particular. Then I copied over the post_body_default field into the post_body field. Those rows now work fine.
However, I still have an issue. When I make a *new* post with unicode characters, the post_body_default fills in fine - but the post_body stays blank. It won't set with the values.
Thoughts?
