Some days ago I've created some slices and they were saved for 10000000%. Today I am opening Prismic and I don't see them anymore.
Furthermore, some properties were also gone on other slices (which were added even earlier).
Any idea what has happened? How do I recover my latest slices... very much looks like a bug.
Welcome to the Prismic community.
I will try to investigate this with you, to do so can you please share with me (in a private message if necessary) your repository name.
Also, it would be great if you can give me some links/ information about the suspected slices.
Looking forward to your reply,
I've shared details in priv, but for the transparency sake I will post also an update on my findings in case if someone is looking for what caused this issue:
The issue occurred when one person changes slices and another has prismic UI open as well, but he/she does not refresh the page before applying changes to the slices. Even if the 1st person added stuff, and pressed save - slices are overwritten to the last known state of the 2nd person.
Prismic does not inform about the newer versions of the file being available, to re-consider save it just blindly trashes them. this required re-adding of all the properties between the saves of the two people...
Hi Damian, thanks for sharing your use case.
There are two ways to create and edit slices:
The first is from the Prismic UI; from here, you can create individual slices for each Custom Type. It is only possible to edit these slices from the repository UI.
The second option is from Slice Machine. From here, you can create slices that you can later reuse among all your Custom Types. The changes sync from Slice Machine to the repository.
We are interested in knowing exactly what elements were being edited when the changes were deleted. Could you help us describe the workflow you carried out to find this error step by step?
These steps can help us reproduce the error from our side.
We close the threads after a week with no new activity. If this happens and you want to continue the conversation, you can easily flag it to reopen it and add a new comment.
Threads close after a period of inactivity. Flag this thread to re-open it and continue the conversation.
So in this workflow 2 people are using Prismic UI to manage slices. When one person does the changes and another one is working in parallel they will be overwriting each-other changes without even knowing about it. There should be a way to inform the person applying the changes that someone already made changes and he/she is not using the latest version of the json, or Prismic should be able to merge changes from the two people editing it.
Thanks for the additional information. Since this is not currently possible, I am going to mark your post as a feature request so I can take it into account for future implementations.
We are sorry for the inconvenience.
To be honest this should be viewed more as a bug rather than a feature request
That is understandable.
Thanks for your feedback.
This is being tracked as an open feature request.
If you have another use-case for this feature, you can 'Flag' this topic to reopen. Please use the button to show your support for the feature and check out our Feature Request Guidelines.