From MediaWiki.org
Jump to: navigation, search
MediaWiki extensions manualManual:Extensions
Crystal Clear action run.png

Release status:Extension status stable

ImplementationTemplate:Extension#type Parser extension
DescriptionTemplate:Extension#description Provides a framework for embedding scripting languages into MediaWiki pages
Author(s)Template:Extension#username Victor and Tim (Tim Starlingtalk)
Latest versionTemplate:Extension#version Continuous updates
MediaWikiTemplate:Extension#mediawiki master supports 1.25+, use REL1_XX branches for older versions
PHPTemplate:Extension#php 5.3+
Database changesTemplate:Extension#needs-updatephp No
LicenseTemplate:Extension#license GPL-2.0+ AND MIT
NamespaceTemplate:Extension#namespace Module
  • $wgScribuntoDefaultEngine
  • $wgScribuntoEngineConf
  • $wgScribuntoUseGeSHi
  • $wgScribuntoUseCodeEditor
Hooks usedTemplate:Extension#hook

Translate the Scribunto extension if it is available at translatewiki.net

Check usage and version matrix.


Open tasks · Report a bug

The Scribunto (Latin: "they shall write") extension allows for embedding scripting languages in MediaWiki. Currently the only supported scripting language is Lua.


This extension contains code licensed GNU General Public License v2.0 or later (GPL-2.0+) as well as code licensed MIT License (MIT).


PCRE version compatibility[edit]

PCRE 8.33 or later is recommended. You can see the version of PCRE used by PHP by viewing a phpinfo() web page, or from the command line with the command php -i | grep 'PCRE'.

CentOS 6 and RHEL 6 are stuck on PCRE 7 and need to be upgraded.

Updating to 8.33 on a server with an older version may be relatively complicated. See Updating to PCRE 8.33 or Higher for details.

PHP pcntl[edit]

Since Scribunto for MediaWiki 1.25, your PHP server also needs to have pcntl enabled (only works with Unix/Linux platforms) if you want to use "LuaStandAlone" (i.e. running in a separate child process). Under Windows, Scribunto will run Lua only as "LuaSandbox" (within the same PHP thread as the thread used by MediaWiki to run this Scribunto extension, but within the sandboxing PHP environment configured by Scribunto).

PHP mbstring extension[edit]

PHP needs to have the mbstring extension enabled.

To see if it installed on your server, you can check if it is enabled by running the command php -m on the server. If the string mbstring is present in the output, the extension is enabled.

Lua binary[edit]

Bundled binaries[edit]

Scribunto comes bundled with Lua binary distributions for Linux (x86 and x86-64), Mac OS X Lion, and Windows (32- and 64-bit).

Scribunto should work for you out of the box if:

  1. Your web server is run on one of the above platforms.
  2. PHP's proc_open function is not restricted[1]
  3. Your web server is configured to allow the execution of binary files in the MediaWiki tree.
Note Note: Execute permissions may need to be set; for example, in Linux use
chmod a+x /path/to/extensions/Scribunto/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua

Additional binaries[edit]

Additional Lua binary distributions, which may be needed for your web server if its operating system is not in the list above, can be obtained from http://luabinaries.sourceforge.net/ or from your Linux distribution. Only binary files for Lua 5.1.x are supported. Once you've installed the appropriate binary file on your web server, configure the location of the file with:

# where lua is the name of the binary file
# e.g. sourceforge LuaBinaries 5.1.5 - Release 2 name the binary file lua5.1
$wgScribuntoEngineConf['luastandalone']['luaPath'] = '/path/to/binaries/lua5.1';

Note that you should not add the above line unless you've confirmed that Scribunto's built-in binaries don't work for you.


Manual installation

  • Download and place the file(s) in a directory called Scribunto in your extensions/ folder.
  • Add the following code at the bottom of your LocalSettings.php:
    require_once "$IP/extensions/Scribunto/Scribunto.php";
    $wgScribuntoDefaultEngine = 'luastandalone';
  • Set execute permissions for the Lua binaries bundled with this extension:
