Answers.Body: <p>This is intended behavior – when you first create a new entry, any content you enter will be copied to other sites, up until the point where you either save the entry, or start editing one of the other sites.</p>
  <p>If you’re worried about unintended content getting published in other locales, then I’d suggest you set the other sites’ default statuses to disabled, from your section’s settings. Once Craft 3.5 comes out you’ll have another option as well: sections have a new propagation method option which gives entries control over which sites they should be saved to, so the entry won’t exist at all in other sites up until someone explicitly enables the site for the entry.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-24T12:19:51.943Z
Answers.LastActivityDate: 2020-06-24T12:19:51.943Z
Answers.UserDisplayName: Brandon Kelly
Body: <p>Craft 3.4.20.
  Site is running multiple localizations</p>
  <p>Sections:</p>
  <p><strong>Blog Post</strong>
  Propagation method set to, &quot;<strong>Save entries to all sites enabled for this section</strong>&quot;</p>
  <p><strong>Blog Category</strong> (Structure entry with nothing more than the default Title)</p>
  <p>Blog Post Section entry has a field to relate to our Blog Category Structure. We have a field under our Blog Posts entry with the option, &quot;<strong>Manage relations on a per-site basis</strong>&quot;.</p>
  <hr />
  <p>A Blog Post entry has an entry field to where you can select multiple Blog Category entries from a Structure.</p>
  <p>Issue is that editors publish Blog Posts and may not consider the other locales. You would think the relationship field would take into consideration of the setting, <strong>Manage relations on a per-site basis</strong>.</p>
  <p>When publishing an entry under the Default site (in our case North America), and the publishing editor disregards the other Locales (the toggle drop-down for an entry on publish view), the field data of the entry relationship for &quot;Blog Category&quot; on North America duplicates itself to the Europe relationship field.</p>
  <p>I don't know if this is intentional, or if the <strong>Manage relations on a per-site basis</strong> setting is not being factored in?</p>
  <p>Is there a way to exclude certain fields from being populated with the same localization data as the default entry. I simply thought the field settings, <strong>Manage relations on a per-site basis</strong> would be factored into this and be left null when publishing a North America entry, but Europe, and all the other sites receive that same field relationship value based on North America Blog Post publish. It seems as though there is no way to exclude certain fields from doing this, and is there a solution to this?</p>
  <p>Is it intended for the Section settings <strong>Save entries to all sites enabled for this section</strong> to override this field setting with first publish?</p>
  <p><a href="https://i.sstatic.net/eOCf9.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/eOCf9.png" alt="enter image description here" /></a></p>
  
Tags: <craft3><localization><relations>
Title: Localization Section propagation settings, and related entry field setting "Manage relations on a per-site basis"
ThreadText: # Localization Section propagation settings, and related entry field setting "Manage relations on a per-site basis"
  
  (Asked by: username_0 on 2020-06-23)
  
  Craft 3.4.20.
  Site is running multiple localizations
  
  Sections:
  
  **Blog Post**
  Propagation method set to, "**Save entries to all sites enabled for this section**"
  
  **Blog Category** (Structure entry with nothing more than the default Title)
  
  Blog Post Section entry has a field to relate to our Blog Category Structure. We have a field under our Blog Posts entry with the option, "**Manage relations on a per-site basis**".
  
  ---
  
  A Blog Post entry has an entry field to where you can select multiple Blog Category entries from a Structure.
  
  Issue is that editors publish Blog Posts and may not consider the other locales. You would think the relationship field would take into consideration of the setting, **Manage relations on a per-site basis**.
  
  When publishing an entry under the Default site (in our case North America), and the publishing editor disregards the other Locales (the toggle drop-down for an entry on publish view), the field data of the entry relationship for "Blog Category" on North America duplicates itself to the Europe relationship field.
  
  I don't know if this is intentional, or if the **Manage relations on a per-site basis** setting is not being factored in?
  
  Is there a way to exclude certain fields from being populated with the same localization data as the default entry. I simply thought the field settings, **Manage relations on a per-site basis** would be factored into this and be left null when publishing a North America entry, but Europe, and all the other sites receive that same field relationship value based on North America Blog Post publish. It seems as though there is no way to exclude certain fields from doing this, and is there a solution to this?
  
  Is it intended for the Section settings **Save entries to all sites enabled for this section** to override this field setting with first publish?
  
  [![enter image description here](https://i.sstatic.net/eOCf9.png)](https://i.sstatic.net/eOCf9.png)
  
  **Tags:** craft3, localization, relations
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-06-24. Score: 2 | Accepted answer
  
  This is intended behavior – when you first create a new entry, any content you enter will be copied to other sites, up until the point where you either save the entry, or start editing one of the other sites.
  
  If you’re worried about unintended content getting published in other locales, then I’d suggest you set the other sites’ default statuses to disabled, from your section’s settings. Once Craft 3.5 comes out you’ll have another option as well: sections have a new propagation method option which gives entries control over which sites they should be saved to, so the entry won’t exist at all in other sites up until someone explicitly enables the site for the entry.
  
  
  ---
  
  