We’re rolling out a new Real-Time Collaboration (RTC) feature in Prismic, including auto save, and we’d love your feedback!
Let us know what’s working well, what’s confusing, and what could make RTC or auto save more helpful for your workflow. We’re especially interested in anything that would make collaboration smoother or more reliable for you.
For bugs or unexpected behavior, please contact support directly.
Feedback suggestion template:
What worked well? Share what you liked or found useful.
What could be improved? Tell us what was confusing or what would make the experience better.
Thanks for helping us shape the future of collaboration in Prismic!
Could you give us a bit more context about this? When are you seeing all those errors, do you know what they’re related to? When have you seen the Publish button being in a disabled state? Any details helps us troubleshoot this more efficiently
In the first 2 days of using this new feature, this case occurs when I am edited continuously for a short time and click the Publish button (this dialog box appears). Sometimes press Publish -> The button is disabled but it still holds a long time (may be due to the network or some other reasons).
To this day (October 4) perhaps the feature has been more stable, used quite smoothly and no longer has the above situation. I will update if there is a problem arising when using this feature.
Thanks for the details @thanhnamnguyen, could indeed be related to your network. Either way we want to know any stressors for the feature and how it feels to use day by day, so absolutely keep an eye out and update this thread if you see it coming back or run into more trouble In the meantime I’m happy to hear it’s been working better so far.
Is there any option to turn off this “amazing” feature completely and not have it at all? We received this “super feature” today, and now none of the content managers have any idea how to manage releases or how they work. The entire dev team is also confused about what this “mega feature” actually does — apart from creating chaos in our project and making it unusable.
The results of returned queries are random and have no logical sorting by lastPublicationDate. In the panel/admin, after saving, the “last modification date” doesn’t change and still shows the creation date. As a result, the entire flow built around lastPublicationDate and releases no longer works.
Additionally, there is no proper API change documentation — just about 10 lines at https://prismic.io/updates/collaboration — and that’s all. Yet, the changes in the API and data responses are breaking processes that have been working for the last five years (again).
Not sure if it’s intentional or not, but the ‘handle’ in my repo used to auto-populate when I entered the title. Now it doesn’t. As I say, could be intentional, could be not. I generally found that feature saved me time. Just letting you know.
Hey @jono.hey, indeed, we noticed this was no longer auto-populating. There's a feature request to bring it back here: https://prismic.atlassian.net/browse/BT-345, I'll link this thread to it so I can return and let you know when we have any updates on it
Hey there, it looks like that since the introduction of autosave, switching to a locale that has an empty page automatically creates a new page. This is not necessarily the intention when we switch languages, so I’m wondering if this is something that could be improved? Thank you!
Hey @petra, welcome to the community Thanks for raising this. Indeed, with the autosave feature, there's no such thing as an unsaved draft anymore. In order to address this properly, would you be able to elaborate a bit on what's your intention here when you switch locales from within a page? How is this impacting your workflow compared to the previous behavior of empty drafts? There may be something we're missing here in how we're going about this. Thanks!
Hey @Ezekiel thank you for your reply! In our team, we switch a lot between locales to compare and check translations and page set-ups, but each team member owns their own locale, so we don’t want to create pages in other locales that we don’t own. Before switching the locale, we can’t be sure that other language versions exist, so we’d create a lot of empty draft pages in the future.
Hey @petra, that makes sense! I've logged a feature request to see if we can do something about this and improve the experience for you. No promise on when or how it will be implemented, but the message has been passed on Thanks for taking the time to leave us this feedback.
Are there any plans to allow us to disable the auto-save feature?
I've been asked by multiple clients if they are able to disable it as they find it confusing and unintuitive.
I tend to agree with them, especially in certain situations such as if you want to check responsive sizes of images. If you click the "Crop & Resize" button to do this, and close without making any changes, the document will auto-save and now be in a draft state, forcing you to publish even though there are no changes.
There also doesn't seem to be a way to discard changes without re-publishing the document, as to "discard" changes you seemingly now need to restore an old version via the version history, but again this puts the document into a draft state, even if there are no changes compared to the live version.
We're also still experiencing issues around document caching, as content will appear/disappear at random, forcing us to constantly have hard-refresh the tab in hopes it appears. I've had content and entire documents completely disappear at some points and never return. I'm not sure if this is directly related to this feature or not, but it started happening around the same time.
There are no plans to disable the feature. Auto-save is a key part of enabling collaboration within Prismic i.e. without auto-saving there is no real-time collaboration. The team has been working hard to resolve the caching issues and this should be working correctly.
Please let me know if you are still having issues and the team can prioritise a fix.
Hi @connor, To confirm, there isn’t a way to disable real-time collaboration independently. Auto-save is a core part of how collaboration works in Prismic, so it can’t be turned off.
That said, the caching issues you’re seeing are known and the team has been actively working on improvements there. If you’re still running into problems, feel free to share any recent examples and we can make sure they’re surfaced so the team can prioritize accordingly.
For bugs or unexpected behavior, please contact support directly.
