WordPress:Answers-Troubleshooting

These FAQs have been deprecated. You will find the new updated Frequently Asked Questions on the new pages for the WordPress:FAQ.

這些常見問題解答已經(jīng)取消了。你在常見問題解答的新的頁面上會看到新的已更新的常見問題解答。

Back to FAQ

返回到常見問題解答

目錄

• 1 CSS Problems
• 2 CSS 問題
• 3 No posts matched your criteria
• 4 沒有文章匹配你的標(biāo)準(zhǔn)
• 5 base64 encoding
• 6 base64 編碼
• 7 Errorcode 13
• 8 Errorcode 13
• 9 Error 28
• 10 錯(cuò)誤28
• 11 Headers already sent
• 12 已經(jīng)發(fā)送了標(biāo)頭
• 13 No Quicktag buttons in Safari
• 14 Safari中沒有Quicktag按鈕
• 15 Emailed passwords not received
• 16 沒有收到帶有密碼的電子郵件

CSS 問題

The following are articles that will help you troubleshoot and solve many of your CSS problems:

下面的這些文章會幫助你發(fā)現(xiàn)并且解決許多CSS問題：

• WordPress:Blog Design and Layout
• WordPress:Finding Your CSS Styles
• WordPress:CSS Fixing Browser Bugs
• WordPress:CSS Troubleshooting
• WordPress CSS Information and Resources

• 博客設(shè)計(jì)和布局
• 找到你的CSS樣式
• CSS解決瀏覽器程序錯(cuò)誤
• CSS發(fā)現(xiàn)并解決問題
• WordPress CSS信息和資源

沒有文章匹配你的標(biāo)準(zhǔn)

Clear your browser cache and cookies. This may sort this issue. Read WordPress:I Make Changes and Nothing Happens for more information. Also, check your search.php and index.php template files for errors.

清除你的瀏覽器儲存和cookies。這樣可能能解決問題。更多的信息，請閱讀我更改了，但是什么變化也沒有出現(xiàn)。同時(shí)檢查你的search.php 和 index.php模板文件上的錯(cuò)誤。

base64 編碼

If the password emailed to you looks strange, the following article might clear this up: Solving Garbled Text.

如果用電子郵件向你發(fā)送的密碼看起來很奇怪，下面的文章可能會幫你解決：解決斷章取義的文本問題。

Errorcode 13

The Problem: The MySQL variable tmpdir is set to a directory that cannot be written to when using PHP to access MySQL.

問題：MySQL變數(shù)設(shè)置到目錄，使用PHP訪問MySQL的時(shí)候，不能夠編寫這個(gè)目錄。

To verify this, enter MySQL at the command line and type show variables;

要檢驗(yàn)這個(gè)，在命令行中輸入MySQL并且輸入顯示變數(shù);

You'll get a long list and one of them will read: tmpdir = /somedir/ (whatever your setting is.)

你會得到很長的列表，其中一項(xiàng)是：tmpdir = /somedir/（不管你的設(shè)置是什么。） The Solution: Alter the tmpdir variable to point to a writable directory.

解決方法：將tmpdir變數(shù)更改，指向可寫的目錄。

The Steps: 步驟：

1. Find the my.cnf file. On *nix systems this is usually in /etc/.
2. Once found, open this in a simple text editor and find the [mysqld] section.
3. 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//.
4. Save the file.
5. Shutdown MySQL by typing mysqlshutdown -u -p shutdown.
6. Start MySQL by going to the MySQL directory and typing ./bin/safe_mysqld &. Usually the MySQL directory is in /usr/local or sometimes in /usr/ on Linux systems.

