Regression: not possible to delete source strings in Drupal (>7) interface translation

Created on 10 June 2015, about 9 years ago
Updated 12 May 2024, about 1 month ago

Problem/Motivation

When user is on User Interface translation page then user is not able to see Delete string.

Original report
Hello, In D7 we had the option to edit and delete text strings in theme_locale_languages_overview_form

Now, in D8 we have the option to edit in-line, but where is the option to delete? (in TranslateEditForm)

Any alternative to deleting strings?

Thanks

Steps to reproduce

- Goto: Configuration -> User Interface Tranlsation
- Delete string is not appearing at right side.

Proposed resolution

Introduce Delete checkbox to delete the translation.
Once the checkbox is checked and the form is saved then it will delete the string.

Remaining tasks

Needs a Usability review.
Patch review
Commit

User interface changes

New checkbox will be added on string translation form.

After
Screenshot after patch in #25 (screenshot from #28)

API changes

Data model changes

Release notes snippet

πŸ› Bug report
Status

Needs work

Version

11.0 πŸ”₯

Component
LocaleΒ  β†’

Last updated 3 days ago

Created by

πŸ‡ͺπŸ‡ΈSpain facine

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

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

  • Needs usability review

    Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

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

Production build 0.69.0 2024