index.php/ PATHINFO forced when mod_rewrite/iis7 permalinks not available

[bloggus]

(Created by dd32: Originally reported in #13104)
Hi,

I have been using WP and WPMU with IIS6 and compatibility with mod_rewrite for years. No problem.

Also have been testing out laterst beta1 and today I decided to make a clean install of nightly build of the code.

This are the issues I discovered, divided in three section:

1. - Single Site

After installing I realized that in the permalinks section I'm forced to use /index.php whick is hardcoded. dd32 explained in the list that this is because I'm not runing IIS7 or Apache. I had to add a filter to remove it. I think most of all this is wrong to force index.php on anybody and this should be removed. I would have to add the filter in all themes for example and there are stil many using IIS6 with some mod_rewrite compatible software.

[dd32]

Issues 2&3 are still in #13104

Comment from nacin on pathinfo links:

I agree we probably should adjust index.php handling, but note that MU never handled PATHINFO links properly it seems.

This is where it was changed (by me)

[14051] Check the appropriate radio option on the Permalinks page for the Root blog; Display index.php prefixes properly for the root Multisite Blog. Fixes #12952

[dd32]

After looking into an alternative implementation of this, I've also noticed that the Permalink selection page does not operate without javascript.

[dd32]

I've got a patch coming up this week that implements no-js support, uses jQuery, restores the ability to remove the index.php/ prefix, AND works with Multisite still..

[dd32]

I've got a patch coming up this week that implements no-js support, uses jQuery, restores the ability to remove the index.php/ prefix, AND works with Multisite still..

Will post this during the WCSF Code sprint next week, Flying out pretty soon and dont have time to finalise the code.

[bloggus]

Do you think this commit will make into final 3.0?

[wpmuguru]

In MU the /index.php was added to the textbox(es) so the user could remove it if they know they are using an alternate web server. Many MU installs use Nginx for performance. This is a significant issue for those installs.

[anointed]

I am currently solving the problem by using a plugin with the following code in it:

add_filter('got_rewrite', '__return_true');

This solves the problem, although I am sure there is a better way to fix the issue

[nacin]

[14553] revert non-rewrite permalink settings to be compatible with 2.9, see #13106

[wpmuguru]

taking the blocker off because the main issue is fixed.

[dd32]

Cheers nacin, I was just coming to ask someone to revert it for me.

Someone should note however, That index.php permalinks will now be broken for the main blog on MU.

[nacin]

Actually, it was wpmuguru, but the ticket wasn't referenced right in the commit so the hook never fired. I would have done it anyway, of course :-)

So, we still need to fix pathinfo links on the main blog still. While these have never worked in MU (apparently), I'm going to bump the severity again as that's quite crippling.

[wpmuguru]

Replying to dd32:

Cheers nacin, I was just coming to ask someone to revert it for me.

Someone should note however, That index.php permalinks will now be broken for the main blog on MU.

This behaves identically to MU 2.9.X. I wonder if with the index.php permalink base whether the /blog is necessary? Probably not, since the /blog was added to prevent collisions with other blogs.

[ocean90]

See also #13303

[nacin]

Related: [14732]

[wpmuguru]

(In [14733]) don't use both /blog & /index.php on main site permalinks, see #13106

[wpmuguru]

Can some folks with IIS test that and let us know if that fixes the issue?

[bloggus]

I have updated to latest nightly build and updated the options-permalink.php manually, updated the permalinks settings.

Running: IIS6, PHP 5.2x, MySQL, subdomain installation of WP (MS)

So far I see that the issues I have reported are gone. index.php is not forced on the links anymore.

My server with IIS7 is not up at the moment, but it shouldn't be a problem if it works on IIS6.

Thanks.