Nazgul

See this and this topic.

Your host should be able to recover it.

(If they can’t, I suggest looking for another host, with decent support)

Errcode 13 is a generic error thrown by MySQL. It’s not a WordPress specific error.
So ask your host if they did anything to the database.

It looks like it’s Extended Live Archive.

It has to do with and old version of PHP in combination with a change they made in WordPress 2.0.3.

They fixed it in the yet to be released 2.0.4 version, but take a look at this topic for some workarounds in the meantime.

1: It’s already fixed in trunk, but this way you don’t have to wait for version 2.0.4 to be released to use those fixes.

If you just open the files one by one and translate just the texts, you should be fine. You can just edit around the PHP.

And the worst that can happen is that your changed theme goes wonky, which is easily solved by deleting that theme from the server to go back to the default and then try again with a fresh uploaded version.

peter-b, try installing the WordPress 2.0.3 Tuneup plugin. That should fix your problem.

It depends on the theme you’re using if your frontpage language matches your backend language.

Most of the themes I’ve encountered don’t support multi-language/language switching and most of the text in it is still hard-coded.

So if you install the English WordPress your back-end wil be English, but the front-end can be French by using a French theme, or manually translating an English one.

I’ve done this on my blog, where the back-end is English and the front-end is Dutch. It took me just 5 minutes to translate the theme, although I have some experience with PHP and XHTML.

Take a look at the Role Manager plugin.

Go to https://validator.w3.org for the validator.

You have your comment. ??

Try fixing your XHTML validation errors. That usually fixes these kind of things.

The default maximum execution time is 30 seconds, so if they set it to 5 seconds on that machine, I’d go talk to your hoster, because there are a lot of scripts that have a valid reasson for taking a few seconds to execute.

I don’t know what the Akismet options page does exactly, but if it queries another website for instance, it’s quite easy to timeout after those 5 seconds.

I’m assuming, you’re talking about the blog mentioned in your profile?

If so, try fixing the validation errors, as they are the most likely source for these kind of problems.