<p>One way would be to create two Asset fields. One is the default field and one is the field which is translatable into each locale.</p>

<p>You could then steer the two fields via conditional logic: If no image is present in the default field, switch to the localised field.</p>

<p>You could add a light switch field which disables the localized field for further safety &amp; usability.</p>

CC BY-SA 3.0
2016-02-03T15:08:37.000Z
Yes, it´s a good approach. The default field always will have a image ( since it´s a required field ), and the default locale will take the image from there, for the others locales will check if specific image exist and shows it, if not, shows the default image instead.
Maybe a simpler way would be filter entry locales ( thinking out loud :) ), like this example: 
http://craftcms.stackexchange.com/questions/11958/fallbacks-for-assets-not-avilable-in-a-locale
But i´m doing something wrong this example don´t works for me...
Sebastián.
CC BY-SA 3.0
2016-02-03T14:39:12.260Z
2016-02-03T14:39:12.260Z
KSPR
<p>I´m working in a multi country website ( resolved with locales ) with products, and each product will show information for each country and the <strong>product image could change from one country to another</strong>, <strong>but the picture will usually be the same</strong>. Because the image can change for each locale, i check it like a <strong>Translatable field</strong>, but i realize that the client will have to fill the image field with the same image for each of the 4 languages, resulting in extra work to enter each product... so my question is:</p>

<p>Is there a way to assign the image in the default locale, and the others locales <strong>taking this image as default</strong>, except that you specify an image for that language specifically?</p>

<p>Thanks!
Sebastian</p>

<assets><localization><craft-pro>
Craft Locales and translatable image field
# Craft Locales and translatable image field

(Asked by: username_0 on 2016-02-03)

I´m working in a multi country website ( resolved with locales ) with products, and each product will show information for each country and the **product image could change from one country to another**, **but the picture will usually be the same**. Because the image can change for each locale, i check it like a **Translatable field**, but i realize that the client will have to fill the image field with the same image for each of the 4 languages, resulting in extra work to enter each product... so my question is:

Is there a way to assign the image in the default locale, and the others locales **taking this image as default**, except that you specify an image for that language specifically?

Thanks!
Sebastian

**Tags:** assets, localization, craft-pro


---

## 1 answers

### Answer by username_1 on 2016-02-03. Score: 2

One way would be to create two Asset fields. One is the default field and one is the field which is translatable into each locale.

You could then steer the two fields via conditional logic: If no image is present in the default field, switch to the localised field.

You could add a light switch field which disables the localized field for further safety & usability.

> **Comments:**
> **username_0**: Yes, it´s a good approach. The default field always will have a image ( since it´s a required field ), and the default locale will take the image from there, for the others locales will check if specific image exist and shows it, if not, shows the default image instead. Maybe a simpler way would be filter entry locales ( thinking out loud :) ), like this example:  http://craftcms.stackexchange.com/questions/11958/fallbacks-for-assets-not-avilable-in-a-locale But i´m doing something wrong this example don´t works for me...  

---

