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 Data Picker field value can't be selected after validation error. #439

Open
1 task done
jawood1 opened this issue Dec 16, 2024 · 2 comments
Open
1 task done

Comments

@jawood1
Copy link

jawood1 commented Dec 16, 2024

Which Contentment version are you using?

4.7.0

Which Umbraco version are you using? For example: 13.2.1 - don't just write v13

13.5.2

Bug summary

When setting a datapicker field as mandatory and not applying a value to the field after save and publish you are unable to select a value to clear the validation error without reloading the page.

When looking at the console after save and publish the first log appears and then after attempting to click select to choose a value the 'n.model.value.push' errors occur.

image

Please see the attached video example showing the issue:

AwesomeScreenshot-06_01_2025.09_13_43.webm

Steps to reproduce

  1. Create a data picker field in this example with display mode being list
  2. Set the field as mandatory
  3. Attempt to save and publish without inputting a value
  4. Validation error fires
  5. Attempt to apply a value to the field
  6. You are unable to select a value from the list

Expected result / actual result

You should be able to select a value after a validation error has occurred in-order to save and publish.

Do you have Umbraco ModelsBuilder enabled?

  • Yes, it is enabled.

What browsers are you seeing the problem on?

Chrome, Edge, Firefox, Safari

@leekelleher
Copy link
Owner

@jawood1 Thanks for reporting this. It sounds remarkably similar to the issue raised in #315, (but that one is about the Content Blocks editor).

My gut feel is that this isn't Data Picker specific, more of a general Umbraco property-editor concern. But last time I investigated this scenario, I wasn't able to pinpoint what was causing the bug.

@jawood1
Copy link
Author

jawood1 commented Jan 17, 2025

Hi @leekelleher thanks for the response! yeah that seems like the same issue, I did have a stab at it myself but Angular isn't my strongest point!

It's not a huge issue as you can work around it by refreshing the page just not ideal!

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

No branches or pull requests

2 participants