1. 找到 my.cnf文件。在 *nix 系統(tǒng)，這通常在/etc/。
2. 找打文件后，在簡單的文本編輯器中打開這個(gè)文件并且找到[mysqld]部分。
3. 在這個(gè)部分的下面，找到tmpdir 行。如果這一行已經(jīng)被評論 (行開頭有個(gè) #), 刪除 # 并且編輯這一行： tmpdir = /writable/dir 其中 /writable/dir是個(gè)你可以編寫的目錄。一些人使用 /tmp, 你也可以嘗試使用 /home//。
4. 保存文件。
5. 通過輸入mysqlshutdown -u -p shutdown，關(guān)閉MySQL。
6. 通過進(jìn)入MySQL目錄并且輸入./bin/safe_mysqld &，啟動MySQL。 通常MySQL 目錄位于 /usr/local 或者有時(shí)候位于Linux系統(tǒng)上的/usr/ 。

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.

如果這些操作都不起作用，而且你是讓其他人管理你的系統(tǒng)，你可以向他們顯示上述的操作，他們能夠解決問題。

錯(cuò)誤28

This is a MySQL error and has nothing to do with WordPress directly. You should probably contact your host about it. Some users have reported that running a repair table command in phpMyAdmin fixed the problem.

這是個(gè)MySQL錯(cuò)誤與WordPress沒有直接的聯(lián)系。你可能要聯(lián)系你的主機(jī)，說明這個(gè)錯(cuò)誤。一些用戶指出在phpMyAdmin中運(yùn)行修復(fù)表格命令行能夠解決這個(gè)問題。

You can also check this newsletter on Error 28, and how to avoid it at MySQL.com

你也可以在MySQL.com上查看錯(cuò)誤28的即時(shí)消息，以及怎樣避免這個(gè)錯(cuò)誤。

已經(jīng)發(fā)送了標(biāo)頭

Description: You get a warning message on your browser that says:

描述:你在瀏覽器上得到一條警告信息，顯示：

Warning: Cannot modify header information - headers already sent by (output started at 警告: 不能夠更改標(biāo)頭信息- 標(biāo)頭已經(jīng)發(fā)送 (output started at

Reason and Solution :

原因和解決方法 :

It is usually because there are spaces, new lines, or other garbage before an opening <?php tag or after a closing ?> 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.

通常因?yàn)樵陂_放的<?php標(biāo)簽或者關(guān)閉的?> tag標(biāo)簽后面，特別是在wp-config.php中，有空格，新行，和其它無用標(biāo)記。其它文件也會出現(xiàn)這樣的情況，因此請查看錯(cuò)誤信息，上面會列出出現(xiàn)錯(cuò)誤的文件名稱（請看看下面的"解釋錯(cuò)誤信息"）。使用你最近更新的備份中的文件取代有問題的文件，或者用你最新下載的WordPress文件取消有文件的問題，都是最好的方法。但是如果這兩種方法都行不通，請遵循下面的步驟。

Just because you cannot see anything does not mean that PHP sees the same.

你看不到任何內(nèi)容并不能夠代表PHP也不能夠看到任何內(nèi)容。

1. Download the file mentioned in the error message.

1. 下載錯(cuò)誤信息中提到的文件。

1. Open that file in a plain text editor (NOT MS Word or similar. Notepad or BBEdit are fine).

1. 在一個(gè)純文本編輯器中打開文件（不是MS Word或者類似的。Notepad 或者 BBEdit也行）。

1. Check that the very first characters are <?php

1. 核實(shí)最先字符是<?php
2. Check that the very last characters are ?>

1. 核實(shí)最后的字符是?>

To be sure about the end of the file, do this:

確定結(jié)束文件，請操作：

1. Place the cursor between the ? and >

1. 在?和 >之間放上鼠標(biāo)

1. Now press the DELETE key on your computer

1. 現(xiàn)在按住你的電腦上的DELETE鍵

1. • Note to MAC users: The "DELETE" key on a PC deletes characters to the right of the cursor. That's the key meant here.

1. • MAC用戶注意：個(gè)人電腦上的"DELETE"鍵刪除了鼠標(biāo)右邊的字符。那是這里提到的鍵。

1. Keep that key pressed

1. 安裝那個(gè)鍵

1. For at least 15 seconds

1. 至少按15秒

1. Now type > and
2. 現(xiàn)在輸入>并且

1. save without pressing any other key at all.

1. 不要輸入其它鍵，保存。

1. If you press another key, you will bring the problem back.

1. 如果你按了其它鍵，你將會又遇到麻煩。

Interpreting the Error Message:

解釋錯(cuò)誤信息: If the error message states: 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, then the problem is at line #34 of wp-config.php, not line #42 of wp-login.php. In this scenario, line #42 of wp-login.php is the victim. It is being affected by the excess whitespace at line #34 of wp-config.php.

如果錯(cuò)誤信息顯示：警告:不能更改標(biāo)頭信息-在第42行/path/blog/wp-login.php，標(biāo)頭已經(jīng)發(fā)送(從/path/blog/wp-config.php:34開始輸出)，然后問題出現(xiàn)在wp-config.php的第#34行，而不是wp-login.php的第#42行。在這里，wp-login.php的第#42行是問題所在。受到wp-config.php的第#34行的的過度的空格的影響。

If the error message states: 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, then the problem is at line #8 of admin-header.php, not line #569 of post.php. In this scenario, line #569 of post.php is the victim. It is being affected by the excess whitespace at line #8 of admin-header.php.

如果錯(cuò)誤信息顯示：警告:不能更改標(biāo)頭信息-在第42行/path/blog/wp-login.php，標(biāo)頭已經(jīng)發(fā)送(從/path/wp-admin/admin-header.php:8開始輸出)在/path/wp-admin/post.php on line 569中，然后問題出現(xiàn)在admin-header.php的第#8行，而不是post.php的第#569行。在這里，post.php的第#569行是問題所在。受到admin-header.php的第#8行的的過多的空格的影響。

No Quicktag buttons in Safari

Safari中沒有Quicktag按鈕

Description: The Quicktag buttons in the Write interface do not display when using Apple's Safari browser.

描述:使用Apple的Safari瀏覽器時(shí)，寫界面中的Quicktag按鈕不顯示。

Reason and Solution :

原因和解決方法 :

In Safari, the Quicktag buttons will function, but not as intended. This is due to a bug in Safari, not WordPress. Since the WordPress developers have no way of correcting this, they have chosen to disable the Quicktag buttons for Safari users. At this point in time, there are a few choices to make. One could use Firefox, or comment lines 581 and 589 in /wp-admin/admin-functions.php .

在Safari中，Quicktag按鈕能夠運(yùn)行，但是不如想象地那樣運(yùn)行。這是因?yàn)镾afari而不是WordPress中的程序缺陷問題。因?yàn)閃ordPress開發(fā)人員沒有方法來解決這個(gè)問題，他們只能夠選擇為Safari用戶取消Quicktag按鈕。這時(shí)，可以做出一些選擇。一種是可以使用Firefox，或者在/wp-admin/admin-functions.php中，comment lines 581 和 589。

