New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve visualisation of actions for "Pending delete" content #4567
Comments
alansemenov
added a commit
that referenced
this issue
Mar 8, 2017
…eplace the Publish button with "Confirm Delete" (#4567)
alansemenov
added a commit
that referenced
this issue
Mar 8, 2017
…e Publish button with "Confirm Delete" (#4567)
alansemenov
added a commit
that referenced
this issue
Mar 9, 2017
… content items are Pending Delete (#4567)
alansemenov
added a commit
that referenced
this issue
Mar 9, 2017
alansemenov
added a commit
that referenced
this issue
Mar 9, 2017
alansemenov
added a commit
that referenced
this issue
Mar 14, 2017
alansemenov
added a commit
that referenced
this issue
Mar 14, 2017
(cherry picked from commit 1f2a664)
alansemenov
added a commit
that referenced
this issue
Mar 14, 2017
alansemenov
added a commit
that referenced
this issue
Mar 15, 2017
…ether the item is in "Pending Delete" state. Massive refactoring. (#4567)
alansemenov
added a commit
that referenced
this issue
Mar 15, 2017
…med "Pending Delete" to "Deleted". (#4567)
alansemenov
added a commit
that referenced
this issue
Mar 16, 2017
…ted content with no available Page Editor. Refactoring. (#4567)
alansemenov
added a commit
that referenced
this issue
Mar 16, 2017
Improve visualisation of actions for "Pending delete" content (#4567)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When content is in "Pending delete" state it has to be published to be physically deleted. However,
after marking content as "Pending Delete" nothing changes visually except for status, all the same actions are available for pending content and that is confusing for many users.
Do the following:
The text was updated successfully, but these errors were encountered: