WLW and WordPress Invalid Server Response
I have been trying to use Windows Live Writer Beta 2 to post to my wordpress blog but to no avail!
I’d keep getting this error:
Windows Live Writer was not able to automatically detect your blog: Invalid Server Response – The response to the blogger.getUsersBlogs method received from the weblog server was invalid: Invalid response document returned from XmlRpc server
I have just found this solution; add to .htaccess file
<Files xmlrpc.php>
SecFilterInheritance Off
</Files>
Done! It’s all good now.
Check out Digital Inspiration for some more solutions
[...] Solution: Add the following lines of code to your .htaccess file contained in WordPress installation folder where the xmlrpc.php file also resides. Thanks Alpesh. [...]
Alpesh,
I too had same problem. For configuring WLW its asking the path fro xmlrpc.php file. What do I give here?
http:////xmlrpc.php
I have added the code you have given to .htaccess file.
Please help me.
When I add the path as http://www.nirmaltv.com/xmlrpc.php, then it gives error 405, method not allowed.
Nirmal,
Where is .htaccess have you added this code?
It should be after
I cant see the code you have written, can you please mail me the instructions?
[...] Solução: Adicione as linhas a seguir no código do arquivo .htacess contido na pasta onde sua instação de WordPress reside, juntamente do xmlrpc.php. Agradecimentos a Alpesh. [...]
what about wordpress.com blog?
I have been trying to use Windows Live Writer 2 to post to my wordpress.com blog but to no avail!
I’d keep getting this error:
Windows Live Writer was not able to automatically detect your blog: Invalid Server Response – The response to the blogger.getUsersBlogs method received from the weblog server was invalid: Invalid response document returned from XmlRpc server
Have a look at
http://www.corelan.be:8800/index.php/2008/10/14/windows-live-writer-unable-to-connect-to-wordpress-blog/
Не помогает этот ваш код, после его вставки в .htaccess сайт вобще перестал работать.
Kind Regards,
Alpesh Nakar
alpesh@nakars.com
[...] Another solution by Alpash Nakers is to add the following lines in your .htaccess [...]