Template:Extension/nl

  {{Documentation|content= {{intricate template}} {{lua|Module:Extension|Module:ExtensionJson|Module:String}} {{Uses TemplateStyles|Template:Infobox/styles.css|Template:Extension/styles.css|Template:Extension/status.css}} Dit sjabloon moet toegevoegd worden aan elke hoofdpagina van een extensie op deze wiki (alleen op de hoofdpagina). Het voegt een nuttige box met informatie (zie onder) toe en voegt de extensie toe aan {{ll|Category:All extensions}}, met de betreffende {{ll|Category:Extensions by status|status}} en {{ll|Category:Extensions by implementation type|implementatie type}} categorieën.

Inhoud parameters
Deze sectie beschrijft de parameters die de box met informatie vullen. Voor hulp met templatemode en andere controle parameters, zie Controle parameters. Any other value for 'type' is invalid, and will cause the extension to be placed in Category:Extensions with invalid or missing type.
 *  - aangepaste opmaak sjabloon met parameters, bijv.
 *  - aangepaste opmaak XML tag, bijv. 
 *  - aangepaste opmaak sjabloon zonder parameters, bijv.
 *  - Extensies die niet standaard wiki syntaxis toevoegen (bijv. not tags, parser functies of variabelen).
 * - vangnet voor, dat zijn extensies die rechten aanmaken, authenticeren, verlenen, intrekken of de activiteiten van gebruikers volgen. Als u een extensie voor de toegang heeft gemaakt, gebruik dan een van de volgende meer specifieke types:
 * - extensies die gebruikersactiviteiten monitoren (logins, logouts, gebruiker toevoegen, enz.)
 * - extensies die gebruikers toevoegen of verwijderen en/of de identiteit van een gebruiker verifiëren
 * - extensions to the rights management system, e.g. changes to the way rights are assigned, API, maintenance tools (does not include extensions that merely name the rights needed to use the features of that extension; for this purpose use the rights parameter)
 * - vangnet voor gebruikersinterface extensies zonder categorie.
 *  - extensions that permit the embedding of multimedia content on wiki pages by registering a file extension with.
 *  - extensions that provide infrastructure so that users may personalize their MediaWiki experience and/or assist in the management of that infrastructure
 * - extensions that email users, broadcast messages and provide other forms of community notification
 *  - extensions that enhance or modify s. This includes anything that implements an action that reads, writes, searches for, creates, renames, deletes, redirects or discusses a page. It does not include rights (use user rights) or logs (use user activity).
 * - extensions that search through and select pages for users.
 * - extensions adding CSS or JavaScript, or implementing hook functions to change the look and feel of MediaWiki via the skins framework.
 * - extensions that use Ajax programming techniques.
 * - extensions that subclass the class, use one of its hooks, or patch one or more functions in . See  for more information.
 * other
 * - extensions that add a new API module or extend a core API module.
 * - Hook extension - defines a new hook - see hook1, etc. below if you want to define hooks used by your extension
 * - adds tables and/or fields to the database backing a MediaWiki installation
 * - Gegevens extractie
 * - extension that adds new file repository types as file backend
 * - Not a real extension, but an example of how to write one
 * - extensions that new.
 * - extensions to the underlying programming language.
 * - extensions associated with localization
 * - extensions associated with localization

Note: Many extensions have more than one type, if this applies to yours, replace  with. You may define up to six types for an extension. hook1 hook2 hook3 hook4 ...  naam van elke hook die door de extensie wordt gebruikt Entering values in this field is a good way to get exposure for your extension and help other developers. Each documented hook will automatically add the extension to a category listing extensions that use that hook. This category is autolinked to each hook page so that programmers can easily find examples of extensions that use a particular hook.

For built-in hooks:
 * use the hook name alone. Please see for values (but omit introductory '/').

For custom hooks defined by extensions:
 * use extensionName/hookName. For a partial list of custom hooks, see Extension hook registry.

For multiple hooks, assign the first hook to hook1, the second to hook2 and so on. newhook1 newhook2 newhook3 newhook4 ... newhook90 name of each hook provided by the extension

You might also want to add the hooks to Extension hook registry. username  The author's username on MediaWiki.org (if they have one). May be omitted, but if present it will be used to link to the author's user & user_talk page. It should be provided without namespace and without s.     The extension author's name, if different from their MediaWiki.org username. Vrije tekst. Indien weggelaten wordt het veld 'gebruikersnaam' gebruikt (indien aanwezig). description  korte beschrijving schermafbeelding of logo van extensie. Het moet zonder namespace en zonder s worden ingevuld. facultatief, grootte van de afbeelding (standaardgrootte is 220px) laatste versie datum van de laatste wijziging compatibility policy   (geaccepteerde waarden zijn master, rel en ltsrel). Verplichte versie van MediaWiki. Most extensions should not need to use this — it defaults to the value of the property of. See also Category:Extensions without MediaWiki version and Category:Extensions with manual MediaWiki version. verplichte versie van PHP indicates that the extension requires a database table schema change or a similar action, before the MediaWiki can run. It is a common pitfall: your MediaWiki will stall, if you forgot to run update.php - if the extension requires it. should be set as a value since this assures that the extension does not need update.php to be run and thus avoids uncertainty

Extensions which conform to MediaWiki extension standards come with a schema change script which you need to start manually (once) before starting and accessing the MediaWiki through your browser, and after you copied all the extension files to  and inserted   into "LocalSettings.php", run from the command line:

composer  The extension's Composer package name, in the standard format. It will be automatically included if set in an extension's "composer.json" file (i.e. this parameter is not required in that case). It will be linked to the extension's page on Packagist. table1 table2 table3 table4 ... table30 name of each non-core table used by the extension

Links to a subpage of your extension page. For instance, "table1 = cu_changes" at will link to. Don't list core tables such as or ; only list tables that are added by extensions. license governing use of this extension, as one of the codes found in https://spdx.org/licenses/, e.g.,   or  , etc. download  link om te downloaden : Git, WikimediaDownload. repo  Naam van de Gerrit repository waar de code staat, indien dat afwijkt van de naam van de pagina. Door het invullen hiervan wordt automatisch download gezet, en mag het sjabloon automatisch gegevens downloaden uit het passende bestand. externe link naar het bestand readme, bijv. https://phabricator.wikimedia.org/r/browse/mediawiki/extensions/Flow;master;README externe link naar het bestand changelog, bijv. Extension:LDAP Authentication/Changelog beschikbare parameters voor LocalSettings.php elke tag die de extensie gebruikt (bijv. &lt;tag1&gt;, &lt;tag2&gt;). rights added by the extension. Not to be confused with the license! Rights are such as ' or ', not such as GFDL or LGPL or GPL - those are licenses! namespace in which this extension is used Link to user-help for the extension. If not provided, will look for. If provided, full wikitext link should be given (because you may want to link to e.g. an external page). example, website or screenshot of working extension Additional compatibility information, for instance compatibility charts. It's encouraged to add any client-side compatibility information here too, especially when diverging from expectations of full support for a browser. Optional parameter to link the exact page where (message group id with which) the extension will be translatable on translatewiki.net if enabled. If the default link is incorrect, manually set it to: Bugzilla MediaWiki extension component name Phabricator projectnaam overschrijf de paginanaam die gebruikt wordt voor de link controleer gebruik.
 * ext-LOWERCASE(NOSPACES(Label as defined in )), aka
 * the parameter you get in the URL after
 * typing the name of the extension in the search/filter box at translatewiki:Special:Translate or
 * searching for its name in languagestats after clicking "expand all".

Controle parameters
because this isn't an actual extension page and we don't want to add this page to any categories on account of it.
 * nousage - suppresses the 'check usage' link. Link is also suppressed if the page is a subpage; it is not in the Extension: namespace; or if suppressed by 'templatemode=nocats'

If this is left blank, this template will add the host page to Category:All extensions and to one or more additional categories, depending on the values assigned to the Content parameters.

Bestaande extensie pagina
If you want to add the infobox to an existing page, copy and paste the code at the top of this page.

Een extensie pagina aanmaken
If you want to create a new extension page, enter the name below and click the button. A new page will be created with the infobox template already in place.

Sjabloon verbeteren
Als u dit sjabloon wilt verbeteren, alvast bedankt! Dit is een complex sjabloon, er is wat hulp geweest bij de ontwikkeling:

Knop Extensie aanmaken
Om het gedrag te verbeteren van de knop om een extensie aan te maken:


 * : The boilerplate extension that is preloaded into newly-created pages.
 * : An input box that can be inserted wherever you want users to easily create extensions. For documentation on the tag, please see.

Infobox parameters
In het algemeen:


 * To make this template easy to use, each label in the infobox is linked to documentation on the template parameter(s) it displays. If you add a parameter, please be sure to also add it to the content parameter documentation and link its label to that documentation.

To change/correct/add to the implementation type parameters:
 * Check the talk page - there have been some extensive discussions about this field.
 * The valid types and what they link to are defined at Module:Extension

To change the behavior of the hook parameters:


 * Template:Extension/HookInUse: Adds links and categories for a hook in use. Multiple hooks in use are implemented by calling this template with Template:Foreach.
 * Template:Extension/HookInUseNoCats: Used instead of Template:Extension/HookInUse when this template is used in . Templates used with Template:Foreach can only take one parameter so we need to wrap the call to Template:Extension/HookInUse with another template that sets the mode.

Testgeval
Controleer of de volgende pagina's nog goed zijn na het wijzigen van dit sjabloon.
 * Extension:Description2
 * Template:Extension

}} Maintenance: vulnerabilities, archived