Extension:HeadScripts
From MediaWiki.org
 Release status: beta |
|||
|---|---|---|---|
| Implementation | Parser extension | ||
| Description | |||
| Author(s) | Jean-Lou Dupont | ||
| Last Version | 1.0.0 | ||
| MediaWiki | 1.11 | ||
| License | No license specified | ||
| Download | SVN See SVN ($Id: HeadScripts.doc.wikitext 658 2007-10-29 16:10:50Z jeanlou.dupont $) |
||
|
|||
|
check usage (experimental) |
|||
Contents |
[edit] Purpose
Provides adding scripts to the site's HEAD.
[edit] Features
- Secure: only users allowed to access the namespace MediaWiki
- Accessible through a wiki page in the MediaWiki namespace under the 'Registry' sub-namespace
- MediaWiki:Registry/HeadScripts
[edit] Example
Here is an example of 'MediaWiki:Registry/HeadScripts' page:
{| border=1
{{#headscript:http://code.jquery.com/jquery-latest.min.js|jQuery}}
|}
[edit] Dependancies
[edit] Installation
See the Mediawiki Extension table entry "download" above.[1]
[edit] LocalSettings.php
Extension:ExtensionManager: See footnote[2]
- Add the following to LocalSettings.php if the extension was downloaded from Jean-Lou Dupont's MediaWiki SVN directory (link in the download entry of the table above)[2]:
require_once( "$IP/extensions/HeadScripts/HeadScripts.php" );
[edit] PEARPEAR is a repository of en:PHP software code.
require 'MediaWiki/HeadScripts/HeadScripts.php';
[edit] Upgrades through PEARSometimes, it is necessary to clear PEAR's cache in order to perform upgrades.
or use the force method:
[edit] PEAR Web FrontendFor easier remote package management, PEAR Frontend WEB can be installed. Installation notes can be found here. An example of the WEB frontend is available here. |
[edit] RSS feed
To keep kept up-to-date with this channel, use the following RSS feed__
.
[edit] Notes
[edit] Other Extensions From the same author
Consult User Jldupont's page.
- ↑ The most recent release is always available through the extension's PEAR and SVN repositories. This page is not necessarily up-to-date.
- ↑ 2.0 2.1 2.2 Extension:ExtensionManager does not require any modification to LocalSettings.php because ExtensionManager includes the extension.
Note that if PHP code caching is in place (e.g. APC, eAccelerator), then to successfully complete the installation a cache flush might be needed. - ↑ Modifications to
LocalSettings.phpis only necessary if not using Extension:ExtensionManager
