<blockquote>
<p>How to avoid singles content to be duplicated accross all sites?</p>
</blockquote>
<p>Singles only exist once, so they don't have propagation settings. You can only choose the sites in which to enable the single section, and the single entry will be propagated to all of them.</p>
<p>You can, however, use translation settings for the fields you use in the single section. For example, if you set each field to be translatable for every site, the field values in the single entry will not be propagated between the sites.</p>
<blockquote>
<p>What are the best propagations rules in the single section and the fields?</p>
</blockquote>
<p>There are no objectively good or bad settings. It depends on what you want to achieve in terms of content modelling and author experience.</p>

CC BY-SA 4.0
2024-03-11T14:18:53.503Z
Thanks for reply. I setup single with "translate for each sites" fields. Event that, I noticed a different behaviour between Craft 3.7.38 and 4.8.0. In 3.7.38, the content entry wasn't duplicated through all sites activate the single, therefore in 4.8.0, the content is duplicated to all sites, I just need to activate the single as empty to new sites. So is it a new behaviour ?
emilie zawadzki
CC BY-SA 4.0
2024-03-13T15:25:03.630Z
@emiliezawadzki Haven't checked out Craft 4.8 yet, but I don't think it changes anything regarding this behaviour. What you might be seeing is the initial propagation of an entry, this always uses copies over the current values of the entry (otherwise, you would get a completely empty entry). So if you activate a single on a new site, you _might_ get contents from another site copied over once (not quite sure though). However, the fields will not be synced again as long as the translation settings are configured accordingly.
MoritzLost
CC BY-SA 4.0
2024-03-05T19:04:32.063Z
2024-03-05T19:04:32.063Z
MoritzLost
<p>How to avoid singles content to be duplicated accross all sites ?</p>
<p>What are the best propagations rules in the single section and the fields ?</p>

<localization><craft4><singles>
4.8.0 - How to avoid singles content to be duplicated accross all sites
# 4.8.0 - How to avoid singles content to be duplicated accross all sites

(Asked by: username_0 on 2024-03-05)

How to avoid singles content to be duplicated accross all sites ?

What are the best propagations rules in the single section and the fields ?

**Tags:** localization, craft4, singles


---

## 1 answers

### Answer by username_1 on 2024-03-05. Score: 1

> How to avoid singles content to be duplicated accross all sites?

Singles only exist once, so they don't have propagation settings. You can only choose the sites in which to enable the single section, and the single entry will be propagated to all of them.

You can, however, use translation settings for the fields you use in the single section. For example, if you set each field to be translatable for every site, the field values in the single entry will not be propagated between the sites.

> What are the best propagations rules in the single section and the fields?

There are no objectively good or bad settings. It depends on what you want to achieve in terms of content modelling and author experience.

> **Comments:**
> **username_0**: Thanks for reply. I setup single with "translate for each sites" fields. Event that, I noticed a different behaviour between Craft 3.7.38 and 4.8.0. In 3.7.38, the content entry wasn't duplicated through all sites activate the single, therefore in 4.8.0, the content is duplicated to all sites, I just need to activate the single as empty to new sites. So is it a new behaviour ?  
> **username_1**: @emiliezawadzki Haven't checked out Craft 4.8 yet, but I don't think it changes anything regarding this behaviour. What you might be seeing is the initial propagation of an entry, this always uses copies over the current values of the entry (otherwise, you would get a completely empty entry). So if you activate a single on a new site, you _might_ get contents from another site copied over once (not quite sure though). However, the fields will not be synced again as long as the translation settings are configured accordingly.  

---

