We have a page type with a ContentItemSelectorComponent field for a card image (an Image content type). The field is required from a content perspective (and is correctly required on the page type) - without it, the page renders incorrectly.
When an editor publishes the page, Kentico shows the cascade publishing dialog listing any unpublished linked items. However, this dialog is optional - editors can dismiss it and publish the parent page anyway, leaving the linked image unpublished. The result is a live page with missing content.
Does anyone else find this scenario a bit odd, should there be a better way of maybe blocking the publishing of a page that requires a linked item that is unpublished? Should it be a more prominent warning if it's a required field?
We're currently handling this defensively in the frontend (graceful null handling), but ideally we'd catch it at the content authoring stage.
Have others run into this? Any approaches - custom workflow steps, validation hooks, or otherwise - that have worked well?