chmod a+x /path/to/extensions/Scribunto/engines/LuaStandalone/binaries/yourOS/lua
  • Set type to httpd_sys_script_exec_t if SELinux is enforced:
chcon -t httpd_sys_script_exec_t /path/to/extensions/Scribunto/engines/LuaStandalone/binaries/yourOS/lua
  • YesY Done - Navigate to Special:Version on your wiki to verify that the extension is successfully installed.

Optional Installation[edit]

Integrating extensions[edit]

For a more pleasant user interface, with syntax highlighting and a code editor with autoindent, install the following extensions:

Then in your LocalSettings.php after all the extension registrations, add:

$wgScribuntoUseGeSHi = true;
$wgScribuntoUseCodeEditor = true;


We have developed a PHP extension written in C called LuaSandbox. It can be used as an alternative to the standalone binary, and will provide improved performance.


In (MW install path)/extensions or elsewhere:

git clone https://gerrit.wikimedia.org/r/p/mediawiki/php/luasandbox.git


Install the headers and library files for PHP and either Lua 5.1.x or LuaJIT 1.1.x.

  • For Debian-derived Linux distributions, such as Ubuntu:
sudo apt-get install php5-dev
sudo apt-get install liblua5.1-dev
  • For Centos/Redhat-derived Linux distributions:
sudo yum install php-devel lua lua-devel
  • For Mac OS X:
brew install lua


luasandbox here is the directory that luasandbox git repository was cloned to.

For php-fpm or PHP module of Apache[edit]
cd luasandbox
phpize && ./configure && make && sudo make install

Then make sure that there is file luasandbox.ini at /etc/php5/conf.d with extension=luasandbox.so inside. You may have to do this yourself. Also, your installation of PHP5 may have separate directories for Apache and the PHP command line interface: /etc/php5/apache2/conf.d and /etc/php5/cli/conf.d respectively.

If you initially installed the extension to use the Lua standalone binary, be sure to update LocalSettings.php with this: $wgScribuntoDefaultEngine = 'luasandbox';.

After Apache or php-fpm restart, the extension should be reported by phpinfo () and Special:Version.

For HHVM[edit]
cd luasandbox
hphpize && cmake . && sudo make install

Under Debian systems, you could need to replace cmake . with cmake . -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DLUA_USE_CPP=1[2].

Then add

hhvm.enable_zend_compat = true

to /etc/hhvm/php.ini. You may need to replace the path to luasandbox.so (/usr/lib/x86_64-linux-gnu/hhvm/extensions/20150212) with whatever install path was reported by make install.

After executing sudo service hhvm restart, the extension should be present in get_loaded_extensions () and reported by Special:Version.


  • Add the following extension reference: extension=luasandbox.so
  • Restart the web server
  • Verify that there is a luasandbox section on the phpinfo() page
    • if you use nginx, make sure you edit the fpm php.ini file (e.g. /etc/php5/fpm/php.ini in Ubuntu)
  • Some PHP installations have two php.ini files, see Manual:php.ini


The following configuration variables are available:

Select the engine. Valid values are the keys in $wgScribuntoEngineConf, which by default are 'luasandbox' or 'luastandalone'.
When Extension:SyntaxHighlight is installed, set this true to use it when displaying Module pages.
When Extension:CodeEditor is installed, set this true to use it when editing Module pages.
An associative array for engine configuration. Keys are the valid values for $wgScribuntoDefaultEngine, and values are associative arrays of configuration data. Each configuration array must contain a 'class' key naming the ScribuntoEngineBase subclass to use.


Error output produced by the standalone interpreter are not logged by default. Configure logging with:

$wgScribuntoEngineConf['luastandalone']['errorFile'] = '/path/to/file.log';


The following keys are used in $wgScribuntoEngineConf for Scribunto_LuaStandaloneEngine. Generally you'd set these as something like

