Is it possible to make the buttons "Publish" and "Save Draft" disabled when the state of the entity (e.g. article) is reverted back to the already published version? #7462
AlyaPod
started this conversation in
Feature Requests & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello :) My team and I are currently working on improvements for editorial team and we have noticed this flow for entities:
you open a published article -> "Publish" and "Save Draft" buttons are disabled -> change something (for example, add space to the title) -> "Publish" and "Save Draft" buttons are enabled now since there were changes applied -> remove the prev. added space (so, initially go back to the published version) -> "Publish" and "Save Draft" buttons are still enabled.
Our editors are getting confused by this thinking that they haven't removed all the non-intended changes or missed some things. So the ideal flow would be to make the "Publish" and "Save Draft" disabled again if all the implemented changes were removed.
Is there any way to implement comparison of published and current versions or may be that is an improvement that is already on the way with v3? Or may be you can help us with figuring out how to set this up? Thank you in advance for the answer :)
Beta Was this translation helpful? Give feedback.
All reactions