Search results

The Technical manual  is in the "Manual" namespace of MediaWiki.org (http://www.mediawiki.org/wiki/Manual:Contents) The User manual  is in the "Help" namespace

to provide a report on all the pages in the Feature Category Namespaces Using the namespaces feature of MediaWiki, you can setup areas that segregate content

their own 'template' namespace while regular articles are in the default namespace and thus use a preceding colon According to mw:Manual:$wgEnableScaryTranscluding

article title) SELECT p.page_id 'id', p.page_title 'title', p.page_namespace 'namespace', t.old_id 'latest text id', t.old_text 'content', r.rev_id, r.rev_comment

export Wikifarm Namespaces or go directly to Special:PrefixIndex Main What is sounds like, there is no need to specify this namespace when making links

Using https://github.com/moy/Git-Mediawiki/wiki/User-manual which is part of the contrib in Git itself, provides a "remote" that talks to a Mediawiki instance

library included in MediaWiki core mw:OOjs UI The skinning manual http://www.mediawiki.org/wiki/Manual:Skinning is probably the most comprehensive and best introduction

Family  Farm-Fresh emoticons  Feature  Features  File message boxes  File namespace templates  File system  Files  Files that transclude the Non-free media

have to explicitly enable them as magic links and also setup a Project namespace page like wp:Book sources See the local version of Project:Book sources

my-service Service in the prod namespace to my.database.example.com: apiVersion: v1 kind: Service metadata: name: my-service namespace: prod spec: type: ExternalName

maintenance/update.php after upgrading? See: https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script Query: SELECT page_id,page_len,page_is_redirect

string is in a loan namespace, returns boolean. Note that this function only checks if the namespace is in the list of all loan namespaces, it doesn't do any