v16.2.0 Toggle Preset value not working

[TRexStark]

Which Umbraco version are you using?

16.2.0

Bug summary

The 'Preset value' option in the Toggle property doesn't seem to do anything. Is it supposed to check the toggle by default? if it is, then it's not working.

Specifics

No response

Steps to reproduce

Create a toggle property and activate the "Preset value' option in the property configuration, add the property to a node.

Expected result / actual result

I believe the toggle should be checked/on by default?

[github-actions]

Hi there @TRexStark!

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]

From my testing of this I can see that it does work when used to create new content, but not if you add it to a document type and go to an already existing document that uses the document type.

This is expected based on the work done for presets in the PR #18423 linked to #17212, but I'll take it for discussion as to whether it should/could work in this instance too.

[nielslyngsoe]

Hi @TRexStark, a completely fair assumption — this perception is actually the reason why this 'feature' has been renamed to Preset compared to 'Initial State' as of v.13.

The experience is data-wise identical with V.13, with a noticeable difference that I will get into.

In v.13, when adding a new property with a data set to have an initial state, this value was neither persisted or outputtet.

When visiting the Document it would look like it as set to be True:

But when visiting the page it would not be True.

Meaning in v.13 you got the experience as if it was set to True, but in reality, it would not until you saved & published the Document.

This is why we renamed the feature to 'Preset', hoping to clarify that it is the preset value, but it's not a 'default' or 'fallback' value as some might expect.

This also makes sense from a technical perspective, let me explain my perspective:
In a static site setup or some heavy cached setup — you would need such a new Property to be outputtet as 'true', meaning all pages with this property would have to be re-published in order for this to be captured.
In general, we do not want to manipulate data or re-publishing documents, explaining why we would not like to make this partically use case work.

I hope it makes sense, and therefor I will close this issue. That does though not mean closing the conversation, please share you thoughts on the matter I would love to hear how you see this case in the light of this information.

Thanks in advance

[TRexStark]

Thanks @AndyButland and @nielslyngsoe
I understand the reasoning behind it. I initially thought that it doesn't make sense, bcause I will still need to go to the node and edit and/or publish to see the end result, but thinking from a UX perspective, it makes sense if the toggle is used in a composition that is called from multiple nodes as example.

Thank you for the clarification.