-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Open
Labels
area/frontendstate/reproducedstate/sprint-candidateWe're trying to get this in a sprint at HQ in the next few weeksWe're trying to get this in a sprint at HQ in the next few weekstype/bug
Description
Which Umbraco version are you using?
16.0.0
Bug summary
When using a document type that contains compositions, the fields inside said compositions if they have preset/default values, dont have said values saved into the CMS when saving/publishing the content
Specifics
No response
Steps to reproduce
Fresh install of Umbraco 16
Create:
- Toggle type with preset value as true/enabled
- Slider type with min value 0, max value 1, step value 0.1 and starting/preset value 0.5
Create a composition with fields contain one of each data type (add them to a "Composition" tab):
- Default toggle data type
- Custom created toggle with default true
- Custom created slider
Now create a document type that is allowed to be created as a root node and:
- Add the composition to it
- Re-create the same exact fields as the composition, but on the document type itself, in a separately named tab for ease of distinction
Create the document type and save it without touching any of the inputs/fields
Expected result / actual result
Expected result:
- Both the composition and the direct fields should take their preset values
Actual results:
- Direct fields take preset values correctly
- Composition fields don't take preset values and are then null in their respective published content access (Delivery api, etc)
This item has been added to our backlog AB#54968
Metadata
Metadata
Assignees
Labels
area/frontendstate/reproducedstate/sprint-candidateWe're trying to get this in a sprint at HQ in the next few weeksWe're trying to get this in a sprint at HQ in the next few weekstype/bug