Content updated via Release feature doesn't get updated when you go directly back to same content without refreshing the page
Impacted feature
Releases and content (maybe only legacy slices, can't verify since I do not have slice machine instance)
What steps have you taken to resolve this issue already?
Simple page refresh solves the issue.
However if someone else goes into the page without refreshing, it could overwrite with older content.
Errors
Expected to see the updated content, however I see the old content (pre-release state).
However, if I refresh the page (browser refresh button or ctrl/cmd + R), I see the updated content.
Your Role
Web Dev
Steps to reproduce
Make an update to legacy slice content
Save and add it to new release or existing release.
Publish the release.
Click on "Work" tab left of "Planned" (Release) to go back to list of contents
Click on content that just got updated via Release.
This has caused issue where updated content being reverted to older content because other person unknowingly saved other update on same content without refreshing the page.
This is expected behavior. When you add a new field or modify a slice, it won’t immediately update across all your documents and API. You'll need to make a small change in each document for the update to appear.
@Pau this is not about adding field or modifying a slice.
This is about entering content and using Release feature.
Once content is updated on existing content and published via Release, going back to content from "Work" tab won't display updated content that was published via Release, but shows pre-published content, and require refresh (either browser refresh or cmd/ctrl + R) to show the content published via Refresh
Thanks for clarifying. What I mentioned before was about editing the content modeling of a legacy slice, but I see what you're referring to now.
It sounds like you might have two tabs open, one for the document and another for the document list. It’s true that if you publish a change in one tab and then switch to the "Work" tab, the updated content might not show up immediately. The page does need a refresh to display the changes.
If there’s something else I’m missing here, please let me know, as we haven't been able to reproduce this issue on our end.
This happens with just one tab and in same tab.
Publishing Release from either all release page or individual release page have same results and it happened on 3 different repositories on 3 different tiers (Enterprise, pro, free).
Could you try reproducing the issue and record it using Jam?
Just make sure to start the recording from inside your repository’s window so we can catch any console warnings.