Greg creates a great matrix to compare the features of Live Spaces, WordPress, Blogger and LiveJournal. If you are thinking about to start a blog or switch to another blog software maybe this list will help you to find the best blog software for your needs.

Link: Metablogging – Windows Live Community

1. Select a text

   

2. Hit the SEO Slug plugin from the insert panle on the right side

   

3. Click on OK

   

4. Now hit F2 and press CTRL+V in the Slug field

   

Normaly the slugs of my post and the titles are the same but in some special cases the seo slug plugin can be very usefull:[rate:4/5]

Download: Tech MOSS Team – Release: Imtech SEO Slugs Live Writer Plugin

[rate:overall]

via mastykarz.nl

But there is another less dangerous possibility, a wrong character set. If you blog is set for example to UTF-8 and the Windows Live Writer tries to publish with ISO-8859-2 you will get the following error message:

“an unexpected error has occured while attempting to log in: Blog Server Error -32700 Occured parse error. not well formed”

How do you change the character set?

Windows Live Writer auf Tools >> Accounts

Edit >> Advanced

Done.

Thanks to ichsags.de

Invalid Server Response – The response to the blogger.getUsersBlogs method received from the weblog server was invalid: Invalid response document returned from XmlRpc server.

Unfortunately there is more than one reason for this error message and maybe you have to try them all.

Php problem

There is an error in the php modul. Open the xmlrpc.php in your wordpress root directory and enter this code on the first line:

$HTTP_RAW_POST_DATA = file_get_contents(“php://input”);

Htaccess problem

There is a conflict in the htaccess file, enter the following code somewhere in the htaccess file:

<Files xmlrpc.php>
SecFilterInheritance Off
</Files>

PlugIn conflict

A plugin is causing a conflict. Try to deactivate all plugins and repeat the setup.

Lowercase vs. capital letters

WordPress runs on Apache and on apache lowercase matters. Login with your FTP program and check if the xmlrpc.php is written in lowercase if not upload again all files in the right format.

Note: It happens often after a WordPress update

XMLRPC activated?

With WordPress 2.6 there is the a new option (wordpress >> write) to deactivate the xmlprc api (standard: deactivated) Box must be checked

Add a new blog or if it is the first blog you are adding the window will appear automatically.

Select "Another weblog service"

Enter the url to your weblog, your username and the password

The Windows Live Writer tries now to detect your blog software

Unfortunately it doesn’t detect Serendipity automatically. You have to do it by yourself.

Choose "Movable Type API" as weblog type

In the field below enter http://{full path to Serendipity}/serendipity_xmlrpc.php where you have to enter the url to you weblog without the { }

Finish

Note: If you don’t want to setup an ftp connection and use the Windows Live Writer to upload the photos, just create a folder "WindowsLiveWriter" inside the folder "upload" and give it write rights (666).

via s9y.org and suntsu.ch

Problem:

When you try to publish a post to your blog you are getting this error: “An unexpected error has occured while attempting to log in: Blog Server Error  Server Error -32700 Occured parse error. not well formed”

Solution:

This Problem occures when you use wordpress as your blog software. In fact it is a spam injection to your wordpress installation. This is possible when your wordpress installation or your server isn’t as secure as it should be. Some wordpress files were changed on the server so you getting this error.

To solve this problem, you should replace the files on your server with the original wordpress files of the same version as installed. It looks like the following files are affected:index.php

• xmlrpc.php
• wp-admin/admin.php
• wp-admin/index.php
• wp-includes/wp-db.php
• wp-includes/pluggable.php
• wp-includes/gettext.php
• wp-includes/default-filters.php (critical!)

You also should check your .htaccess file for suspicious redirects and remove them. You have to remove the wp-includes/class-mail.php file. This file does not belong to wordpress and is a security leak.

The server wordpress is installed have to get secure. There is an article on wordpress codex that shows some methods to hardening wordpress.

Further informations:
gordon.dewis.ca
Kakkoi
via Windows Live Writer Group

In some cases, the tagging console is not available, even with WordPress 2.3.1. To solve this problem you have to add a simple code line between <head> and </head> in your WordPress theme.

<link rel=”wlwmanifest” type=”application/wlwmanifest+xml” href=”http://www.domain.com/wp-includes/wlwmanifest.xml” />

After this little step the tagging console will be available in the Windows Live Writer 2008

Via MyDigitalLife

It’s a little known fact, but deep within the labyrinths of Microsoft there is a team of rogue ninjas making a fantastic Windows blogging client.

If you compare the capabilities of the last Windows Live Writer release and WordPress 2.1 with the new Windows Live Writer and WordPress 2.2 you notice that much work was done.

Special thanks to:

• Tobbi
• Markus
• Roland
• Scott

If you want to contribute to expand this list, please send me a screenshot

Weblog >> Edit Weblog Settings >> Account >> Capabilities >> View capabilities

• Image uploading fails
• Posting fails for some blogs that don’t use UTF-8, ISO-8859-1, or US-ASCII encodings
• Bad Behavior plugin doesn’t like Windows Live Writer
• Invalid response from blogger.getUsersBlog
• Non-ASCII characters render incorrectly on UTF-8 encoded blogs
• ArgumentOutOfRangeException while attempting to open posts from WordPress blogs