Comments on: Enable custom errors in WordPress on IIS 7.0

By: ruslany

ruslany — Fri, 28 Aug 2009 20:42:43 +0000

@kjcristiano: I have been using the Passthrough approach now on my blog for couple of months not and it seems to work fine so far. If there is not custom messager from the app, then IIS should use the default custom error.

By: kjcristiano

kjcristiano — Fri, 28 Aug 2009 20:36:07 +0000

I see you have now linked to the blog post about using Passthrough Error messages for IIS 7 and wordpress.

Have you tested this out?

I know with wp_die it will through IIS a 500 error if a comment does not have all the required fields which returns an Internal Servber Error on IIS7, but the custom text on apache. So the passthrough will solve this issue, but what if there is no custom message from the App?

I have started to test this out (and so far it works fine), but before I implement on my blogs I’d love to know how others have fared with this.

Thanks,

Kevin

By: ruslany

ruslany — Wed, 12 Aug 2009 23:13:39 +0000

This blog post explains a better way of enabling custom errors on IIS 7.

By: Alan

Alan — Fri, 31 Jul 2009 11:10:56 +0000

Thank you!

This is the stuff that works! Thank you, thank you, thank you!

Alan.

By: ruslany

ruslany — Fri, 09 Jan 2009 00:50:32 +0000

On IIS 6.0 follow these steps:

1. In the IIS manger tree view choose the web site where WordPress is installed;
2. Right click and select “Properties”;
3. In the dialog choose the “Custom Errors” tab;
4. In the list of the errors find the 404 error and double click on it;
5. In the “Edit Custom Errors Properties” dialog, choose message type as URL and enter URL as /index.php?error=404

By: naokiharu

naokiharu — Tue, 06 Jan 2009 16:17:46 +0000

Hi,
Would you also tell me know how to configure the same thing on IIS6.0? I’m using WHS + IIS 6.0 + FastCGI + PHP 5x.