Answers.Body: <p>Using <code>&lt;input type="hidden" name="locale" value="en_us”&gt;</code> works as expected, as long as the section settings for that entry has all the locales set to be disabled by default.</p>
  
  <p>Upon creating a new entry via front-end form, only the specific locale was activated. However, creating the entry in the admin panel, they are all left off by default. (Seems correct, just remind any clients that might be using the admin panel to enable whichever locale).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-20T21:39:27.490Z
Answers.LastActivityDate: 2015-06-23T18:26:24.780Z
Answers.LastEditDate: 2015-06-23T18:26:24.780Z
Answers.UserDisplayName: Chase Giunta
Body: <p>Is there any way, upon creating new entries via front-end form, to <em><strong>not</strong></em> have all locale versions of those entries active?</p>
  
  <p>I’d like to think I could just set something like<br>
  <code>&lt;input type="hidden" name="locale" value="en_us”&gt;</code></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-06-23T17:37:34.200Z
Comments.Text: Why not just set the locales to be disabled by default under your section's settings?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-06-23T17:47:13.463Z
Comments.Text: That's what I originally did (see answer below). Yet it still doesn't activate the correct locale. Submitting a new entry *did* activate a locale, but not the correct one (a form filled out on `en_us` domain should trigger the `en_us` locale only). Instead it triggered the very first in the list of locales (not sure whether it detected that from locale ID or alphabetical, in my case)
Comments.UserDisplayName: Chase Giunta
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-06-23T18:02:47.583Z
Comments.Text: And using `<input type="hidden" name="locale" value="en_us">`  and `<input type="hidden" name="localeEnabled" value="1">` doesn't do it?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-06-23T18:23:09.143Z
Comments.Text: Yes. Yes it does. I wasn't sure `<input type="hidden" name="locale" value="en_us">` was even a thing because I couldn't find documentation on it, so I removed it- assuming saving an entry from my locale would trigger the correct one. I'll update the answer. Thanks.
Comments.UserDisplayName: Chase Giunta
Tags: <entries><localization><frontend>
Title: Activate correct locale upon front-end entry
ThreadText: # Activate correct locale upon front-end entry
  
  (Asked by: username_0 on 2015-06-11)
  
  Is there any way, upon creating new entries via front-end form, to ***not*** have all locale versions of those entries active?
  
  I’d like to think I could just set something like  
  `<input type="hidden" name="locale" value="en_us”>`
  
  **Tags:** entries, localization, frontend
  
  > **Comments:**
  > **username_1**: Why not just set the locales to be disabled by default under your section's settings?  
  > **username_0**: That's what I originally did (see answer below). Yet it still doesn't activate the correct locale. Submitting a new entry *did* activate a locale, but not the correct one (a form filled out on `en_us` domain should trigger the `en_us` locale only). Instead it triggered the very first in the list of locales (not sure whether it detected that from locale ID or alphabetical, in my case)  
  > **username_1**: And using `<input type="hidden" name="locale" value="en_us">`  and `<input type="hidden" name="localeEnabled" value="1">` doesn't do it?  
  > **username_0**: Yes. Yes it does. I wasn't sure `<input type="hidden" name="locale" value="en_us">` was even a thing because I couldn't find documentation on it, so I removed it- assuming saving an entry from my locale would trigger the correct one. I'll update the answer. Thanks.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2015-06-20. Score: 3 | Accepted answer
  
  Using `<input type="hidden" name="locale" value="en_us”>` works as expected, as long as the section settings for that entry has all the locales set to be disabled by default.
  
  Upon creating a new entry via front-end form, only the specific locale was activated. However, creating the entry in the admin panel, they are all left off by default. (Seems correct, just remind any clients that might be using the admin panel to enable whichever locale).
  
  
  ---
  
  