Can you please provide more info so we can investigate such as your repo url and the uid of the page that you are testing with.
Thank you.
Hi @Phil ,
You can easily reproduce it:
- Create a non-repeatable group with any field in it. Push changes from slicemachine.
- Edit the field.
- Click the (+) button on the that non-repeatable field.
I think it's an UI bug. Since it create a new item to array, but the UI only can show 1 item so it shows the last created item.
With auto-saving feature, there no way to get the old content.
https://renew.prismic.io/ - Custom type document: "Section1" - Slice name "SectionIntro" - Field name: Texts.
Hi Cody,
Thanks for the detailed reproduction steps. I was able to confirm the behavior you described.
This does look like a UI bug: the + button should not be available on a non-repeatable group field. When clicked, it appears to create an additional item in the group array, while the editor only displays one item. Because autosave then saves that new state, it can look like the previous content has been overwritten.
I’ve escalated this to our Product/Engineering team with the reproduction details and the affected examples:
| Custom type / slice | Field | Behavior |
|---|---|---|
| Section1 → SectionIntro | Texts | Clicking + on the non-repeatable group can replace the visible content |
| Section4Block2 | image | Same behavior, even though the model appears to have repeat: false |
For now, please avoid clicking the + button on non-repeatable group fields. If content has already been lost, the best recovery option is to check the document’s version history in the Prismic dashboard, if versioning is available for that document.
We’ll update this thread once we have more information from the team.