Make the "Event Save Error" More Clear to the User on What is Missing
The most common issue I deal with when people are trying to input and save events is that they get the "event save error" and cannot for the life of them figure out what is missing. 99.9999% of the time, the issue is that a custom attribute answer is missing. I know the page jumps to that section to try to show them, but all they see is the tiny text at the bottom of the section that states "Please enter a value for required custom attributes". People always think it refers to the very last question in that section, which isn't even required on our form.
My suggestion is to put a big red box around the question(s) that is missing, just like for the acknowledgement, so that users can easily see what they need to complete in order to move forward. Or have some sort of indicator that points to the exact question(s) that are missing.
Comments: 4
-
05 Jan, '23
Pamela MasonWe have the same problem. I think there are two reasons for this. The "Required" text next to the field is not red which is how every other web for I have ever used works. People are used to that and if they don't see it they assume the field is optional without reading. Hence my request https://25live.featureupvote.com/suggestions/175251/text-indicating-a-field-is-required-should-be-red.
The other is when people edit an existing event and don't look through the event form. This feature request would differently help catch both. Although perhaps just separating the errors message out into a popup so it is not on the same screen and then making sure that whatever is required is indicated in read would be best. If not at least putting the error message in a header that is at the top of the page would be better to. -
13 Jan, '23
MeganOh my gosh, yes please do this!
-
24 Jan, '23
Tammy MillerYes, please!
-
05 Jun, '23
Julie HoyenskiAgreed. Our end users won't have patience with this. I'm testing a new form and have trouble spotting the field/s I missed - even though I built the form myself. An incomplete Yes/No toggle is especially hard to spot. There's not much visual difference from a completed "No" toggle. At least when toggled to Yes the button and slide bar turn blue.
Highlighting incomplete attributes would be ideal.