Extension:Scribunto: verschil tussen versies

Uit HisGIS
Naar navigatie springen Naar zoeken springen
interwiki>Anomie
(Undid revision 3410036 by Tenbergen (talk) - Thanks, but let's not tell people to manually mangle their database as official instructions. The real solution would be for something like [[phab:...)
 
k (1 versie geïmporteerd)
 
(geen verschil)

Huidige versie van 25 sep 2019 om 13:46

<languages/>

MediaWiki extensions manual
Bestand:OOjs UI icon advanced.svg
Scribunto
Release status: stableLua-fout: callParserFunction: function "#translation" was not found.[[Category:stable extensions{{#translation:}}]]
Implementation Lua-fout: callParserFunction: function "#translation" was not found.
Description <translate> Provides a framework for embedding scripting languages into MediaWiki pages</translate>
Author(s)
  • Victor Vasiliev
  • Tim Starling
and others
Latest version Lua-fout: callParserFunction: function "#translation" was not found.
Compatibility policy release branches
PHP 5.5+
Database changes No
License Lua-fout: callParserFunction: function "#translation" was not found.
Download
Download extension
Git [?]:
[[Category:Extensions in Wikimedia version control{{#translation:}}]]
Namespace
Module
Parameters

  • $wgScribuntoDefaultEngine
  • $wgScribuntoEngineConf
  • $wgScribuntoUseGeSHi
  • $wgScribuntoUseCodeEditor
Hooks used
Hooks provided
Translate the Extension:Scribunto extension if it is available at translatewiki.net
Check usage and version matrix.
Issues Open tasks · Report a bug

[[Category:All extensions{{#translation:}}]]

<translate> The Scribunto (Latin: "they shall write/let them write (in the future)") extension allows for embedding scripting languages in MediaWiki.</translate> <translate> Currently the only supported scripting language is Lua. </translate>

<translate>

License

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

Requirements

PCRE version compatibility

PCRE 8.33+ is recommended.</translate> <translate> You can see the version of PCRE used by PHP by viewing a phpinfo() web page, or from the command line with the command <tvar|1>php -r 'echo "pcre: " . ( extension_loaded( "pcre" ) ? PCRE_VERSION : "no" ) . "\n";'</>.

  • Scribunto will not work with versions of PCRE lower than 8.10.</translate>

<translate>

  • PCRE 8.31 has bugs with JIT pattern studying that [[<tvar|1>phab:T73922</>|breaks various patterns when used with HHVM]].</translate>

<translate>

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.</translate> <translate> See Updating to PCRE 8.33 or Higher for details.

PHP pcntl (LTS)

</translate>

MediaWiki versions: 1.25 – 1.28

<translate> Scribunto versions for MediaWiki 1.25 to 1.28 required PHP's [<tvar|url>https://secure.php.net/pcntl.installation</> pcntl extension], which is only available on Unix/Linux platforms, if you want to use "LuaStandalone" (i.e. running in a separate child process).</translate> <translate> This requirement was removed in Scribunto for MediaWiki 1.29.

You can check whether pcntl support is enabled by viewing a phpinfo() web page, or from the command line with the command <tvar|1>php -r 'echo "pcntl: " . ( extension_loaded( "pcntl" ) ? "yes" : "no" ) . "\n";'</>. </translate>

PHP mbstring extension

PHP needs to have the mbstring extension enabled.

You can check whether mbstring support is enabled by viewing a phpinfo() web page, or from the command line with the command php -r 'echo "mbstring: " . ( extension_loaded( "mbstring" ) ? "yes" : "no" ) . "\n";'.

Lua binary

Bundled binaries

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
<syntaxhighlight lang="bash">chmod a+x /path/to/extensions/Scribunto/includes/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua</syntaxhighlight>If you are using SELinux in "Enforcing" mode on your server, you might need to set a proper context for the binaries. Example for RHEL/CentOS 7:<syntaxhighlight lang="bash">

chcon -t httpd_sys_script_exec_t /path/to/extensions/Scribunto/includes/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua </syntaxhighlight>

Additional binaries

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:

<syntaxhighlight lang="php">

  1. where lua is the name of the binary file
  2. e.g. sourceforge LuaBinaries 5.1.5 - Release 2 name the binary file lua5.1

$wgScribuntoEngineConf['luastandalone']['luaPath'] = '/path/to/binaries/lua5.1'; </syntaxhighlight> Note that you should not add the above line unless you've confirmed that Scribunto's built-in binaries don't work for you.

Installation

  • If using Vagrant , install with vagrant roles enable scribunto --provision
Manual installation
  • Download and place the file(s) in a directory called Extension:Scribunto in your extensions/ folder.
  • Add the following code at the bottom of your LocalSettings.php: <syntaxhighlight lang="php">

wfLoadExtension( 'Extension:Scribunto' ); $wgScribuntoDefaultEngine = 'luastandalone'; </syntaxhighlight>

  • Set execute permissions for the Lua binaries bundled with this extension:

<syntaxhighlight lang="bash">chmod a+x /path/to/extensions/Scribunto/includes/engines/LuaStandalone/binaries/yourOS/lua</syntaxhighlight>

  • Set type to httpd_sys_script_exec_t if SELinux is enforced:

<syntaxhighlight lang="bash">chcon -t httpd_sys_script_exec_t /path/to/extensions/Scribunto/includes/engines/LuaStandalone/binaries/yourOS/lua</syntaxhighlight>

To users running MediaWiki 1.29 or earlier:

The instructions above describe the new way of installing this extension using wfLoadExtension(). If you need to install this extension on these earlier versions (MediaWiki 1.29 and earlier), instead of <syntaxhighlight lang="php" inline="true">wfLoadExtension( 'Extension:Scribunto' );</syntaxhighlight>, you need to use: <syntaxhighlight lang="php"> require_once "$IP/extensions/Extension:Scribunto/Extension:Scribunto.php"; </syntaxhighlight>

Optional Installation

Integrating extensions

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

(MediaWiki 1.30 or earlier)Then in your LocalSettings.php after all the extension registrations, add: <syntaxhighlight lang="php"> $wgScribuntoUseGeSHi = true; $wgScribuntoUseCodeEditor = true; </syntaxhighlight>

LuaSandbox

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. See LuaSandbox for details and installation instructions.

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

Configuration

The following configuration variables are available:

$wgScribuntoDefaultEngine
Select the engine. Valid values are the keys in $wgScribuntoEngineConf, which by default are 'luasandbox' or 'luastandalone'.
$wgScribuntoUseGeSHi
When Extension:SyntaxHighlight is installed, set this true to use it when displaying Module pages.
$wgScribuntoUseCodeEditor
When Extension:CodeEditor is installed, set this true to use it when editing Module pages.
$wgScribuntoEngineConf
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.

Logging

Error output produced by the standalone interpreter are not logged by default. Configure logging with: <syntaxhighlight lang="php">$wgScribuntoEngineConf['luastandalone']['errorFile'] = '/path/to/file.log';</syntaxhighlight>

LuaStandalone

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

$wgScribuntoEngineConf['luastandalone']['key'] = 'value';
luaPath
Specify the path to a Lua interpreter.
errorFile
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.
memoryLimit
Specify the memory limit in bytes for the standalone interpreter on Linux (enforced using ulimit).
cpuLimit
Specify the CPU time limit in seconds for the standalone interpreter on Linux (enforced using ulimit).
allowEnvFuncs
Set true to allow use of setfenv and getfenv in modules.

LuaSandbox

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

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

Usage

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 ... }}

Lua

Learning Lua

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

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.

Debug console

Bestand:Scribunto debug console usage example.png
Debug console usage example

When editing a Lua module a so called "debug console" can be found underneath the edit form. In this debug console Lua code can be executed without having to save or even create the Lua module in question.

Troubleshooting

Bestand:Script error clickable Scribunto.png
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

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

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: <syntaxhighlight lang="php"> $wgScribuntoEngineConf['luastandalone']['memoryLimit'] = 209715200; # bytes </syntaxhighlight> Finally, depending on the server configuration, some installations may be helped by adding another LocalSettings.php line <syntaxhighlight lang="php"> $wgMaxShellMemory = 204800; # in KB </syntaxhighlight> Note that all 3 memory limits are given in different units.

Lua error: Internal error: The interpreter exited with status 24

When using the LuaStandalone engine (this is the default), status 24 suggests CPU time limit errors, although those should be generating a "The time allocated for running scripts has expired" message instead. It would be useful to file a task in Phabricator and participate in determining why the XCPU signal isn't being caught.

Lua error: Internal error: The interpreter exited with status 126

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

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

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

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

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

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

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

Design documents

<translate>

Other pages

</translate>

<translate>

See also

</translate>

General
  • Lua Wikibase client functionality for the Scribunto extension.
  • 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.
  • 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.
  • 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)
Extensions

<translate>

Notes

</translate>

  1. ↑ i.e. proc_open is not within the array of disable_functions in your server's "php.ini" file.

[[Category:Skins used on Wikimedia{{#translation:}}|Extension:Scribunto]]

[[Category:Scribunto extensions{{#translation:}}| ]] [[Category:ContentHandler extensions{{#translation:}}]] [[Category:GPL licensed extensions{{#translation:}}]] [[Category:MIT licensed extensions{{#translation:}}]]

Overgenomen van "https://wiki.hisgis.nl/index.php?title=Extension:Scribunto&oldid=1515"