Slider is broken when range is disabled

[arknu]

Which Umbraco version are you using?

17.0.2

Bug summary

The slider is broken when range is not enabled. You get an error that a value has been set, but that a range was not expected:

I initially assumed the built-in property value preset was at fault, but the issue seems to lie deeper than that.

Specifics

No response

Steps to reproduce

Create a slider data type. Range should not be enabled. It should have an initial value set.

Use this data type on a content type and create some content using this type.

You are unable to publish until you manually change the value.

Expected result / actual result

No response

[github-actions]

Hi there @arknu!

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 think this is the same issue as reported in #20771 and fixed via #20772 for 17.1. As such I'll close this as a duplicate.

Of course if you still find problems once you have tried the 17.1 release candidate, please feel free to re-open.

[arknu]

@AndyButland Yeah, sorry, just noticed that as well... Definitely the same issue.