Collection items partially published before site publishing

Helpdesk Collections
1

I have a website with a blog. The blog posts are collection items in a collection, they get shown on my home page and on my blog aggregate page.

When i create a new collection item (new blog post), i have to save the basic data (eg. title, slug) in the Collections Manager - the system forces me to.

The problem is: these blog posts partially go live, meaning they appear in my collections listings on my live website, despite them not actually being published. This means that they are on my homepage and blog aggregate page as clickable elements, but they redirect to a 404 error page, since the blog posts are not ACTUALLY published (meaning, i didn’t click the Publish button on the backend).

Example:
Website ID 766770

Saved (NOT published) collections item show up on live website:

kép
kép590×532 24.7 KB

redirects to 404 page:

This means that every time i create a new blog post, there is a period of time where my website displays a non-published blog post that all my viewers can see and click, and that redirects them to a 404 page.

Is this the expected behavior of the Sitejet Collections Manager? Can this be fixed so that collection items are not public until the site get re-published?

Thank you in advance!

2

Hey there, did you filter the blogs in the collection listings to show only the ones being published?

That would mean that you are able to set each article to “published” and “unpublished” (for example). In that case, only published articles are being shown.

4

Do you mean i should add a new Data Field to my collections, then filter all my collection listings based on this field?

If yes: this is a great manual workaround, but i don’t understand why it’s necessary. Why is this not the default behavior? Why does the live website display non-published collection items by default, only to redirect them to a 404 error page?

Also, in this case, the pre-built filter “Date Published” with value “is: in the past” does not work properly, as it display items that should not have a “Date Published” value - after all, the collection item was not Published, but Saved!

5

I just discovered the same behaviour. The collection listing shows the new items, but the individual single page layout returns a 404. So it looks like sitejet is part publishing the listing in the background. I’ll use the extra “publish” field as a workaround but the behaviour was quite unexpected.