All posts in category Wordpress
Quick update for today, but I wanted to alert all visitors that the site just went live with a brand-new theme that I’ve been working on for quite some time now.
I also upgraded the site to WordPress 3.11, implemented native menus and re-worked some of the plug-ins (got rid of a bunch of redundancy and tried to optimize things as much as possible).
I’m also super-happy to report that brokentoken now has its first sponsor!
We are now hosted on the CBeyond (formerly MaximumASP) cloud services platform, so this is a huge upgrade in bandwidth, uptime and reliability than was previously available, so they are making the site nice and fast and their support is greatly appreciated.
Please page around the site and feel free to leave any comments/issues/constructive criticism.
First off, let me say this - Wincache FTW!
OK – with that off my chest, I can get down to business. This post is a long time in the making. I’ve spent a considerable amount of time over the past few months testing numerous site configurations (Windows/IIS versions, PHP, mySQL, WordPress plug-ins, etc.) to find out which will run best for me. In short, it’s been nothing short of a learning experience – many times very frustrating but finally very rewarding.
When I originally put up the site, I was steadfast in my commitment to having everything running on 64-bit Windows. That meant that I had three choice to deploy on:
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.