Zend Framework 1.9
When upgrading from a previous release to Zend Framework 1.9 or higher you
should note the following migration notes.
Zend_Filter
Prior to the 1.9 release, Zend_Filter allowed
the usage of the static get() method. As with
release 1.9 this method has been renamed to
filterStatic() to be more descriptive. The
old get() method is marked as deprecated.
Zend_Http_Client
Changes to internal uploaded file information storage
In version 1.9 of Zend Framework, there has been a change in the way
Zend_Http_Client internally stores information about
files to be uploaded, set using the Zend_Http_Client::setFileUpload()
method.
This change was introduced in order to allow multiple files to be uploaded
with the same form name, as an array of files. More information about this issue
can be found in this bug report.
Internal storage of uploaded file information
setFileUpload('file1.txt',
'userfile[]',
'some raw data',
'text/plain');
$client->setFileUpload('file2.txt',
'userfile[]',
'some other data',
'application/octet-stream');
// In Zend Framework 1.8 or older, the value of
// the protected member $client->files is:
// $client->files = array(
// 'userfile[]' => array('file2.txt',
'application/octet-stream',
'some other data')
// );
// In Zend Framework 1.9 or newer, the value of $client->files is:
// $client->files = array(
// array(
// 'formname' => 'userfile[]',
// 'filename' => 'file1.txt,
// 'ctype' => 'text/plain',
// 'data' => 'some raw data'
// ),
// array(
// 'formname' => 'userfile[]',
// 'filename' => 'file2.txt',
// 'formname' => 'application/octet-stream',
// 'formname' => 'some other data'
// )
// );
]]>
As you can see, this change permits the usage of the same form element name with
more than one file - however, it introduces a subtle backwards-compatibility change
and as such should be noted.
Deprecation of Zend_Http_Client::_getParametersRecursive()
Starting from version 1.9, the protected method _getParametersRecursive()
is no longer used by Zend_Http_Client and is deprecated.
Using it will cause an E_NOTICE message to be emitted by PHP.
If you subclass Zend_Http_Client and call this method, you
should look into using the Zend_Http_Client::_flattenParametersArray()
static method instead.
Again, since this _getParametersRecursive is a protected method,
this change will only affect users who subclass Zend_Http_Client.
Zend_Locale
Depreciated methods
Some specialized translation methods have been depreciated because they duplicate
existing behaviour. Note that the old methods will still work, but a user notice is
triggered which describes the new call. The methods will be erased with 2.0.
See the following list for old and new method call.
List of measurement types
Old call
New call
getLanguageTranslationList($locale)
getTranslationList('language', $locale)
getScriptTranslationList($locale)
getTranslationList('script', $locale)
getCountryTranslationList($locale)
getTranslationList('territory', $locale, 2)
getTerritoryTranslationList($locale)
getTranslationList('territory', $locale, 1)
getLanguageTranslation($value, $locale)
getTranslation($value, 'language', $locale)
getScriptTranslation($value, $locale)
getTranslation($value, 'script', $locale)
getCountryTranslation($value, $locale)
getTranslation($value, 'country', $locale)
getTerritoryTranslation($value, $locale)
getTranslation($value, 'territory', $locale)
Zend_View_Helper_Navigation
Prior to the 1.9 release, the menu helper
(Zend_View_Helper_Navigation_Menu) did not
render sub menus correctly. When the onlyActiveBranch
was TRUE and the option renderParents
FALSE, nothing would be rendered if the deepest active
page was at a depth lower than the minDepth option.
In simpler words; if minDepth was set to 1
and the active page was at one of the first level pages, nothing
would be rendered, as the following example shows.
Consider the following container setup:
'Home',
'uri' => '#'
),
array(
'label' => 'Products',
'uri' => '#',
'active' => true,
'pages' => array(
array(
'label' => 'Server',
'uri' => '#'
),
array(
'label' => 'Studio',
'uri' => '#'
)
)
),
array(
'label' => 'Solutions',
'uri' => '#'
)
));
]]>
The following code is used in a view script:
navigation()->menu()->renderMenu($container, array(
'minDepth' => 1,
'onlyActiveBranch' => true,
'renderParents' => false
)); ?>
]]>
Before release 1.9, the code snippet above would output nothing.
Since release 1.9, the _renderDeepestMenu() method in
Zend_View_Helper_Navigation_Menu will accept
active pages at one level below minDepth, as long as
the page has children.
The same code snippet will now output the following:
Server
Studio
]]>