ZF-7135: null values are treated as missing data instead of an empty value

Issue Type: Bug Created: 2009-06-26T11:01:08.000+0000 Last Updated: 2009-08-22T14:07:52.000+0000 Status: Resolved Fix version(s): - 1.9.2 (25/Aug/09)

Reporter: Jordan Ryan Moore (jordanryanmoore) Assignee: Thomas Weidner (thomas) Tags: - Zend_Filter_Input

Related issues: Attachments:


A couple of BC breaks occurred in the latest releases of Zend Framework (1.8.3/1.8.4) to Zend_Filter_Input. Specifically, the way "allowEmpty" and empty fields are being handled. Part of it is that isset() is being used on line 830 of Zend/Filter/Input.php, so null data values are considered missing, even though the key exists in the array. The usage of isset() should be changed to array_key_exists() on that line. This is a huge BC break as it now requires me to mark the presence of fields optional where I only previously had to allow them to be empty.


Posted by Thomas Weidner (thomas) on 2009-08-22T14:07:51.000+0000

Fixed with r17757

Have you found an issue?

See the Overview section for more details.


© 2006-2018 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.