Answers.Body: <p>On localized sites, each entry has two statuses: the primary entry status (the big “Status” lightswitch field at the bottom of the sidebar) and the locale-specific statuses (the small lightswitch field beside the currently selected locale).</p>
  
  <p>For an entry to be enabled, both of those lightswitches have to be turned on. But only one of them has to be turned off for it to be disabled.</p>
  
  <p>The confusion here is because the entry index page doesn’t communicate <em>why</em> an entry is disabled - whether it’s because the entry’s primary status is disabled, or just because the current locale’s status is disabled.</p>
  
  <p>So, when you have an entry whose primary status is disabled, but its locale-specific statuses are enabled, enabling the entry from the index page is going to end up enabling it across all locales, not just the one you’re currently looking at.</p>
  
  <p>If this is a common problem for you, you may want to go into your section’s settings and set all of the default locale statuses to disabled. So you will always have to explicitly enable a locale’s status before it starts showing up for that locale.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-09T15:57:21.817Z
Answers.Text: Thanks for the follow-up, Brandon. I'll work around it. It would be nice, though, to have the ability to bulk change locale-specific statuses as the UI would seem to indicate is possible.
Answers.UserDisplayName: Chris
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-09T14:28:06.973Z
Answers.LastActivityDate: 2015-02-09T14:28:06.973Z
Answers.UserDisplayName: Brandon Kelly
Answers.Body: <p>I agree this is confusing.</p>
  
  <p>If you are editing the entry, you can change the status per/locale by selecting the locale in the box in the upper right corner, and then using the lightswitch next to the selected locale.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-09T02:28:17.633Z
Answers.Text: Thank you for the comment. However, I'm well aware of the per-entry statuses and this doesn't address the issue at hand.
Answers.UserDisplayName: Chris
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-09T14:43:49.570Z
Answers.Text: It does address your issue, @cliquenoir. Because this is the only way to set the per locale status on an entry.
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-09T16:00:11.807Z
Answers.Text: I'm sorry, but I disagree. This was not a how-to question. I was already aware of how to change locale-specific statuses from within the entry which is how this originated. My question instead was directed at the UI which, as some would agree, does introduce the potential for unexpected results.
Answers.UserDisplayName: Chris
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-08T23:40:09.943Z
Answers.LastActivityDate: 2015-02-08T23:40:09.943Z
Answers.UserDisplayName: Marion Newlevant
Body: <p>I'm not certain if this is expected behavior but if so the user experience is confusing/unexpected:</p>
  
  <p>When viewing a list of entries in the control panel, swapping between locales shows the expected statuses--either enabled or disabled--for each entry. Accordingly, example, an entry that is enabled in English but disabled in Spanish, is properly displayed as such. However, making a change to the status when switched to either locale applies the status to <em>both</em> locales, rather than just the selected locale.</p>
  
  <p>This seems to indicate that adjusting statuses through the entries list applies only to the entry's master enabled/disabled status, not the selected locale's status (which was my expectation). Should this be the be case? I found out the hard way by switching to my Spanish locale, selecting all entries, and then setting their status to disabled. Switching to the other status showed that they too had been disabled. Bummer.</p>
  
  <p>Any thoughts or similar experiences? Did I miss something in the docs?</p>
  
  <p>Cheers.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-02-09T03:10:09.817Z
Comments.Text: This probably falls under 'feature request' or 'bug report'. I would suggest sending the issue to P&T or posting it on Craft Google+.
Comments.UserDisplayName: Douglas McDonald
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-02-09T05:17:44.317Z
Comments.Text: I agree with Douglas... This is simultaneously a bug report and a feature request. I'd highly recommend contacting P&T directly to get their thoughts on the matter. (support@buildwithcraft.com)
Comments.UserDisplayName: Lindsey D
Tags: <entries><localization><status>
Title: Changing status via entries list in one locale also (unexpectedly) changes status in other locale(s)
ThreadText: # Changing status via entries list in one locale also (unexpectedly) changes status in other locale(s)
  
  (Asked by: username_0 on 2015-02-08)
  
  I'm not certain if this is expected behavior but if so the user experience is confusing/unexpected:
  
  When viewing a list of entries in the control panel, swapping between locales shows the expected statuses--either enabled or disabled--for each entry. Accordingly, example, an entry that is enabled in English but disabled in Spanish, is properly displayed as such. However, making a change to the status when switched to either locale applies the status to *both* locales, rather than just the selected locale.
  
  This seems to indicate that adjusting statuses through the entries list applies only to the entry's master enabled/disabled status, not the selected locale's status (which was my expectation). Should this be the be case? I found out the hard way by switching to my Spanish locale, selecting all entries, and then setting their status to disabled. Switching to the other status showed that they too had been disabled. Bummer.
  
  Any thoughts or similar experiences? Did I miss something in the docs?
  
  Cheers.
  
  **Tags:** entries, localization, status
  
  > **Comments:**
  > **username_1**: This probably falls under 'feature request' or 'bug report'. I would suggest sending the issue to P&T or posting it on Craft Google+.  
  > **username_2**: I agree with username_1... This is simultaneously a bug report and a feature request. I'd highly recommend contacting P&T directly to get their thoughts on the matter. (support@buildwithcraft.com)  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2015-02-09. Score: 2 | Accepted answer
  
  On localized sites, each entry has two statuses: the primary entry status (the big “Status” lightswitch field at the bottom of the sidebar) and the locale-specific statuses (the small lightswitch field beside the currently selected locale).
  
  For an entry to be enabled, both of those lightswitches have to be turned on. But only one of them has to be turned off for it to be disabled.
  
  The confusion here is because the entry index page doesn’t communicate *why* an entry is disabled - whether it’s because the entry’s primary status is disabled, or just because the current locale’s status is disabled.
  
  So, when you have an entry whose primary status is disabled, but its locale-specific statuses are enabled, enabling the entry from the index page is going to end up enabling it across all locales, not just the one you’re currently looking at.
  
  If this is a common problem for you, you may want to go into your section’s settings and set all of the default locale statuses to disabled. So you will always have to explicitly enable a locale’s status before it starts showing up for that locale.
  
  > **Comments:**
  > **username_0**: Thanks for the follow-up, username_3. I'll work around it. It would be nice, though, to have the ability to bulk change locale-specific statuses as the UI would seem to indicate is possible.  
  
  ---
  
  ### Answer by username_4 on 2015-02-08. Score: 2
  
  I agree this is confusing.
  
  If you are editing the entry, you can change the status per/locale by selecting the locale in the box in the upper right corner, and then using the lightswitch next to the selected locale.
  
  > **Comments:**
  > **username_0**: Thank you for the comment. However, I'm well aware of the per-entry statuses and this doesn't address the issue at hand.  
  > **username_5**: It does address your issue, @cliquenoir. Because this is the only way to set the per locale status on an entry.  
  > **username_0**: I'm sorry, but I disagree. This was not a how-to question. I was already aware of how to change locale-specific statuses from within the entry which is how this originated. My question instead was directed at the UI which, as some would agree, does introduce the potential for unexpected results.  
  
  ---
  
  