Bug #75848
closed
Translated file meta data preassign wrong image meta for media elements
0%
Description
In the filelist I have added some translations for meta data of an image file. This works as expected so far.
Now I've added an Text & Media content element and added this image to it. In default and any other language the meta data of the image will be preassigned with the meta data from the latest translation.
To make it more understandable:
Text & Media element with image gets this meta data at the moment:
German content element <- Japanese meta data
English content element <- Japanese meta data
Japanese content element <- Japanese meta data
It should be:
German content element <- German meta data
English content element <- English meta data
Japanese content element <- Japanese meta data
Updated by schmitz no-lastname-given about 8 years ago
PS: I use the latest TYPO3 7.6.6
Updated by schmitz no-lastname-given almost 8 years ago
- Project changed from TYPO3 Core to 1985
EDIT: wrong project
Updated by schmitz no-lastname-given almost 8 years ago
- Project changed from 1985 to TYPO3 Core
correct project
Updated by schmitz no-lastname-given almost 8 years ago
- Target version set to 7.6.5
Updated by Riccardo De Contardi almost 8 years ago
- Target version changed from 7.6.5 to Candidate for patchlevel
- TYPO3 Version set to 7
- Is Regression set to No
Updated by Riccardo De Contardi over 7 years ago
- Status changed from New to Needs Feedback
Could you tell me if the issue still occurs with the latest 7.6.x or the latest master?
Thank you!
Updated by schmitz no-lastname-given over 7 years ago
Riccardo De Contardi wrote:
Could you tell me if the issue still occurs with the latest 7.6.x or the latest master?
Thank you!
Seems it is working in latest 7.6.x in the frontend. In the backend at media file added to the content element you find always the translation, which was added at last.
But that is ok. Thank you very much!
Updated by Riccardo De Contardi over 7 years ago
@schmitz no-lastname-given no-lastname-given Thank you for your feedback; so, do you think I can safely close it? Thanks!
Updated by schmitz no-lastname-given over 7 years ago
Riccardo De Contardi wrote:
@schmitz no-lastname-given no-lastname-given Thank you for your feedback; so, do you think I can safely close it? Thanks!
I think the handling in the backend is stil wrong, but it doesn't make any trouble, because the translation fallback in the frontend is working correctly.
So I think you can close it.
Updated by Riccardo De Contardi over 7 years ago
- Status changed from Needs Feedback to Closed
I close it for now; if you think that this is the wrong decision or there is still work to do on this topic, please reopen it or create a new issue with a reference to this one.
Thank you.