ZF Blog

Zend Framework 2.1.3 Released!

The Zend Framework community is pleased to announce the immediate availability of Zend Framework 2.1.3! Packages and installation instructions are available at:

This release has been pushed out quickly on the heels of 2.1.2 to fix an issue with autoloading PHP version-specific class implementations that was affecting PHP 5.3.3 users. Two other potential regressions were also addressed.

PHP 5.3.3 Users

This release finally resolves issues with providing PHP version-specific classes, specifically for PHP 5.3.3 users.

If you are using Composer to manager your dependencies, a composer.phar update should resolve any issues.

If you are not, you have two options.

First, when starting new applications with the ZendSkeletonApplication, class substitution will now happen by default.

Otherwise, add the following lines to your init_autoloader.php file, as indicated by the comments below:

// The following line should be on or around line 34:
if ($zf2Path) {
    if (isset(
$loader)) {
    } else {
$zf2Path '/Zend/Loader/AutoloaderFactory.php';
'Zend\Loader\StandardAutoloader' => array(
'autoregister_zf' => true

// Add the following two lines:
require $zf2Path '/Zend/Stdlib/compatibility/autoload.php';
$zf2Path '/Zend/Session/compatibility/autoload.php';

Routing Fixes

Two fixes to routing were made after discovering potential regressions.

The first was to hostname routing. Changes were introduced in 2.1.2 to make matching optional nested subdomains possible; unfortunately, this broke cases where the primary domain was specified. A fix has been included in 2.1.3 that fixes the regression (while simultaneously allowing the new behavior).

A bug in console routing was also uncovered; camelCased or MixedCase options were allowed in route definitions, but route matching was normalizing options to lowercase, causing false negative matches. This was fixed for 2.1.3.


Below are links to the issues addressed.

Thank You!

I'd like to thank those that tested the PHP 5.3.3 autoloading fixes, as well as Nick Calugar for providing the fix to hostname routing and Michael Gallego for the fixes to console routing.


Maintenance releases happen monthly on the third Wednesday; expect version 2.1.4 to drop 20 March 2013. We're also gearing up for version 2.2.0, which we are targetting at the end of April 2013.

Return to entries

blog comments powered by Disqus