Help:System message

From SacredWiki
Jump to navigation Jump to search
MediaWiki Handbook: Contents, Readers, Editors, Moderators, System admins +/-
45px 50px
A proposal to move this page to was rejected.
Because the Template:MoveToMediaWiki tag was on the page for a year without any importers seeing fit to transwiki it, the move proposal was regarded as rejected by the community.

The user language of a page rendering is:

The user language determines the interface texts; also the page body may depend on the user language, because the result of parser function int does, and hence also the result of templates which call that function directly or indirectly (see Category:User interface language dependent templates).

In principle for every language a set of ca. 1800 system messages in that language is provided in the message file languages/messages/Messageslanguagecode.php. With language code qqx the message keys are returned.

MediaWiki supports over 330 languages. For completeness of the language files see localization statistics.

As of October 2007 there were ca. 100 languages with a Wikipedia but without a language file. These Wikipedias usually had English as site language, and/or translated the interface locally. However, nowadays creating the language file is a condition for opening a new language edition of Wikipedia, see Meta:Language proposal policy#Requisites, and the translation is done on, so that number has decreased to a handful.

MediaWiki namespace

The MediaWiki namespace is one of the 16 standard MediaWiki namespaces. It allows administrators to change the default system messages. The MediaWiki namespace is enabled by $wgUseDatabaseMessages=true;, which is the default.

For example, see MediaWiki:Aboutpage, MediaWiki:Aboutpage/fr, and MediaWiki:Aboutpage/de.

However, MediaWiki:Sidebar/language_code does not work (for a sidebar for users with that interface language); instead, the page MediaWiki:Sidebar can refer to message IDs which provides link labels dependent on the user-specified interface language. If the message is neither defined in the message file concerned, nor on the MediaWiki page, the message in the message file for English is used.

When viewing a "non-existing" page of which the name is an existing message name, the page shows the default. A "non-existing" page can be recognized by the lack of a history link. When editing such a page, the default is automatically preloaded into the edit window. Transclusion of a "non-existing" page in the MediaWiki namespace trancludes the default.

For the names of all "existing" pages see @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

For all supported languages, all default messages and current versions can be viewed at Special:Allmessages. When creating a page to override the default it is useful to first save the default version, to allow diffs with it.

An administrator with access to the language files can choose between adapting these and creating pages in the MediaWiki namespace. The latter makes it easier to update to a new version of MediaWiki while keeping the own versions of messages. On the other hand, is easier to transfer a language file to another MediaWiki site than to export and import pages, for the benefit of users who have selected the language concerned as interface language.

Also, an administrator can add extra pages to the MediaWiki namespace, to be accessed, for example, by function int (e.g. MediaWiki:Lang), or by a gadget. These are not shown in Special:Allmessages.

An extension can set e.g. message key aaa to bbb by:

  global $wgMessageCache;
  $wgMessageCache->addMessages( array ('aaa' => 'bbb') );

The key has to start with a lowercase letter, even though message files define messages using an ID written with a capital, and even though the corresponding MediaWiki page has a capital after the colon, in this case MediaWiki:Aaa, even on wikis which allow a lowercase first letter in page names. (The default content of MediaWiki:aaa becomes bbb, but changing it has no effect.)

After getting the array $ma of extension messages:

  $ma = $wgMessageCache->getExtensionMessagesFor( 'en' );

the value can be retrieved with $ma['aaa'], e.g. by:

  $wgOut->addWikiText( $ma['aaa'] );

The result after possible overriding by the contents of the MediaWiki page can be retrieved by wfMsg('aaa').

This applies not only for a message in the strict sense; for example, an extension can allow the user community, through an administrator, to supply parameters in this way; this can even be the name of an extension tag, see e.g. mw:Extension:PropertyTable, where the tag <properties> is the default, but e.g. the tag <pr> can be used after creating the page "MediaWiki:propertyTable tag" with the content "pr" (but note that for portability of wikitext across wikis with the same extension this flexibility has also disadvantages).

All characters of namespace prefixes are case-insensitive, so one can write "mediawiki:".

