Search translations

The page has a <code><nowiki>__INDEX__</nowiki></code> on it (and is in a namespace where that flag is allowed), and hence is indexed by robots where it normally wouldn't be.

The page is not indexed by robots because it has the magic word <code><nowiki>__NOINDEX__</nowiki></code> on it and is in a namespace where that flag is allowed.

This is a special page, and it cannot be edited

The page has an ignored <code><nowiki>{{DISPLAYTITLE}}</nowiki></code> because it is not equivalent to the page's actual title.

Adds a parser function <code><nowiki>{{#incat:...}}</nowiki></code> to determine if the current page is in a specified category

The page has a malformed <code><nowiki>{{#coordinates:}}</nowiki></code> tag.

It is recommended that you view and edit file annotations on [[:$1|the file page]], where they are available in a visual format.

The symbol "$1" was used in a place where it is not useful.

Segment using custom parameters. The tag <code>sup</code> is removed and so is <code>div</code> when it has the class <code>toc</code>. The tags <code>h1</code> and <code>h2</code> break segments.

The following is a list of all disambiguation pages on {{SITENAME}}.<br />
A page is treated as a disambiguation page if it contains the tag <code><nowiki>__DISAMBIG__</nowiki></code> (or an equivalent alias).

The page includes a <code><nowiki><DynamicPageList></nowiki></code> tag

The page includes a <code><nowiki><graph></nowiki></code> tag.

The category contains <code><nowiki>__HIDDENCAT__</nowiki></code> in its page content, which prevents it from showing up in the category links box on pages by default.

Where is this?

<code>$1</code> is deprecated and will be removed in $2

The page contains <code><nowiki>{{=}}</nowiki></code> but on this wiki that does not expand to <code>=</code>. This usage is deprecated; a future MediaWiki version will implement <code><nowiki>{{=}}</nowiki></code> as a parser function.

This namespace is a system namespace and cannot be deleted.

This special page takes wikitext and expands all templates in it recursively.
It also expands supported parser functions like
<code><nowiki>{{</nowiki>#language:…}}</code> and variables like
<code><nowiki>{{</nowiki>CURRENTDAY}}</code>.
In fact, it expands pretty much everything in double-braces.

Property "$1" has a <code>must_exists</code> constraint and value ''$2'' is violating that requirement.

The specified namespace "<nowiki>$1</nowiki>" is invalid.
Specify a different project namespace.

Also add prefixes to your links: <code><nowiki>[[Page title]]</nowiki></code> to <code><nowiki>[[Wx/xx/Page title]]</nowiki></code> and <code><nowiki>{{Page title}}</nowiki></code> to <code><nowiki>{{Wx/xx/Page title}}</nowiki></code>.

A <code><nowiki>[[ ... ]]</nowiki></code> input will signal to the input processor to use the Semantic MediaWiki search back-end. It should be noted that combining <code><nowiki>[[ ... ]]</nowiki></code> with an unstructured text search such as <code><nowiki>[[ ... ]] OR Lorem ipsum</nowiki></code> is not supported.

The requested page must not be exported because it is on category blacklist.

It is suspected that JavaScript is disabled or not available and we recommend to use a browser where this is supported. Other options are discussed on the [https://www.semantic-mediawiki.org/wiki/Help:$smwgBrowseByApi <code>$smwgBrowseByApi</code>] configuration parameter page.

* <code>in:</code> to find anything that contains "..." and is especially useful when the search context or properties involved are unknown (e.g. <code>in:(lorem && ipsum)</code> is equivalent to <code><nowiki>[[~~*lorem*]] && [[~~*ipsum*]]</nowiki></code>).