Opened 16 years ago
Last modified 5 weeks ago
#10384 new enhancement
Make IIS Permalink support enabled based on capability not on version number
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | 2.8 |
Component: | Permalinks | Keywords: | needs-refresh close |
Focuses: | Cc: |
Description
At the moment we enable the IIS permalink support based on checks for IIS7 and then some capabilities.
We should remove the version checking and work solely on capabilities so that we don't have to revisit when IIS8 is released.
Attachments (2)
Change History (16)
#2
@
16 years ago
- Keywords has-patch added; needs-patch removed
The suggestion in the bug makes sense. There is no need to have a version check. It is possible to reliably figure out permalinks support on IIS even without version check.
I've attached the patch.
#3
@
16 years ago
I think functions should be deprecated first before they are completely removed. In addition, some filters have to be preserved for existing plugins (if any). A new patch, based on Ruslany's patch, has been uploaded to improve backward compatibility.
#12
@
10 years ago
- Keywords needs-refresh added; has-patch commit early removed
Refresh to avoid changing version numnbers in comments. Then re-eval for commit
#14
@
5 weeks ago
- Keywords close added
- Milestone set to Awaiting Review
I came across this ticket going through ones missing a milestone.
When this was created, IIS market share was sitting around 35%. A lot has changed, and this number now sits at roughly 4% with less than 0.4% of all WordPress sites now using Windows-based hosting.
I'm going to add a close
suggestion to allow time for any additional feedback, but I think this (and other IIS enhancements) can probably be closed out as wontfix
.
see also #10186