LocalSettings.php can set messages too, see thread.

MediaWiki before version 1.9.x

The concept of messages has changed in release 1.9.x (January 10, 2007). Before, there existed a page for each message, even if it was the default. On upgrade, all pages with default messages are deleted.


By default, the whole MediaWiki namespace is protected. This is necessary for a number of reasons:

  • Many messages are in plain HTML, hence users could insert malicious scripts
  • Vandalism of some messages would be extremely disruptive, for example changes to the text of the links in the sidebar would immediately be visible to all users

On the other hand, especially for pages MediaWiki:message_ID/language_code the protection is somewhat impractical because administrators do not know all the languages that can be set for the user interface.

If an administrator wishes to allow general editing of a system message, a template call can be placed in the MediaWiki page, with the template containing the message itself.

A few messages can in theory cause the software to stop working if they are changed, for example "linktrail". Therefore and for processing efficiency the effect of page MediaWiki:Linktrail has been disabled: the software ignores its contents, taking the regular expression straight out of the message files.

Technical details

The namespace number of MediaWiki messages is 8, with a corresponding MediaWiki talk namespace 9 to discuss individual messages. Some MediaWiki wikis offer templates like w:template:editprotected ( talk edit history links ) to propose modifications, others have a page like Meta:Requests for help from a sysop or bureaucrat for this purpose.

For links to MediaWiki messages, existence detection applies to existence of the message, not existence of the page:

  • "[[mediawiki:1movedto2]]" → "mediawiki:1movedto2" [2] - link to non-existing page (view mode) for existing message
  • "[[mediawiki:1movedto3]]" → "mediawiki:1movedto3" [3] - link to non-existing page (edit mode) for non-existing message
  • "[[w:de:MediaWiki:Edit]]" → "w:de:MediaWiki:Edit" [4]
  • "[ demo]" → "demo" [5]

Each message in the $wgAllMessagesEn array in Messages.php corresponds to a page in the MediaWiki namespace. For example, there is a line in the php file:

'protect-text' => 'Protect-text',

To this corresponds the page MediaWiki:Protect-text, and "{{int:Protect-text}}" → "Here you may view and change the protection level for the page $1." [6]. When this page is edited the new message is automatically used for say Similarly w:fr:MediaWiki:Protect-text has the content Confirmer la protection, note that the page name itself is not translated.


Transclusion of a system message can be done with the regular tranclusion syntax for the MediaWiki page, even if the page does not exist and the default is used:

"{{mediaWiki:edit}}" → "Edit" [7], the content of MediaWiki:Edit, or if it does not exist, the system message with id "edit" for the site language

Also, parser function int can be used (for an application, see e.g. Template:Ed):

"{{int:edit}}" → "Edit" [8], the content of MediaWiki:Edit/xx where xx is the user language, or if it does not exist, the system message with id "edit" for this language.

If there is neither a page nor a default the result of "int" is different from "MediaWiki:" even if the user uses the default interface language of the site:

"{{mediaWiki:erehwon}}" → "MediaWiki:Erehwon" [9]
"{{int:erehwon}}" → "⧼erehwon⧽" [10]

Messages defined in extensions, even if they are in Special:Allmessages, may or may not be transcluded:

"{{mediaWiki:dynamicpagelist noresults}}" → "MediaWiki:Dynamicpagelist noresults" [11]
"{{mediaWiki:expandtemplates}}" → "Expand templates" [12]

However many messages are not suited for inclusion, because they contain $1 and similar parameters not evaluated by the template parser, or raw CSS and XHTML markup not permitted on normal pages.

While $1, $2, etc. do not work as parameters when using "mediawiki":

  • "{{mediawiki:revertpage|a|b}}" gives "Reverted changes by $2 (talk) to last version by $1" [13]

they do when using "int":

  • "{{int:revertpage|a|b}}" gives "Reverted changes by b (talk) to last version by a" [14]

Error messages

Error messages are in the site language, e.g. "{{#expr:a}}" → "Expression error: Unrecognized word "a"." [15]. This allows branching depending on the type of error, independent of the user language. Note however that wikitext for such branching has to be adapted when transferring it to a wiki with an other site language. This is not needed in the case of branching depending on whether any error occurs, with #iferror.

