Manual:Using custom namespaces/id

Selain ruang nama bawaan, juga mungkin untuk menambahkan ruang nama buatan sendiri ke sebuah instalasi MediaWiki, untuk memperinci pemisahan konten dan membuat organisasi yang lebih logis.

Ruang nama buatan sendiri mudah dikelola menggunakan perintah konfigurasi. Juga mungkin untuk mendefinisikan nama alias untuk ruang nama buatan sendiri (dan juga ruang nama bawaan), menggunakan perintah konfigurasi.

Membuat ruang nama buatan sendiri
Anda mendaftarkan ruang nama tambahan dengan menambahkannya ke variabel global ke berkas  Anda. Semua ruang nama membutuhkan sebuah indeks numerik unik di dalam larik ini. Sebagai contoh sederhana pembuatan ruang nama buatan sendiri, menambahkan baris-baris berikut ke  akan mendefinisikan sebuah ruang nama "Foo" 3000 dan ruang nama terkaitnya "Foo_talk":


 * Pilih nomor yang belum dipakai
 * Sebagai konvensi, ruang nama yang dinomori 100-199 disimpan untuk ruang nama khusus situs, meskipun terdapat beberapa ekstensi yang tidak mengikuti konvensi ini. Penulis ekstensi menggunakan bilangan yang lebih tinggi, hingga 32767. Ketika memilih indeks Anda, Anda sebaiknya menghindari nomor yang sudah ada di ruang nama standar ekstensi, karena mungkin nanti Anda mau memasang ekstensi itu. Nomor dari 3000 hingga 4999 disimpan bagi administrator sistem untuk mendefinisikan ruang nama buatan mereka. (Juga, Anda sebaiknya menghindari nama ruang nama yang sudah ada di Ruang nama standar ekstensi.)


 * Genap lalu ganjil
 * Perhatikan bahwa indeks larik ruang namanya adalah 3000 di contoh di atas.
 * indeks ruang nama yang genap menandakan sebuah ruang nama subjek.
 * indeks ganjil setelah nomor tersebut menandakan ruang nama pembicaraan yang terkait dengannya


 * Buat ruang nama pembicaraan juga
 * Anda biasanya membuat sebuah ruang nama "Pembicaraan" beserta setiap ruang nama buatan sendiri. Dengan contoh ini, jika Anda memindahkan sebuah halaman ke ruang nama "Foo", Anda akan diberi pilihan untuk memindahkan halaman pembicaraannya, jika ada, dan apabila Anda memilih untuk melakukannya, MediaWiki akan meletakkan halaman pembicaraannya di "Foo talk".


 * Jangan pakai spasi
 * Gunakan tanda garis bawah bukannya spasi ketika mendaftarkan nama ruang nama. "Ruang Namaku" tidak valid di sini; gunakan "Ruang_Namaku".

Bagian huruf kapital tidak membolehkan tanda hubung tetapi tanda hubung masih bisa ditambahkan ke judul prefiks. Contoh:
 * Jangan gunakan tanda hubung


 * Beri nama kepada nomor yang Anda pilih
 * Contoh di atas mendefinisikan konstanta untuk ID ruang nama, jadi Anda bisa menggunakannya untuk menyebut ruang nama di konfigurasi, sebagai contoh di, , atau.

Anda bisa mengonfigurasi pengaturan tambahan untuk ruang nama baru Anda.


 * Lakukan sejak awal
 * Manipulation of  must be completed during MediaWiki initialization, i.e. in case an extension etc. should work with the newly created custom namespace, make sure that you define and name them prior to invoking the respective extension. For instance it cannot be manipulated in a post-initialization hook like.


 * Watch out for collisions with URL protocols
 * MediaWiki's linking code knows about a number of URL protocols, defined in the variable. If your namespace name is identical to one of these protocols, you're going to have trouble creating wikilinks to pages in your custom namespace. This most commonly arises when someone tries to create a "News" namespace, because   is a URL protocol for NNTP newsgroups.
 * To avoid this issue, you can deregister the relevant URL protocol by adding the following code to LocalSettings.php (replacing  by the lowercased name of the protocol you wish to remove):

In extensions
Extensions often add their own namespaces, such as the extension's "Topic" namespace. An extension can unconditionally add to  as described above, or if its namespace registration is conditional (for example  only defines its "Schema" namespace on the wiki where it stores schemas), then it can add a handler function for the  hook that decides what to do.

