Allow extension folder other than $IP/extensions
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	siebrand
	Nov 25 2008, 9:14 PM

Description

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.

Version: unspecified
Severity: enhancement

Details

Reference: bz16460

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:28 PM

• bzimport added a project: MediaWiki-extensions-Configure.

• bzimport set Reference to bz16460.

siebrand created this task.Nov 25 2008, 9:14 PM

Apparently already implemented in r43904, which I missed. Thank you, Alex!

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

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.

Allow extension folder other than $IP/extensionsClosed, ResolvedPublicActions

Description

Details

Event Timeline

Allow extension folder other than $IP/extensions
Closed, ResolvedPublic
Actions