Projects ⇒ Bugs ⇒ How to search the PHP Bugs database ⇒ CPG Dragonfly™ CMS

How to Search

The bug database has been logging bugs since Oktober 27, 2004. This HOWTO will allow for a useful experience while scouring the bug database. Do note that a lot of information is entered in by the general public and therefore cannot be fully trusted. Also, the information contained within a bug report is what setup found the bug, so other setups may apply.

Advanced Search

Some explanations for most of the advanced search options.

Feature Explanation Possible reasons for use
Find bugs The main search text box for your search terms with each term being separated by a space. The searched database fields are: subject, and description. Minimum term length is three characters. There are three types of searches:
  • any : (default) One or more (any) of the search terms may be present.
  • all : All search terms are required.
  • raw : Allows full use of MySQL's FULLTEXT boolean search operators.
For any, you might search for a function and its alias while not caring which shows up. Or a name that has changed in a project. Use of all makes sense if you require every term in your results, as this can provide precise searching. The raw option is for custom searches, like you might require one term but also want to disallow another from the result. Also, adding optional terms always affects relevancy/order.
Status Each bug has a status, this allows searching for a specific (or all) status type. Here are a few explanations:
  • Open : This also includes assigned, analyzed, critical, and verified bugs. (default)
  • Feedback : Bugs requesting feedback. Typically a bug that requests feedback will be marked as No Feedback if no feedback transpires after 15 days.
  • Old feedback : Bugs that have been requesting feedback for over 60 days.
  • Fresh : Bugs commented on in the last 30 days that are not closed, duplicates, or bogus. Only developers and the original author can affect this date as public comments do not.
  • Stale : Bugs last commented on at least 30 days ago that are not closed, duplicates, or bogus. Only developers and the original author can affect this date as public comments do not count.
  • All : All types, even bogus.
If you're only interested in critical bugs, or want to see which have been verified, or perhaps just those seeking feedback.
Category Bugs are categorized although sometimes it might seem like a bug could be in multiple categories. You may choose a specific category or allow any, and also disallow certain categories. If you're unable to locate a bug, consider trying a any status.
HTTPD Server Bugs that may be specific to an operating server. This value is entered in by the reporter as the HTTPD Server they used while finding the bug so this may or may not have meaning. Although not an accurate field, it may be of some use.
PHP Version Limit bugs to a specific version of PHP. Defaults to all. Limit returned bugs to a specific version of PHP. This is fairly reliable as initial version entries are standardized, but on occasion people are known to enter in bogus version information.
Assigned Some bugs get assigned to developers, in which case you may specify by entering in the username of said developer. Example use is limiting the bugs assigned to yourself.
Date Limit bugs that were reported by a specific time period. This is not only the amount of time since a comment or developer remark was last made, but this is the time when the bug was originally reported. Looking for recently reported bugs. For example, choosing 30 days ago will limit the search to all bugs reported in the last 30 days.

Bug System Statistics

You can view a variety of statistics about the bugs that have been reported on our statistics page.

User Info

Welcome Anonymous


Support for DragonflyCMS in a other languages: