I'm not sure about the www. compatibility, I dont believe they are
supposed to work with WPMU / 3.0 Multisite, "www" is itself, a site.
What is the server environment you're running under? How are you handling
the rewrite rules?
I mis-understood your original post, I didnt realise that what you were
doing was ignoring the suggested pathinfo permastruct, and inserting your
own permastruct. I assumed that this was the first version that WordPress
had told you that you required them..
Feel free to open a new trac ticket on http://core.trac.wordpress.org/
explaining the issue
On Sat, 24 Apr 2010 13:34:24 +1000, HelixGalaxy <[email protected]>
wrote:
Hello,
I'm asking this because it seems like some changes have been made, where
in
single site mode all urls are stripped of "www":
www.site1.com --> *site1.com*
I don't know why the www is stripped? Looks starnge to me on a single
site
install.
----
The bigger problems is when switching to multi-site setup, the
www.site1.comgive an 404-error
Also is another site is created, lets say test1.site2.com then
www.test1.site1.com --> redirected to signup page with www.test1 as a
subdomain. So www is not stripped, but www.test1 treated as a new
subdomain.
Seems like some logic have been changed that don't work properly.
Regards,
Martin
---------- Forwarded message ----------
From: HelixGalaxy <[email protected]>
Date: 2010/4/24
Subject: Re: [wp-testers] Forced custom permalink structure with
PATHINFO?
To: [email protected]
Hello Dion ,
Was some of the logic also that all links are stripped out of www?
This is not the case with 2.9.2?
Regards,
Martin
2010/4/24 HelixGalaxy <[email protected]>
Hello,
Thanks.
That filter works, but I don't think this is the right way to go,
forcing
it like that. It is enough having /index.php explained in the codex and
let people shoose it for themselves if they need it.
Think this should be taken out.
Having IIS6 and mod_rewrite compatibility confuses people what is going
on.
Regards,
Martin
2010/4/24 Dion Hulse (dd32) <[email protected]>
Some logic was changed recently (by me) which might've caused it.
(See
http://core.trac.wordpress.org/changeset/14051/trunk/wp-admin/options-permalink.php)
The check for forcing it is:
79 if ( ! got_mod_rewrite() && ! $iis7_permalinks )
80 $prefix .= '/index.php';
If you're running IIS7 then you shouldnt be seeing it.
If you're running something else, you may need to force WordPress to
realise it.
For example:
add_filter('iis7_supports_permalinks', '__return_true');
//__return_true
is a 3.0 function, that does what it says..)
You can put that in a plugin, or in a theme functions.php file, or in a
/wp-content/mu-plugins/force-iis_permalinks.php file, etc.
On Sat, 24 Apr 2010 11:58:14 +1000, HelixGalaxy <[email protected]>
wrote:
Hi,
Downloaded the latest nightbuild and after installing I see that when
I
want
to set the custom permalink structure is forced on me with /index.php
in
front?
Why and how can this be removed? Is it a bug?
It wasn't a problem some nights ago ...
Yes I run IIS on WIndows, but have no problem with mod_rewrite
compatibility.
Regards,
Martin
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
--
Dion Hulse / dd32
Contact:
e: [email protected]
msn: [email protected]
skype: theonly_dd32
Web: http://dd32.id.au/
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
--
Dion Hulse / dd32
Contact:
e: [email protected]
Web: http://dd32.id.au/
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
