Problem/Motivation

Field Group uses Config translation to localize labels and descriptions. However, this mechanic is difficult to discover for site builders as indicated by created issues:

Proposed resolution

Resolve blocking issues described above. Add documentation how to translate field group labels and descriptions.

Remaining tasks

  1. Solve: #2546212: Entity view/form mode formatter/widget settings have no translation UI
  2. Solve: #3173509: When a config field is a textarea. the translation field should also be a textarea.
  3. Add a documentation page to drupal.org, or include instructions in a readme file (or both).

User interface changes

None.

API changes

None.

Data model changes

None.

CommentFileSizeAuthor
#20 3114825-20.patch785 bytessmustgrave
#8 3114825-8.patch783 bytesPooja Ganjage
#2 translate-field-group.png90.97 KBidebr
#2 manage-form-display.png132.91 KBidebr
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

idebr created an issue. See original summary.

idebr’s picture

idebr CreditAttribution: idebr at iO commented
Issue summary: View changes
FileSize
manage-form-display.png132.91 KB
translate-field-group.png90.97 KB

Probably the easiest way is to add a patch from #2546212: Entity view/form mode formatter/widget settings have no translation UI

You now have a 'Translate' tab available on 'Manage form display':

The translate tab allows translating the field group:

PieterDC’s picture

PieterDC
Primary language Dutch
Location Ghent
CreditAttribution: PieterDC at Dropsolid commented

Thanks for hinting a patch from that other issue @idebr

joseph.olstad’s picture

joseph.olstad
Primary language French
CreditAttribution: joseph.olstad commented
Related issues: +#3129292: The field group module lacks the description field translation.

I did not see a way to add a translation to a 'description.

calbasi’s picture

calbasi
Primary language Catalan
Location Catalonia
CreditAttribution: calbasi at calbasi.net for Experience Box Spain commented

I don't think it was a good idea to disable the old method to translate the labels (even it's not the drupal way to do) while there is not a way, WITHOUT A PATCH from another module/core to translate them.

More: there is not a warning, in 3.0 version, to avoid all websites simply break their translated labels without any alternative but discover this issue and apply an external patch.

csedax90’s picture

csedax90 CreditAttribution: csedax90 commented

So... how can we do this?

Martijn de Wit’s picture

Martijn de Wit
Primary language Dutch
Location 🇳🇱 The Netherlands
CreditAttribution: Martijn de Wit at Ablerz commented
Issue summary: View changes
Related issues: +#3173509: When a config field is a textarea. the translation field should also be a textarea.

Added some extra info for related tickets.

Pooja Ganjage’s picture

Pooja Ganjage CreditAttribution: Pooja Ganjage at Asentech LLC commented
FileSize
3114825-8.patch783 bytes

Hi,

I am creating patch for adding instructions in readme file.

Please review the patch.

Thanks.

Pooja Ganjage’s picture

Pooja Ganjage CreditAttribution: Pooja Ganjage at Asentech LLC commented
Status: Active » Needs review
Webbeh’s picture

Webbeh
he/him/his
Location Georgia, USA
CreditAttribution: Webbeh at Georgia Institute of Technology commented
Status: Needs review » Needs work

The patch above relies on the patch of #2546212: Entity view/form mode formatter/widget settings have no translation UI to complete.

Martijn de Wit’s picture

Martijn de Wit
Primary language Dutch
Location 🇳🇱 The Netherlands
CreditAttribution: Martijn de Wit at Ablerz commented
Issue summary: View changes
Martijn de Wit’s picture

Martijn de Wit
Primary language Dutch
Location 🇳🇱 The Netherlands
CreditAttribution: Martijn de Wit at Ablerz commented

Maybe add a sentence explaining it is "configuration" and not "content". Many times I encounter editors that find it hard to see the difference.

Martijn de Wit’s picture

Martijn de Wit
Primary language Dutch
Location 🇳🇱 The Netherlands
CreditAttribution: Martijn de Wit at Ablerz commented
Issue summary: View changes
csedax90’s picture

csedax90 CreditAttribution: csedax90 commented

a way to translate it without this #2546212: Entity view/form mode formatter/widget settings have no translation UI ?

Martijn de Wit’s picture

Martijn de Wit
Primary language Dutch
Location 🇳🇱 The Netherlands
CreditAttribution: Martijn de Wit at Ablerz commented

As far as I know; That is correct. #2546212 is adding the missing UI.

We are using the patch from #2546212 for a site. And is is working as it should be. One little bug regarding descriptions/textarea's (see other issue)

liquidcms’s picture

liquidcms CreditAttribution: liquidcms commented

Trying to summarize this... so at the moment FG labels are not translatable. The core patch listed above is required. Correct?

And I see Pooja's doc patch above; is that for after the core patch is applied - as without it, none of the things mentioned in that patch exist.

Martijn de Wit’s picture

Martijn de Wit
Primary language Dutch
Location 🇳🇱 The Netherlands
CreditAttribution: Martijn de Wit at Ablerz commented

Yes, this issue / patch is only to describe how it should work if all patches are used.

Martijn de Wit’s picture

Martijn de Wit
Primary language Dutch
Location 🇳🇱 The Netherlands
CreditAttribution: Martijn de Wit at Ablerz commented
Issue summary: View changes

#3173509: When a config field is a textarea. the translation field should also be a textarea. is solved.

alorenc’s picture

alorenc
Location Wolsztyn, 🇵🇱
CreditAttribution: alorenc commented

Patch #8 allows me to translate Content view display configuration. Thanks!

smustgrave’s picture

smustgrave CreditAttribution: smustgrave at Mobomo commented
Status: Needs work » Postponed
Related issues: +#2546212: Entity view/form mode formatter/widget settings have no translation UI
FileSize
3114825-20.patch785 bytes

Postponed until https://www.drupal.org/project/drupal/issues/2546212 lands.

Added a patch for how to use that once it does.

cestmoi’s picture

cestmoi CreditAttribution: cestmoi as a volunteer commented

And yet years later and this "simple" issue is still not officially solved. I am translating a site and knocking my head off the wall once with an "ago" instance that I cannot find where-to anywhere and now with this field_group thing, just to name a few. It seems Drupal still has a long way to go to say it's a reasonably "fully" ready multilingual CMS.

batigolix’s picture

batigolix
Primary language Dutch
Location Utrecht
CreditAttribution: batigolix at Finalist commented

@cestmoi: this issue is pending a fix for drupal core which is being worked on #2546212: Entity view/form mode formatter/widget settings have no translation UI.

Yes, some issue take a long time to be fixed. But you do not need to wait because a patch is being provided in that ticket that can help you move forward.