WordPress Codex 日本語版 - 最近の更新 [ja]

Administration Screens

2012-05-15T16:55:26Z

日本語ページへ転送

新規ページ

#REDIRECT [[管理画面]]

Appearance Header Screen

2012-05-15T15:48:22Z

日本語ページに転送

新規ページ

#REDIRECT [[管理画面/外観/ヘッダー]]

Custom Headers

2012-05-15T15:47:06Z

en:Custom Headers 2012-05-15T15:26:15 Bono 版を翻訳用にコピー

新規ページ

{{NeedTrans}}

'''Custom Header''' is a [[Theme Features|theme feature]] introduced with [[Version 2.1]]. Custom header is an image that is chosen as the representative image in the theme top header section.

See also [[Appearance Header Screen]].

== Adding Theme Support ==

Since [[Version 3.4]], themes need to use [[Function_Reference/add_theme_support|add_theme_support()]] in the [[Theme_Development#Functions_File|functions.php]] file to supports custom headers, like so:

<pre>add_theme_support( 'custom-header' );</pre>

Note that you can add default arguments using:

<pre>
$defaults = array(
'default-image' => '',
'random-default' => false,
'width' => 0,
'height' => 0,
'flex-height' => false,
'flex-width' => false,
'default-text-color' => '',
'header-text' => true,
'uploads' => true,
'wp-head-callback' => '',
'admin-head-callback' => '',
'admin-preview-callback' => '',
);
add_theme_support( 'custom-header', $defaults );
</pre>

== Example ==

=== Set a custom header image ===

Set a default header image 980px width and 60px height:

<pre>
$args = array(
'width' => 980,
'height' => 60,
'default-image' => get_template_directory_uri() . '/images/header.jpg',
);
add_theme_support( 'custom-header', $args );
</pre>

=== Upload other custom header images ===

Set a default header image and allow the site owner to upload other images:

<pre>
$args = array(
'width' => 980,
'height' => 60,
'default-image' => get_template_directory_uri() . '/images/header.jpg',
'uploads' => true,
);
add_theme_support( 'custom-header', $args );
</pre>

=== Use flexible headers ===

Set flexible headers:

<pre>
$args = array(
'flex-width' => true,
'width' => 980,
'flex-width' => true,
'height' => 200,
'default-image' => get_template_directory_uri() . '/images/header.jpg',
);
add_theme_support( 'custom-header', $args );
</pre>

update your header.php file to:

<pre>
<img src="<?php header_image(); ?>" height="<?php echo get_custom_header()->height; ?>" width="<?php echo get_custom_header()->width; ?>" alt="" />
</pre>

== Related ==
{{Theme Support}}

{{原文|Custom Headers|117909}}

[[Category:上級トピック]]
[[Category:wp3.4]]

[[en:Custom Headers]]

Appearance Background Screen

2012-05-15T15:42:12Z

日本語ページに転送

新規ページ

#REDIRECT [[管理画面/外観/背景]]

Media Library Screen

2012-05-15T15:38:31Z

日本語ページに転送

新規ページ

#REDIRECT [[管理画面/メディア/ライブラリ]]

Custom Backgrounds

2012-05-15T15:34:20Z

en:Custom Backgrounds 2012-05-15T15:27:48 Bono 版を翻訳用にコピー

新規ページ

{{NeedTrans}}

'''Custom Backgrounds''' is a [[Theme Features|theme feature]] that provides for customization of the background color and image.

See also [[Appearance Background Screen]].

== Adding Theme Support ==

Since [[Version 3.4]], themes need to use [[Function_Reference/add_theme_support|add_theme_support()]] in the [[Theme_Development#Functions_File|functions.php]] file to supports custom backgrounds, like so:

<pre>add_theme_support( 'custom-background' );</pre>

Note that you can add default arguments using:

<pre>
$defaults = array(
'default-color' => '',
'default-image' => '',
'wp-head-callback' => '_custom_background_cb',
'admin-head-callback' => '',
'admin-preview-callback' => ''
);
add_theme_support( 'custom-background', $defaults );
</pre>

== Example ==

An example using default '#000000' background color with 'background.jpg' background image:

<pre>
$args = array(
'default-color' => '000000',
'default-image' => get_template_directory_uri() . '/images/background.jpg',
);
add_theme_support( 'custom-background', $args );
</pre>

== Related ==
* [[Theme Development]]

{{Theme Support}}

{{原文|Custom Backgrounds|117910}}

[[Category:上級トピック]]
[[Category:デザインとレイアウト]]
[[Category:WordPress の開発]]
[[Category:wp3.4]]

[[en:Custom Backgrounds]]

MediaWiki:Sidebar

2012-05-15T14:26:11Z

3.4追加、3.2削除、談話室削除（P2会議室に切り替え）

レンタルサーバ情報

2012-05-10T22:42:35Z

←前の版		2012年5月10日 (木) 22:42時点における版
19行：		19行：

	= 国内サーバ =		= 国内サーバ =
−
−	~~== レオサーバー ==~~
−
−	* 公式サイト: [http://www.leosv.jp/ レオサーバー]
−	* サーバ環境: [http://www.leosv.jp/products/function.html レオサーバー｜機能一覧]
−	** PHP 5
−	** MySQL 5 無制限（WordPressを複数インストールする際に接頭辞を気にする必要なし）
−	** FTPS（FTP over SSL）対応
−	** SSH、SFTP、Cron、phpMyAdmin、共有SSL 利用可能
−	** トップドメイン、サブドメイン、サブディレクトリのいずれも運用可能
−	* マルチサイト機能
−	** サブディレクトリ形式：可
−	** サブドメイン形式：不可
−	* 参考リンク
−	** [http://www.leosv.jp/manual/svadmin/app-wordpress.html WordPress簡単インストールマニュアル]
−	** [http://www.leosv.jp/manual/svadmin/ap-wordpress.html WordPressインストールマニュアル]（手動インストール）

	== プラスアルファレンタルサーバー ==		== プラスアルファレンタルサーバー ==

Before You Create A Network

2012-05-10T04:28:05Z

[[Before You Create A Network]]を[[ネットワーク作成の前に]]へ移動和訳。

Before You Create A Network

2012-05-09T15:56:26Z

2012-03-04T10:07:12 Ipstenu 版から新規作成

新規ページ

{{NeedTrans}}
This section outlines some requirements to consider before you begin [[Create A Network|creating a multisite network]].

== Do you really need a network? ==
The sites in a multisite network are separate, very like the separate blogs at WordPress.com. They are not ''interconnected'' like things in other kinds of networks (even though plugins can create various kinds of interconnections between the sites). If you plan on creating sites that are strongly interconnected, that share data, or share users, then a multisite network might not be the best solution.

For example, if all you want is for different collections of web pages to look very different, then you can probably achieve what you want in a single site by using a plugin to switch themes, templates, or stylesheets.

For another example, if all you want is for different groups of users to have access to different information, then you can probably achieve what you want in a single site by using a plugin to switch capabilities, menus, and link URLs.

This guide describes how to install manually WordPress Multisite in your current WordPress installation. There are also available [http://codex.wordpress.org/User:Beltranrubo/BitNami_Multisite ready-to-run packages] from BitNami.

== Types of multisite network ==
You can choose between several different types of multisite network depending on how you want your network to handle URLs, and on whether it will allow end users to create new sites on demand.

Different types of network have different server requirements, which are described in a section below. If you do not have full control over your server then certain types of multisite network might not be available to you. For example, you might not have full control over your server because you use a shared hosting environment. In that case you will have to negotiate the requirements with whoever operates the hosting environment.

The sites in a network have different URLs. You can choose one of two ways for the URL to specify the site:

* Each site has a different ''domain''. For example: <tt>example1.com</tt>, <tt>example2.com</tt>, <tt>site1.example.com</tt>, <tt>site2.example.com</tt>.
* Each site has a different ''path''. For example: <tt>example.com/site1</tt>, <tt>example.com/site2</tt>

[[File:sites-edit-site.png||Properties of a site in a network. The site's URL is http://example3.com/]]

You can also choose whether or not to allow end users to create new sites on demand. Domain-based on-demand sites are normally only possible using subdomains like <tt>site1.example.com</tt> and <tt>site2.example.com</tt>. Path-based on-demand sites are also possible.

The multisite installation process uses different terminology. A ''sub-domain install'' creates a domain-based network, even though you might use separate domains, and not subdomains, for your sites. A ''sub-directory install'' creates a path-based network, even though it does not use file system directories. If you want to use a ''sub-domain'' install, you must install WordPress in the root of your webpath (commonly <tt>public_html</tt>).

After the multisite network installation is complete, WordPress uses the terminology ''domain'' and ''path'' for each site's domain and path in the Network Admin user interface. A super admin (that is, a multisite network administrator) can edit sites' domain and path settings, although it is unusual to do this to established sites because it changes their URLs.

Plugins can extend the options available and help with administration. For example, you can use the [http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/ WordPress MU Domain Mapping] plugin to help you map individual sites to independent domain names. For another example, you can use the [http://wordpress.org/extend/plugins/networks-for-wordpress/ Networks for WordPress] plugin to configure multiple networks in the same WordPress installation.

== Admin Requirements ==
To create a multisite network you must be the administrator of a WordPress installation, and you normally need access to the server's file system so that you can edit files and create a directory. For example, you could access the server's file system using [[Glossary#FTP|FTP]], or using the File Manager in [[Glossary#cPanel|cPanel]], or in some other way.

You do not necessarily need any knowledge of WordPress [[Glossary#Developer|development]], [[Glossary#PHP|PHP]], [[Glossary#HTML|HTML]], [[Glossary#CSS|CSS]], server administration or system administration, although knowledge of these things might be useful for troubleshooting or for customizing your multisite network after installation.

== Server Requirements ==
When you are planning a network, it can sometimes be helpful to use a development server for initial testing. However, setting up a development server that exactly matches your production server is not always possible, and transferring an entire network to a production server may not be easy. A test site on your production server is sometimes a more useful way to test your planned network.

Some server requirements depend on the type of multisite network you want to create, as follows.

=== Domain-based ===
Also known as 'Subdomain' installs, a Domain-based network uses URLs like <code>http://subsite.example.com</code>

For a domain-based network you require to map different domain names to the same directory in the server's file system where WordPress is installed. You can do this in various ways, for example:

* by configuring wildcard subdomains
* by configuring virtual hosts, specifying the same document root for each
* by creating addon domains or subdomains in [[Glossary#cPanel|cPanel]] or in a similar web hosting control panel

On-demand domain-based sites require the wildcard subdomains method. You can create additional sites manually in the same network using other methods.

Whichever methods you use require DNS configuration to map the domain name to the server's IP address, and also server configuration to map the domain name to the WordPress installation directory. (WordPress then maps the domain name to the site.)

WordPress ''must'' be installed in the root of your webfolder (i.e. <tt>public_html</tt>) for subdomains to function correctly. They will not function in a subdirectory.

External links:
*[http://en.wikipedia.org/wiki/Wildcard_DNS_record Wildcard DNS record] (Wikipedia)
*[http://httpd.apache.org/docs/2.0/en/vhosts/ Apache Virtual Host] (Apache HTTP Server documentation)
*[http://etwiki.cpanel.net/twiki/bin/view/AllDocumentation/CpanelDocs/CpanelDomains cPanel Domains] (cPanel documentation)

For some examples of how to configure wildcard subdomains on various systems, see: [[Configuring Wildcard Subdomains]]

=== Path-based ===
Also known as 'Subfolder' installs, a path-based network uses URLs like <code>http://example.com/subsite</code>

If you are using pretty permalinks in your site already, then a path-based network will work as well, and you do not need any of the other information in this section.

For a path-based network you normally require [[Glossary#mod_rewrite|mod_rewrite]] to be loaded on the Apache server, support for it in [[Glossary#.htaccess|.htaccess]] files, and Options FollowSymLinks either already enabled or at least not permanently disabled. If you have access to the server configuration, then you could use a Directory section instead of a .htaccess file.

The requirement is the same for on-demand path-based sites.

'''Example:''' Configuring mod_rewrite in an Apache server on Ubuntu Linux.

: To check if mod_rewrite is running, create 'nano /var/www/test.php' and inside that file put '<?php phpinfo(); ?>' then go to your web browser and try loading test.php and search for mod_rewrite in the loaded apache modules.

: If not loaded, then use command from cli 'sudo a2enmod rewrite'; 'sudo nano /etc/apache2/sites-enabled/000-default' changing the Allow None to Allow All under the /var/www sections (2 places) and 'sudo /etc/init.d/apache2 restart' Otherwise you won't get sub sites to show up. The above is under Ubuntu server 10.04 with LAMP, other distros will likely be similar (Centos 6.0 also does not have set under default). Ubuntu 12.04 LAMP needs "Allow from All" rather than the older "Allow All" noted above.

== WordPress Settings Requirements ==
When you install a multisite network you start from an existing WordPress installation. If it is a fresh install with its own domain name, then you do not need to read this section. If it is an established site, or not reachable using just a domain name, then the following requirements apply to allow it to be converted to a multisite network.

[[Giving WordPress Its Own Directory|Giving WordPress its own directory]] will not work in WordPress 3.0 with multisite enabled. If you wish to install WordPress in a folder AND have that folder name it will work. Domain mapping, however, will not work.

If you have www in the settings for your domain url, and plan to use subdomains for multisite, make sure that both the site address and the WordPress address are the same. If you plan on changing them to domain.com or www.domain.com, do so before you begin the rest of the setup for MultiSite, as changing the domain name after the fact is more complicated.

You '''cannot create a network''' in the following cases:
* "WordPress address (URL)" is different from "Site address (URL)".
* "WordPress address (URL)" uses a port number other than ':80', ':443'.

You ''cannot choose '''Sub-domain''' Install'' (for a domain-based network) in the following cases:
* The WordPress URL contains a path, not just a domain. (That is, WordPress is not installed in a document root, or you are not using the URL of that document root.)
* "WordPress address (URL)" is <code>localhost</code>.
* "WordPress address (URL)" is IP address such as <var>127.0.0.1</var>.

(Note that you can create a domain-based network on your local machine for testing purposes by using your hosts file to map some other hostnames to the IP address 127.0.0.1, so that you never have to use the hostname <code>localhost</code>.)


You ''cannot choose '''Sub-directory''' Install'' (for a path-based network) if your existing WordPress installation has been set up for more than a month, due to issues with existing permalinks. (This problem will be fixed in a future version. See [[#Switching_network_types|Switching network types]] for more information.)

(See {{Trac|wp-admin/network.php}} for more detail)

{{原文|Create A Network| 114461}}

{{DEFAULTSORT:}}
[[Category:WPMU]]
[[Category:ネットワーク]]
[[Category:UI Link]]
[[Category:ホスティング]]

利用者:Drinter

2012-05-09T01:35:12Z

が新規にアカウント利用者:Drinter を作成しましたパスワードを電子メールで送信しました

利用者・トーク:Drinter

2012-05-09T01:35:11Z

新規利用者の会話ページに歓迎のメッセージを記入

新規ページ

{{Template:Welcome|realName=|name=Drinter}}

-- [[利用者:Tai|tai]] 2012年5月9日 (水) 10:35 (JST)

テンプレートタグ/get posts

2012-05-08T13:45:36Z

訳文を一部修正。

差分を表示