<p>You could have a single News section that is enabled for each of the locales, and choose which locale each entry should target from their Edit pages.</p>

<p>To make it easer on the authors, you can set the default status to Disabled for each of the locales, from the section’s settings. Then when creating a new entry, the authors only have to enable the one locale that they actually want the entry to be published for.</p>

<p><strong>Update</strong></p>

<p>As of <a href="https://craftcms.com/changelog#2-6-2972" rel="nofollow noreferrer">Craft 2.6.2972</a>, you can configure the Entries index to only show entries that are enabled for the selected locale by installing the <a href="https://github.com/lindseydiloreto/craft-cpjs" rel="nofollow noreferrer">CP JS</a> plugin, and pasting this code into its “Additional JavaScript” setting:</p>



<pre class="lang-js prettyprint-override"><code>Craft.defaultIndexCriteria.localeEnabled = true;
</code></pre>

<p>You also may want to add this bit, to ensure that entries’ locale statuses are switched on by default from the Edit Entry page, so they don’t get lost in the entry index, which is now configured to only show locale-enabled entries:</p>

<pre class="lang-js prettyprint-override"><code>$(document).ready(function() {
    var ls = $('#locales .lightswitch').data('lightswitch');
    if (ls) {
        ls.turnOn();
    }
});
</code></pre>

CC BY-SA 3.0
2017-04-11T14:18:00.027Z
"and choose which locale each entry should target from their Edit pages" - by only giving them permission for that locale you mean?
Jan Henckens
CC BY-SA 3.0
2017-04-11T17:43:46.250Z
@JanHenckens Not necessarily. If you have a section that's enabled for multiple locales, the Edit Entry pages will have a bunch of small status toggles – one per locale. So you can have an entry that is visible on the English site but not on the German site, etc.
Brandon Kelly
CC BY-SA 3.0
2017-04-12T10:17:53.637Z
That still leaves the English entry visible in the German backend overview, even though it's not translated in German. That's what we're trying to avoid.
Jan Henckens
CC BY-SA 3.0
2017-04-12T23:32:45.483Z
@JanHenckens Yep, in this case that’s not a great UX. Updated my answer with how you can hide the undesired entries, as of (just-released) Craft 2.6.2972.
Brandon Kelly
CC BY-SA 3.0
2017-06-30T07:14:41.047Z
Thanks for the update but that doesn't work on our end. There's no data attribute called lightswitch.
Jan Henckens
CC BY-SA 3.0
2017-07-03T16:16:17.167Z
@JanHenckens Sorry, fixed.
Brandon Kelly
CC BY-SA 3.0
2017-04-11T14:10:21.097Z
2017-07-03T16:15:43.667Z
2017-07-03T16:15:43.667Z
Brandon Kelly
<p>Not so much a technical question as a how-to/best practice one, here goes:</p>

<p>I'm building out a site that has 3 content-types (channels), a structure and a bunch of singles.</p>

<p>The site has <strong>35 locales</strong>.</p>

<p>The pages &amp; singles consist of normal translated content. </p>

<p>But the channels should be separate in each locale. Meaning, for example, that news items from <code>en_UK</code> should not be translatable to <code>jp_JA</code>. Content will be managed by a different user/group per locale and they should only see content published in their locale, not translatable entries from others.</p>

<p>The "best" solution we've come up with so far is to create a channel per locale. But that adds up quickly (3 x 35...), not to mention managing fields and permissions for each channel separately.</p>

<p>Is there a way to simplify this or are we going to have to bite the bullet?</p>

<p><em>Craft 3 and multisite sounds like a dream for this but sadly we can't wait for that</em> </p>

<localization><best-practice>
Scaling channels with 35 locales
# Scaling channels with 35 locales

(Asked by: username_0 on 2017-04-11)

Not so much a technical question as a how-to/best practice one, here goes:

I'm building out a site that has 3 content-types (channels), a structure and a bunch of singles.

The site has **35 locales**.

The pages & singles consist of normal translated content.

But the channels should be separate in each locale. Meaning, for example, that news items from `en_UK` should not be translatable to `jp_JA`. Content will be managed by a different user/group per locale and they should only see content published in their locale, not translatable entries from others.

The "best" solution we've come up with so far is to create a channel per locale. But that adds up quickly (3 x 35...), not to mention managing fields and permissions for each channel separately.

Is there a way to simplify this or are we going to have to bite the bullet?

*Craft 3 and multisite sounds like a dream for this but sadly we can't wait for that*

**Tags:** localization, best-practice

---

## 1 answers

### Answer by username_1 on 2017-04-11. Score: 6 | Accepted answer

You could have a single News section that is enabled for each of the locales, and choose which locale each entry should target from their Edit pages.
To make it easer on the authors, you can set the default status to Disabled for each of the locales, from the section’s settings. Then when creating a new entry, the authors only have to enable the one locale that they actually want the entry to be published for.
Update
As of Craft 2.6.2972, you can configure the Entries index to only show entries that are enabled for the selected locale by installing the CP JS plugin, and pasting this code into its “Additional JavaScript” setting:
Craft.defaultIndexCriteria.localeEnabled = true;

You also may want to add this bit, to ensure that entries’ locale statuses are switched on by default from the Edit Entry page, so they don’t get lost in the entry index, which is now configured to only show locale-enabled entries:
$(document).ready(function() {
    var ls = $('#locales .lightswitch').data('lightswitch');
    if (ls) {
        ls.turnOn();
    }
});

> **Comments:**
> **username_0**: "and choose which locale each entry should target from their Edit pages" - by only giving them permission for that locale you mean?  
> **username_1**: @JanHenckens Not necessarily. If you have a section that's enabled for multiple locales, the Edit Entry pages will have a bunch of small status toggles – one per locale. So you can have an entry that is visible on the English site but not on the German site, etc.  
> **username_0**: That still leaves the English entry visible in the German backend overview, even though it's not translated in German. That's what we're trying to avoid.  
> **username_1**: @JanHenckens Yep, in this case that’s not a great UX. Updated my answer with how you can hide the undesired entries, as of (just-released) Craft 2.6.2972.  
> **username_0**: Thanks for the update but that doesn't work on our end. There's no data attribute called lightswitch.  
> **username_1**: @JanHenckens Sorry, fixed.  

---

