Skip to main content
answered
Source Link

For my specific situation, I was trying to save an entry on the front-end for onlyUsing one of<input type="hidden" name="locale" value="en_us”> works as expected, as long as the locales. I did not realize that in my section settings, for that entry has all the locales were set to be activedisabled by default. Changing this default setting off allowed the desired behavior:

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

EDIT: Unfortunately, I was wrong. This didn't activate the correct locale, it only activates the first locale it hits (either by ID or alphabetical order).

Still seeking an answer.

For my specific situation, I was trying to save an entry on the front-end for only one of the locales. I did not realize that in my section settings, all the locales were set to be active by default. Changing this default setting off allowed the desired behavior:

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

EDIT: Unfortunately, I was wrong. This didn't activate the correct locale, it only activates the first locale it hits (either by ID or alphabetical order).

Still seeking an 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).

added 187 characters in body
Source Link

For my specific situation, I was trying to save an entry on the front-end for only one of the locales. I did not realize that in my section settings, all the locales were set to be active by default. Changing this default setting off allowed the desired behavior:

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

EDIT: Unfortunately, I was wrong. This didn't activate the correct locale, it only activates the first locale it hits (either by ID or alphabetical order).

Still seeking an answer.

For my specific situation, I was trying to save an entry on the front-end for only one of the locales. I did not realize that in my section settings, all the locales were set to be active by default. Changing this default setting off allowed the desired behavior:

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

For my specific situation, I was trying to save an entry on the front-end for only one of the locales. I did not realize that in my section settings, all the locales were set to be active by default. Changing this default setting off allowed the desired behavior:

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

EDIT: Unfortunately, I was wrong. This didn't activate the correct locale, it only activates the first locale it hits (either by ID or alphabetical order).

Still seeking an answer.

Source Link

For my specific situation, I was trying to save an entry on the front-end for only one of the locales. I did not realize that in my section settings, all the locales were set to be active by default. Changing this default setting off allowed the desired behavior:

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