Cannot mark a translation itself as outdated

Created on 6 November 2012, about 12 years ago
Updated 30 January 2023, almost 2 years ago

Follow up for #1831530: Entity translation UI in core (part 2) β†’

Problem/Motivation

cannot mark a translation as outdated. can only edit another translation and from there, check the box to more all other translations outdated, then edit every translation that is not meant to be outdated and uncheck the needs updating check box in those translations. ick.

Proposed resolution

show the "mark this outdated" on every translation (even ones where they are not outdated)

Remaining tasks

  • write down steps to reproduce exactly
  • get screen shots or find ones in #1188388: Entity translation UI in core β†’ to reuse
  • find comments in #1188388: Entity translation UI in core β†’ about this issue. link to them in Original report section below. There are several.
  • reroll (relevant part of) the patch from that issue in comment 188 and post it here
  • document usual workflows to decide how making outdated should be
  • code solution
  • update tests(?)
  • more screen shots
  • manually test
  • ui review new screen shots
  • code review

User interface changes

This is a ui issue. See above.

API changes

no api changes anticipated.

Original report

Link to original comments from et ui issue

πŸ“Œ Task
Status

Needs work

Version

9.5

Component
Content translationΒ  β†’

Last updated about 16 hours ago

No maintainer
Created by

πŸ‡ΊπŸ‡ΈUnited States yesct

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

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

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

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.

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

Production build 0.71.5 2024