<p>Solved - What was needed was to use the Update Asset Indexes tool in the settings of craft. If I do this just after creating a new Locale, before doing anything else, when my articles are created they know where to look for their assets. So relieved</p>

<p>Also noticed that to get a matrix to copy across locales (as well as setting the matrix field to NOT TRANSLATABLE and the fields within the matrix to TRANSLATABLE) it was necessary to do a slight change to the original matrix after creating a new asset (such as adding a space after the title). This forced the matrix to copy across. </p>

<p>Hope this helps someone else </p>

CC BY-SA 3.0
2017-01-15T15:28:24.100Z
2017-01-15T15:28:24.100Z
Paul Mckenna
<p>If the Asset field is set up to be <strong>not translatable</strong>, the selected assets should actually be the same across all of your locales.</p>

<p>If it is set up to be <strong>translatable</strong>, it doesn’t copy over the selection on the first save (or when a new locale was added) because of a Craft bug. See this question for more info: <a href="https://craftcms.stackexchange.com/questions/1709/how-do-i-get-matrix-elements-to-copy-their-content-across-language-locales">How do I get Matrix elements to copy their content across language Locales?</a></p>

CC BY-SA 3.0
2017-01-13T17:00:02.270Z
Hi carlcs, thanks for responding! I have tried setting new locales with the fields set to not translatable as well as trying with the fields set to translatable (after seeing the question you linked). This still is not working, very strange
Paul Mckenna
CC BY-SA 3.0
2017-01-14T10:22:22.107Z
See original post for solution to this particular problem, although everything carlcs said was right, I also needed to update my asset indexes directly after adding a locale.
Paul Mckenna
CC BY-SA 3.0
2017-01-13T16:08:26.903Z
2017-01-13T16:08:26.903Z
2017-04-13T12:50:59.930Z
carlcs
<p>I have a site made in English and need to add another locale that will be almost identical to the original site. However while adding new locales everything bar the asset entries are being copied. This is a problem as there are already many articles with image asset fields and new articles are not copying assets across locales either.</p>

<p>I have tried making the asset field Translatable and Not Translatable. These fields are not in a matrix.  </p>

<p>UPDATE: Solved - What was needed was to use the Update Asset Indexes tool in the settings of craft. If I do this just after creating a new Locale, before doing anything else, when my articles are created they know where to look for their assets. So relieved </p>

CC BY-SA 3.0
2017-01-13T15:59:29.187Z
Possible duplicate of [How do I get Matrix elements to copy their content across language Locales?](http://craftcms.stackexchange.com/questions/1709/how-do-i-get-matrix-elements-to-copy-their-content-across-language-locales)
carlcs
CC BY-SA 3.0
2017-01-13T18:14:49.713Z
as stated in my question, I had tried the suggestion laid out in the proposed duplicate and noted that my problem was not with a matrix but a normal asset field
Paul Mckenna
CC BY-SA 3.0
2017-01-13T18:45:52.787Z
*"new articles are not copying assets across locales either."* – you have an assets field which is not set to be translatable and the assets selected are different between locales? I can hardly believe that tbh…
carlcs
CC BY-SA 3.0
2017-01-14T09:41:36.437Z
I know right? It was working on my local version of the site but when I tried it on live it's still not working. I've tried every permutation I can think of. think it must be a bug
Paul Mckenna
CC BY-SA 3.0
2017-01-15T04:38:31.273Z
Looks like you found a solution, @PaulMckenna.  Would you mind adding that as an official answer instead of an edit to your original question?
Brad Bell
CC BY-SA 3.0
2017-01-15T15:29:55.000Z
Sure @BradBell , popped it down below, learned a lot with this task so hopefully will be able to answer some more posts, not just my own
Paul Mckenna
CC BY-SA 3.0
2017-01-17T08:51:10.570Z
@BradBell have you heard of this problem before? I never needed to do anything like this after adding a locale, it sounds like a bug to me. What irritates me the most is that non translatable asset fields get out of sync.
carlcs
<assets><localization>
Locales - New locales not copying assets across
# Locales - New locales not copying assets across

(Asked by: username_0 on 2017-01-13)

I have a site made in English and need to add another locale that will be almost identical to the original site. However while adding new locales everything bar the asset entries are being copied. This is a problem as there are already many articles with image asset fields and new articles are not copying assets across locales either.

I have tried making the asset field Translatable and Not Translatable. These fields are not in a matrix.

UPDATE: Solved - What was needed was to use the Update Asset Indexes tool in the settings of craft. If I do this just after creating a new Locale, before doing anything else, when my articles are created they know where to look for their assets. So relieved

**Tags:** assets, localization

> **Comments:**
> **username_1**: Possible duplicate of [How do I get Matrix elements to copy their content across language Locales?](http://craftcms.stackexchange.com/questions/1709/how-do-i-get-matrix-elements-to-copy-their-content-across-language-locales)  
> **username_0**: as stated in my question, I had tried the suggestion laid out in the proposed duplicate and noted that my problem was not with a matrix but a normal asset field  
> **username_1**: *"new articles are not copying assets across locales either."* – you have an assets field which is not set to be translatable and the assets selected are different between locales? I can hardly believe that tbh…  
> **username_0**: I know right? It was working on my local version of the site but when I tried it on live it's still not working. I've tried every permutation I can think of. think it must be a bug  
> **username_2**: Looks like you found a solution, @PaulMckenna.  Would you mind adding that as an official answer instead of an edit to your original question?  
> **username_0**: Sure @BradBell , popped it down below, learned a lot with this task so hopefully will be able to answer some more posts, not just my own  
> **username_1**: @BradBell have you heard of this problem before? I never needed to do anything like this after adding a locale, it sounds like a bug to me. What irritates me the most is that non translatable asset fields get out of sync.  

---

## 2 answers

### Answer by username_0 on 2017-01-15. Score: 2

Solved - What was needed was to use the Update Asset Indexes tool in the settings of craft. If I do this just after creating a new Locale, before doing anything else, when my articles are created they know where to look for their assets. So relieved

Also noticed that to get a matrix to copy across locales (as well as setting the matrix field to NOT TRANSLATABLE and the fields within the matrix to TRANSLATABLE) it was necessary to do a slight change to the original matrix after creating a new asset (such as adding a space after the title). This forced the matrix to copy across.

Hope this helps someone else


---

### Answer by username_1 on 2017-01-13. Score: 1

If the Asset field is set up to be **not translatable**, the selected assets should actually be the same across all of your locales.

If it is set up to be **translatable**, it doesn’t copy over the selection on the first save (or when a new locale was added) because of a Craft bug. See this question for more info: [How do I get Matrix elements to copy their content across language Locales?](https://craftcms.stackexchange.com/questions/1709/how-do-i-get-matrix-elements-to-copy-their-content-across-language-locales)

> **Comments:**
> **username_0**: Hi username_1, thanks for responding! I have tried setting new locales with the fields set to not translatable as well as trying with the fields set to translatable (after seeing the question you linked). This still is not working, very strange  
> **username_0**: See original post for solution to this particular problem, although everything username_1 said was right, I also needed to update my asset indexes directly after adding a locale.  

---

