[rt-users] CustomField input must match formatting in edit

[Kevin Falcone]

On Mon, Feb 06, 2012 at 04:54:51PM -0700, Brent Wiese wrote:
> Sorry, wasn't sure if a screenshot would come through on the list.

The layout of that field could use some loving, it has a CSS class
these days so it should be much easier to do things to it:
cfinvalidfield

> Maybe a different topic, but while debugging the formatting above, I 
> noticed if I use a * in a custom field validation (ie: I want to allow 
> the field to contain only digits or be empty, so I modified the regex 
> from ^[\d.]+$ to ^[\d.]*$), the validation works, but it doesn’t 
> display the “Input must match…” text at all.

RT decides whether or not display the hint by validating all the CFs
at page render time.  This means that since * matches the empty field,
it doesn't have an error hint to show.

Frankly - it'd probably be a lot better if we just started showing the
Description of Custom Fields as a Hint box on 4.2.

-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20120207/40f4acfb/attachment.sig>