Firas

Try putting this in wp-config.php:

set_time_limit(300);

Remove it once you’re done.

It’s near-impossible to do via a plugin. You’ll need someone to create a custom newsletter design and even if they do I’m not sure how carefully it can be matched to the wp template.

Definitely, Jane, it’s the standard approach with this issue. Check out Multiple Loops… though their writeup makes it sound pretty hairy. Essentially you’d be using query_posts.

.narrowcolumn { float: left; }

Maureen, I experienced the same thing—commenting out the two lines in wp-config.php changed the weird characters in question, but didn’t set them back to the actual character I’d typed in.

Anyway, eureka—a fix! (Suggested by Eric Anderson):

1. Convert text columns to blobs
2. Change collation on the table
3. Convert blobs back to text

I tried it on a copy of my wp_posts table and it worked, though I haven’t done it on all my live data yet.

I was going to make a plugin that takes care of this issue, but not sure that I’ll get around to it—figured I’d at least point out the manual way of fixing things.

Remember to backup your database first!!

Only you can make the cost/benefit decision re: wp vs. blogger, but you know, you might as well try figuring out what the problem is. Try putting this near the top of wp-config.php:

error_reporting(E_ALL); ini_set('display_errors', 1);

If you’re on Apache you can add this to your .htaccess before the WP rewriterules:

RewriteBase /
RewriteRule ^blog/(.*) /$1 [R=301,L]

Yes it does. The least you could do is look it up.

If you’re familiar with LEFT JOIN… you need to cross reference the post_ID with the one in post2cat

I’m not sure what you’re asking for… some plugins work, some don’t. C’est la vie, eh?

You could drop a note to the plugin author asking about it or post to this forum about the specific plugin in question.

You need query_posts, not get_posts.

Wow, that’s bizarre. Are you the sysadmin on the hosting machine? Definitely something different about your setup. Is the http response being proxied somehow? I’d get in touch with the host just to see if they’re familiar with what would have caused that sort of output.

(Clearly a sign from Xenu. Find your nearest E-meter.)

More to the point, what automated backup method are you using?

This is getting fairly comical. The collation is not relevant. I promise. It has little to do with the blog language. And it has nothing to do with Safari’s behavior.

I think you have a problematic plugin, or maybe internet connection issues. Does everything work fine in Firefox?

(PS. The collation is just the default setting your database came with. So if you reply to this with, “but—Swedish!“, I shall despair for our species.)

Keep in mind that these are different issues:

-> Characters in database are ok but not displaying correctly.
-> Characters in database are wrong but fine after re-editing post content (which is the case with me.)
-> Characters wrong in wp but still not fixed after re-editing via wp.

They’re symptoms of entirely different problems, with accordingly different probable solutions. Make triple-sure you know where the error is occurring:

-> Check your database in phpmyadmin to see if the original characters within it are wrong.
-> The other thing that could be introducing the error is WP and/or its configuration (or something else in the php layer including phpmyadmin.)
-> Then there could be a http/html issue making the browser misunderstand the intended character mapping.

Again, first step when you see this: make sure you know what level the error is being introduced in.