Fix for HTTP error 500/XMLRPC issue when publishing via Live Writer and the post has embedded images3
Whew – long title I know, but it’s what I started running into when attempting to upload a post to brokentoken via Windows Live Writer (WLW).
I’m still trying to determine whether or not I’m going to stick with/ WLW for post composition or use WordPress’ built in editor – I’m split 50/50 on it right now. Regardless of the outcome on that, I ran into an issue where I was publishing a post that had some embedded images in it, and the XMLRPC interface of WordPress kicked back an “internal server error” with a HTTP status code of 500.
Enter a little Google-fu and I found this to be a very clean and simple solution:
I have verified here on brokentoken that it was necessary and have also verified that my development environment is afflicted as well.
Simple enough fix via phpMyAdmin and all is well. I hope this helps someone else out if they run into this issue using WLW (or any XMLRPC publishing method) with embedded images.
I recently built a Windows XP virtual machine with the intention of doing wordpress theme development and testing on it.
Getting WordPress up and running normally requires running Apache, MySQL and the wordpress binaries, but instead of running Apache, I wanted to use the version of IIS included in Windows XP.
Getting everything for WordPress up and running wasn’t that difficult, but I wanted to record my steps and sources in case anyone else is considering doing the same.
Also consider installing FTP with IIS so that you have a mechanism to move files in/out of the VM. I choose to go this route so I can more easily replicate my production server configuration since mapping drives and Windows networking is out of the question in an internet-facing/production scenario.