[dev] horde_form / read-only fields

[Chuck Hagenbuch]

Quoting Marko Djukic <marko at oblo.com>:

> if a field is marked as required, but then during some logic is switched
> over to 'read-only' when being set up (ie. same form code being used in a 
> few situations)... it remains required, will generate unseen "is required"
> messages and fail to submit.
> 
> should a read-only, required field be passed along as hidden, or in
> should this be handled behind the sense, or something completely 
> different?

I'm not sure how we're supposed to answer the question without seeing the
code in question, but it sounds like you should be doing the logic *before*
creating the field.

-chuck

--
Charles Hagenbuch, <chuck at horde.org>
must ... find ... acorns ... *thud*