When entering a date value in textstring it gets parsed as a real date with time

[seanhakbb]

Which Umbraco version are you using?

15.4.1

Bug summary

When entering a date value in textstring it gets parsed as a real date with time

Specifics

No response

Steps to reproduce

Create/use a normal field of datatype textstring inside a block list (havent tested if this is for scenarios outside block list but possibly)

Enter date formatted like this: 2025-03-28
Publish page, go back to the block list item where u entered. the data should now say:
3/28/2025 12:00:00 AM +01:00 (the rendered value of Umbraco is also this in the template - so not just a render bug)

Expected result / actual result

Textstring field type should display and save content "as is", without any transformations

[github-actions]

Hi there @seanhakbb!

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 🤖 🙂

[AndyButland]

I can reproduce this and see where it's happening, but not sure there's an easy solution.

In JsonObjectConverter we have code to detect if the incoming string can be parsed into an integer, date etc., and if so, to handle it as that type (see the switch statement in ParseObject). At this point we only have the value to work with, and we can't simply remove this, as of course if we do have a numeric or date property editor we do want this parsing to occur.