Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mandatory field error displaying above the incorrect field. #18102

Open
jawood1 opened this issue Jan 23, 2025 · 1 comment
Open

Mandatory field error displaying above the incorrect field. #18102

jawood1 opened this issue Jan 23, 2025 · 1 comment
Labels

Comments

@jawood1
Copy link

jawood1 commented Jan 23, 2025

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.5.3

Bug summary

When at least two fields are set as mandatory and one field is left unpopulated on save and publish the incorrect fields are being highlighted as being invalid.

I'm not sure if this is just specific fields but so far I've managed to re-create this on textstring and repeatable textstrings and within nested blocklist/grid.

It doesn't seem 100% consistent when it does or does not occur.

Specifics

I've tested this on Firefox and Chrome and the same issue occurs.

Tested on a basic project with only Umbraco CMS installed.

Attached examples of the issue:

https://github.com/user-attachments/assets/31f41b5c-d282-41ed-bc8d-e71a9d465b8e
https://github.com/user-attachments/assets/508bb865-3274-41cb-82ad-a73126ec791e

Steps to reproduce

  • Create a page with at-least two mandatory fields
  • Leave one field unpopulated
  • Save and publish
  • Fields with correct values display errors and field with error either displays error as well or not at all.

Expected result / actual result

Validation should display above correct fields

Copy link

Hi there @jawood1!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant