Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
- Install with Standard profile in English.
- Turn on the 4 multilingual modules.
- Add Spanish language.
- Make User content translatable (both content types). Note that by default, the Picture field's alt/title text are translatable but not the image file itself. Also note that by default, the Picture field on User does not have alt or title text enabled. Leave these defaults as they are.
Now go to your user 1 account and translate it into Spanish. The Picture field does not say "all languages" on it, but if you upload a new picture, it does in fact get used for all languages.
I suspect this is a problem for all file/image fields, but I haven't tested it for anything but the User Picture field.
Proposed resolution
Fix the UI so it says "all languages" on the Picture file field.
Remaining tasks
Make a patch. Test it.
User interface changes
UI will correctly tell you when changing files/images will affect all translations.
API changes
None.
Data model changes
None.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | noindication.png | 22.72 KB | jhodgdon |
Comments
Comment #2
rosinegrean commentedComment #3
peterarnold commentedThis fix will modify the core/profiles/standard/config/install/field.field.user.user.user_picture.yml and update the description filed.
I'm not sure I understood exactly if this is what you want.
Comment #4
jhodgdonThanks for trying! But sorry -- that's not the right thing to do.
Whether the Picture field is used for all languages or can be "translated" (a different picture supplied for each language) is configurable. By default, file or at least image fields are marked as not translatable, meaning the same file is used for all languages, but you can change that on the content translation settings page.
The problem is that the UI for translating this file field, from the Content Translation module, is not properly marking the field as "all languages" if the file is marked not translatable. So the fix needs to be somewhere in the Content Translation module, and we should not be changing the description of the Picture field.
Comment #5
peterarnold commentedComment #6
perseaalexandra commentedI could not reproduce the issue. If picture field is marked not translatable, translation module sets it to all languages. Could you give more explanation in reproducing the problem or maybe some pictures?
Comment #7
perseaalexandra commentedComment #8
jhodgdonDid you follow the steps in the issue summary? When I do exactly those steps, here is what I see for the Picture field when I am translating user 1:
As you can see, there is no indication that when I change this field, I will be changing the value for all languages. However, if I do change the image file, it will apply to all languages. Hence, the bug.
Comment #9
perseaalexandra commentedComment #15
matsbla commentedI think this might be a duplicate
Comment #19
penyaskitoI think I duplicated this in #3152587: Add a mark when editing a field property will affect all the translations as we do with fields themselves.
Comment #23
smustgrave commentedThis was brought up as daily triage ticket in the bugsmash channel.
Closing out as a duplicate of https://www.drupal.org/project/drupal/issues/3152587
If anyone disagrees please reopen with how this is different.
Thanks!
Comment #24
quietone commentedI agree with #23. This issue is earlier but is specific to the picture field. The other issue is not so specific so let's go with that one.