2

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”>

  • Why not just set the locales to be disabled by default under your section's settings? – Brad Bell Jun 23 '15 at 17:37
  • 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) – Chase Giunta Jun 23 '15 at 17:47
  • And using <input type="hidden" name="locale" value="en_us"> and <input type="hidden" name="localeEnabled" value="1"> doesn't do it? – Brad Bell Jun 23 '15 at 18:02
  • 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. – Chase Giunta Jun 23 '15 at 18:23
3

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).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.