zern

I just auto-upgraded the plug in to 0.4.8 from 0.3 and it stopped working with WordPress 3.0.5.

I have rolled back to the previous stable (for me) version 0.3 and all is well again.

0.3 worked well with all versions of WP 3 so far for me.

Nope – it did not work for me on 2.3.2

The script reported Done. But it truncated every post after the first 60(?) words or so.

Lucky I had a backup!

I have had this issue twice – when migrating to 2.2, and then to 2.2.1. Both upgrades via Fantastico.

My fix is this:
– Comment out the ‘DB_CHARSET’ and ‘DB_COLLATE’ lines.
– Go to Options/Permalinks and re-save that page. (otherwise the links to posts break).

Hope this helps someone.

Thanks Moshu. All fixed now.
I upgraded via Fantastico in CPanel. (Yes, I should have read the upgrade notes before pressing Upgrade…)

There were two issues that affected my upgrade. Here’s a summary for future ref. The two problems may or may not be directly related. I found the fixes separately.

1. Upgrading to WP2.2 caused funny characters to appear.

FIX: Commenting these two lines out in wp-config.php fixed it.
// define(‘DB_CHARSET’, ‘utf8’);
// define(‘DB_COLLATE’, ”);

2. WP2.2 links to single posts from archive pages (or blog home page or search page) fails because of the presence of double byte characters in posts.

FIX: In the admin pages, I went to Options/Permalinks and re-saved the page.

This fix works on Pages only.

With Posts, the problem only appears to go away. But links to posts no longer work (page not found error).
And WordPress reports this on every non-Page page:
Warning: Invalid argument supplied for foreach() in …wp-includes/classes.php on line 88

I have just moved to WP 2.2 and these characters are everywhere. All the curly single and double quotes, ellipses, n and m dashes, bullets, and double byte (Chinese, Arabic, etc) characters are now utter gibberish.

Manually removing these characters from the DB is out of the question given the volume of material. It is not a matter of search and replace given there are double byte characters present. Aaargh!!!