WordPress:Reporting Bugs

Every application has bugs -- as long as humans write code, there will continue to be errors in software. Some errors are trivial, while others are critical. Open-source projects like WordPress:WordPress need the participation of their user communities to identify bugs in their software, as well as to plan for new features.

每個應用軟件都有程序錯誤—只要是人類在編寫代碼，軟件不斷地就會有程序錯誤。有的錯誤是輕微的，而有的錯誤確實致命的。開放源碼軟件，像WordPress需要WordPress的用戶參與，識別軟件中的程序錯誤，準備新的功能。

All types of feedback — whether they're genuine bugs or feature requests — are reported the same way in the WordPress project. Read on to learn how to report bugs and issues for WordPress... you may also want to read WordPress:Contributing to WordPress to find out how to contribute to the documentation and other areas of the WordPress project.

所有類型的feedback —不管是真正的程序錯誤還是功能請求—都是以同樣的方式在WordPress軟件中報告的。繼續(xù)閱讀，學習關(guān)于怎樣報告程序錯誤和關(guān)于WordPress方面的問題… 你也可能想要閱讀奉獻于WordPress了解怎樣對WordPress文檔以及WordPress軟件項目的其它領域做貢獻。

目錄

• 1 Reporting security issues
• 2 報告安全問題
• 3 Reporting Bugs in Plugins and Themes
• 4 在插件和主題中報告程序錯誤
• 5 Overview of Bug Reporting and Resolution
• 6 程序錯誤報告和解決方法概述
• 7 Details of Bug Reporting and Resolution
• 8 程序錯誤報告和解決辦法的詳細信息
  • 8.1 Before You Report a Bug
  • 8.2 報告程序錯誤之前
  • 8.3 Reporting a Bug
  • 8.4 報告程序錯誤
  • 8.5 Finding Bugs to Fix
  • 8.6 查找程序錯誤并修正
  • 8.7 Patching Bugs
  • 8.8 修補程序錯誤
  • 8.9 Trac Keywords
  • 8.10 Trac 關(guān)鍵詞
  • 8.11 Bug Resolutions
  • 8.12 解決程序錯誤的方法
• 9 Notes
• 10 注意

報告安全問題

While we try to be proactive in preventing security problems, we do not assume they'll never come up. If you believe you've found a security problem in a release of WordPress please send mail to security at the WordPress.org domain and we'll do our best to address it as soon as possible.

雖然我們試著提前預防安全問題，我們并沒有假定安全問題永遠都不會出現(xiàn)。如果你相信在WordPress發(fā)行的某個版本中發(fā)現(xiàn)了安全問題，請發(fā)送電子郵件到WordPress.org domain的security，我們會盡快地解決這個問題。

It is standard practice to notify the vendor (the WordPress developers, in this case) of a security problem before publicizing so a fix can be prepared and public damage due to the vulnerability minimized.

先通知出售商（在這種情況是WordPress開發(fā)人員），關(guān)于安全方面的問題，再將WordPress發(fā)行，這樣可以準備解決程序錯誤的方法，因為程序錯誤而導致的危害，也能夠最小化。

在插件和主題中報告程序錯誤

If you find a bug in a Plugin or Theme you are using with WordPress, do NOT report it using the procedures in this article! Instructions in this article apply only to bugs in the WordPress core, and do not apply to bugs in plugins and themes.

如果你在WordPress插件或者主題中發(fā)現(xiàn)了程序錯誤，不要使用這篇文章所述的步驟，報告錯誤。這篇文章中報告程序錯誤的方法，只適用于WordPress核心，不適用于插件和主題。

Plugins which reside in the WordPress Plugin Repository have a separate bug tracking system from the WordPress core. Separate instructions are available for using that system.

WordPress 插件 資源庫中的插件擁有來自WordPress核心的分開的程序錯誤追蹤系統(tǒng)?？梢允褂?a target="_blank" rel="nofollow noreferrer noopener" class="external text" >Separate instructions來使用這個系統(tǒng)。

