https://bugzilla.wikimedia.org/show_bug.cgi?id=33120

--- Comment #6 from George Herson <[email protected]> 2011-12-15 07:24:56 
UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > My PHP's rusty, so I didn't immediately remember dirname():
> > $wgScriptPath = dirname($_SERVER["SCRIPT_NAME"]); 
> > 
> 
> That won't work on Windows.

It is working on MediaWiki 1.15.1 on XAMPP 1.7.7 on Windows 7.

(In reply to comment #5)
> My goal is to ensure that MediaWiki is not fragile enough to break simply
> because an extension defines a new entry point.
> As it stands with the pattern you are suggesting if an extension defines an
> entry point like /extensions/FooBar/baz.php the SCRIPT_NAME will be
> /extensions/FooBar/baz.php, then $wgScriptPath will become 
> "/extensions/FooBar"
> and suddenly every link generated from that entrypoint breaks. 

Let us focus.  Does calculation of an autodetecting $wgScriptPath default cause
a problem when a valid $wgScriptPath setting in LocalSettings exists?  If it
doesn't (and it won't with IFs checking for the relevant environmental
conditions, like CLI), all we have done with autodetection is increase the
generality of our default, and lost nothing.  No?

When the default value doesn't work, the administrator will simply have to set
the value manually, just as currently.  But in the meantime, their MediaWiki is
more likely to work, entirely or sometimes.  Additionally, if/when the wiki
doesn't work will provide the admin with important clues absent from the
universal breakage that results for a completely non-functioning $wgScriptPath.
 What we have now is a MediaWiki that, after a site move within XAMPP that does
not include a diligent updating of $wgScriptPath, hands the browsing user the
XAMPP homepage unconditionally, which is really very little info with which to
find and fix their wayward $wgScriptPath.  No?

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.

_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to