In a previous post, I mentioned that I was investigating a way to use real permalinks without using any of the ISAPI mod_rewrite dlls. For the uninitiated, mod_rewrite is not natively supported in IIS (Window’s server), and to get the same functionality, you have to install separate programs. I’ve done that and that is how this blog has survived on a Windows server for the past year or so.

I was convinced that needn’t be the case though. There must be a way to have permalinks without having to install a whole separate mod_rewrite program (or extension). I detailed my plan in this post.

Well, I finally got around to it – and the plan worked!

Here’s the gist of it. It uses custom 404 redirect to send all “Page Not Found” errors to a script that reads a bunch of regular expressions (don’t worry, you don’t have learn regular expressions to use this) and figures out what page to feed back.

Now, some people may find my solution a bit odd considering it is written in ASP. You used ASP to extend wordpress?? Yes, and it worked :).

More detailed instructions, and a link to the needed files are located here:

WordPress Permalinks in IIS

WordPress 2.0 came out a little while ago. I’m installing it on a new site and ran into a problem on the install step.

The fix is to comment out line 38:

Line 38 in wp-settings.php is a “fix” for (quote):
// Fix for PHP as CGI hosts that set SCRIPT_FILENAME to something ending in php.cgi for all requests

Is this the case with your server?

http://wordpress.org/support/topic/53438

Note: I’m running WordPress on a Windows 2003 server with MySQL on the same box. That might have been the source of the error.

Took a little while, but I managed to reset my root password. I’m installing a new blog and forgot the root. Here’s the official documentation on how to do it:

http://dev.mysql.com/doc/refman/5.0/en/resetting-permissions.html