Prismic Preview only updates once

Developing with Prismic
1

Hello,

I'm seeing a new issue with Prismic Previews, using the Nuxt implementation.

To reproduce:

  1. Click into a document in the Prismic CMS
  2. Click preview
  3. Website opens and navigates to the document's page
  4. Make a change in the CMS and save
  5. Website updates content to match saved document
  6. Make another change and save
  7. Website does not update

This is happening on all three of our Prismic-based sites on Chrome. It happens both in a local environment and hosted on Cloudflare Pages.

Previously the websites did update content every time the document was saved, so I'm not sure what has changed here!

Is there something I'm missing? Has anything changed that we need to update on our end?

Happy to provide details of sites, repos etc in private messages.

Thank you!

p.s. I have added both prismic.io and our websites to "Sites that can always use cookies" in Chrome's settings and unfortunately that hasn't helped

3

Hey @jarod, that's odd. The newest version of the toolbar accepts preview reloads on Nuxt. Which version of the kit are you using?

4

Hi Pau, we're on "@nuxtjs/prismic": "^1.4.2", which looks like the latest package.

What seems most strange is that the preview reloads once, and then not again until the page is manually reloaded!

5

Is it possible that there's a setup in your project that clears the preview cookie after the first session is started?

6

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:

image

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 :person_shrugging:

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!

7

Hello everyone. We found the root case of the issue and are now working on a fix.
We'll update this same thread when we have updates.

Thanks

1 Like
10

Hi @Pau, is there any ETA on a fix for this?

Cheers,
Jarod

11

Hello @jarod, we released a fix for this issue. Don't hesitate to get in touch with us if this ever occurs again.

1 Like