If you have a node with a image field, leave the image empty, then create a translated version and add an image to that, you'd expect the image field to stay empty in the original one. But it doesn't. The image you add to the translated version will be added to the original too.
If you add the image to the translated node and then go back to the original and delete the image, the original is without and image and the translated has the image. But if you edit the translated, the image gets added back to the original.
Steps to reproduce - did this in simplytest.me with RC4
- Enable Language and Content translation
- Add language (I added Finnish)
- Add translation support for Article (which already has field_image per default installation). Make sure the "File" under "Image" is also checked.
- Add article, keep it in English (default). Add a file for the image field or leave it empty.
- Add a translation for the node, put a different image to the field_image
- Go back to the original - it has the file you added to the translated one
Vanilla RC4 seems to be having problems with even the alt text - the same text goes for the both translations.
Comments
Comment #2
holist commentedI can confirm this issue is still present in 8.0.0.
Comment #3
toniteof commentedComment #4
toniteof commentedWorking fine. Just add one more step.
Comment #5
tormu commentedat admin/structure/types/manage/page/fields/node.page.field_image I have checked following form items:
x Users may translate this field
x "File" under Translatable elements
This makes it possible to have different image on different translated versions of the node, but the original problem still exists. If you set the image field empty for language X and then add an image to the language Y version, the image gets added to the language X version too.
X doesn't remain empty.
Comment #6
toniteof commentedI confirm issue.
It work only if all three check boxes (File, Alt, Title) are checked on both pages (admin/config/regional/content-language and admin/structure/types/manage/article/fields/node.article.field_image).
Comment #7
swentel commentedThis is probably fixed by #2639352: File records, files themselves lost in translation, we should see if we can still reproduce this now.
Comment #8
swentel commentedClosing, re-open if it still occurs, but it should be fixed normally.
Comment #9
swentel commentedPossibly still an issue, but #2496867: Translatable image file is not working unless you also config the image field. Config can get lost anyway. is for that.