WordPress.org

Ready to get started?Download WordPress

Codex

ko: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 need the participation of their user communities to identify bugs in their software, as well as to plan for new features.

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 Contributing to WordPress to find out how to contribute to the documentation and other areas of the WordPress project.

Contents

보안문제 보고하기

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 see the Security FAQ for information on how to report the problem.

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.

플러그인 및 테마 버그 보고하기

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.

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.

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.

Overview of Bug Reporting and Resolution

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

  1. A user finds a bug that appears to be in the core of WordPress (not in a Theme or Plugin).
  2. The user tries to make sure it is actually a bug. See Before You Report a Bug (below).
  3. 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 Reporting a Bug (below).
  4. 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 Trac Keywords list (below) and Bug Resolutions (below).
  5. 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 Patching Bugs (below). Also, if you want to help with fixing bugs, but don't know what bugs to fix, see Finding Bugs to Fix (below).
  6. 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 Trac Keywords list (below).
  7. One of the WordPress developers with authority to modify the official WordPress source code 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.
  8. Finally, the person who commits the patch sets the bug ticket status to closed and the resolution to fixed. See Bug Resolutions (below).

Details of Bug Reporting and Resolution

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

Before You Report a Bug

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.

  1. Make sure the bug is actually caused by WP Core code
    • Just because an error message points to a core file, doesn't mean that's where the problem is.
    • Here is a debugging file that you can place in your wp-content/mu-plugins folder (create it if it doesn't exist) to see where the error is coming from.
  2. Search for your bug or feature request in Trac by using Search or a Query.
    • 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.
    • 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.
    • 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.
    • It is best not to re-open bugs that have been closed for some time (E.G. On a milestone relating to a version more than 1 release old) - in that event consider a new ticket.
    • Please do not change the version number on bugs that have been reported already. The version number relates to the version in which the bug was originally discovered. If you're seeing the same bug in a newer version, mention so in a comment.
  3. 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.

버그 보고하기

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:

  1. Read Before You Report a Bug (above), and verify that you have a new bug that is appropriate to report.
  2. Read this article on How to Report Bugs Effectively, and the Trac Ticket documentation.
  3. 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).
  4. Click New Ticket in Trac to reach the bug reporting page.
  5. Fill in the [#Ticket_Fields].
  6. Click Submit Ticket (after previewing it).

Finding Bugs to Fix

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:

버그 패치하기

If you 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:

  1. Read Finding Bugs to Fix (above), and find a bug to fix in Trac.
  2. Connect to the WordPress Subversion (SVN) Repository using the username and password you acquired when registering. Read Using Subversion if you are unfamiliar with SVN.
  3. 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.
  4. Test your fix, verifying that the bug has been fixed, and that nothing else in WordPress is broken in the process.
  5. 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 Westi's Blog.
  6. Upload it to the ticket using the Trac Attach file button, and add has-patch to the keywords. Please don't overwrite any existing (previous) patches. If the patch needs testing, you might also put needs-testing, or one of the other Trac keywords; see Trac Keywords (below) for more information.

Patch Writing Guidelines

All patches should:

  • be made against the latest code in the SVN repository.
  • be made against the root WordPress directory and not against a subfolder.
  • adhere to the coding standards.

Ticket Fields

Short Summary
Make the summary short but informative and accurate, as this is the ticket title that will be displayed in search results.
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.
Ticket Properties
Priority
This is how urgent the bug is. The core developers will usually rank the bug's priority, so this option may be read-only.
Component
Select the component of WordPress where the bug was found
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.
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.
Milestone
By what version this issue should be resolved, at the latest. The developers generally set this, so this option may be read only.
Version
The earliest version of WordPress where the bug was found or the current stable version for enhancements and feature requests. (Do not change the version on pre-existing tickets.)
Keywords
There are some standard keywords used to flag your bug's status (see Trac Keywords below).
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. Note: If you are the bug's reporter, you will already get messages (if your email is known), so no need for CC.

Ticket Types

bug 
expected behaviour isn't happening
enhancement 
current behaviour is improved or modified
feature 
completely new behaviour is added

Trac Keywords

There are a number of keywords with defined meaning used in Trac that are commonly used; some are also searched for by Trac Reports. Keywords should not be thought of as generic 'tags,' which are not necessary.

reporter-feedback 
A response is needed from the reporter. Further investigation is unlikely without a response to the questions from someone experiencing the problem.
dev-feedback 
A response is wanted from a core developer or trusted members of the development community.
ux-feedback and ui-feedback 
A response is needed from the core team with regards to the desired user experience or interface.
rtl-feedback 
Feedback is needed with regards to RTL support or a patch for RTL support is needed.
2nd-opinion 
Another person is needed to express an opinion about the problem or the solution.
has-patch 
A proposed solution to the ticket has been attached, and it is ready for review.
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-ui 
The ticket requires changing the visual appearance of one or more elements.
needs-refresh 
A submitted patch no longer applies cleanly to the WordPress core files, usually because nearby code has been modified since the patch was submitted. The patch needs to be merged and re-submitted.
needs-testing 
One or more people are needed to test the solution. When testing a patch, 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).
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-docs 
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. A ticket created specifically for inline documentation should be added to the Inline Docs component instead.
needs-codex 
Documentation in codex needs updating or expanding. Remove the keyword from the ticket once the codex is updated.
commit 
The patch has been reviewed and tested by a trusted member of the development community; therefore the patch should be considered a commit candidate and is ready to be added to the WordPress core files.
early 
This keyword should only be applied by committers. The keyword signals that the ticket is a priority and should be handled early in the next release cycle.
i18n-change 
Only used late in the development cycle (after string freeze) to track potential string changes, as translators need to be notified.
close 
The ticket is a candidate for closure with a disposition other than fixed (i.e. wontfix, worksforme, invalid, or duplicate). Often seen with reporter-feedback or 2nd-opinion, otherwise the ticket would have been closed in lieu of the close keyword.

Bug Resolutions

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:

duplicate 
If your bug has already been reported in another ticket. If the bug has already been fixed in the latest development branch (which is probably not what you're running unless you have a local test blog), it will likely be closed as a duplicate of the original ticket.
invalid 
If it is decided that your bug isn't in fact a bug, but is the intended behaviour.
worksforme 
If no one else can replicate the symptoms you describe.
wontfix 
If your bug is a feature request that the developers don't want in the core.
maybelater 
If your bug is a feature request that the developers don't plan on adding in the core, but might reconsider in the future.
fixed 
If the bug is fixed in the core subversion repository.

노트

  • The processing of your bug may require your participation. Please be willing and prepared to aid the developers in resolving the issue.
  • Thank you for contributing to the development of WordPress!

Developer "levels"

  • lead developer: one of the commiters that have the final word on important technical decisions. See Development Team.
  • core commiter: a developer that has permanent commit access
  • guest commiter: a developer granted commit access temporarily, usually for a specific feature
  • core contributor: a person actively involved in Core development, but without commit access