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.
Thread Starter
Jon
(@ezkim0x)
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?
Thread Starter
Jon
(@ezkim0x)
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
http://jonindie.com/index.php/2005-10-14/test/
That’s because you’ve created an invalid permalink rule. The % symbols need to be separated by backslashes (/). You should use:
/index.php/%year%/%monthnum%/%day%/%postname%/
Thread Starter
Jon
(@ezkim0x)
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.
Check the .htaccess file in WordPress’ directory. Are there any WordPress-specific re-write rules in it?
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…
Thread Starter
Jon
(@ezkim0x)
there isn’t a .htaccess file in the dir.. should there be? and if so, what should it have in it?
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.ww.wp.xz.cn).
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.
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:(
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 …
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.
