2.2 Migration Guide
CakePHP 2.2 is a fully API compatible upgrade from 2.0/2.1. This page outlines the
changes and improvements made for 2.2.
Required steps to upgrade
When upgrading to CakePHP 2.2 its important to add a few new configuration
app/Config/bootstrap.php. Adding these will ensure consistent
behavior with 2.1.x:
// Enable the Dispatcher filters for plugin assets, and
// Add logging configuration.
'engine' => 'FileLog',
'types' => array('notice', 'info', 'debug'),
'file' => 'debug',
'engine' => 'FileLog',
'types' => array('warning', 'error', 'critical', 'alert', 'emergency'),
'file' => 'error',
You will also need to modify
app/Config/core.php. Change the value of
primary model validation fails, the validation errors of associated models are no longer wiped out.
Model::$validationErrors will now always show all the errors.
You might need to update your test cases to reflect this change.
Model::find('count') will now call the custom find methods with
$state = 'before' and
$queryData['operation'] = 'count'.
In many cases custom finds already return correct counts for pagination,
'operation' key allows more flexibility to build other queries,
or drop joins which are required for the custom finder itself.
As the pagination of custom find methods never worked quite well it required
workarounds for this in the model level, which are now no longer needed.
Model::find('first') will now return an empty array when no records are found.
- Dbo datasources now supports real nested transactions. If you need to use this
feature in your application, enable it using
ConnectionManager::getDataSource('default')->useNestedTransactions = true;
- The webrunner now includes links to re-run a test with debug output.
- Generated test cases for Controller now subclass
- When repeat exceptions, or exception are raised when rendering error pages,
error layout will be used. It’s recommended to not use additional
helpers in this layout as its intended for development level errors only. This
fixes issues with fatal errors in rendering error pages due to helper usage in
- It is important to copy the
app/View/Layouts/error.ctp into your app
directory. Failing to do so will make error page rendering fail.
- You can now configure application specific console error handling. By setting
Exception.consoleHandler you can define the
callback that will handle errors/exceptions raised in console applications.
- The handler configured in
receive fatal error codes (ie.
Configure::dump() was added. It is used to persist configuration
data in durable storage like files. Both
IniReader work with it.
- A new config parameter ‘Config.timezone’ is available in which you can set
users’ timezone string. eg. You can do
'Europe/Paris'). If a method of
CakeTime class is called with
$timezone parameter as null and ‘Config.timezone’ is set, then the value
of ‘Config.timezone’ will be used. This feature allows you to set users’
timezone just once instead of passing it each time in function calls.
- The options for adapters defined in
now accepts a
contain option. This is used to set containable options for
when user records are loaded.
- Legacy Japanese encodings are now handled correctly.
ISO-2202-JP is used
when the encoding is
ISO-2202-JP-MS which works around a number of issues
in mail clients when dealing with the CP932 and Shift_JIS encodings.
CakeEmail::theme() was added.
CakeEmail::domain() was added. You can use this method to set the
domain name used when sending email from a CLI script or if you want to
control the hostname used to send email.
- You can now define
helpers in your EmailConfig class.
- CakeRequest will now automatically decode
application/x-www-form-urlencoded request bodies on
requests. This data will be available as
$this->data just like POST data
Set class is now deprecated, and replaced by the
Set will not be removed until 3.0.
Set::expand() was added.
Hash class was added in 2.2. It replaced Set providing a more
consistent, reliable and performant API to doing many of the same tasks Set
does. See the Hash page for more detail.
$userOffset parameter has been replaced with
in all relevant functions. So instead of numeric offset you can now pass in a
timezone string or DateTimeZone object. Passing numeric offsets for
$timezone parameter is still possible for backwards compatibility.
CakeTime::timeAgoInWords() had the
accuracy option added.
This option allows you to specify how accurate formatted times should be.
- New methods added:
$dateString parameter in all methods now accepts a DateTime object.
- FormHelper now better handles adding required classes to inputs. It now
FormHelper::radio() now supports an
empty which works similar
to the empty option on
FormHelper::inputDefaults() to set common properties for
each of the inputs generated by the helper
- Since 2.1, TimeHelper uses the CakeTime class for all its relevant methods.
$userOffset parameter has been replaced with
TimeHelper::timeAgoInWords() has the
element option added.
This allows you to specify an HTML element to wrap the formatted time.
- Event listeners can now be attached to the dispatcher calls, those will have
the ability to change the request information or the response before it is
sent to the client. Check the full documentation for this new features in
- With the addition of Dispatcher Filters you’ll need to
Required steps to upgrade.
Router::setExtensions() has been added. With the new method you can
now add more extensions to be parsed, for example within a plugin routes file.
A new caching engine was added using the phpredis extension it is configured similarly to the
It is now possible to tag or label cache keys under groups. This makes it
simpler to mass-delete cache entries associated to the same label. Groups are
declared at configuration time when creating the cache engine:
'engine' => 'Redis',
'groups' => array('post', 'comment', 'user')
You can have as many groups as you like, but keep in mind they cannot be
Cache::clearGroup() class method was added. It takes the group
name and deletes all entries labeled with the same string.
CakeLog now require, some additional configuration in
app/Config/bootstrap.php. See Required steps to upgrade,
CakeLog class now accepts the same log levels as defined in
RFC 5424. Several convenience
methods have also been added:
CakeLog::emergency($message, $scope = array())
CakeLog::alert($message, $scope = array())
CakeLog::critical($message, $scope = array())
CakeLog::error($message, $scope = array())
CakeLog::warning($message, $scope = array())
CakeLog::notice($message, $scope = array())
CakeLog::info($message, $scope = array())
CakeLog::debug($message, $scope = array())
- A third argument
$scope has been added to
See Logging Scopes.
- A new log engine:
ConsoleLog has been added.
- A new object
ModelValidator was added to delegate the work of validating
model data, it should be transparent to the application and fully backwards
compatible. It also exposes a rich API to add, modify and remove validation
rules. Check docs for this object in Data Validation.
- Custom validation functions in your models need to have “public” visibility
so that they are accessible by
- New validation rules added: