Welcome to the Cookbook

There is no translation yet for this section. Please help out and translate this.. More information about translations

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

There is no translation yet for this section. Please help out and translate this.. More information about translations

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.

There is no translation yet for this section. Please help out and translate this.. More information about translations

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.

View Current Tickets

Report a bug