Interlanguage links

Interlanguage links in MediaWiki messages typically do not work: noinclude tags and the link syntax may not be interpreted.

Instead, one can use in-page interlanguage links on the talk pages, Template:Ilm does this for some major MediaWiki wikis.

Strings exclusive to language file

Some text strings cannot be customised using this feature, and so can only be changed by editing the language file:

  • The namespace titles "User", "Wikipedia", "Image", etc. ($namespaceNames)
  • The names of the special pages ($specialPageAliases)
  • $skinNames (shown in Special:Preferences)
  • $bookstoreList
  • $separatorTransformTable
  • $linkTrail
  • $dateFormats

Branching based on the user language

We have seen that the result of expansion of wikitext can depend on the user language through the use of "int". The exact behaviour with that regard is not completely clear and may change in the future (see in particular bugs 1495 and its duplicate 8188 for Commons, 13010 and 2085; $wgForceUIMsgAsContentMsg).

In addition to the possibility of directly storing the alternative texts in the MediaWiki namespace we can also use "int" only to find the code of the user language, and then use any branching method.

The code of the user language is not directly available, but can be obtained with {{int:lang}} after creating a collection of pages Mediawiki:lang/xx, each containing the corresponding language code xx, see e.g. [16]:

"{{int:lang}}" → "⧼lang⧽" [17] (gives the code of the user language if the MediaWiki page has been created, otherwise <lang>)

and using Template:Uselang:

"{{uselang}}" → "⧼Lang⧽" [18] (gives the code of the user language if the MediaWiki page has been created, otherwise en)

Thus, while internationalization of month names can be done directly:

"{{int:January}}" → "January" [19]

we can now adapt the format to the language, e.g.

17{{#switch:{{int:lang}}|de=.}} {{int:January}} 2010 gives 17 January 2010.

or more generally, apply Template:Date, where the default language is the user language, determined inside the template.

If a separate page is used for every language version, this is commonly done with the naming scheme pagename/xx for the language with code xx (just like in the MediaWiki namespace). The templates in Category:Autotranslated templates use Template:Autotranslate, which is based on this naming scheme, and selects the local version of a template. It checks existence and applies a fall-back scheme (see also commons:Template:Fallback). If the tasks of the language versions have much in common, such as computations, or formatting unrelated to language, then it is practical to let them call a common auxiliary template, with as parameters language specific data, such as texts, see e.g. Template:Unblock granted/layout, commons:Template:Creator/layout, commons:Template:Museum/layout, and commons:Template:TemplateBox/layout.

See also

Links to other help pages

Help contents
Meta · Wikinews · Wikipedia · Wikiquote · Wiktionary · Commons: · mw: · b: · s: · mw:Manual · Google
Versions of this help page (for other languages see further)
Meta · Wikinews · Wikipedia · Wikiquote · Wiktionary
What links here on Meta or from Meta · Wikipedia · MediaWiki
Go · Search · Stop words · Namespace · Page name · Section · Backlinks · Redirect · Category · Image page · Special pages · Printable version
Tracking changes
Recent changes (enhanced) | Related changes · Watching pages · Diff · Page history · Edit summary · User contributions · Minor edit · Patrolled edit
Logging in and preferences
Logging in · Preferences · User style
Starting a new page · Advanced editing · Editing FAQ · Edit toolbar · Export · Import · Shortcuts · Edit conflict · Page size
Links · URLs · Piped links · Interwiki linking · Footnotes
Style and formatting
Wikitext examples · CSS · Reference card · HTML in wikitext · Formula · List · Table · Sorting · Colors · Images and file uploads
Fixing mistakes
Show preview · Testing · Reverting edits
Advanced functioning
Expansion · Template · Advanced templates · Parser function · Parameter default · Variable · System message · Substitution · Array · Calculation · Embed page
Special characters · Renaming (moving) a page · Talk page · Signatures · Sandbox · Legal issues for editors