Inconsistent labelling of content status between list view and form view #5985
Replies: 2 comments
-
Thanks for reporting your issue. I've moved it to a discussion based because it represents new functionality beyond how things currently work. I agree that this would be confusing, in that you only see the latest status and it would be helpful to know if it there is a version that is published, not just the most recent status. For the list view to work the collection is queried with drafts=true so that it can show published and non-published records. To add to the user experience we could add a virtual field to versions that can show separately from the |
Beta Was this translation helpful? Give feedback.
-
I was able to implement a "fix" on my own through hooks + custom components:
I do think this would be nice to have in core tho, since the default draft behavior is to serve the latest published version even if there's newer drafts, and the list view UI would make you think otherwise. Could be as simple as changing the Cell text from "Draft" to "Published (drafts pending)" or similar 💭 |
Beta Was this translation helpful? Give feedback.
-
Link to reproduction
No response
Describe the Bug
We've noticed a minor issue with the labelling of post status being inconsistent on the list view and the form view. If you have a published document that has a draft version after the publish date it is marked as draft
However on the list view itself it appears as changed
Should this not be consistent? It makes it dificult for cms editors to know what content is truly published
To Reproduce
Payload Version
2.13.0
Adapters and Plugins
No response
Beta Was this translation helpful? Give feedback.
All reactions