Noticed while testing, but not caused by: #1987124: Convert filter_admin_format_page() and filter_admin_overview() to a Controller
Updated: Comment #0
Problem/Motivation
The label disable on the action does not seem to indicate the reprocusions of disabling a format. At first time, I disabled, and then was very surprised to have the format disappear from the UI. I thought I would be able to re-enable it after disabling it. The second time I tried it, I noticed the warning message said that it would disappear from the UI and that it was permanent.
The warning message also says that content using the format will not be displayed. ... it was the thought of others that the point of calling it disable instead of delete was that the content would still be displayed, but not editable? Hm.
Proposed resolution
Call it delete.
Change the class on the delete disable to be the warning/danger red of other deletes.
Update the help text.
Remaining tasks
- Check if the help text on the disable confirmation is accurate.
- Research why it is called disable instead of delete.
- Discuss.
User interface changes
Yes.
API changes
No.
Related Issues
- ? (maybe do a grep for the disable help text and do a git blame to find issues that relate to why it is called disable)