Login / Status
developer.Resource
Home . Development . Bug Fixing . Bug hunting
Sponsors
hosted by punkt.deTYPO3 and Open Source Magazine

Reporting

When creating a bug report, there are a few rules to follow that will improve the chances of the issue being fixed:

Bug hunting

When you think you've found a bug, the first thing to do is to make sure it really is so. You should test if the bug is reproducible and check whether it could be due to invalid settings rather than really a defect in the original code (either the TYPO3 Core or an extension). If you are using an old version of TYPO3 or of an extension, you should try updating to the latest version and check if the bug still happens.

It is also worth checking the TYPO3 bug trackers to see if someone already reported the bug. This is not always easy as people may have worded the bug in a different way that you would. It is quite possible to miss an existing bug report, but it's still worth searching for it.
Bug trackers:
TYPO3 v4: http://forge.typo3.org/projects/typo3v4-core/issues
TYPO3 v5: http://forge.typo3.org/projects/typo3-v5/issues

As a last step before actually opening a bug report you may also want to ask in the general mailing list (typo3.english on lists.typo3.org) if anyone has encountered the same bug. Maybe someone already has a solution or can at least point you in the right direction.

All these steps may not be necessary all the time, but they represent recommended practices. Once you have ensured that you are onto a true bug, open a bug report in the relevant bug tracker.

Issue trackers on forge.typo3.org

The following TYPO3 Core Projects now have their own issue tracker on Forge. Please post your bug reports and feature requests there:

These general topics have issue trackers on Forge as well: