How to skip fetching archived content

Technical Questions
1

We are fetching builder page as per Integrating Pages - Builder.io
If we have 2 pages “page1” & “page2” with exact same URL and fields, according to builder logic, it will show the first page “page1” from the list.
Now, if I archive “page1”, it still shows “page1” but it should show “page2”.

How can we achieve this? Is there any query parameter we can pass which will not fetch archived entries?

1 Like
2

Hi Olivela!

That seems like a very strange issue, it’s not supposed to return archived content. Will you be able to help us with the page1 and page2 content links for further investigation?

1 Like
3

I’m experiencing this with this archived content shadowing this published content when using this JS API query:

builder
  .get('learning-hub-article', {
    fields: 'data,firstPublished,id,name',
    includeRefs: true,
    options: {
      includeUnpublished: builder.previewingModel === 'learning-hub-article',
    },
    url: '/learn/climate-action-framework',
  })
  .promise()

Public API key: 4a52b3b8ac444b998a4f90d60aa6fcc3

Interestingly, it doesn’t occur with this URL generated by the Builder editor. It’s something about the URL the JS API generates.

4

Hi @balleverte!

We are not able to reproduce this from our end, could you try clearing the cache as well as republishing the content again and see if that fixes the issue?

5

With caching disabled, compare the results of these URLs:

This one generated by the Builder visual editor (using includeUnpublished=true) returns the archived data (id=5c7e20f2a8ff4915bc348cb63ac6b278):

https://cdn.builder.io/api/v1/query/4a52b3b8ac444b998a4f90d60aa6fcc3/learning-hub-article?omit=meta.componentsUsed&apiKey=4a52b3b8ac444b998a4f90d60aa6fcc3&includeUnpublished=true&fields=data%2CfirstPublished%2Cid%2Cname&userAttributes.urlPath=%2Flearn%2Fclimate-action-framework&userAttributes.host=null&userAttributes.device=desktop&options.learning-hub-article.model=%22learning-hub-article%22

This one generated by the application running standalone (not in preview mode, using includeUnpublished=false) returns the published content (id=dcce36ec6a2d421c8b650966a9470bdc):

https://cdn.builder.io/api/v1/query/4a52b3b8ac444b998a4f90d60aa6fcc3/learning-hub-article?omit=meta.componentsUsed&apiKey=4a52b3b8ac444b998a4f90d60aa6fcc3&includeUnpublished=false&fields=data%2CfirstPublished%2Cid%2Cname&userAttributes.urlPath=%2Flearn%2Fclimate-action-framework&userAttributes.host=null&userAttributes.device=desktop&options.learning-hub-article.model=%22learning-hub-article%22
6

Hi @balleverte,

If you use includeUnpublished=true that is going to include archived content as well by default. In case you don’t want archived content then I recommend you delete them.

7

In that case, the answer seems to be to add includeUnpublished=true as well as either &query.published.$ne=archived or &query.published.$in=%5B%27draft%27%2C%20%27published%27%5D.

2 Likes
8

balleverte’s solution worked for me, thanks!

I’m using the Content API v3 and was getting the same error - archived content is being returned. The Content API docs say that includeUnpublished should:

Include content entries in a response that are still in draft mode and unarchived.

https://cdn.builder.io/api/v3/content/page?apiKey=2fe4147bb8c843bb8ebba475c8973899&includeUnpublished=true&url=/experience&locale=en-US&data.locale=en-US&cachebust=true&noTraverse=false

The above returns two entries - one draft and one archived.

  1. Is there a way to disable this or is using &query.published.$ne=archived the only way?
  2. The docs should be updated
  3. Is there a way to see archived content in the Builder UI?