Hi Waqar
Thanks for getting back to me.
In this case, it's definitely the "Translate" option we need, as we want the field values to be translated and NOT kept in sync. However, since updating to WP5.6 (and updating Toolset/WPML), it is behaving as if set to "Copy" - but ONLY if the field in the original language is blank/empty.
I've set up a page on our development site to demonstrate the problem:
English (Original) - hidden link
Spanish (Translation) - hidden link
This is a simple page with the following custom fields:
block-1-content
block-1-image
block-2-content
block-2-image
Steps to replicate the problem:
1. Update block-1-image on the ES translation. As long as there is a value in the EN original, it will behave as expected ("Translate").
2. Update block-1-image on the EN original. Again, behaviour is as expected. We can update the original image without it affecting the translation ("Translate" and NOT "Copy").
3. Delete the value for block-1-image on the EN original so the field is blank/empty. The image is removed from the ES translation. This is behaving as "Copy" and NOT "Translate" as it should be. NOTE this is only since WP5.6.
4. Now try to update the value for block-1-image on the ES translation. So long as the EN original field is blank it is not possible to populate the translated field. Again this is incorrect behaviour and is only since WP5.6.
Note that this also applies to any of the custom field types, it is not an image translation problem.
I hope I've explained this clearly but please let me know if you want me to screencast an example. I've removed the password protection from the dev site so you should be able to access it now.
Hope to hear back from you soon,
James