[Tickets #14130] Re: monthdayyear form element not saved in DB
noreply at bugs.horde.org
noreply at bugs.horde.org
Thu Jan 14 13:54:26 UTC 2016
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: https://bugs.horde.org/ticket/14130
------------------------------------------------------------------------------
Ticket | 14130
Updated By | Git Commit <commits at lists.horde.org>
Summary | monthdayyear form element not saved in DB
Queue | Horde Framework Packages
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch | 1
Owners |
------------------------------------------------------------------------------
Git Commit <commits at lists.horde.org> (2016-01-14 13:54) wrote:
Changes have been made in Git (master):
commit 9f65a05d470ee9e2ca797ce26f09acb4dcef9b5c
Author: Jan Schneider <jan at horde.org>
Date: Thu Jan 14 14:51:08 2016 +0100
Loosen the the test for the date format (Bug #14130).
Theoretically it might have been intended to explicitly pass an
empty string (as opposed to a null value) as the date format. But this
doesn't make sense because that would generate a form field that never
has a result value. Beside that we already *do* catch an empty value,
even if it's a strict null check.
framework/Form/lib/Horde/Form/Type.php | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
http://github.com/horde/horde/commit/9f65a05d470ee9e2ca797ce26f09acb4dcef9b5c
More information about the bugs
mailing list