[Tickets #9947] Certain custom attributes fail to save and render correctly
bugs at horde.org
bugs at horde.org
Wed Apr 20 18:07:46 UTC 2011
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/9947
------------------------------------------------------------------------------
Ticket | 9947
Created By | Ben Klang <bklang at horde.org>
Summary | Certain custom attributes fail to save and render
| correctly
Queue | Whups
Version | Git master
Type | Bug
State | Unconfirmed
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
Ben Klang <bklang at horde.org> (2011-04-20 18:07) wrote:
When defining custom attributes (specifically, the different enum
forms) the posted attribute data doesn't work as expected:
These issues were observed when using an attribute with the type of
"Drop down list"
* When saving the first attribute in the list, it has a value of 0,
which seems to get interpreted as "no value." Choosing the second,
third or fourth (etc) value makes the correct association.
* The ticket change history says: "Lead Source ? 0" or "Lead Source ?
1". This should be the normalized name
More information about the bugs
mailing list