Problem/Motivation

  • As an editor, I can translate asymmetrically, meaning a translated node gets all the original content copied over, but can remove / add content in the translation at will, without interfering with the original node contents.
  • As an editor, I can translate all fields of all content types, unless there is an explicit reason why the field should not be translatable.

Translatable entity types:

  • Content (node)
  • Menu links
  • Taxonomy terms
  • Content blocks & Paragraphs
  • Site setting & labels
  • Media

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork la_eu-3565065

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

taran2l created an issue. See original summary.

taran2l’s picture

taran2l
Primary language Ukrainian
Location Lviv
commented
Issue summary: View changes

taran2l opened merge request !54

taran2l’s picture

taran2l
Primary language Ukrainian
Location Lviv
commented

The MR has translation support enabled for all fields, except the following types (which in my opinion does not make a lot of sense):

  • Date (event)
  • Address (event, partner)
  • Entity references (e.g. Category, Related Partner, Tags etc)
  • Promoted/Sticky (not sure those are used anywhere though)
  • Image/Logo/Media
  • URLs/Email/Phone (e.g. Partner URL/Email/Phone, Case URL etc)
  • Number fields (Runner up, Website of the year, Winner etc)
  • Social links

Would like to hear any feedback on that decision.

The other thing related to this: atm there is moderation workflow enabled for nodes which enforces "Moderated content requires non-translatable fields to be edited in the original language form.". This means that non-translatable are not visible at all on the translation edit pages.

I feel that moderation workflow is not required for our use case, so it can be safely disabled. Then non-translatable fields can be made visible on all translations.

Let me know your thoughts on this

taran2l’s picture

taran2l
Primary language Ukrainian
Location Lviv
commented
Status: Active » Needs review
evilargest’s picture

evilargest commented
Status: Needs review » Reviewed & tested by the community

I have reviewed the changes and tested the translations of content, including Layout Builder, and everything looks fine and works as expected. Moving the issue forward to RTBC

svendecabooter’s picture

svendecabooter
he/him
Primary language Dutch
Location Gent
commented

+1 tested this locally and seems to work as intended.
No particular preference regarding workflow. In BE we certainly don't need an advanced publication workflow. But if it means untranslatable fields get hidden on translation, that's not really an issue IMHO.

  • taran2l committed 9ea319ca on staging 
    feat: #3565065 Configure content translation

By: taran2l
By: evilargest...
taran2l’s picture

taran2l
Primary language Ukrainian
Location Lviv
commented
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.