Tickets :: Comment on [#11124] decode_attribute hook an exceptions

Search Results: 4 of 27 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: .___..__.. .. .. . \| \| \|\| \|\|\ \|\|__\| \| \|__\|\|/\\|\| \\|\| \|
Comment	> >> I can imagine a field that requires different inputs from the user, >> i.e. different attributes, but the result should be rendered in a >> single composite field, after passed through the decode hook. >> > Just for completeness, can you be a bit more specific, i don't understand, > why the composite field is essential here. > > For now i have no new arguments/ideas. Returning an array is ok. > > Btw. i havn't had a closer look at the opposite side (setValue/encode), > composite fields seem to be a special case here too (not editable in > the contact form)
Attachment
Watch this ticket