Page 1 of 1
Required field caption not displaying with red asterisk
Posted: 2013-10-11 16:21
by artemisia
Using v5.12. I have two fields configured as not NULL, neither one shows the red asterisk in front of the field caption in the Detail View. One is a Text multiple-choice List Box, the other is Varchar radio button. I will get the error message when attempting to submit without values, but I don't see the expected field caption indicator like other fields. Workaround is to append "(required)" to the field caption.
Is this a known bug? Is there a way to fix it?
Thanks,
~Bob
Re: Required field caption not displaying with red asterisk
Posted: 2013-10-24 20:12
by artemisia
Followup to my first post: Does anyone know if this is actually a bug, or "as designed"? It would seem that the red mark should display on any field that's configured "not null", not just single-value fields. Field in mysql looks OK, and there are no other issues with these fields, display or operational. I found where the red asterisks seem to be coded - in *templateDV.html, using <%%TRANSLATION(*)%%>, but when I tried adding that code manually the page display was seriously malformatted.
any ideas?
~Bob
Re: Required field caption not displaying with red asterisk
Posted: 2013-11-09 22:19
by artemisia
Have confirmed that this is a bug in pre-5.2 versions, it's fixed in 5.2.
However, as noted in another post in this forum, it seems that if field is required and there is a dropdown, instead of seeing an empty field to prompt user, it will fill with the first value in the list, which is very easy to overlook. This behavior will keep me from upgrading, hopefully will be fixed in next minor release.
Re: Required field caption not displaying with red asterisk
Posted: 2013-11-11 02:46
by a.gneady
artemisia wrote:if field is required and there is a dropdown, instead of seeing an empty field to prompt user, it will fill with the first value in the list, which is very easy to overlook. This behavior will keep me from upgrading, hopefully will be fixed in next minor release.
This is now fixed in 5.21