Issue with duplicate content in portfolio section, resolved by adjusting the groq query.

Hello, I'm seeing a duplicate in my

Portfolio

content section. The

WebGlobe

'collection' appears once on the backend cms as it should but is now being duplicated in the array of data being passed to the frontend as seen here: This error occurred after I cleared the image field and added a new image. Does anyone know how I can fix this?

Can you share the groq query?

Sure its

const query = '*[_type == "portfolio"]';

Well that’s weird. I feel like there is an obvious reason but I’m not seeing it. Is your site rendering the Sanity response directly or are you manipulating it first? If you change the image again does it give you another item?

Do you use a token with your client?

Gut feeling: you are using the authenticated client, so you’re querying drafts as well, and that entry has unpublished changes.

No, I just changed the image again and after I published the change, refreshed my site, and checked the response, the duplicate was no longer there.

Yes, I do use a token but, I'm not sure how it would have unpublished changes because I hit the publish button after the image change.

Is there a way for me to avoid this in the future?

Try this:

What Cory said, otherwise you could also not use a token in the client, so you only get published content.

So this enables me to query the portfolio collection but, ignore anything in the drafts correct?

Yes. A draft is just a document whose

_id

starts with

drafts.

, so what Cory gave you is a good way to discard drafts from your results. But you should ask yourself why you’re querying drafts at all. They’re typically not wanted since, well, they’re drafts.

I don't have any need for drafts. I thought I needed to use the token to get access to the db from my client.

I guess it depends if your dataset is public or private. If it is public, than you shouldn’t need a token. If it is private, then yes, and in that case you need to do what Cory suggested.

That makes sense.

I'll have to keep it in that case because it's private data.

Thanks you guys for all of the help, I really appreciate it.

All good. 🙂 ❤️