Problem/Motivation
Throughout the administration interface, there are often lists of items with a column for operations. These operations often include items like "edit", "delete", "view" ... However, there is a huge inconsistency across not only the wording of these options, but the options available. Here is a quick run down of the available operations for each admin interface.
There are quite a few inconsistencies. Places where there could be delete options do not have one such as comments and users, sometimes the operation is appended with the object such as "edit permission" and "edit vocabulary", and the difference between edit and configure is unclear.
Proposed resolution
When the list deals with content, the operations should be "edit" and "delete". When the list deals with structure, we should use the term "configure" instead of "edit". In the cases where we are both editing and configuring on the same screen (Blocks, for example) we will use the operation "edit"
Comments admin/content/comment
- edit
- delete needed
Content admin/content
- edit
- delete
Taxonomy admin/structure/taxonomy
after #1340500: Merge "list terms" page into "edit vocabulary" page
- edit
- add terms
List Terms admin/structure/taxonomy/[vocab]
- edit
- delete needed
Blocks admin/structure/block
- configure change to edit
- delete (only custom)
Content types admin/structure/types
- edit change to "configure"
- manage fields
- manage display
- delete
Menus admin/structure/menu
after #663946: Merge "List links" page into "Edit menu" page
- edit
- add link
- delete needed
Menu: list links admin/structure/menu/manage/[menu-name]
- edit
- delete
Modules admin/modules
after #1355442: Add "Update available" indicator to the modules list
- help
- permissions change to "set permissions"
- configure
- update
Themes admin/appearance
- settings change to "configure"
- disable
- set default
Actions admin/config/system/actions/manage
- configure
- delete
Triggers admin/structure/trigger
- unassign change to "disable"
Text Formats admin/config/content/formats
- configure
- disable
Roles admin/people/permissions/roles
- edit role change to "configure"
- edit permissions change to "set permissions"
Users admin/people
- edit
- not going to add delete here - for good reasons
Remaining tasks
Below is a list of issues that will need to be resolved to cleanup these interfaces:
Add a "delete" operation for Comments at admin/content/comment
Add a "delete" operation for List Terms at admin/structure/taxonomy/[vocab]
Add a "delete" operation for Menus at admin/structure/menu
Change "configure" to "edit" for Blocks types at admin/structure/block
Change "edit" to "configure" for Content types at admin/structure/types
Change "edit role" to "configure" for Roles at admin/people/permissions/roles
Change "edit permissions" to "set permissions" for Roles at admin/people/permissions/roles
Change "permissions" to "set permissions" for Modules at admin/modules
Change "settings" to "configure" for Themes at admin/appearance
Change "unassign" to "disable" for Triggers at admin/structure/trigger
Comments
Comment #1
ultimateboy CreditAttribution: ultimateboy commentedhttp://drupal.org/node/341984 address the two cases where "no operations" is listed above.
Comment #2
yoroy CreditAttribution: yoroy commentedConsistency is still a worthy goal here.
Comment #3
ultimateboy CreditAttribution: ultimateboy commentedComment #4
jenlampton+1 for this effort.
Additionally, I find it really frustrating when we say "edit" when we mean "configure". Can we limit the word "edit" to circumstances where we're actually changing the content, and use "configure" when we are adjusting settings?
Also, some of the above list will change based on #663946: Merge "List links" page into "Edit menu" page and #1340500: Merge "list terms" page into "edit vocabulary" page
Comment #5
jenlamptondoh, forgot the tag.
Comment #5.0
jenlamptonUpdating to latest strings
Comment #5.1
jenlamptonIssue summary initiative, clarify suggested changes.
Comment #5.2
jenlamptonAdd some more changes, possibly.
Comment #5.3
jenlamptonAdd a few more, delete the delete operation for users
Comment #5.4
jenlamptonremove ?s and change of terms to term.
Comment #5.5
jenlamptonadded change to modules page
Comment #6
yoroy CreditAttribution: yoroy commentedEdit applies to content & Configure applies to settings makes sense.
A couple of issues to tackle that for consistency should be fine. Adding 'delete' operations, sounds fair, but I didn't look and check, there's some history in previous discussions around this.
I'm dubious about the 'set permissions' changes, I'm not sure there's a problem that needs fixing there.
I think this will be most productive with a first round of edit/configure cleanups. Going through those will probably teach us a couple of things about how to approach the others.
Comment #7
jenlampton@yoroy Re "set permissions"
On the roles page it's "edit permissions" and on the modules page it's just "permissions" We should consistently call it the same thing. I'm open to suggestions/alternatives though.
Comment #8
Dave ReidNote that these string should be capitalized if changed or modified as per #421118: [Meta] Standardize capitalization on actions
Comment #8.0
Dave Reidrearranged TODO list
Comment #9
greta_drupal CreditAttribution: greta_drupal as a volunteer commentedI would add to that the button label "Cancel" for user accounts. This really should be "Delete". Cancel is commonly used to 'interrupt' an operation. You might CANCEL the registration process for a new account, but once created you would delete it.
I get that in the real world one might 'cancel their cable tv account' or whatever. But, there does exist a conflict with the two uses of that word meaning different things.
Comment #12
tkoleary CreditAttribution: tkoleary at Acquia commented