Manual:Using custom namespaces/ko

기존의 이름공간 이외에도 미디어위키에 사용자 정의 이름공간을 추가할 수 있으며, 이를 통해 컨텐츠를 나누는 것, 보다 논리적으로 위키를 구성하는 것이 가능합니다.

사용자 정의 이름공간은  설정 지시어(configuration directive)를 사용하여 쉽게 관리할 수 있습니다. 설정 지시어를 사용하여 기본 이름공간 또는 사용자 정의 이름공간에 대해 별칭(alias name)을 정의할 수 있습니다. Some extensions make it easy for you to create custom namespaces. Examples include and.

사용자 정의 이름공간 만들기
파일의 전역 변수에 추가하여 추가 네임 스페이스를 등록합니다. 모든 이름공간은 이 배열에서 사용될 유일한 숫자 인덱스가 필요합니다. 사용자 정의 이름공간을 간단하게 정의하는 예로써, 다음 코드를 추가하면 "Foo" 이름공간을 3000으로 정의하고 연관된(associated) "Foo talk" 이름공간도 정의합니다.


 * 사용되지 않은 수를 고르세요
 * 관례적으로, 100-199 숫자가 할당된 이름공간은 특수 목적(site-specific) 이름공간으로 예약되어있습니다. 어떤 확장 도구는 이 관례를 따르지 않기도 합니다. 확장 도구 개발자는 32767까지의 큰 수를 사용합니다. 인덱스를 선택할 때는 확장 도구의 기본 이름공간에 이미 정의된 수는 피해야 하는데, 왜냐하면 당신이 해당 확장 도구를 나중에 설치할 수 있기 때문입니다. 3000에서 4999 사이의 숫자는 시스템 관리자가 사용자 정의 네임 스페이스를 정의하도록 예약되어 있습니다. (Also, you’ll want to avoid any namespace name that’s already in Extension default namespaces.)


 * 짝수 다음 홀수
 * 위 예제에서 이름공간 배열의 인덱스가 3000인 것에 주목하십시오.
 * 짝수 이름공간 인덱스는 주제 이름공간(subject namespace)를 의미합니다.
 * 곧바로 따라오는 홀수 인덱스는 이에 연관된 토론 이름공간(discussion ("talk") namespace)을 의미합니다.


 * 토론 이름공간도 같이 만드세요
 * You typically create a discussion "Talk" namespace along with each custom namespace. With this example, if you move a page into the "Foo" namespace, will be prompted to move its associated talk page, if any, and if you choose to do so, MediaWiki will place the talk page in "Foo talk".


 * 공백 문자를 쓰지 마세요
 * 이름공간 이름을 등록할 때는 공백 대신 밑줄을 사용하세요. "My Namespace"는 올바르지 않습니다. "My_Namespace"를 대신 사용하세요.

The uppercase part does not permit hyphens but they can still be safely added to the prefix title. 예시:
 * 하이픈(-)을 사용하지 마세요


 * 선택한 수에 이름을 지으세요
 * The example defines constants for the namespace IDs, so that you can refer to these namespaces later on in the configuration, for example in, , or.

새 이름공간에 대해 추가적인 설정을 계속할 수 있습니다.


 * 일찍 하세요
 * 의 조작은 미디어 위키 초기화 중에 완료되어야합니다. 예를 들어 와 같은 초기화 후 후크에서 조작 할 수 없습니다.


 * 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 the "LocalSettings.php" file (replacing  by the lowercased name of the protocol you wish to remove):

확장기능에서
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. 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:


 * 기본 이름공간이거나, 정의된 본문 이름공간이어야 함
 * 넘겨주기 문서가 아님
 * 하나 이상의 내부 링크 포함

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 the "LocalSettings.php" file:


 * 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 configuration parameter, it is a good idea to run either the "path/to/maintenance/updateArticleCount.php or "path/to/maintenance/initSiteStats.php" script to update the internal statistics cache (see ).

Why you would want a custom namespace
There are several reasons you might 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
 * 1) Access each affected page, and move it out of the pseudo-namespace, e.g. move "Bar:Some page" to "Bar2:Some page"
 * 1) Un-comment the namespace definition
 * 1) 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).

데이터베이스 쿼리 사용
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.

변경

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.

같이 보기
Currently in use by the OmegaWiki project.
 * for management of namespaces
 * for management of namespaces
 * for management of namespaces
 * Namespace manager as originally proposed for MW1.6-wikidata and its successors.
 * - to use a different skin in a namespace
 * - a modified version of the which changes it to provide a namespace manager as a special page.
 * - to control access to namespaces
 * Extension namespace registration