Ready to get started?Download WordPress


Windows Server - Using Permalinks with IIS no apache. (17 posts)

  1. Jon
    Posted 8 years ago #

    I can't get permalinks to work on my site.


    I've read that, and my host doesn't use apache, I emailed them and they responded with the following..


    The reason companies provide Windows hosting is because customers want the functionality of IIS and not Apache :) We certainly dont use apache on Windows and I can't really think of any 'real' Windows hosting company using Apache for their webserver."

    Is there anyway to still use permalinks?

  2. Yes, the link that you have posted details how to use permalinks on a IIS server. As detailed in the link, you have to tag /index.php/ onto the front of the permalink rule, but that's the only downfall.

  3. Jon
    Posted 8 years ago #

    I've tried that, and it still doesn't work.. It just acts like the page doesn't exist.. Do the posts need to be made after you've changed your permalinks?

  4. Jon
    Posted 8 years ago #

    Just tested by changing them again, and then posting.. same thing. I'll leave the permalinks changed, so you can see what I mean.

    Here's what I have: /index.php/%year%-%monthnum%-%day%/%postname%/

    domain: jonindie.com

  5. That's because you've created an invalid permalink rule. The % symbols need to be separated by backslashes (/). You should use:


  6. Jon
    Posted 8 years ago #

    Ok, I put in exactly what you said.. and now my link should be: http://jonindie.com/index.php/2005/10/14/test/

    but it still doesn't work.

  7. Check the .htaccess file in WordPress' directory. Are there any WordPress-specific re-write rules in it?

  8. RustIndy
    Posted 8 years ago #

    macmanx - the variables do not need to be seperated by / characters - that's only a folder designation. It's fine to use hyphens, spaces, the letter "s", or even nothing between those % variables.

    at least, it worked for me...

  9. Jon
    Posted 8 years ago #

    there isn't a .htaccess file in the dir.. should there be? and if so, what should it have in it?

  10. RustIndy
    Posted 8 years ago #

    To be honest, I'm not a 'real' Windows host, so I stupidly run Apache 2 on my Windows server (alongside IIS), where htaccess works just fine ;) So I'm not sure how the permalinks for IIS work - but the codex does contain that information, so that should be your first stop to look for it (http://codex.wordpress.org).

  11. Well, according to this, you don't need a .htaccess file for this kind of set. So, I have no clue as to what's wrong.

  12. Jon
    Posted 8 years ago #

    any more suggestions?

    get a new host? ;/

  13. fredCZ
    Posted 8 years ago #

    As far as I know - there is only one way how to get working parmalinks on Windows and IIS. You have to install (ask your webhosting company to install:) a ISAPI rewrite or similar thing into IIS.

    Trick with /index.php/ works only on Apache:(

  14. w1m
    Posted 8 years ago #

    I got it to work by creating the php.ini file mentioned in the docs: http://codex.wordpress.org/Using_Permalinks#Using_Permalinks_Without_mod_rewrite

  15. tsimmons
    Posted 8 years ago #

    I have never gotten permalinks to work on my IIS server. I think I have tried all of the suggestions out there, but adding the two lines to my php.ini makes no difference. I still receive a 404 error anytime I try to request index.php (or any php page) with a trailing slash. Has anyone else gotten permalinks to work on IIS without using ISAPI_rewrite or anything like that?

    This has become like a hangnail, just an irritating thing that lingers and lingers ...

  16. mountaineer
    Posted 8 years ago #

    I'm running WordPress on a WIMP host account (Windows, IIS, MySql, PHP) and just got permalinks to work using both the /index.php/ trick in combination with the php.ini file (http://www.webthingsconsidered.com is the site).

    I created an empty php.ini file with the following two lines as directed in the help:
    cgi.fix_pathinfo = 1
    cgi.force_redirect = 0

    Uploaded this to the web root and I was in business.

  17. freakazoid
    Posted 7 years ago #

    Here is the solution that worked for me (my host is running IIS 6 servers)

    Go to this site http://www.nathanm.com/wordpress-plugins/ and download his plugin "WordPress Remove Index.php from Permalinks in IIS Plugin."

    Run it and install it into the plugins directory. Before activating it, go to the control panel that your host offers and set up your 404 error page to the relative root path of your blog. For instance, if your blog is installed in a subfolder on your domain, simply direct the 404 error page to that subfolder . . . e.g., /subfolder/.

    Activate the plugin and voila!

    NathanM has directions at the link I supplied as well.

    Worked for me when nothing else would!

Topic Closed

This topic has been closed to new replies.

About this Topic