For plugins which do not reside in the official repository, and for themes, check the documentation that came with the plugin or theme for instructions on where to report bugs. If no bug reporting information came with your plugin or theme, you'll need to contact the author directly.

對于官方的插件資源庫以外的插件和主題，查看插件或者主題的指示說明，了解怎樣報告程序錯誤。如果你的插件或者主題沒有關(guān)于報告程序錯誤的信息，你就需要直接地聯(lián)系插件或者主題的作者。

程序錯誤報告和解決方法概述

There are several steps in the process of reporting and resolving a WordPress bug. Here is an overview; more details are in sections below.

關(guān)于報告和解決WordPress程序錯誤問題，有幾個步驟。這里是概述；更多的詳細信息，在下面的部分。

1. A user finds a bug that appears to be in the core of WordPress (not in a Theme or Plugin).

1. 用戶在WordPress核心發(fā)現(xiàn)了一個程序錯誤（錯誤不是在主題或者插件中0

1. The user tries to make sure it is actually a bug. See [[WordPress:#Before You Report a Bug|Before You Report a Bug (below)]].

1. 用戶試著確定那的確是個程序錯誤。請看看[[WordPress:#Before You Report a Bug|報告程序錯誤之前 (下面的)]]。

1. If it is determined to be a bug, the user submits the bug report, called a ticket, to Trac, the WordPress bug tracking system. See [[WordPress:#Reporting a Bug|Reporting a Bug (below)]].

1. 如果確定那是個程序錯誤，用戶遞交程序錯誤報告，稱之為ticket，遞交到Trac，WordPress程序錯誤追蹤系統(tǒng)。請看看[[WordPress:#Reporting a Bug|報告一個程序錯誤 (下面的)]]。

1. A WordPress developer (who could be a volunteer like you) confirms that the bug does actually exist, and that it should be fixed, and marks it as such in the ticket. See [[WordPress:#Trac Keywords|Trac Keywords list (below)]] and [[WordPress:#Bug Resolutions|Bug Resolutions (below)]].

1. WordPress開發(fā)人員（可能像你一樣，是個志愿者）證實了的確存在程序錯誤，而且應該得到解決，并且在ticket對這個錯誤進行標記。請看看[[WordPress:#Trac Keywords|Trac Keywords 列表(下面的)]] 和 [[WordPress:#Bug Resolutions|程序錯誤解決方法(下面的)]]。

1. A WordPress developer (which could be you) decides to fix the bug. The developer may choose to take responsibility for the bug by clicking on the Accept ticket option near the bottom of the ticket, though this is not required. Then the developer figures out how to fix the bug, creates one or more patch files, and uploads them to Trac. See [[WordPress:#Patching Bugs|Patching Bugs (below)]]. Also, if you want to help with fixing bugs, but don't know what bugs to fix, see [[WordPress:#Finding Bugs to Fix|Finding Bugs to Fix (below)]].

1. WordPress開發(fā)人員（可能是你）決定解決這個程序錯誤。開發(fā)人員可能選擇通過點擊ticket底部旁邊的接受 ticket選項，負責解決程序錯誤，但是這并不是必須的。然后開發(fā)人員思索怎樣解決程序錯誤，創(chuàng)建一個或者更多的補丁文件，并且將這些文件上傳到Trac。請看看[[WordPress:#Patching Bugs|Patching Bugs (下面的)]]。同時，如果你想要幫助解決程序錯誤，但是不知道要解決哪個程序錯誤問題，請看看[[WordPress:#Finding Bugs to Fix|找到程序錯誤來解決 (下面的)]]。

1. Members of the WordPress development group (including volunteers) test the patch, to see if it fixes the bug and doesn't break anything else. They add comments and keywords to the ticket to indicate their results. See [[WordPress:#Trac Keywords|Trac Keywords list (below)]].

1. WordPress開發(fā)小組的成員（包括志愿者）測試補丁，看看是否能夠解決程序錯誤，同時不會破壞其它的內(nèi)容。他們給tickets添加評論和keywords，暗示結(jié)果。請看看[[WordPress:#Trac Keywords|Trac Keywords list (下面的)]]。

1. One of the WordPress developers with authority to modify the official WordPress source code (Matt Mullenweg, Ryan Boren, Mark Jaquith or Peter Westwood) commits the patch to the core code in the SVN repository. They are more likely to do this if the bug and patch has been verified by someone they trust.

1. 1. 更改WordPress官方源代碼，權(quán)威的WordPress開發(fā)人員(Matt Mullenweg, Ryan Boren, Mark Jaquith 或者 Peter Westwood) 遞交 補丁到SVN資源庫的核心代碼。如果程序和補丁由某個他們信任的人證實了，開發(fā)人員更會這么做。

1. Finally, the person who commits the patch sets the bug ticket status to closed and the resolution to fixed. See [[WordPress:#Bug Resolutions|Bug Resolutions (below)]].

1. 最后，遞交補丁的人，將程序錯誤ticket級別設置為關(guān)閉的，將解決辦法設置為解決的。請看看[[WordPress:#Bug Resolutions|程序錯誤解決辦法 (下面的)]]。

程序錯誤報告和解決辦法的詳細信息

The sections below add details to some of the steps outlined above.

下面的部分，給上面列出的一些步驟，添加了詳細信息。

報告程序錯誤之前

With large projects like WordPress, so many users report bugs that there's a good chance your bug has already been reported. Because of this, it's very important to check to be sure it's not already in the system before you submit it. If you are new to reporting bugs in WordPress, it is also a good idea to discuss the issue with more experienced developers before reporting it. Please follow the steps below.

像WordPress這么大的軟件項目，許多用戶都會報告程序錯誤，很有可能你報告的程序錯誤，其他人已經(jīng)報告了。因此在遞交錯誤報告之前，看看系統(tǒng)中是否已經(jīng)存在這樣的報告，非常重要。如果對于報告WordPress程序錯誤，你還是個新手，與有經(jīng)驗的開發(fā)人員，討論這個問題，然后再報告程序錯誤，這是個好主意。請遵循下面的步驟。

1. Search for your bug or feature request in Trac by using Search or a Query.

1. 通過使用搜索 或者查詢搜索你的程序錯誤或者Trac需求的功能。

1. • If your issue has already been reported, please do not report a duplicate bug. If you have further information to contribute, log in and add a note to the existing bug.

1. 如果你要報告的程序錯誤，他人已經(jīng)報告了，請不要重復報告。如果你還需要貢獻關(guān)于這個錯誤的更深層次的信息，請登錄并且給當前存在的程序錯誤，添加內(nèi)容。

1. • If your issue is similar, but not quite the same as another issue, you may decide whether to add a note to the similar issue, or report a new one. It can be difficult to decide whether your issue warrants a new submission, but in general if you just have more information to contribute to a current, open issue, simply add a note to that issue. If you have a different enough issue, or if you are experiencing a recurrence of an issue that was previously resolved, report a new bug.

1. • 如果你報告的程序錯誤與其他人報告的相似，但是不是完全一樣的，你可能決定是否向相似的報告添加一些信息，還是報告一個新的程序錯誤。決定你的報告是否值得再遞交一次，很難。但是遺憾，如果你有更多的信息，可以添加到當前的錯誤報告了，你可以添加一個便條即可。如果你有足夠多的不同的信息，或者你發(fā)現(xiàn)了一個先前解決好的程序錯誤問題有出現(xiàn)了，你可以將其作為一個新的程序錯誤報告。

1. • If your issue was recently reported and then closed, and you do not agree with the resolution, you can also reopen the ticket and add a comment as to your reasoning.

1. • 如果你發(fā)現(xiàn)的程序錯誤，最近已經(jīng)有人報告了，但是又關(guān)閉了，而且你不同意解決那個錯誤的方法，你可以再次打開ticket并且根據(jù)你的推理 ，再次地添加一個評論。

1. To discuss a bug before reporting it in Trac (e.g. to figure out if it is really a bug in the core of WordPress and not in a plugin or theme), you can post a question on the WordPress Support Forum, discuss your issue on the #wordpress IRC channel, or have an email discussion on the Testers or Hackers mailing list.

1. 討論程序錯誤然后再將它報告到Trac（例如，了解程序錯誤是否真是WordPress核心中的程序錯誤，而不是插件或者主題中的程序錯誤），你可以在WordPress 支持論壇上發(fā)表一個問題，討論你在#wordpress IRC channel上遇到的問題，或者在Testers 或者Hackers郵件列表上發(fā)郵件討論這個問題。

報告程序錯誤

Trac is the name of the official WordPress bug tracker. It uses the open source bug tracking software Trac which is a product from Edgewall Software. Follow these steps to create a good bug report in Trac:

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

1. 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.

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

1. Read this article on How to Report Bugs Effectively, and the Trac Ticket documentation.

1. 在怎樣有效地報告程序錯誤和Trac Ticket 文檔上閱讀這篇文章。

1. Log into WordPress Trac using your support forum username and password. If you don't have an account at the support forums, 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).

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

1. Click New Ticket in Trac to reach the bug reporting page.

1. 點擊Trac中的新的Ticket得到報告程序錯誤的網(wǎng)頁。

1. Fill in the following fields on the new ticket page:

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

1. Short Summary

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

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

1. 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.

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

1. Ticket Properties

1. Ticket屬性：

1. 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.

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

1. Component

   Select the component of WordPress where the bug was found

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

1. 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.

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

1. 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.

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

1. 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.

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

1. 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.

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

1. 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).

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

1. 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.

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

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

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

查找程序錯誤并修正

If you want to fix bugs in the core parts of WordPress, but don't know which ones to fix, here are some suggestions on how to find bugs to fix:

如果你想要解決WordPress核心部分的程序錯誤，但是不知道要解決那個錯誤，下面有一些提議，關(guān)于怎樣找到程序錯誤，對其進行修正：

• Look through the Needs Patch Report on Trac (which lists bugs that have not been marked with the "has_patch" keyword), the Lacks Attachment Report on Trac (which lists bugs that do not have a patch file attached), or other Trac reports for bugs that look interesting.

• 通讀Needs Patch Report on Trac(列出了沒有標記"has_patch"關(guān)鍵詞的程序錯誤)，Lacks Attachment Report on Trac（列出了沒有附加補丁文件的程序錯誤），或者其它的看起來有趣的程序錯誤Trac 報告。

• Send an email message to the wp-hackers mailing list and ask how you can help.

• 向wp-hackers 郵件列表發(fā)送一封電子郵件，并且詢問你可以怎么幫忙。

• There is also sometimes bug triage on the #wordpress-dev WordPress:IRC channel

• 還有一些程序錯誤在#wordpress-dev WordPress:IRC channel上優(yōu)先得到修正

• Occasionally there are bug days on #wordpress-bugs. You can read about what happens in a bug day in WordPress:WordPress Bug Hunts, and subscribe to either the wp-hackers or wp-testers mailing list to find out when they happen.

• 有時候#wordpress-bugs上會有程序錯誤日。你可以在WordPress程序錯誤搜索上閱讀，程序錯誤日那天發(fā)生了什么事，并且訂閱wp-hackers 或者wp-testers列表，看看程序錯誤日是哪一天。

• Consider joining the wp-trac email list to follow the discussions about each Trac Ticket.

• 考慮加入wp-trac 電子郵件列表看看關(guān)于每個Trac Ticket的討論。

修補程序錯誤

If you and are familiar with PHP and MySQL, and would like to help in the development of WordPress, then you are encouraged to patch WordPress bugs. Here are the steps to follow:

如果你熟悉PHP 和MySQL，并且希望在WordPress發(fā)展過程中，盡自己的一臂之力，你可以解決程序錯誤問題。下面是一些你可以遵循的步驟：

1. Read [[WordPress:#Finding Bugs to Fix|Finding Bugs to Fix (above)]], and find a bug to fix in Trac.

1. 請閱讀[[WordPress:#Finding Bugs to Fix|查找修正程序錯誤 (上面的)]]，查找程序錯誤，在Trac中修正。

1. Connect to the WordPress Subversion (SVN) Repository using the username and password you acquired when registering. Read WordPress:Using Subversion if you are unfamiliar with SVN. All patches should be submitted against the latest code in the SVN repository.

1. 連接到WordPress 子版本(SVN) 資源庫，注冊時，使用你得到的用戶名和密碼。如果你不熟悉子版本，請閱讀使用子版本。所有的補丁都必須根據(jù)子版本資源庫中最新的代碼，遞交。

1. Figure out how to fix the bug, by modifying WordPress core files. You may want to discuss your proposed solution on the wp-hackers mailing list before finalizing it.

1. 了解怎樣通過更改WordPress核心文件，解決程序錯誤問題。你可能希望在wp-hackers 郵件列表上討論你建議的解決辦法，再最后決定使用這個方法。

1. Test your fix, verifying that the bug has been fixed, and that nothing else in WordPress is broken in the process.

1. 測試你的方法，確認程序錯誤已經(jīng)得到了解決，而且在解決過程中，WordPress中的其它內(nèi)容都沒有受損。

1. Create a patch file (or files) containing your fix. This is basically a diff of the fixed file(s) and the originals from SVN. See How to Patch WordPress by Owen Winkler for detailed instructions. There are also instructions for Linux/Mac command-line users in Mark Jaquith's Toolbox and Windows Tortoise SVN users in .

1. 創(chuàng)建一個(或者多個)包含解決方法的補丁文件。這基本上是固定文件的diff，而且是SVN的原始資料。請看看Owen Winkler的怎樣修補WordPress上面的詳細指示。在Mark Jaquith's Toolbox上也有對于Linux/Mac 命令行用戶的指導和Westi的博客上的Windows Tortoise SVN用戶的指導。

1. Upload it to the ticket using the Trac Attach file button, and add has-patch to the keywords. If the patch needs testing, you might also put needs-testing, or one of the other Trac keywords; see [[WordPress:#Trac Keywords|Trac Keywords (below)]] for more information.

1. 使用Trac 附加文件按鈕，將其上傳到ticket上，并且將has-patch添加到關(guān)鍵詞上。如果補丁需要測試，你可能需要加入需要測試，或者其它的某個Trac關(guān)鍵詞；更多的信息，請看看[[WordPress:#Trac Keywords|Trac 關(guān)鍵詞 (下面的)]]

Trac 關(guān)鍵詞

There are a number of keywords with defined meaning used in Trac that are commonly used; some are also searched for by Trac Reports.

有許多關(guān)鍵詞，擁有規(guī)定的意思，用在經(jīng)常使用的Trac中；有的關(guān)鍵詞也可以通過Trac報告搜索。

reporter-feedback

A response is needed from the reporter. Further investigation is unlikely without a response to the questions from someone experiencing the problem.

報告人員反饋

需要來自報告人員的反饋信息。如果沒有來自遇到這個程序錯誤的人員的響應信息，就很難進行深入的調(diào)查。

has-patch

A solution to the ticket has been attached, and it is ready for review and/or committing.

has-patch

附加ticket的一個解決方法，而且可以閱讀和/或者遞交這個方法。

needs-testing

Someone needs to test the solution.

需要測試

有的人需要測試這個解決方法。

2nd-opinion

Another person is needed to express an opinion about the problem or the solution.

第二種觀點

另一個人需要對問題或者解決方法提出自己的觀點。

dev-feedback

A response is wanted from a developer (not commonly used)

dev-feedback

需要來自開發(fā)人員的回應(不經(jīng)常使用)

tested

The patch has been tested. When adding this tag please comment with the patch filename that was tested, how the patch was tested, and which version of WordPress was used (including the SVN revision number, if it is not an officially released version).

tested

補丁需要經(jīng)過測試。添加這個標簽的時候，請用經(jīng)過測試后的文件名評論，補丁是怎樣測試的，使用的是WordPress的哪個版本（如果不是官方發(fā)行的版本，包括SVN修訂數(shù)字）。

commit

The patch has been reviewed and tested by a trusted member of the development community; therefore the patch is ready to be added to the WordPress core files.

commit

補丁有發(fā)展團隊中一名可以信任的隊員閱讀并測試了；那么補丁就要添加到WordPress核心文件了。

needs-patch

The ticket has been reviewed, found to be desirable to solve, and marked as especially needing a patch, or the submitted patch doesn't work and needs to be redone.

needs-patch

ticket已經(jīng)得到了瀏覽，而且發(fā)現(xiàn)需要解決程序錯誤問題，同時標記為特別需要修補，或者如果不能夠遞交補丁，就需要重新遞交。

needs-unit-tests

The ticket has been reviewed, found to be desirable to solve and we would like some unit tests written to test the functionality and any patch that may exist before committing a change as the risk of causing other issues is high.

needs-unit-tests

:ticket已經(jīng)得到了瀏覽，而且發(fā)現(xiàn)需要解決程序錯誤問題，我們希望編寫一些unit測試，測試泛函性以及任何可能存在的補丁，再做出更改，以防止導致其它更嚴重的問題。

needs-doc

Inline documentation for the code is needed. These are either place holder tickets for individual files or tickets with patches for new functions which need documenting before they are committed.

needs-doc

需要代碼的inline文檔。這些是單個文件的place holder或者是擁有補丁的需要證明才能遞交的新函數(shù)的ticket的place holder。

解決程序錯誤的方法

A ticket in Trac starts its life in the open status, and (hopefully) is eventually closed. When a ticket is closed, it is marked with one of the following status designations:

Trac中的ticket從打開的status開始運行，而且（希望）是最終關(guān)閉的。當一個ticket關(guān)閉的時候，ticket標記有下面的其中一個級別：

• If your bug has been reported elsewhere, it will likely be closed with duplicate.

• 如果你的程序錯誤是在其它位置報告的，ticket關(guān)閉時，帶有復制級別。

• If the bug has already been fixed in the latest subversion code (which is probably not what you're running unless you have a local test blog), then it will be closed with fixed.

如果程序錯誤在最新的子版本代碼中已經(jīng)修正了（除非你有一個本地測試博客，否則子版本代碼并不是你運行的內(nèi)容），ticket關(guān)閉時，擁有已解決級別。

• If it is decided that your bug isn't in fact a bug, but is the intended behaviour, it will be closed with invalid.

• 如果確定你報告的程序錯誤事實上并不是一個錯誤，而是一個正常的代碼，那么ticket關(guān)閉時，會標有無效的。

• If no-one else can replicate the symptoms you describe, it will be closed with worksforme.

• 如果你沒有人能夠復制你描述的符號，那么ticket關(guān)閉時候，會標有worksforme。

• If your bug is a feature request that the developers don't want in the core, it will be marked as wontfix.

• 如果你報告的程序錯誤是個功能請求，但是開發(fā)人員并不想在WordPress核心中添加這個功能，那么ticket關(guān)閉時，會標有wontfix。

Please verify that your bug doesn't fall into one of these categories before submission.

在遞交程序錯誤之前，請確認你發(fā)現(xiàn)的程序錯誤不屬于以上的任何一類。

注意

• The processing of your bug may require your participation. Please be willing and prepared to aid the developers in resolving the issue.

• 處理程序錯誤，可能需要你的參與。請樂意準備幫助程序員解決程序錯誤問題。

• Don't be upset if your bug gets resolved as "Not a bug" or "Won't fix". What seems like a bug to you may very well be a "feature". These resolutions just mean "not going to fix now", maybe in the future it will be a priority to solve.

• 如果你報告的程序錯誤"不是程序錯誤" 或者 "不能夠解決"，請不要焦慮不安。你認為是程序錯誤的內(nèi)容，可能是個"feature"。這里只是指"現(xiàn)在不解決"，但是將來某天可能會首先解決這個程序問題。

• Thank you for contributing to the development of WordPress!
• 非常感謝你對WordPress的發(fā)展做貢獻！