New content not displaying in Nuxt3

Developing with Prismic
1

Hi Prismic team,

I’m having some issue with Nuxt not displaying new Prismic Fields after they are published.

I have added several RichTextFields to the website I am developing but they just come through as empty arrays no matter what I do. These fields are all within slices and have content inside Prismic.

I can see the content inside the API via the web explorer, but it renders an empty array in Nuxt3.

All other fields are working fine except for these new ones I have added.

Nuxt: 3.17.0
@nuxtjs/prismic": "^4.1.0"
Am using useAsyncData to get the data
Node 20.19.0

Thing I have tried:

  1. Re-adding a different field (same issue)
  2. Restarting my machine
  3. Clear the nuxt cache
  4. Opened the page in incognito

Any ideas as to why Nuxt is not displaying the data, is this a known issue? What is the work around?

Thanks

2

After waiting a bit of time, the test data in the new field in Prismic has been wiped, and now the fields work (after I re-added content)

Maybe this is an issue with SliceMachine or the prismic website caching? (I did copy and paste from one field to another to duplicate data)

3

Hey @Impossible,

Thanks for sharing the details.

I can see the content inside the API via the web explorer, but it renders an empty array in Nuxt3.

Since you see content in the API Explorer but Nuxt shows [], that doesn’t sound like a content modeling issue but more likely ref, path, or cache

  • Ref match: In the API Explorer, switch to Published (master) and note ref. Make sure your app isn’t using an older ref, clear preview and give the CDN ~1-2 min after publish.

    • Can always compare the ref in the API Explorer

  • Ensure the correct slice path, they live under:

    • slice.primary.my_field (non-repeatable zone)
    • slice.items[n].my_field (repeatable zone)
    • Render with <PrismicRichText :field="..."/>

That said, glad to hear the data appeared - it’s hard to pinpoint retroactively but checking the API Explorer first for ref/model/data is the quickest way to isolate where the issue is stemming from.