Unfortunately not, I can see the cookie is still there after the session is started. It looks like we just stop pinging for content after the first update — see the network trace here:
Those pings are from the Prismic toolbar iframe, and the v2 line is where a document is saved on the CMS side and content is refreshed. There's then no more pings coming from the Prismic toolbar, but it's still visible on-screen
I'm digging around in our code but can't see anything that's changed in our implementation of the toolbar in the last month or so!
I'm having this issue: the preview is working, but the document data shown is outdated. When we click Publish, the preview gets updated — which is strange, because our setup is split as follows:
Main page (server1):
This page doesn’t have the preview script or Slice Machine. It’s built as a static site and doesn’t change until we trigger a rebuild (for security reasons). It’s working perfectly fine.
Slice Machine + Preview (server2):
This server handles all the preview and routing scripts. It uses the same branch as the main page, but it’s dedicated to preview and Slice Machine.
Slice Machine: working perfectly.
Preview: it loads correctly, but when you make a change in a document and save it, the preview still shows the old data. I also tried creating a release and previewing it — same result, the data is still outdated.
Because the main page is static and lives on a separate server, publishing doesn’t affect it directly. However, when I click Publish, the preview page updates with the new data. I thought the preview functionality was supposed to show the latest document changes without needing to publish them.
Okay, end up being my routing, preview is showing new content in pages where the category is not set, so i will need to check more in deep the routing or the prismicio, because pages from the first and second level are okay “/level1/level2“ but as soon as i have a category “/level1/level2/[category]“ the problem start, the page work, but the preview is showing old data.