Timeline for Activate correct locale upon front-end entry
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 23, 2015 at 18:26 | vote | accept | Chase Giunta | ||
| Jun 23, 2015 at 18:23 | comment | added | Chase Giunta |
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.
|
|
| Jun 23, 2015 at 18:02 | comment | added | Brad Bell♦ |
And using <input type="hidden" name="locale" value="en_us"> and <input type="hidden" name="localeEnabled" value="1"> doesn't do it?
|
|
| Jun 23, 2015 at 17:47 | comment | added | Chase Giunta |
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)
|
|
| Jun 23, 2015 at 17:37 | comment | added | Brad Bell♦ | Why not just set the locales to be disabled by default under your section's settings? | |
| Jun 23, 2015 at 16:31 | history | edited | Chase Giunta | CC BY-SA 3.0 |
made question more specific, clearer
|
| Jun 20, 2015 at 21:39 | vote | accept | Chase Giunta | ||
| Jun 23, 2015 at 3:27 | |||||
| Jun 20, 2015 at 21:39 | answer | added | Chase Giunta | timeline score: 3 | |
| Jun 11, 2015 at 22:10 | history | asked | Chase Giunta | CC BY-SA 3.0 |