Tickets
The following is a list of shortcuts which point to custom queries on the CakePHP Lighthouse (ticket tracking) site. These queries help break down the mass of tickets into smaller groups, categorized by subject matter. These links point only to tickets which are currently open, sorted from oldest to newest.
"Tiny URLs" for the queries are provided (in addition to the direct URLs) as a convenience for copying and pasting into the various communication channels used by the community.
# Enhancement Freeze
- Please be advised that all enhancement tickets for created 1.3 are being pushed to 2.0.
- Please note that enhancement tickets are no longer accepted for 1.1, 1.2 or 1.3 as they are stable releases.
# How to help close existing tickets
The best way to help out is by creating tests and patches, which can be submitted as tickets via Lighthouse. This will ease the burden on the core development team. Refer to the Testing section within the Cookbook which covers how to install SimpleTest and how to create test cases. It's important that your tests be verified on the latest version of CakePHP, available via GitHub.
If you feel more comfortable/skilled/knowledgeable in a certain category listed below, bookmark the link and browse the tickets within that category. It is possible to submit test cases and patches for other people's tickets once you have registered on the Lighthouse site — it could help bring resolution to an outstanding bug or highly sought after enhancement.
# Bugreport
You must be registered on lighthouse to be able to submit a ticket. Register here.
# Before you submit a ticket
- Ask someone in the irc channel for help confirming it is a bug and not a simple error/misunderstanding.
- Search the google group archives to see if someone has already solved your problem.
- Send an email (post a message) to the google group to see if anyone else has seen the issue.
- Check the current tickets to see if your bug has already been reported.
- Look at the Timeline to see if the problem you experienced has already been fixed.
- Verify your version of CakePHP. If you are not using the latest code (http://code.cakephp.org/source) try updating to the newest stable or obtaining the HEAD of the relevant git branch see if your problem is already fixed.
# How to report a bug
There are a small number of people who actually develop CakePHP. In between documenting, planning, answering questions, developing features for new releases and sometimes pretending that they have lives outside of CakePHP, bugs tend to be last on a very long to-do list for them. To catch the eye of one of these few volunteers, you'll need to take to heart a few tips on how to report a bug so that they can and will help you.
Please note the word volunteer :). The people who are going to help you with a bug are volunteers. Not only are you not paying them to help you, but nobody else is either. So, be nice to them.
Beyond that golden rule, what follows are some additional tips on ways to make your bug report better so that someone will be able to help you.
# The basics: what you did, what you expected, and what actually happened
There are three basic parts of a bug report which can greatly reduce the amount of time spent finding the solution: You need to be specific in describing what you did, what you were expecting, and why it didn't meet your expectations. If you don't provide this information, then we have to guess and we all know that doesn't work too well. :)
- Report one problem in each bug report.
- If you have encountered two bugs that don't appear to be related, create a new bug report for each one. This makes it easier for different people to help with the different bugs.
- Please select the appropriate values for the ticket properties that match your problem. Pay special attention to the Component, Milestone and Version values.
- Valid test cases are a great help, patches are invited. Test cases and patches included together with a ticket are preferred.
# Trac links
The following is a list of shortcuts which point to custom queries on the CakePHP Trac (ticket tracking) site. These queries help break down the mass of tickets into smaller groups, categorized by subject matter. These links point only to tickets which are currently open, sorted from oldest to newest.
"Tiny URLs" for the queries are provided (in addition to the direct URLs) as a convenience for copying and pasting into the various communication channels used by the community.


























