Extension default namespaces

To prevent conflicts in new namespaces added by extensions, please list your extension's namespace here. If a constant for the custom namespace exists, you can list it here too.

Note that these are only default namespaces. All extensions defining new namespaces should take care to provide the installer with a method of configuring the extension to use a different range of namespaces for it's custom namespaces.

Naturally some namespaces listed on this page will overlap, and violate the recommendations listed here. The recommendations are good practices new extensions should try to adhere to to avoid conflicts, for legacy reasons old extensions that have already created conflicts and bad practice can't simply be changed but are listed here to help avoid even more conflicts.

0-99
Namespaces 0-99 are typically used by core, preferably extensions would avoid defining default namespaces in this range.

MediaWiki Core

 * 0 : (constant: NS_MAIN)
 * 1 Talk: (constant: NS_TALK)
 * 2 User: (constant: NS_USER)
 * 3 User_talk: (constant: NS_USER_TALK)
 * 4 Project: (constant: NS_PROJECT)
 * 5 Project_talk: (constant: NS_PROJECT_TALK)
 * 6 File: (constant: NS_FILE)
 * 7 File_talk: (constant: NS_FILE_TALK)
 * 8</tt> MediaWiki: (constant: NS_MEDIAWIKI)
 * 9</tt> MediaWiki_talk: (constant: NS_MEDIAWIKI_TALK)
 * 10</tt> Template: (constant: NS_TEMPLATE)
 * 11</tt> Template_talk: (constant: NS_TEMPLATE_TALK)
 * 12</tt> Help: (constant: NS_HELP)
 * 13</tt> Help_talk: (constant: NS_HELP_TALK)
 * 14</tt> Category: (constant: NS_CATEGORY)
 * 15</tt> Category_talk: (constant: NS_CATEGORY_TALK)
 * ... If core is to define any new default namespace it will likely continue on from here with 16-17, please take care to avoid this area.

LiquidThreads

 * 90</tt> Thread: (constant: NS_LQT_THREAD)
 * 91</tt> Thread_talk: (constant: NS_LQT_THREAD_TALK)
 * 92</tt> Summary: (constant: NS_LQT_SUMMARY)
 * 93</tt> Summary_talk: (constant: NS_LQT_SUMMARY_TALK)

100-199
The namespaces in 100-199 have been used by some extensions, however they are often used as site namespaces as well. If you're writing a new extension you should try and avoid defining new namespaces inside the 100-199 range.

Semantic MediaWiki & Semantic Forms

 * 100</tt> Relation: (constant: SMW_NS_RELATION; no longer used, as of version 1.0; support dropped with 1.5.0)
 * 101</tt> Relation_talk: (constant: SMW_NS_RELATION_TALK; no longer used, as of version 1.0; support dropped with 1.5.0)
 * 102</tt> Property: (constant: SMW_NS_PROPERTY)
 * 103</tt> Property_talk: (constant: SMW_NS_PROPERTY_TALK)
 * <tt>104</tt> Type: (constant: SMW_NS_TYPE; no longer used, as of version 1.6.0; still supported)
 * <tt>105</tt> Type_talk: (constant: SMW_NS_TYPE_TALK; no longer used, as of version 1.6.0; still supported)
 * <tt>106</tt> Form: (constant: SF_NS_FORM)
 * <tt>107</tt> Form_talk: (constant: SF_NS_FORM_TALK)
 * <tt>108</tt> Concept: (constant: SMW_NS_CONCEPT)
 * <tt>109</tt> Concept_talk: (constant: SMW_NS_CONCEPT_TALK)

DPLforum

 * <tt>110</tt> Forum (constant: NS_FORUM)
 * <tt>111</tt> Forum_talk (constant: NS_FORUM_TALK)

RefHelper

 * <tt>120</tt> Cite (constant: NS_CITE)
 * <tt>121</tt> Cite_talk (constant: NS_CITE_TALK)

Semantic Drilldown

 * <tt>170</tt> Filter: (constant: SD_NS_FILTER)
 * <tt>171</tt> Filter_talk: (constant: SD_NS_FILTER_TALK)

SocialProfile

 * <tt>200</tt> UserWiki: (constant: NS_USER_WIKI)
 * <tt>201</tt> UserWiki_talk: (constant: NS_USER_WIKI_TALK since r93317)
 * <tt>202</tt> User_profile: (constant: NS_USER_PROFILE)
 * <tt>203</tt> User_profile_talk: (constant: NS_USER_PROFILE_TALK since r93317)

Widgets

 * <tt>274</tt> Widget: (constant: NS_WIDGET)
 * <tt>275</tt> Widget_talk: (constant: NS_WIDGET_TALK)

PollNY

 * <tt>300</tt> Poll (constant: NS_POLL)
 * <tt>301</tt> Poll_talk (constant: NS_POLL_TALK)

