Moderator
James Huff
(@macmanx)
Volunteer Moderator
if it was an apache only feature for windows and not iis, then evidentally some people wouldn’t have gotten it to work..
Give me a break… because it is an issue for you then it should be removed for the rest of us? You need a more realistic view of your self-importance. I’d say it is a bit more than excessive.
Edit: 🙂
My point was if the feature doesn’t reliably work on Windows/IIS, make that clear. It has nothing to do with being self-important. estjohn has the best point here – if some have gotten it to work with IIS 6, then its NOT an Apache-only feature. Its a feature that’s problematic with IIS, to say the least. And I think it counters the “famous 5 minute install” concept (which except for this feature has been my experience), but then again, I’m new to all of this, and that’s probably just the NEXT comment that will piss someone off.
As for it “being an issue for me”, I’d say its more like “its an issue for everyone running WP in an IIS-hosted environment. WP should probably handle permalinks differently if it takes an act of Congress to configure them to work outside of its own environment. THAT was the point.
Macmanx – the php.ini solution won’t work in many (most?) shared hosted environments. The webhost enabling the fix for me probably breaks something for someone else (the scope of php.ini at my host is server-wide, not account wide).
Why not just be able to feed a querystring to WP and have it sort out what to retrieve, rather than sodding around with redirects at all?
Huh. That’s a real problem with your host then, cchurch. My host is able to give me a totally customized php.ini file…. doesn’t have any effect on any space but mine….
But then, my host runs linux.
cchurch, what DOES work reliably on an MS product?
Let’s pull out the whip, huh?
I have no problem warning about custom permalinks being an iffy affair for IIS users (WP knows when when it’s running on IIS, so it could add such a note appropriately). However, I don’t see how this conflicts with the “famous 5 minute install.” The permalink structure is a customization issue, not an installation one.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
The php.ini file can easily be made to affect only it’s directory and those below it, similar to a .htaccess file. I have been through five shared hosting providers in my life, and all have allowed php.ini customization. But, then again, I have always used Linux-based Apache hosting providers. So, I guess that could be yet another IIS issue.
To clarify my last comment above… I should have said the fix may not work in most IIS SHARED HOSTED environments. I don’t want to imply its a problem elsewhere…
For macmanx – the three Windows shared hosting providers I have access to do not support php.ini at the scope of an account, only at the scope of a server. I think you’re right – this is some (additional) quirk related to IIS.
Kafka – my comment on the 5 minute install is that every other aspect of the product works in 5 minutes. You’re right – technically, configuring pretty permalinks is not part of the 5 minute install. I guess I equated “5 minute install” with “all features up and running in 5 minutes”, which has pretty much been my experience with the notable exception of the permalinks. Its a gap… but maybe non-technical users should use permalinks. Doesn’t seem like a reasonable solution to me, but that’s a solution.
How can I help fix this? Rather than just complain, what sort of resources does WP need to look at the issue and perhaps either craft a mass-workaround for IIS hosted implementations, or rearchitect the feature and allow a new approach to run in parallel with the existing approach? Its a valuable feature, and the product is awesome otherwise in my mind.
I don’t understand your fervent desire to alter WP for IIS. Should there be a caveat in the documentation about possible problems with IIS and permalinks, sure, but altering WP core for that is like designing my theme to work in IE, then hacking it be standards compliant, IMHO.
Personally, if I was using Windows and IIS and I couldn’t get it to work.. then I would install Apache on Windows and drop the IIS. Then it would work quicker than waiting till someone came up with a new vesion tailored just for IIS. I always had less problems with Apache on Windows that I have with IIS anyway.
