Last modified: 2008-11-25 21:41:48 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T18460, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 16460 - Allow extension folder other than $IP/extensions
Allow extension folder other than $IP/extensions
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Configure (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Alexandre Emsenhuber [IAlex]
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2008-11-25 21:14 UTC by Siebrand Mazeland
Modified: 2008-11-25 21:41 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Siebrand Mazeland 2008-11-25 21:14:40 UTC 
Configure currently only allows configuration of extensions in $IP/extensions/.

Bug:
* does not allow configuration for allowed and enabled extensions in a different path

Feature request:
* allow a different path to be set for all extensions. In case of running from a checkout of mediawiki/trunk/, extensions are at $IP/../extensions for example.
Comment 1 Siebrand Mazeland 2008-11-25 21:30:24 UTC 
Apparently already implemented in r43904, which I missed. Thank you, Alex!
Comment 2 Brion Vibber 2008-11-25 21:34:20 UTC 
MediaWiki and MediaWiki extensions assume all extensions will be in the 'extensions' directory, and things will generally fail if you pull them from a non-standard location. Particularly anything with:

* CSS
* JavaScript
* maintenance scripts
Comment 3 Alexandre Emsenhuber [IAlex] 2008-11-25 21:41:48 UTC 
Some extensions (e.g. Configure itself) allow to use the MW_INSTALL_PATH env variable in maintenance scripts to set the path to the core, so this is not really an issue.
However CSS and JS might be a problem.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links