For example, change this:

例如，將這個(gè):

function the_quicktags () {
// Browser detection sucks, but until Safari supports 
the JS needed for this to work people just assume it's a bug in WP
if ( !strstr($_SERVER['HTTP_USER_AGENT'], 'Safari') ) :
echo '
<div id="quicktags">
<a  title="' 
. __('Help with quicktags') . '">' . __('Quicktags') . '</a>:
<script src="quicktags.js" type="text/javascript"></script>
<script type="text/javascript">edToolbar();</script>
';
echo '</div>';
endif;
}

function the_quicktags () {
// Browser detection sucks, but until Safari supports 
the JS needed for this to work people just assume it's a bug in WP
if ( !strstr($_SERVER['HTTP_USER_AGENT'], 'Safari') ) :
echo '
<div id="quicktags">
<a  title="' 
. __('Help with quicktags') . '">' . __('Quicktags') . '</a>:
<script src="quicktags.js" type="text/javascript"></script>
<script type="text/javascript">edToolbar();</script>
';
echo '</div>';
endif;
}

to this: 更改為：

function the_quicktags () {
// Browser detection sucks, but until Safari supports the JS needed for this to work people just assume it's a bug in WP
//if ( !strstr($_SERVER['HTTP_USER_AGENT'], 'Safari') ) :
echo '
<div id="quicktags">
<a  title="' 
. __('Help with quicktags') . '">' . __('Quicktags') . '</a>:
<script src="quicktags.js" type="text/javascript"></script>
<script type="text/javascript">edToolbar();</script>
';
echo '</div>';
//endif;
}

Emailed passwords not received

沒有收到帶有密碼的電子郵件

Description: When users try to register with your blog or change their passwords by entering their username and email, Wordpress says that their password has been emailed to them, but it's never received.

描述:當(dāng)用戶試著在你的博客上注冊或者通過輸入他們的用戶名和電子郵件來更改密碼的時(shí)候，WordPress顯示他們的密碼已經(jīng)發(fā)送給他們了，但是他們沒有收到郵件。

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're using a hosting service, but if you're using your own box and don't have an SMTP server, the mail won't ever send. If you're using a *NIX box, you should have either postfix or sendmail on your machine; you'll just need to set them up (google for how-to's). If you don't want to go through setting up a complete mail server on you *NIX box you may find 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 Glob SendMail.

原因和解決方法:Wordpress使用標(biāo)準(zhǔn)的php郵件函數(shù)，這個(gè)函數(shù)使用sendmail。不需要帳戶信息。如果你正使用托管服務(wù)，但是如果你正使用自己的框而且沒有SMTP服務(wù)器，郵件永遠(yuǎn)都不會發(fā)送給你。如果你正使用*NIX框，你的電腦上應(yīng)該有postfix 或者sendmail；你只要將這些設(shè)置好就行了(google for how-to's)。如果你不希望在你的*NIX框中設(shè)置完整的郵件服務(wù)器，你可能覺得。在Windows電腦上，嘗試sendmail emulator，如Glob SendMail。

More help can be found on the forums at: http://wordpress.org/support/topic.php?id=24981

可以在http://wordpress.org/support/topic.php?id=24981的論壇上找到更多的幫助

Back to FAQ

返回到常見問題解答