search

silverstripe / silverstripe-versioned

Versioning for Silverstripe model
BSD 3-Clause "New" or "Revised" License
8 stars 35 forks source link

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

Open maxime-rainville opened 1 year ago

maxime-rainville commented 1 year ago

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

mfendeksilverstripe commented 1 year ago

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

https://github.com/silverstripe/silverstripe-cms/issues/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 commented 1 year ago

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.