Handbuch:$wgNamespaceContentModels
| Content Models and Handlers |
|---|
| MediaWiki erlaubt für Seiteninhaltstypen, die nicht Wikitext sind. Es bietet integrierte Unterstützung für JavaScript, CSS, JSON und Klartext. Extensions can use MediaWiki's ContentHandler mechanism to add new content models for accepting different formats and controlling how they are rendered, stored and edited. |
 Über |
|
Über den ContentHandler Content handlers and their implementation |
 Verwendung |
|
Changing the content model of a page Changing the content model of a namespace Extensions using the ContentHandler Adding content models with an extension Beispiele: |
 Konfigurationseinstellungen |
|
$wgContentHandlers $wgNamespaceContentModels |
| Unterstützung und Entwicklung |
 Neuste technische Dokumentation (Git) Phabricator |
| Inhalts-Handler und Speicher: $wgNamespaceContentModels | |
|---|---|
| Content types defined for a given namespace |
|
| Eingeführt in Version: | 1.21.0 |
| Entfernt in Version: | Weiterhin vorhanden |
| Erlaubte Werte: | Nicht angegeben |
| Standardwert: | [] |
| Andere Einstellungen: Alphabetisch | Nach Funktion | |
Details
Associative array mapping namespace IDs to the name of the content model pages in that namespace should have by default (use the CONTENT_MODEL_XXX constants).
If no special content type is defined for a given namespace, pages in that namespace will use the CONTENT_MODEL_WIKITEXT (except for the special case of JavaScript and CSS pages).
Beispiel
JSON
Suppose you have created a new custom namespace NS_JSON and you want all new pages in this namespace to have JSON content and to be supported by the appropriate content handler.
Add the following to your LocalSettings.php file.
$wgNamespaceContentModels[NS_JSON] = CONTENT_MODEL_JSON;
If you already created pages in this namespace, see the talk page.