Jump to: navigation, search
This page is a translated version of the page Help:ChangeContentModel and the translation is 44% complete.

Other languages:
English • ‎español • ‎日本語 • ‎português • ‎português do Brasil • ‎中文
PD 注意: このページを編集すると、編集内容が CC0 のもとで公開されることに同意したと見なされます。詳細はパブリック・ドメインのヘルプ ページを参照してください。
Special:ChangeContentModel while using the MonoBook skin.

特別:ページのコンテンツ・モデルの変更は、あるページのコンテンツ・モデルを変更するために使用されます。コンテンツ・モデルは、とても大雑把に言えば、ウィキ上の所与のページのフォーマットや型です。規定値ではページのコンテンツ・モデルはwikitextです。これはウィキのマークアップで使用されるリッチ・テキスト・フォーマットです。 Wikimedia プロジェクトで使用されるコンテンツモデルにはコードを格納するcssjavascript、Wikidataのエントリ用のwikibase-item、Wikimedia CommonsでWiki Loves MonumentsのようなキャンペーンをアップロードするためのCampaignなどがあります。 コンテンツモデルの一覧はcontent handlersで入手できます。より技術的な情報は Manual:ContentHandlerで入手できます。

All actions are logged to Special:Log/contentmodel, with a convenient "revert" link to undo changes if necessary. Users must have the editcontentmodel permission to be able to change content models. On Wikimedia projects this permission is currently granted to sysops.



2012年のWikidataプロジェクト(とWikiベースの拡張機能)の到来と共に、wikitextドキュメント以外のページ作成が可能なContentHandlerブランチが開発されました。MediaWiki 1.21以降、ContentHandlerはMediaWikiソフトウェアの中核の一部になっています。

Some generic content models include those meant for storing and presenting source code, but they can also be used to create customized editing interfaces. For example, instead of using a horrible mess of templates to structure content on a page, you could store the underlying data in a structured format such as JSON and then write a MediaWiki extension that builds a custom editing interface on top of this structured data. This approach is used by MassMessage to create delivery list pages and by CollaborationKit for creating WikiProjects. Although these extensions have their own workflows for creating pages, Special:ChangeContentModel can also be used.

As an alternative to setting content models on a page-by-page basis, you can specify alternative defaults for a given namespace. For example, the default content model in the Module namespace is ScribuntoContent. Similarly, you can enforce that a given content model is only used in a given namespace; ScribuntoContent can only be used in the Module namespace.


To view a page's current content model, click "ページ情報" in the sidebar toolbox. You can also append ?action=info to a URL to get the same page.


Go to Special:ChangeContentModel, enter the page name you wish to change. This can be a non-existent page if you wish to create a new page that uses a different content model from the default. Next, choose the content model you wish to change to. Click "変更" to make the change.

Note that not all conversions are possible. If you are trying to convert a page that already exists and the MediaWiki software cannot figure out how to re-interpret the current page's content, the content model will not be converted and you will get an error message. When this happens, it is recommended that you archive the old page and create the page anew in the new content model. For instance, you could rename "Project:Foo" to "Project:Foo/old" and then use Special:ChangeContentModel to create a new page at "Project:Foo". If possible, you should include a link to "Project:Foo/old" on the new page.


All content model changes are logged at Special:Log/contentmodel on your wiki. To undo a change, go to the relevant entry in the log and click "差し戻し". You will see a pre-filled form; click "変更" to carry out the revert. If you are viewing the page history and the most recent change was the one that changed the content model, you can use the undo feature to change the content model back. Rollback will also undo any content model changes.

Note that this may not always work, particularly if the page was edited after the content model was changed in such a way to make it incompatible with the old content model. When this happens, you will have to undo the edits that made it incompatible. Alternatively, you could carry out the content model change anew and archive the old content. Ideally, content model changes are few and far between. In most situations, a page will not have to change content model more than once.