$wgScribuntoEngineConf['luastandalone']['key'] = 'value';
Specify the path to a Lua interpreter.
Specify the path to a file, writable by the web server user, where the error and debugging output from the standalone interpreter will be logged.
Specify the memory limit in bytes for the standalone interpreter on Linux (enforced using ulimit).
Specify the CPU time limit in seconds for the standalone interpreter on Linux (enforced using ulimit).
Set true to allow use of setfenv and getfenv in modules.


The following keys are used in $wgScribuntoEngineConf for Scribunto_LuaSandboxEngine. Generally you'd set these as something like

$wgScribuntoEngineConf['luasandbox']['key'] = 'value';
Specify the memory limit in bytes.
Specify the CPU time limit in seconds.
Specify the time between polls in sections for the Lua profiler.
Set true to allow use of setfenv and getfenv in modules.


Scripts go in a new namespace called Module. Each module has a collection of functions, which can be called using wikitext syntax such as:

 {{#invoke: Module_name | function_name | arg1 | arg2 | arg3 ... }}


Learning Lua[edit]

Lua is a simple programming language intended to be accessible to beginners. For a quick crash-course on Lua, try Learn Lua in 15 Minutes.

The best comprehensive introduction to Lua is the book Programming in Lua. The first edition (for Lua 5.0) is available online and is mostly relevant to Lua 5.1, the version used by Scribunto:

The reference manual is also useful:

Lua environment[edit]

In Lua, the set of all global variables and functions is called an environment.

Each {{#invoke:}} call runs in a separate environment. Variables defined in one {{#invoke:}} will not be available from another. This restriction was necessary to maintain flexibility in the wikitext parser implementation.

The environment which scripts run in is not quite the same as in standard Lua. These differences are noted in Special:MyLanguage/Extension:Scribunto/Lua reference manual#Differences from standard Lua.


Troubleshooting using the clickable "Script error" link.

Note that red Lua error messages are clickable and will provide more detailed information.

Lua error: Internal error: The interpreter exited with status 1[edit]

When using the LuaStandalone engine (this is the default), errors along the lines of "Lua error: Internal error: The interpreter exited with status 1" may be generated if the standalone Lua interpreter cannot be executed or runs into various runtime errors. To obtain more information, assign a file path to $wgScribuntoEngineConf['luastandalone']['errorFile']. The interpreter's error output will be logged to the specified file, which should prove more helpful in tracking down the issue. The information in the debug log includes debugging information, which is why there is so much of it. You should be able to ignore any line beginning with "TX" or "RX".

Lua error: Internal error: The interpreter exited with status 2[edit]

When using the LuaStandalone engine (this is the default), status 2 suggests memory allocation errors, probably caused by settings that allocate inadequate memory space for PHP or lua, or both. Assigning a file path to $wgScribuntoEngineConf['luastandalone']['errorFile'] and examining that output can be valuable in diagnosing memory allocation errors.

Increase PHP allocation in your PHP configuration; add the line memory_limit = 200M. This allocation of 200MB is often sufficient (as of MediaWiki 1.24) but can be increased as required. Set Scribunto's memory allocation in LocalSettings.php as a line:

  $wgScribuntoEngineConf['luastandalone']['memoryLimit'] = 209715200; # bytes

Finally, depending on the server configuration, some installations may be helped by adding another LocalSettings.php line

  $wgMaxShellMemory = 204800; # in KB

Note that all 3 memory limits are given in different units.

Lua error: Internal error: The interpreter exited with status 126[edit]

When using the LuaStandalone engine (this is the default), errors along the lines of "Lua error: Internal error: The interpreter exited with status 126" may be generated if the standalone Lua interpreter cannot be executed. This generally arises from either of 2 causes:

  • The lua executable file's permissions do not include Execute. Set permissions as described under #Installation.
  • The server does not allow execution of files from the place where the executable is installed, e.g. the filesystem is mounted with the 'noexec' flag. This often occurs with shared hosted servers. Remedies include adjusting $wgScribuntoEngineConf['luastandalone']['luaPath'] to point to a Lua 5.1 binary installed in an executable location, or adjusting or convincing the shared host to adjust the setting preventing execution.

Error condition such as: Fatal exception of type MWException[edit]

Check the MediaWiki, PHP, or webserver logs for more details on the exception, or temporarily set $wgShowExceptionDetails to true.

version `GLIBC_2.11' not found[edit]

If the above gives you errors such as "version `GLIBC_2.11' not found", it means the version of the standard C library on your system is too old for the binaries provided with Scribunto. You should upgrade your C library, or use a version of Lua 5.1 compiled for the C library you do have installed. To upgrade your C library, your best option is usually to follow your distribution's instructions for upgrading packages (or for upgrading to a new release of the distribution, if applicable).

If you copy the lua binaries from Scribunto master (or from gerrit:77905), that should suffice, if you can't or don't want to upgrade your C library. The distributed binaries were recently recompiled against an older version of glibc, so the minimum is now 2.3 rather than 2.11.

Lua errors in Scribunto files[edit]

Errors here include:

  • attempt to index field 'text' (a nil value)
  • Lua error in mw.html.lua at line 253: Invalid class given:

If you are getting errors such these when attempting to use modules imported from WMF wikis, most likely your version of Scribunto is out of date. Upgrade if possible; for advanced users, you might also try to identify the needed newer commits and cherry-pick them into your local installation.

preg_replace_callback(): Compilation failed: unknown property name after \P or \p at offset 7[edit]

preg_replace_callback(): Compilation failed: unknown property name after \P or \p at offset 7

  • this usually indicates an incompatible version of PCRE; you’ll need to update to >= 8.10
  • @todo: link to instructions on how to upgrade

Lua error[edit]

If you copy templates from Wikipedia and then get big red "Lua error: x" messages where the Scribunto invocation (e.g. the template that uses {{#invoke:}}) should be, that probably means that you didn't import everything you needed. Make sure that you tick the "Include templates" box at w:Special:Export when you export.

When importing pages from another wiki, it is also possible for templates or modules in the imported data to overwrite existing templates or modules with the same title, which may break existing pages, templates, and modules that depend on the overwritten versions.

Blank screen[edit]

Make sure your extension version is applicable to your MediaWiki version.

Design documents[edit]

Other pages[edit]

See also[edit]

  • Extension:Capiunto - Provides basic Infobox functionality for the Scribunto extension.
  • Extension:Wikibase Client - Provides Wikibase (part of Wikidata project) Lua client functionality for the Scribunto extension.
  • wikidata:Help:Lua - there may be specific notes for using Lua modules on Wikidata, including additional Lua extensions installed (e.g. for local support of internationalization and for database queries)
  • commons:Commons:Lua - there may be specific notes for using Lua modules on Wikimedia Commons, including additional Lua extensions installed (e.g. for local support of internationalization and for parsing or playing medias). Some general purpose modules may be reused in other wikis in various languages (except specific tunings for policies, namespaces or project/maintenance pages with dedicated names). If possible, modules that could be widely reused across wikis should be tested and internationalized on Commons.
  • metawiki:Lua - some internationalized modules that could be deployed on all wikis are developed and maintained on Wikimedia MetaWiki (because it is less risky than on Wikimedia Commons). These modules will also have less dependencies than those developed on large scale wikis such as Wikimedia Commons and English Wikipedia, and will be easier to port to other wikis.
  • wikipedia:Help:Lua - there may be specific notes for using Lua modules on (English) Wikipedia, including additional Lua extensions installed (including for integrating Wikidata and Wikimedia Commons contents, generating complex infoboxes and navigation boxes, or to facilitate the general administration/maintenance of the wiki contents under applicable policies). Some other localized Wikipedia editions (or other projects such Wiktionnary, Wikisource or Wikinews) may also have their own needs and Lua modules.
  • Extension:Semantic Scribunto - Provides native support for the Scribunto extension for usage with Semantic MediaWiki


  1. i.e. proc_open is not within the array of disable_functions in your server's "php.ini" file.
  2. See https://phabricator.wikimedia.org/T115779.

Language:Project:Language policy English  • 日本語 • português do Brasil