Wikia

 * <tt>300</tt> - <tt>399</tt>. Wikia has been seen using namespaces in this range for it's custom extensions and configurations. To avoid conflicts in case Wikia extensions are ported to work outside of Wikia it would be best to avoid defining new extensions that use this range.

Wiki2LaTeX

 * <tt>400</tt> Wiki2LaTeX: (constant: NS_WIKI2LATEX)
 * <tt>401</tt> Wiki2LaTeX_talk: (constant: NS_WIKI2LATEX_TALK)

500-599
Some sites try to make use of the 500-599 range for site namespaces. To avoid conflicting with those sites it would be a good idea to avoid this range while creating new extensions.

BlogPage

 * <tt>500</tt> Blog (constant: NS_BLOG)
 * <tt>501</tt> Blog_talk (constant: NS_BLOG_TALK)

FanBoxes

 * <tt>600</tt> UserBox (constant: NS_FANTAG)
 * <tt>601</tt> UserBox_talk (constant: NS_FANTAG_TALK)

NagiosConfig

 * <tt>600</tt> NagiosTemplate: (constant: NS_NAGIOS_TEMPLATE)
 * <tt>601</tt> NagiosTemplate_talk: (constant: NS_NAGIOS_TEMPLATE_TALK)
 * <tt>602</tt> NagiosHostType: (constant: NS_NAGIOS_HOSTTYPE)
 * <tt>603</tt> NagiosHostType_talk: (constant: NS_NAGIOS_HOSTTYPE_TALK)
 * <tt>604</tt> NagiosCommand: (constant: NS_NAGIOS_COMMAND)
 * <tt>605</tt> NagiosCommand_talk: (constant: NS_NAGIOS_COMMAND_TALK)
 * <tt>606</tt> NagiosResource: (constant: NS_NAGIOS_RESOURCE)
 * <tt>607</tt> NagiosResource_talk: (constant: NS_NAGIOS_RESOURCE_TALK)
 * <tt>608</tt> NagiosServiceCommand: (constant: NS_NAGIOS_SERVICECOMMAND)
 * <tt>609</tt> NagiosServiceCommand_talk: (constant: NS_NAGIOS_SERVICECOMMAND_TALK)

LinkFilter

 * <tt>700</tt> Link (contant: NS_LINK)
 * <tt>701</tt> Link_talk (contant: NS_LINK_TALK)

TimedMediaHandler
TimedMediaHandler reserves namespaces for timed text tracks:
 * <tt>700</tt> TimedText (constant: NS_TIMEDTEXT)
 * <tt>701</tt> TimedText_talk (constant: NS_TIMEDTEXT_TALK)

QPoll
QPoll reserves namespaces for interpretation scripts:
 * <tt>800</tt> Interpretation (constant: NS_QP_INTERPRETATION)
 * <tt>801</tt> Interpretation_talk (constant: NS_QP_INTERPRETATION_TALK)

1000+
The 1000+ range starts to get fairly high, and it's a possible spot site's may attempt to use to

Hidden pages
HiddenPages requires custom namespaces to be added manually. Thus a specific sequence cannot be registered. Nonetheless, the extension recommends using namespace numbers 1000 and up.
 * <tt>1000</tt> and up

Translate
Translate extension uses these namespaces by default, but it can be overridden.
 * <tt>1198</tt> Translations (constant NS_TRANSLATIONS )
 * <tt>1199</tt> Translations_talk (constant NS_TRANSLATIONS_TALK )

And FYI translatewiki.net uses namespaces from 1200 onward to hold product translations.

PackageForce

 * <tt>1300</tt> PackageForce: (constant: NS_PACKAGEFORCE)
 * <tt>1301</tt> PackageForce_talk: (constant: NS_PACKAGEFORCE_TALK)

Gadgets

 * <tt>2300</tt> Gadget: (constant: NS_GADGET)
 * <tt>2301</tt> Gadget_talk: (constant: NS_GADGET_TALK)
 * <tt>2302</tt> Gadget_definition: (constant: NS_GADGET_DEFINITION)
 * <tt>2303</tt> Gadget_definition_talk: (constant: NS_GADGET_DEFINITION_TALK)

3000+
So far no known extensions have defined default namespaces in the 3000+ range. For now it would be best to avoid using this range to give sites room to define their custom namespaces without fear of conflict.

Wikia
Wikia alters the namespaces for some extensions used on it's own wikis. Please also take these into account while coming up with new namespace numbers to use in new extensions.

Semantic MediaWiki, Semantic Forms, and Semantic Drilldown
As used on several Wikia sites
 * <tt>302</tt> Property:
 * <tt>304</tt> Type:
 * <tt>306</tt> Form:
 * <tt>308</tt> Concept:
 * <tt>370</tt> Filter:
 * and associated Talk pages #+1