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

ultimateboy’s picture

http://drupal.org/node/341984 address the two cases where "no operations" is listed above.

yoroy’s picture

Version: 7.x-dev » 8.x-dev
Component: usability » ajax system

Consistency is still a worthy goal here.

ultimateboy’s picture

Title: Standardize Operations » Standardize operations' text throughout UI
Component: ajax system » user interface text
jenlampton’s picture

+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

jenlampton’s picture

Issue tags: +Usability

doh, forgot the tag.

jenlampton’s picture

Issue summary: View changes

Updating to latest strings

jenlampton’s picture

Issue summary: View changes

Issue summary initiative, clarify suggested changes.

jenlampton’s picture

Issue summary: View changes

Add some more changes, possibly.

jenlampton’s picture

Issue summary: View changes

Add a few more, delete the delete operation for users

jenlampton’s picture

Issue summary: View changes

remove ?s and change of terms to term.

jenlampton’s picture

Issue summary: View changes

added change to modules page

yoroy’s picture

Edit 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.

jenlampton’s picture

@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.

Dave Reid’s picture

Note that these string should be capitalized if changed or modified as per #421118: [Meta] Standardize capitalization on actions

Dave Reid’s picture

Issue summary: View changes

rearranged TODO list

greta_drupal’s picture

I 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.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

tkoleary’s picture

Version: 8.2.x-dev » 8.3.x-dev
Issue tags: +sprint

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.