Follow up for #1834250: Hide Content Translation module until we are able to remove it

Problem/Motivation

Entity Translation is in core. Content Translation is deprecated.

Proposed resolution

Remove Content Translation

Remaining tasks

  • establish what needs to be done to remove Content Translation - @plach
  • open issues for those tasks - lots of people
  • accomplish those tasks - lots of people
  • remove it - anyone

User interface changes

none.

API changes

none. (well, maybe but they would be in the individual issues that accomplish the tasks that need to be done first)

Comments

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented
Issue tags: -language content +language-content

At very least #1498674: Refactor node properties to multilingual.

YesCT’s picture

YesCT CreditAttribution: YesCT commented

I think this is needed too: #1807322: Filter comments taking into account the current content language

... what else?

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy commented
Status: Active » Closed (duplicate)

I'd like to close this down in favor of #1952062: Remove legacy translation module in favor of content translation which is more to the point :) Deals with the same thing essentially. It can maintain a list of issues it is postponed on.