| Summary | Certain custom attributes fail to save and render correctly |
| Queue | Whups |
| Queue Version | Git master |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | jan (at) horde (dot) org |
| Requester | bklang (at) horde (dot) org |
| Created | 04/20/2011 (5189 days ago) |
| Due | |
| Updated | 10/18/2011 (5008 days ago) |
| Assigned | |
| Resolved | 10/18/2011 (5008 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
[jan] Support more complex attributes types (
Bug #9947).10 files changed, 115 insertions(+), 40 deletions(-)
http://git.horde.org/horde-git/-/commit/33f0d5bdb9a12208977cd6b5f54ab99521aebaeb
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Whups
Summary ⇒ Certain custom attributes fail to save and render correctly
Type ⇒ Bug
State ⇒ Unconfirmed
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