The timing of registering extensions is subtle. Functions that extensions register with are executed too late to register additional namespaces (T47031). So extensions should bind the hook at file scope (in ) and check there whether the wiki should activate the extra namespace or not. Extensions can configure namespace permissions and content handlers unconditionally at file scope since they do not require the namespace to actually be created.

The new  registration system has a   key for an extension to list its namespaces that should always exist. From the extension:

It also supports the  hook.

Content namespaces
When building the site statistics page (see Special:Statistics), MediaWiki uses values stored in the database to calculate certain totals. One particular total is the "number of articles" or "number of content pages" figure.

For a page to be considered an article, or proper content, it must:


 * Be in the main namespace, or a defined content namespace
 * Not be a redirect page
 * Contain at least one internal link

When creating custom namespaces to hold additional content, it is a good idea to indicate this in the configuration. This is done via the configuration directive.

To extend the example above, one might add the following to :


 * or

MediaWiki will now consider pages in the "Foo" namespace to be articles, if they meet the remaining criteria, and will include them when updating the site statistics counters.

Running maintenance scripts

 * When adjusting the value of, it is a good idea to run either the   or   script to update the internal statistics cache (see ).

Why you would want a custom namespace
There are several reasons on why you would want this:


 * A custom namespace can be used to hold content that should not be shown on the search results page, for example pages that are used only for transclusion.
 * Certain namespaces require additional privilege(s) for editing.
 * You want certain namespaces not to be subjected to certain limitations or default settings ( for example)
 * A uniform prefix for specific content(s), which is searchable for that namespace only
 * If you're a MW developer, sometimes you need to have a custom namespace for your extension(s)

Dealing with existing pages
When storing page records, MediaWiki uses a namespace's numerical index, along with the remaining title text. Thus, when a page is created in a namespace that doesn't exist, e.g. "Bar:Some page", it is treated as being in the main namespace.

This can cause problems if adding a custom namespace definition for "Bar" at a later date, as MediaWiki will look for a page indexed via the proper namespace, but won't be able to find it, thus making the content inaccessible.

To correct this problem, there are three main approaches.

Move conflicting pages
If the number of pages affected is small (e.g. "Bar" held five pages created before the namespace was defined in the site configuration), then the following approach might be suitable:


 * 1) Comment out the namespace definition in the configuration file
 * 2) Access each affected page, and move it out of the pseudo-namespace, e.g. move "Bar:Some page" to "Bar2:Some page"
 * 3) Un-comment the namespace definition
 * 4) Move the affected pages back into the new namespace

Use a maintenance script
Within the maintenance directory, there is a maintenance script which performs the above operation more effectively for a large number of pages;  It is simple to use, but as with all MediaWiki maintenance scripts, consult the available usage information first (use  as an option).

Use a database query
To move all pages "Bar:Some page" into namespace 3000, make the following database query:

To handle discussion pages:

After such fiddling, run the script and the  script to update internal links and search results in your wiki. Note that external search engines like Google will take some time to update their index.

Removing custom namespaces
The problem addressed above also occurs when a custom namespace definition is removed; MediaWiki is no longer aware of the numerical index for the namespace, and attempts to search the main namespace for the desired pages, leading to inaccessible content. This is a rare occurrence, since most sites will not need namespaces removed, but it is a problem. (See mailing list discussion).

Example on how to remove and the Topic namespace:


 * Uninstall Flow
 * Temporarily add $wgExtraNamespaces[2600] = 'Topic'; to the config
 * Use deleteBatch.php to delete all pages in the Topic namespace
 * Remove the $wgExtraNamespaces config

Renaming custom namespaces
Suppose that you need to rename custom namespace "Foo" to "New" without performing a mass move of pages. The easiest way to achieve this is to preserve the namespace ID (here " ") as well as the namespace constant (here " "), modify the (visible) namespace title and add the old one as an alias.


 * change


 * to

Avoid namespace conflicts
In order for you to avoid namespace conflicts e.g. your namespace has the same number as a namespace defined by an extension, the extension namespace list shows you which numbers to avoid to prevent conflicts.

Defining, , $wgContentNamespaces or for an ID not associated to any existing namespace in $wgExtraNamespaces doesn't break the wiki; MediaWiki gracefully ignores such configurations.

Styling namespaces
For example, to set the background color of pages in a particular namespace (and its associated talk namespace) you can add the following code to your common.css:

where  is the namespace's index and   is the color you want as its background color.