• 赤色のリンクは、まだ日本語Codexに存在しないページ・画像です。英語版と併せてご覧ください。(詳細

このWikiはいつでも誰でも編集できます

「FAQ/トラブルシューティング」の版間の差分

提供: WordPress Codex 日本語版
< FAQ
移動先: 案内検索
(質問のみ和訳。)
(内容を「このページは https://ja.wordpress.org/support/article/faq-troubleshooting/ へ移動しました。」で置換)
 
(3人の利用者による、間の11版が非表示)
1行目: 1行目:
[[FAQ|Back to FAQ]]
+
このページは https://ja.wordpress.org/support/article/faq-troubleshooting/ へ移動しました。
 
+
{{NeedTrans|一部}}
+
 
+
__TOC__
+
 
+
<div id="Why_can.27t_I_see_my_posts.3F_All_I_see_is_Sorry.2C_no_posts_match_your_criteria.3F">
+
==「該当する投稿は見つかりませんでした」と表示されるだけで投稿が見えないのはなぜですか?==
+
</div>
+
 
+
ブラウザーのキャッシュと Cookie を削除すれば問題を解決できるかもしれません。また、<tt>search.php</tt> および <tt>index.php</tt> テンプレートファイルにエラーがないか確認してください。
+
 
+
参照:
+
 
+
* [[I Make Changes and Nothing Happens|変更を加えても何も起こりません]] /[[:en:I Make Changes and Nothing Happens|en]]
+
 
+
<div id="How_do_I_find_more_help.3F">
+
==ヘルプが必要な場合はどうすればいいですか?==
+
</div>
+
 
+
There are various resources that will help you find more help with WordPress, in addition to these [[FAQ]]. You can also increase your search capabilities by adding the [http://asymptomatic.net/2005/07/20/1765/codex-searcher/ Codex and Forum Searcher Plugin] and search both the Codex and Forum from your WordPress Administration Panels. Click on one of the search results and the page will open in a new window or tab so you can have the article or discussion open while working on WordPress.
+
 
+
* [[:Category:トラブルシューティング|トラブルシューティング]]
+
* [[Finding WordPress Help]] /[[:en:Finding WordPress Help|en]]
+
* [[サポートフォーラムの利用]]
+
* [[Technical Articles|Resources and Technical Articles about WordPress]] /[[:en:Technical Articles|en]]
+
* [[Troubleshooting#Installation_Problems|Installation Problems]] /[[:en:Troubleshooting#Installation_Problems|en]]
+
 
+
<div id="Where_can_I_find_help_with_the_CSS_problems_I.27m_having.3F">
+
===CSS 関連の問題のヘルプを得るには?===
+
</div>
+
 
+
The following are articles that will help you troubleshoot and solve many of your [[CSS]] problems:
+
 
+
* [[WordPress サイトデザイン リファレンス]]
+
* [[Finding Your CSS Styles]] /[[:en:Finding Your CSS Styles|en]]
+
* [[CSS Fixing Browser Bugs]] /[[:en:CSS Fixing Browser Bugs|en]]
+
* [[CSS Troubleshooting]] /[[:en:CSS Troubleshooting|en]]
+
* [[CSS|WordPress CSS 情報とリソース]]
+
 
+
<div id="Why_does_the_password_emailed_to_me_look_weird.3F">
+
==メールで届いたパスワードがおかしいのはなぜですか?==
+
</div>
+
 
+
If the password emailed to you looks strange, see [http://allnarfedup.com/2004/11/10/solving-garbled-text/ Solving Garbled Text].
+
 
+
<div id="Why_do_I_get_an_error_message_about_Sending_Referrers.3F">
+
==''リファラー送信''関連のエラーメッセージが表示されるのはなぜですか?==
+
</div>
+
 
+
If you got this message when trying to save a post, consider checking [[管理パネル|Administration]] > [[管理パネル#General|Settings]] > [[Settings General SubPanel|General]] and make sure both your '''WordPress address (URI)'''  and the '''Blog address (URI)''' do not use 'www'.  For example, instead of '''<nowiki>http://www.example.com</nowiki>''' use '''<nowiki>http://example.com</nowiki>''' in those fields.  This information orginally reported via http://wordpress.org/support/topic/72235
+
 
+
参照:
+
* [[Enable Sending Referrers|リファラー送信の有効化]]
+
 
+
<div id="Are_there_are_any_problems_with_using_MySQL_4.1.7_for_WordPress.3F">
+
==MySQL 4.1.7 を WordPress に使う際に何か問題はありますか?==
+
</div>
+
 
+
参照: [[FAQ/インストール#Can_I_install_WordPress_on_Windows_2000.3F|Windows 2000 に WordPress をインストールできますか?]]
+
 
+
<div id="How_do_I_empty_a_database_table.3F">
+
==データベーステーブルを空にするには?==
+
</div>
+
 
+
参照:
+
* [[Emptying a Database Table]] /[[:en:Emptying a Database Table|en]]
+
 
+
<div id="How_do_I_fix_the_following_error_SQL.2FDB_Error_errcode_13_Can.27t_create.2Fwrite_to_file.3F">
+
==''SQL/DB Error errcode 13 Can't create/write to file'' というエラーを解決するには?==
+
'''Problem:''' The MySQL variable <tt>tmpdir</tt> is set to a directory that cannot be written to when using PHP to access MySQL.
+
 
+
To verify this, enter MySQL at the command line and type <tt>show variables</tt>;
+
 
+
You'll get a long list and one of them will read: '''tmpdir = /somedir/''' (whatever your setting is.)
+
 
+
'''Solution:''' Alter the '''tmpdir''' variable to point to a writable directory.
+
 
+
'''Steps:'''
+
<ol>
+
<li>Find the '''my.cnf''' file. On *nix systems this is usually in '''/etc/'''.</li>
+
<li>Once found, open this in a simple text editor and find the '''[mysqld]''' section.</li>
+
<li>Under this section, find the '''tmpdir''' line. If this line is commented (has a '''#''' at the start), delete the '''#''' and edit the line so that it reads: '''tmpdir = /writable/dir''' where '''/writable/dir''' is a directory to which you can write. Some use '''/tmp''', or you might also try '''/home//'''.
+
</li>
+
<li>Save the file.</li>
+
<li>Shutdown MySQL by typing <tt>mysqlshutdown -u -p shutdown</tt>.</li>
+
<li>Start MySQL by going to the MySQL directory and typing <tt>./bin/safe_mysqld &</tt>. Usually the MySQL directory is in '''/usr/local''' or sometimes in '''/usr/''' on Linux systems.
+
</li>
+
</ol>
+
If none of this make sense and you have someone to administrate your system for you, show the above to them and they should be able to figure it out.
+
 
+
<div id="How_do_I_solve_the_Headers_already_sent_warning_problem.3F">
+
==''Headers already sent'' エラーを解決するには?==
+
</div>
+
 
+
'''Description:''' You get a warning message on your browser that says:
+
 
+
<tt>Warning: Cannot modify header information - headers already sent by
+
(output started at</tt>
+
 
+
'''Reason and Solution :'''
+
 
+
It is usually because there are spaces, new lines, or other garbage
+
before an opening '''<tt><?php</tt>''' tag or after a closing '''<tt>?></tt>''' tag, typically in
+
'''wp-config.php'''. This could be true about some other file too, so please check the error message, as it will list the specific file name where the error occurred (see "Interpreting the Error Message" below).  Replacing the faulty file with one from your most recent backup or one from a fresh WordPress download is your best bet, but if neither of those are an option, please follow the steps below.
+
 
+
Just because you cannot see anything does not mean that PHP sees the same.
+
 
+
# Download the file mentioned in the error message.
+
# Open that file in a [[用語集#Text editor|plain text editor]] ('''NOT''' MS Word or similar. Notepad or BBEdit are fine).
+
# Check that the ''very'' first characters are '''<tt><?php</tt>'''
+
# Check that the ''very'' last characters are '''<tt>?></tt>'''
+
 
+
To be sure about the end of the file, do this:
+
#Place the cursor between the ? and >
+
#Now press the DELETE key on your computer
+
#*Note to MAC users: The "DELETE" key on a PC deletes characters to the ''right'' of the cursor.  That is the key noted here.
+
#Keep that key pressed
+
#For at least 15 seconds
+
#Now type > and
+
#'''save''' without pressing any other key at all.
+
#If you press another key, you will bring the problem back.
+
 
+
Also check the encoding of the file. If the file is encoded as UTF-8 with BOM, the BOM is seen as a character which starts the output.
+
 
+
'''Interpreting the Error Message:'''
+
 
+
If the error message states: <code>Warning: Cannot modify header information - headers already sent by (output started at /path/blog/wp-config.php:34) in /path/blog/wp-login.php on line 42</code>, then the problem is at line #34 of <code>wp-config.php</code>, not line #42 of <code>wp-login.php</code>.  In this scenario, line #42 of <code>wp-login.php</code> is the victim.  It is being affected by the excess whitespace at line #34 of <code>wp-config.php</code>.
+
 
+
If the error message states: <code>Warning: Cannot modify header information - headers already sent by (output started at /path/wp-admin/admin-header.php:8) in /path/wp-admin/post.php on line 569</code>, then the problem is at line #8 of <code>admin-header.php</code>, not line #569 of <code>post.php</code>.  In this scenario, line #569 of <code>post.php</code> is the victim.  It is being affected by the excess whitespace at line #8 of <code>admin-header.php</code>.
+
 
+
<div id="Why_can.27t_I_see_the_visual_rich_editor_when_using_Apple.27s_Safari_browser.3F">
+
==Safari ブラウザでビジュアルリッチエディターやクイックタグボタンが使えないのはなぜですか?==
+
</div>
+
 
+
旧版の Safari ブラウザは一部の機能に対応していません。最新版にアップグレードしてください。
+
 
+
<div id="E-mailed_passwords_are_not_being_received">
+
==パスワードリセットのメールが届きません。==
+
</div>
+
 
+
'''Description:''' When users try to register with your blog or change their passwords by entering their username and email, WordPress indicates that their password has been emailed to them, but it is never received.
+
 
+
'''Reason and Solution:'''  WordPress uses the standard php mail function, which uses sendmail.  No account information is needed. This is not generally a problem if you are using a hosting service, but if you are using your own box and do not have an SMTP server, the mail will never send.  If you are using a *NIX box, you should have either postfix or sendmail on your machine; you will just need to set them up (Google for how-to's).  If you do not want to go through setting up a complete mail server on your *NIX box you may find [http://packages.debian.org/stable/mail/ssmtp ssmtp] useful -- it provides ''"A secure, effective and simple way of getting mail off a system to your mail hub"''.  On a Windows machine, try a sendmail emulator like [http://glob.com.au/sendmail/ Glob SendMail].
+
 
+
More help can be found on the forums at: http://wordpress.org/support/topic.php?id=24981
+
 
+
As a plugin-based alternative, you could try [http://coffee2code.com/wp-plugins/configure-smtp/ Configure SMTP].  It ''"Configure SMTP mailing in WordPress, including support for sending e-mail via SSL/TLS (such as GMail)."''
+
 
+
'''Windows Host Specific:'''  With the plugin mentioned above you can work around the issue of e-mails not being received. 
+
 
+
Another alternative is to edit the ''class-pop3.php'' file in wp-includes, there is a variable, ''$MAILSERVER'', which allows you to hard code your smtp server.  However, ''wp-php.php'' in the root directory actually loops through depending on the author to determine a value to set the from address on the e-mail and defaults to the admin address particularly in the case of users registering.
+
 
+
This is fine if your admin address is a valid e-mail address.  For example, if your admin e-mail is: ''admin@"yourhost.com"'', your smtp server must also be ''smtp."yourhost.com"''.  If the domains do not match your mail will not send.  (Your SMTP server may not require authentication however, your host in most cases still checks to make sure incoming SMTP traffic is still valid.  This is to prevent spam.)
+
 
+
When using the plugin wpPHPMailer the same applies, and there is an option to hard code the from address.
+
 
+
<div id="How_do_I_get_the_Quicktag_.3C.21--nextpage--.3E_back.3F">
+
==クイックタグ <nowiki><!--nextpage--></nowiki> をエディタに表示させるには?==
+
</div>
+
 
+
'''In Wordpress 2.0.x'''
+
 
+
Open ''wp-includes/js/quicktags.js'' in a text editor and locate this section (starting at line 135):
+
<pre>
+
//
+
edButtons[edButtons.length] =
+
new edButton('ed_next'
+
,'page'
+
,'<!--nextpage-->'
+
,''
+
,'p'
+
,-1
+
);
+
//
+
</pre>
+
Just remove the two // lines after and before the block of code to uncomment it. 
+
 
+
Now Open '''wp-includes/js/tinymce/plugins/wordpress/editor_plugin.js'' in a text editor and locate this section (starting at line 15):
+
<pre>
+
var buttons = '<a href="javascript:tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpressmore\')" target="_self" onclick="tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpressmore\');return false;"><img id="{$editor_id}_wordpress_more" src="{$pluginurl}/images/more.gif" title="'+titleMore+'" width="20" height="20" class="mceButtonNormal" onmouseover="tinyMCE.switchClass(this,\'mceButtonOver\');" onmouseout="tinyMCE.restoreClass(this);" onmousedown="tinyMCE.restoreAndSwitchClass(this,\'mceButtonDown\');" /></a>';
+
// Add this to the buttons var to put the Page button into the toolbar.
+
// '<a href="javascript:tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpresspage\')" target="_self" onclick="javascript:tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpresspage\');return false;"><img id="{$editor_id}_wordpress_page" src="{$pluginurl}/images/page.gif" title="'+titlePage+'" width="20" height="20" class="mceButtonNormal" onmouseover="tinyMCE.switchClass(this,\'mceButtonOver\');" onmouseout="tinyMCE.restoreClass(this);" onmousedown="tinyMCE.restoreAndSwitchClass(this,\'mceButtonDown\');" /></a>';
+
</pre>
+
 
+
On line 17 copy the text between the apostrophes and paste it at the end of line 15 exactly before the trailing '; as follows:
+
 
+
<pre>
+
var buttons = '<a href="javascript:tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpressmore\')" target="_self" onclick="tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpressmore\');return false;"><img id="{$editor_id}_wordpress_more" src="{$pluginurl}/images/more.gif" title="'+titleMore+'" width="20" height="20" class="mceButtonNormal" onmouseover="tinyMCE.switchClass(this,\'mceButtonOver\');" onmouseout="tinyMCE.restoreClass(this);" onmousedown="tinyMCE.restoreAndSwitchClass(this,\'mceButtonDown\');" /></a> <a href="javascript:tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpresspage\')" target="_self" onclick="javascript:tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpresspage\');return false;"><img id="{$editor_id}_wordpress_page" src="{$pluginurl}/images/page.gif" title="'+titlePage+'" width="20" height="20" class="mceButtonNormal" onmouseover="tinyMCE.switchClass(this,\'mceButtonOver\');" onmouseout="tinyMCE.restoreClass(this);" onmousedown="tinyMCE.restoreAndSwitchClass(this,\'mceButtonDown\');" /></a>';
+
</pre>
+
 
+
This will show the the Quicktag <nowiki><!--nextpage--></nowiki> again. You can also enable the hotkey access by doing just one more thing. Open '''wp-includes/js/tinymce/plugins/wphelp/editor_plugin.js'' with a text editor. Note that it's not the same file as the one from the previous step, as although it has the same name it is on a different path. Locate the following lines (should be line 23 and 24):
+
<pre>
+
+ '<input type="button" accesskey="t" onclick="tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpressmore\');" />'
+
+ '<input type="button" accesskey="u" onclick="tinyMCE.execInstanceCommand(\'{$editor_id}\',\'Undo\',false);" />'
+
</pre>
+
Copy line 23, paste it as a new line just below line 23, and edit it as follows:
+
<pre>
+
+ '<input type="button" accesskey="t" onclick="tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpressmore\');" />'
+
+ '<input type="button" accesskey="p" onclick="tinyMCE.execInstanceCommand(\'{$editor_id}\',\'mcewordpresspage\');" />'
+
+ '<input type="button" accesskey="u" onclick="tinyMCE.execInstanceCommand(\'{$editor_id}\',\'Undo\',false);" />'
+
</pre>
+
This will enable the Alt+P shortcut for the <nowiki><!--nextpage--></nowiki> tag.
+
 
+
<div id="I_used_the_Quicktag_.3C.21--nextpage--.3E_in_a_post_so_why_doesn.27t_it_work.3F">
+
==投稿内で <nowiki><!--nextpage--></nowiki> クイックタグを使いましたが動作しません。どうしてですか?==
+
</div>
+
 
+
In some [[テーマの使い方|Themes]], such as the WordPress Classic Theme, you may see the <nowiki><!--nextpage--></nowiki> work properly on your main page, but other [[テーマの使い方|Themes]], such as the WordPress default Theme,  may only show the ''page break'' when viewing the posts individually.  It may be necessary to change your Theme's [[テンプレート|template]] ''page.php'' or ''index.php'' file to make this feature work according to your wishes.  You'll need to add the following:
+
<pre><?php wp_link_pages(); ?> ?</pre>
+
 
+
<div id="MySQL_Error_28">
+
== MySQL Error 28 ==
+
</div>
+
 
+
以下のようなエラーが表示される場合:
+
 
+
Error code 28: No space left on device
+
 
+
This is a MySQL error and has nothing to do with WordPress directly; you should contact your host about it. Some users have reported that running a "repair table" command in [[phpMyAdmin]]/[[:en:phpMyAdmin|en]] fixed the problem.
+
 
+
[http://www.mysql.com/newsletter/2003-10/a0000000249.html Error 28, and how to avoid it]:
+
 
+
<pre>
+
If you get this error, check all filesystems in
+
which MySQL operates. If you followed recommendations
+
to split datadir, tmpdir and log files into dedicated
+
filesystems, more than one filesystem is involved. In
+
addition, be aware that MySQL often creates temporary
+
tables for some queries. Most of these are placed in
+
tmpdir; however, some may be found in the database
+
directory (e.g. ALTER TABLE). Also, ensure that
+
sufficient free disk space is available for MySQL.
+
</pre>
+
 
+
It could be because:
+
* you are out of space on /tmp (wherever tmpdir is), or,
+
* you have too many files in /tmp (even if there is lots of free space)
+
 
+
Relevant discussion threads:
+
* http://wordpress.org/support/3/1738
+
* http://wordpress.org/support/3/2923
+
* http://wordpress.org/support/3/2760
+
 
+
<div id="Why_are_the_Quote_Marks_escaped_or_not_escaped.3F">
+
==引用符がエスケープされたりされなかったりしているのはなぜですか?==
+
</div>
+
 
+
If you write plugins, or use a plugin like [http://www.nosq.com/2004/10/runphp-wordpress-plugin/ RunPHP], or make advanced custom templates, you may eventually find yourself dealing with data in the database.  WordPress <em>usually</em> manages this data for you in such a way that it is immediately usable.  There are circumstances though (especially if you are dealing directly with the database without using WordPress) where you will experience weirdness.
+
 
+
For example, quote marks cannot be stored directly in the MySQL database. MySQL uses quote marks in its SQL language. When a quote mark is used, for example, in a post, When the post is saved to the database, every quote mark gets escaped. That means a backslash character is prepended, which signifies that the next character should be taken as part of the input, and not as part of the SQL command. 
+
 
+
For example, if you are adding the following in your post:
+
 
+
<pre>...an article about "Happiness" is at
+
<a href="http://example.com/happy" title="Happiness">Happiness</a>
+
if you would like to read it...</pre>
+
 
+
Is actually imported into the database looking like this:
+
 
+
<pre>...an article about \"Happiness\" is at
+
<a href=\"http://example.com/happy\" title=\"Happiness\">Happiness</a>
+
if you would like to read it...</pre>
+
 
+
When pulling data out of the database, the backslashes may not always be automatically removed. If this becomes an issue, you can use the [http://jp.php.net/stripslashes stripslashes()] PHP function on the text.
+
 
+
<div id="Why_do_I_get_a_blank_page_when_I_submit_a_comment.3F">
+
==コメントを投稿したときにページが真っ白になるのはなぜですか?==
+
</div>
+
'''Description:''' When anyone tries to comment on a post, the window goes blank and the comment doesn't appear to have been recognised by WordPress.
+
 
+
'''Reason and Solution:'''
+
The Theme that you are using is missing a critical part of the comment form so WordPress doesn't know which post the comment refers to.  You need to check the comment.php in your Theme and ensure that the following code appears within the form.
+
<pre>
+
<input type="hidden" name="comment_post_ID" value="<?php echo $id; ?>" />
+
</pre>
+
 
+
Relevant discussion threads:
+
 
+
* http://wordpress.org/support/topic/38683
+
 
+
<div id="How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F">
+
== 管理パネルにアクセスできないときに全プラグインを停止するには? ==
+
</div>
+
全てのプラグインを停止(無効化)しなければならないが、それを行なう管理パネルにアクセスできない場合があります。そんなときは、次のどちらかの方法で全プラグインを停止できます。
+
 
+
* '''[[phpMyAdmin]]/[[:en:phpMyAdmin|en]] を使う方法'''
+
*# [[データベース概要#Table: wp_options|wp_options テーブル]]で、''option_name'' フィールド(カラム)の値が ''active_plugins'' の行を探す
+
*# その行の ''option_value'' フィールドを '''a:0:{}''' に変更する
+
 
+
または、
+
 
+
* '''中身が空の plugins ディレクトリを作る方法'''
+
*# [[FTP クライアント]]またはホスト(レンタルサーバ)のコントロールパネルから、
+
*## wp-contents ディレクトリ(フォルダ)へ移動する
+
*## "plugins" ディレクトリを "plugins.hold" にリネーム(名前を変更)する
+
*## 新たに "plugins" というディレクトリを作成する(中身は空)
+
*# WordPress の管理パネルにログイン
+
*# [[FTP クライアント]]またはホスト(レンタルサーバ)のコントロールパネルから、
+
*## 上記 1-3 で作成した空の "plugins" ディレクトリを削除する
+
*## "plugins.hold" ディレクトリを "plugins" に戻す
+
 
+
<div id="How_to_clear_the_.22Briefly_unavailable_for_scheduled_maintenance.22_message_after_doing_automatic_upgrade.3F">
+
 
+
==自動アップグレードの後に出てくる "Briefly unavailable for scheduled maintenance" というメッセージを消すには?==
+
</div>
+
As part of the automatic upgrade WordPress places a file named <tt>.maintenance</tt> in the blog '''base''' folder (folder that contains the wp-admin folder).  If that file exists, then vistors will see the message '''Briefly unavailable for scheduled maintenance. Check back in a minute.''' 
+
 
+
このメッセージが訪問者に表示されないようにするには、<tt>.maintenance</tt> ファイルを削除するだけです。もし自動アップグレードに失敗した際は、再度実行できるはずです。
+
 
+
自動アップグレード機能は[[Version 2.7|バージョン2.7]]で追加されました。
+
 
+
<div id="How_to_fix_404_error_when_using_Pretty_Permalinks.3F">
+
==スラッグを含むパーマリンクを使った場合の404エラーを解決するには?==
+
</div>
+
 
+
If an error 404 occurs when using the [[ブログ入門#Pretty_Permalinks|Pretty Permalink]] choices such as '''Day and Name''' in [[管理パネル]] > [[管理パネル#Settings|設定]] > [[Settings Permalinks SubPanel|パーマリンク設定]] it could be a result of the '''mod_rewrite''' module not being activated/installed.  The solution is to activate '''mod_rewrite''' for the Apache web-server.  Check the apache\conf\httpd.conf file for the line ''`# LoadModule rewrite_module modules/mod_rewrite.so''
+
and delete the # in front of the line.  Then stop Apache and start it again.  '''Note:''' you may have to ask your host to activate mod_rewrite.
+
 
+
参照:
+
* [[パーマリンクの使い方]]
+
<!--
+
Relevant discussion thread:
+
* http://wordpress.org/support/topic/234726 -->
+
 
+
<div id="Why_isn.27t_the_admin_user_listed_as_an_author_when_editing_posts.3F">
+
==投稿を編集する際に管理者が投稿者として表示されないのはなぜですか?==
+
</div>
+
Not sure why this problem happens, but here's a couple of things to try one of these two solutions.
+
 
+
This usually fixes the problem:
+
#Create new admin user (e.g. newadmin) with Administrator Role
+
#Login as 'newadmin'
+
#Degrade the old 'admin' user to Role of Subscriber and Save
+
#Promote the old 'admin' back to Administrator Role and Save
+
#Login as the old 'admin'
+
 
+
If that doesn't work, try:
+
#Create a new admin user (e.g. newadmin) with Administrator Role
+
#Login as 'newadmin'
+
#Delete the old 'admin' user and assign any posts to 'newadmin'
+
#Create 'admin' user with Administrator Role
+
#Login as 'admin'
+
#Delete 'newadmin' user and assign posts to 'admin'
+
 
+
<div id="An_update_was_just_released.2C_so_why_does_my_blog_not_recognize_the_update_is_available.3F">
+
==アップグレードがリリースされた直後に管理画面で表示されないのはなぜですか?==
+
</div>
+
When an update is released, notification of that release is displayed at the top administration panels saying '''WordPress x.x.x is available! Please update now.'''  Not every blog will see that message at the same time.  Your blog is programmed to check for updates every 12 hours, but the timing of that check is purely random.  So if your blog just checked for updates minutes before an update was released, you won't see the update message until your blog checks for updates 12 hours later.
+
 
+
If you want your blog to check right now for updates, you can delete the '''update_core''' option name record in your ''wp_options'' table.  Note that plugins and themes each have their own check and update cycle, controlled by the records '''update_plugins''' and '''update_themes''', in ''wp_options''.
+
 
+
Relevant discussion thread:
+
* http://wordpress.org/support/topic/242485
+
 
+
<div id="#Why_did_I_lose_custom_changes_to_the_WordPress_Default_Theme_during_the_last_automatic_upgrade.3F">
+
==自動アップグレードの際にどうして WordPress デフォルトテーマへの変更が消えてしまうのですか?==
+
</div>
+
A core upgrade copies all the new files from the distribution over the old ones, so if you changed existing files in the WordPress Default Theme (e.g. ''wp-content/themes/default/style.css''), those changes got overwritten with the new version of that file. 
+
 
+
Please note, a core upgrade goes through a list of "old files", as defined in ''wp-admin/includes/update-core.php'', and deletes those files. Any files not on the list, and not in the distribution, are preserved. 
+
 
+
'''Remember, that before upgrades, whether automatic or manual, both the WordPress Files and database should be backed-up as explained in [[WordPress のバックアップ|WordPress Backups]].'''
+
 
+
<div id="#How_do_you_repair_a_MySQL_database_table.3F">
+
==MySQL データベーステーブルを修復するには?==
+
</div>
+
Every once in a while, it may be necessary to repair one or more MySQL database tables.  According to the [http://dev.mysql.com/doc/refman/5.1/en/repair.html How to Repair Tables article at dev.mysql.com] there are a number of reasons to repair a table including errors such as "tbl_name.frm is locked against change",  "Can't find file tbl_name.MYI (Errcode: nnn)", "Unexpected end of file", "Record file is crashed", or "Got error nnn from table handler".
+
 
+
Here are the steps to repair a table in a MySQL database using [[phpMyAdmin]]: 
+
 
+
# Login to hosting account.
+
# Login to [[phpMyAdmin]].
+
# Choose the affected database. If you only have one database, it should choose it by default so you don't need to do anything.
+
# In the main panel, you should see a list of your database tables. Check the boxes by the tables that need repair.
+
# At the bottom of the window just below the list of tables, there is a drop down menu. Choose "Repair Table"
+
 
+
'''Remember, that it is advisable to have a current backup of your database at all times.
+
 
+
参照:
+
*[[WordPress のバックアップ]]
+
 
+
 
+
[[FAQ|Back to FAQ]]
+
 
+
{{原文|FAQ Troubleshooting|84221}}<!-- 2010-03-16T02:44:37 Themedaily 版 -->
+
 
+
{{DEFAULTSORT:}}
+
[[Category:トラブルシューティング]]
+
[[Category:WordPress ヘルプ]]
+
 
+
[[en:FAQ Troubleshooting]]
+
[[zh-cn:错误问题跟踪常见问题解答]]
+

2020年3月17日 (火) 22:53時点における最新版

このページは https://ja.wordpress.org/support/article/faq-troubleshooting/ へ移動しました。