WordPress.org

1. deanlee
   Member
   Posted 5 years ago #

   Because IIS does not support mod_rewrite modules for rewriting url, so whenever you try to use permalinks, you always get something like this: http://deanlee.cn/index.php/2006/09/02/url-rewriting-for-wordpress-under-iis/

   There are some products that enable rewriting on IIS (most are commercial):

   ISAPI_Rewrite (http://www.isapirewrite.com/)
   URL Rewrite (http://www.iismods.com/url-rewrite/index.htm)
   IIS Rewrite (http://www.qwerksoft.com/products/iisrewrite/)
   but these products are much too complex for me,off cause,and no source code available.so I decided to write a IIS plugin that designed specifically for WordPress Permalinks.

   you can download this plugin here:

   http://deanlee.cn/2006/09/02/url-rewriting-for-wordpress-under-iis/

   enjoy it

2. moshu
   Member
   Posted 5 years ago #

   Probably a one line instruction or something would be helpful for the users :)

3. Chris_K
   Member
   Posted 5 years ago #

   ooooh, where were you 1 year ago when I was on a windows server?!? Looks good, bookmarked it. :-)

4. Les Bessant
   Moderator
   Posted 5 years ago #

   Might be worth noting that this is a DLL that has to be installed on the server by the server admin, not something that users of a shared server are going to be able to add to WP to make pretty permalinks work.

   Good to have it for people who are running their own IIS servers, though.

5. moshu
   Member
   Posted 5 years ago #

   Thanks, LesBessant!
   That's exactly what I was missing - though I understand only the "you-have-to-be-a-server-admin" part :)

6. deanlee
   Member
   Posted 5 years ago #

   thanks for your reply,I have updated my document and files,and add some install Instruction in it.

   http://deanlee.cn/2006/09/02/url-rewriting-for-wordpress-under-iis/

   hope it can be helpful to others.

7. Stephane
   Member
   Posted 5 years ago #

   Hi,

   I installed the DLL in the root directory of my website. Registered it in ISAPI filters so now it appears with a green up arrow and a low priority.

   I set permalinks to /%year%/%monthnum%/%day%/%postname%/ or /index.php/%year%/%monthnum%/%day%/%postname%/

   and it still giving me « No input file specified ».

   Am I missing something??

   Thanks,

   Stephane

8. Stephane
   Member
   Posted 5 years ago #

   Finally, I got it to work on IIS 6 and win 2k3 with this:

   http://www.nathanm.com/2006/07/02/wordpress_permalinks_removing_indexphp_in_iis.html

   The plugin is here:

   http://www.nathanm.com/wordpress-plugins/

   Stephane

9. deanlee
   Member
   Posted 5 years ago #

   to Stephane:
   did you install your wordpress as a virtual directory,not in the root directory?

10. deanlee
    Member
    Posted 5 years ago #

    I have added a new feature to this plugin:
    http://www.deanlee.cn/2006/09/02/url-rewriting-for-wordpress-under-iis/

    now,this plugin can generate a 302 redirect to http://www.yourdomain.com when user or spider fetch yourdomain.com. this is a SEO feature, because the search engines usually see them as two separate sites.you can find this SEO tip at http://www.pronetadvertising.com/articles/optimizing-your-blog-for-search-engines.html by Neil Patel

    If you find it useful, I’d love to know. If you have any suggestions on how to improve it, I’d love to hear it

11. mrmmills
    Member
    Posted 5 years ago #

    My ISAPI filter problem - How I fixed it - Remaining Security Questions:

    I had followed the following site word for word:
    http://www.juryriggin.com/2006/11/07/fixing-permalinks-when-using-wordpress-windows-2003-iis-60 but WordPress ISAPI filter was creating many Application log errors 2268 and 2214

    So I then (most hazardly and without web security in mind) added the WordPress users "site_name_Anon" and "site_name_Admin" to the IIS_WPG user Group (it is creatd by W2k3 by default) and I also gave the user IIS_WPG "read" and "execute" permissions to the WordPressPlugin.dll file.

    ** My Permalinks and ISAPI WordPress Filter now work !! **

    The question I have now is: What security holes have I created?

    ******************************
    Why I did what I did:

    I had gone to the following site to troubleshoot my ISAPI WordPress Filter problem.

    http://blogs.msdn.com/david.wang/archive/2005/06/21/HOWTO-Diagnose-and-Fix-Common-ISAPI-Filter-Installation-Failures.aspx?CommentPosted=true#commentmessage

    It educated me and I learned that my error was :
    Data: 05 00 00 00 -Win32 error 5 - NET HELPMSG 5 returns "Access is denied."

    The article then mentions:

    "For IIS6 in worker process isolation mode, the process identity is configurable and is at least a member of the IIS_WPG group" (see more on the link)

    That's when I got the idea to add the WordPress users "site_name_Anon" and "site_name_Admin" to the IIS_WPG user Group (it is creatd by W2k3 by default) and I also gave the user IIS_WPG "read" and "execute" permissions on the WordPressPlugin.dll file.

Topic Closed

This topic has been closed to new replies.