#85596Working with filereferences does not support creating a new metadata-translation
Description
- Have files EN.pdf and DE.pdf
- Have EN your default-language and DE your first translation
- Both files will automatically get metadata in the default-language (here: EN) – although it would probably make more sense for the DE-file to just have metadata in DE
- Create a filelinks-contentelement referencing EN.pdf
- Copy it over to DE (tested with “freemode”)
- Edit filelinks in DE, remove the original file and add DE.pdf instead
- In the backend you don’t have an edit-icon to edit the metadata for DE.pdf (in German) – since only metadata in the default-language exists
- Viewing the DE-page in the frontend you see the filename – since the regular default-metadata only exists for EN and no translation to DE exists
- Where you’d usually have the edit-icon instead have a button to create the new metadata-translation for DE.pdf to DE
Possibly it would also be nice to not always have metadata in the default-language but instead only create language-specific metadata in languages you want (EN.pdf with data in EN only, DE.pdf in DE only).
Tested on 8.7 LTS and master (currently post-9.3).
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
History 2
-
Benni Mack changed Related to #92906 <span data-processor="relativetime" data-value="2026-11-18T19:29:46+00:00" > 11/18/26, 19:29 </span>
-
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-18T19:32:46+00:00" > 11/18/26, 19:32 </span>
Closing this in favor of #92906 as a duplicate. The other one will get fixed likely very soon.