Standardize operations' text throughout UI

Created on 3 December 2008, almost 17 years ago
Updated 2 September 2025, 13 days ago

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 πŸ“Œ Merge "list terms" page into "edit vocabulary" page Postponed

  • 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

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

user interface text

Created by

πŸ‡ΊπŸ‡ΈUnited States ultimateboy

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024