silverstripe / silverstripe-versioned

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

History Viewer: Revert #95

Closed chillu closed 6 years ago

chillu commented 6 years ago

Acceptance Criteria

Notes

Pull requests

chillu commented 6 years ago

I get clear instructions that I need to publish the record for the revert to take effect

@clarkepaul That's currently not part of the designs, I just made up that AC. Do you think it's necessary? It can be counter intuitive to CMS authors that a revert requires a separate user action (publish) to take effect. Maybe that's communicate clearly enough by adding a "draft" label already - although I'm not sure that's the case without a page refresh?

clarkepaul commented 6 years ago

It personally doesn't feel too disjointed when reverting a page with the "save" action showing as "saved", we should also soon have a status (eg Draft) next to the page title which will re-enforce the page state as well. The other option would be to use a in-page alert instead of the temporary right-top notification so that we can elaborate on the page status. Would you mind if we change that AC to "I get a clear indication that I need to publish the record for the revert to take effect" as showing a draft status should suffice IMHO.

I'll add this to a list of possible things we can test (hoping to bundle a bunch of smaller tests together).

chillu commented 6 years ago

I've changed it to indication, which seems to be already present in the current UI (showing "saved" label on button, with a "draft" label)

robbieaverill commented 6 years ago

Primary PRs for the CMS reverting are added to the ticket description, I'll be finishing off elemental tomorrow

raissanorth commented 6 years ago

The PR for Elemental: https://github.com/dnadesign/silverstripe-elemental/pull/230

robbieaverill commented 6 years ago

All merged 🎉