That's the reason why I always symlink extensions/ to my common extensions folder.
/path/to/common/extensions/ /path/to/mywiki/* /path/to/mywiki/extensions -symlink-> /path/to/common/extensions/ /path/to/anotherwiki/* /path/to/anotherwiki/extensions -symlink-> /path/to/common/extensions/
It works perfectly fine for extension's interface components, it's great for checking out the entire svn extensions but still having separate wiki installations, while avoiding eating up disk space unnecessarily. It's perfectly valid, but the maintenance script issue is still there.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
Brion Vibber wrote:
On 8/12/09 6:43 PM, Aryeh Gregor wrote:
On Wed, Aug 12, 2009 at 5:03 PM, Brion Vibberbrion@wikimedia.org wrote:
Your setup is incorrect: the extensions folder *always* goes inside the MediaWiki root dir. Always.
I don't do this on my development wiki. I use a checkout of trunk, so extensions/ is inside phase3/../. Are there any significant problems with us supporting extensions/ being in an arbitrary location,
Yes, it's a pain in the ass. ;)
Note also that many extensions have user interface components including JavaScript, CSS, and image files -- we need a predictable path to reach them, and that's the extensions folder.
as long as phase3/extensions/ reliably points to it both on the web and filesystem level? Is there really no other reliable way to do standalone PHP scripts in extensions than require_once "../../LocalSettings.php"?
Standalone scripts should be loading up includes/WebStart.php or maintenance/commandLine.inc and not attempting to find LocalSettings.php themselves.
In any case they need to be able to find and reach that setup info, which is what a stable directory tree provides.
-- brion