Posts Tagged ‘WordPress’

WordPress and PHP on Windows Server 2008

Tuesday, March 9th, 2010

Guess what? WordPress rocks on Windows Server 2008 and IIS7. Congratulation to Microsoft for the effort. If you didn’t know Microsoft created the FastCGI component to address previous performance issues with PHP on Windows. At the same time Zend worked to make PHP more stable on Windows. The two combined to make reliable and high performance PHP on Windows. FastCGI support is now built in to Windows Server 2008. There is plenty of documentation available for setting everything up manually but let me tell you this, don’t waste your time. Microsoft is really getting serious about PHP on Windows. They have created the Web Platform Installer 2.0 and that’s all you really need. Once you install the Web Platform Installer you can run it and choose to install applications like WordPress and Joomla. The installer checks to see if you have the necessary components, if you don’t then it downloads and installs them. This includes PHP, MySQL, and the application, like WordPress. It also installs an IIS URL ReWrite module so you can have pretty permalinks for your WordPress Blog. For novice or inexperienced Windows server admins I recommend you let the Platform Installer take care of everything for you.

For advanced users I will warn you that, at the time of my last install you could not change the default install path for MySql or PHP. This is easy to get around, just download and install PHP and MySql before you use the Platform Installer for the first time to set up WordPress. The Platform Installer will recognize your installations. Happy Blogging.

Almost forgot, here is how you create 301 redirects on Windows Server 2008 (and server 2003 with IIS6) if you are migrating from an existing site to a CMS platform.

—David Blizzard

Why Use WordPress on Windows Server 2003?

Tuesday, December 9th, 2008

UPDATE: This document is not for Windows Server 2008 please see WordPress and PHP on Windows Server 2008

We have tried a few DotNet blogs and were not completely happy so we have decided to go with WordPress. I will note that Subtext has potential and those of you like us that build sites based on DotNet and MS SQL might want to give that a try if WIMP is not an option. [Download Subtext DotNet Blog]

Another option is to build your own DotNet Blog application from scratch. We started that project but it’s always on the shelf while we keep up with our current customer requests and new design projects. So that leaves us with the option of WordPress on Windows.

Pros: It’s a full featured application with plenty of support articles. It can validate as strict XHTML with the right theme or some minor tweaking. If you want to roll your own using DotNet you have a long way to go just to get 75% of the features that you get in WordPress. It looks, functions, and feels like a commercial application. It’s not difficult to install and performance is quite good using FastCGI on IIS.

Cons: If you are a DotNet website developer then you probably don’t have PHP and MySQL installed on your servers. You might not be comfortable, from a security perspective, running software you are not familiar with on your servers.

Tips:

  1. Use FastCGI from Microsoft to increase PHP performance.
  2. Use this URL rewrite ISAPI filter to remove index.php from WordPress permalinks

Warnings: The above mentioned ISAPI filter seems to have an issue if your WordPress installation is not in the root.

Update: This is a good IIS 6 mod-rewrite workaround that works even when the blog is in a sub folder. Copy John’s code from that website into a custom 404 file in your blog root. Be sure you use a file extension of php and then map your 404 in IIS to the custom file. Choose URL and not File in the custom errors tab of IIS for the 404.

—David Blizzard

WordPress and PHP

Tuesday, December 9th, 2008

I can’t believe we’re actually using PHP on Bliznet.com, and WordPress no less.

Doesn’t mean I’m going to give up on the BlizDev ASP.NET Blog though.

Addendum: This is intimidating. Maybe I will.

—Kyle Blizzard