Any view that use the Has Taxonomy Term I join is done on the taxonomy_index table which appears to only have items that are published load into it. This means that this table is not populated until a node is published. The filter should be done using the field instead.

[Old]
if you have a node that has never been published and you schedule it for a future date it doesn't show up when you change the date condition

Have a node scheduled for the 15th with no published revisions but the promoted to frontpage box checked.
Try viewing the home page as of the 17th with the date condition
That node doesn't show up.

Comments

indytechcook’s picture

Issue tags: +lsd-csi, +lsd-csi sprint 3

Added tags

indytechcook’s picture

Title: Nodes with no currently published revisions are not previewable with ers and date condition. » Nodes with no currently published revisions are not previewable
Assigned: jec006 » e2thex
Priority: Major » Critical
Issue tags: -lsd-csi sprint 3 +lsd-csi sprint 4

This also occurs with Collections.

indytechcook’s picture

Issue tags: -lsd-csi sprint 4

The same issue persists with State Flow Scheduling integration. I have confirmed the Overrides are returning the correct data. Also the query recation does see the correct revision list.

e2thex’s picture

Assigned: e2thex » indytechcook

So this issue appears to not be related to SPS. Any view that use the Has Taxonomy Term I join is done on the taxonomy_index table which appears to only have items that are published load into it. This means that this table is not populated until a node is published.

Instead one should try and use a field for doing filtering.

indytechcook’s picture

Title: Nodes with no currently published revisions are not previewable » Document use of taxonomy filter in views
Component: SPS - Overrides » Documentation

Moving this to documentation

indytechcook’s picture

Issue summary: View changes

Updated issue summary.