EPIC Publication state of parent object should reflects the state of dependant objects

[maxime-rainville]

Big story

As a content author, I want to see at a glance if there are unpublished DataObject tied to a page so I can actioned any required changes.

Context

Sometime a CMS page depends on a child DataObject for its content. Those children might have unpublished changes even if their owner does not. The "Publish" button only reflects the publication state of owner without considering its dependants.

Related

• Implement API to determine if owned object need to be published #420
• SPIKE Update UI to account for a more nuance understanding of unpublished silverstripe-admin#1593
• Smarter publication state is documented developer-docs#373
• Cancel draft changes UI component doesn't show up for draft changes on owned models silverstripe-cms#2892

[mfendeksilverstripe]

@maxime-rainville Adding this one here as well - it's the same root cause.

silverstripe/silverstripe-cms#2892

Cancel draft changes should be displayed under the same condition when we prompt user to publish changes. Basically when there are changes to publish the user needs to be prompted by the UI to either publish them or discard them.

[maxime-rainville]

Maybe once the initial 3 cards are done, we want to have go at improving the versioned state of Elemental Areas with JS to update the dirty state of the Save/Publish buttons.