Content translation metadata is only being saved when using the content translation form

Created on 3 August 2015, over 9 years ago
Updated 22 March 2024, about 1 year ago

Problem/Motivation

Currently when saving an entity translation, the content translation metadata is not being saved, e.g. source translation.
It relies on the form being used.

Proposed resolution

Remaining tasks

  • Discuss if we can implement this or it should be responsibility of the API calling code.

User interface changes

None.

API changes

None.

🐛 Bug report
Status

Needs work

Version

11.0 🔥

Component
Content translation 

Last updated 3 days ago

No maintainer
Created by

🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

Live updates comments and jobs are added and updated live.
  • API clean-up

    Refactors an existing API or subsystem for consistency, performance, modularization, flexibility, third-party integration, etc. May imply an API change. Frequently used during the Code Slush phase of the release cycle.

  • 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

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.71.5 2024