編輯“WordPress:Reporting Bugs”（章節(jié)）

=== 報告程序錯誤 ===

[http://trac.wordpress.org/ Trac] is the name of the official WordPress bug tracker. It uses the open source bug tracking software [http://projects.edgewall.com/trac/ Trac] which is a product from [http://www.edgewall.com/ Edgewall Software]. Follow these steps to create a good bug report in Trac:

[http://trac.wordpress.org/ Trac]是官方WordPress程序追蹤器的名稱，使用開放源碼程序追蹤軟件[http://projects.edgewall.com/trac/ Trac],這個軟件是來自[http://www.edgewall.com/ Edgewall 軟件]的一個產(chǎn)品。遵循下面的步驟在Trac中創(chuàng)建一個良好的程序錯誤報告。

# Read [[WordPress:#Before You Report a Bug|Before You Report a Bug (above)]], and verify that you have a new bug that is appropriate to report.

#閱讀[[WordPress:#Before You Report a Bug|報告程序錯誤之前 的準備(上面的)]]，并且確認你有一個可以報告的程序錯誤。

# Read this article on [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively], and the [http://trac.wordpress.org/wiki/TracTickets Trac Ticket documentation].

#在[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html 怎樣有效地報告程序錯誤]和[http://trac.wordpress.org/wiki/TracTickets Trac Ticket 文檔]上閱讀這篇文章。

# Log into [http://trac.wordpress.org/ WordPress Trac] using your [http://wordpress.org/support/ support forum] username and password. If you don't have an account at the support forums, [http://wordpress.org/support/register.php register] so that you can login to Trac. This is essential for communication about your bug, since the developers may need more information (and you cannot create a ticket without logging in).

#使用[http://wordpress.org/support/ 支持論壇]用戶名和密碼，登錄到[http://trac.wordpress.org/ WordPress Trac]。如果你沒有支持論壇的帳戶，[http://wordpress.org/support/register.php 注冊]一個帳戶，你就可以登錄到Trac。這對于探討程序錯誤至關(guān)重要，因為開發(fā)人員可能需要更多的信息（但是你沒有登錄，就不能創(chuàng)建ticket）。

# Click '''[http://trac.wordpress.org/newticket New Ticket]''' in Trac to reach the bug reporting page. 

#點擊Trac中的'''[http://trac.wordpress.org/newticket 新的Ticket]'''得到報告程序錯誤的網(wǎng)頁。

# Fill in the following fields on the new ticket page:

#在新的ticket網(wǎng)頁，填寫以下的欄：

#; Short Summary: Make the summary short but informative and accurate, as this is the ticket title that will be displayed in search results.

#；簡短的摘錄：使得摘錄簡短，精確，信息明了，因為這是搜索結(jié)果中顯示的ticket 標題。

#; Full Description: Fill in a full description of your bug or feature request. Include a description of the problem, steps someone else would have to take to reproduce the problem, maybe an example of the bug in action (i.e. a URL), and a description of why it is a problem worthy of being corrected. Also include information about your platform, such as operating system, web server software, PHP version, MySQL version, and WordPress version. The better your description, the better the chances of having the bug resolved promptly.

#；完整的描述：完整地描述程序錯誤或者需要的功能。包括描述程序錯誤，其他人復制這個程序錯誤需要采取的步驟，可能還有一個運轉(zhuǎn)的程序錯誤的例子（例如URL），以及描述為什么這個程序錯誤值得修正。同時還包括你的平臺的信息，例如操作系統(tǒng)，網(wǎng)絡服務器軟件，PHP版本，MySQL版本，和WordPress版本。你描述地越好，程序錯誤得到合理解決的可能性越大。

#; Ticket Properties:

#; Ticket屬性：

#:; Priority: You will need to decide on a priority for the issue -- this is how urgent the bug is. Unless it is a critical bug, this is best left to the default as developers will usually rank the bug's priority.

#：；優(yōu)先權(quán)：你需要決定問題的優(yōu)先性—意思是程序錯誤問題有多么嚴重。除非那是個嚴重的程序錯誤問題，最好將這個問題設置為默認的，因為開發(fā)人員通常會對程序錯誤的優(yōu)先性進行排名。

#:; Component: Select the component of WordPress where the bug was found

#：；組成部分：選擇發(fā)現(xiàn)程序錯誤的WordPress的那部分。

#:; Severity : The ''significance'' of the issue. Select a severity based on how critical you consider the issue to be. If in doubt, leave this option as ''Normal''.

#：；重要性：問題的''重要性''。根據(jù)你認為問題有多么重要，給問題選擇一個重要性級別。如果有疑問，將這個選項保持為''一般的''。

#:; Assign to: If you know of the developer who is responsible for the code that the bug is in, place their Trac username here. You can also take responsibility for the bug yourself, by putting your own Trac user name here. This is optional and could speed up developer attention to the bug.

#：；遞交：如果你知道哪個開發(fā)人員負責錯誤程序的代碼，你可以將這個開發(fā)人員的Trac用戶名放在這兒。你也可以自己對程序錯誤負責，將你自己的Trac用戶名放在這里。這是可選的，也能夠加快程序員注意這個程序錯誤。

#:; Milestone: By what version this issue should be resolved, at the latest. Do not change this. This is an option that WordPress developers will set.

#：；最遲在哪個版本，這個程序錯誤會得到修正。不要更改這個版本數(shù)字。這是WordPress開發(fā)人員設置的一個選項。

#:; Version: The version of WordPress where the bug was found. You can find the version number of WordPress in the footer of the admin panel.

#：；版本：發(fā)現(xiàn)程序錯誤的WordPress版本。你可以在管理面板的頁底文字上發(fā)現(xiàn)WordPress的版本數(shù)字。

#:; Keywords: Keywords that will make it easier for developers to find the bug, and identify the areas it affects. An example might be 'posting' for a bug involving the posting mechanism in WordPress. Also, there are some standard keywords used to flag your bug's status (see [[WordPress:#Trac Keywords|Trac Keywords]] below).

#：；關(guān)鍵詞：關(guān)鍵詞，能夠幫助開發(fā)人員更輕易地找到程序錯誤并且識別這個程序錯誤可能影響的區(qū)域?？赡軙樯婕癢ordPress posting 機制的程序錯誤，'posting'一個例子。同時，可以使用一些標準的鍵，表示程序錯誤的級別（請看看下面的[[WordPress:#Trac Keywords|Trac Keywords]]）。

#:; CC: Who bug information and updates should be sent to. If you want to be kept informed, enter your own Trac user name here. You will then  be notified by email any time a change is made to this report, or a note to the bug is added. Don't ignore these emails; any time a change is made, be sure to check the report for updates. Developers may need further information from you, and this is their only way of getting in contact with you. '''Note''': you need to go to the Trac ''Settings'' page to set your email address. Putting it into your Support Forum profile will not get it into Trac for purposes of CC messages.

#：；CC：程序錯誤信息和更新信息，應該發(fā)送給誰。如果你希望得到通知，請在這里輸入你的Trac 用戶名。然后，如果這個程序錯誤發(fā)生了任何更改或者添加了額外信息，你都會得到一封電子郵件的通知。不要忽視這些電子郵件；任何時候這個錯誤報告更改了，你要確定更新這個報告。開發(fā)人員可能需要你提供更深入的信息，這是他們與你聯(lián)系的唯一方式。'''注''':你可能需要進入Trac ''設置''網(wǎng)頁，設置你的電子郵件地址。將電子郵件地址放到支持論壇你的基本資料中，不能使郵件地址為了CC信息，而進入Trac中。

# Click '''Submit Ticket''' (after previewing it). Then pat yourself on the back.

#點擊'''遞交Ticket'''(預覽Ticket后)。這樣你可以放松了。