You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You chose the locale field from Polylang to distinguish option keys (eg. options_fr_FR_my_key, options_en_US_my_key, etc.). The problem is that you can store multiple languages with the same locale whereas you can't with the same slug. Polylang forbids it.
Polylang isn't always used in a multilingual site. It can be used for a multi country site (you could have the same locale for two or more countries and not necessarily use sub locale).
This is of course quite an edge case issue but I think it's worth to be noticed and should be fixed in a future major release because it would introduce a BC issue.
The text was updated successfully, but these errors were encountered:
nlemoine
changed the title
Wrong language field used for option key
Wrong language field used in option key
Jun 7, 2019
Version information
You chose the
locale
field from Polylang to distinguish option keys (eg.options_fr_FR_my_key
,options_en_US_my_key
, etc.). The problem is that you can store multiple languages with the same locale whereas you can't with the sameslug
. Polylang forbids it.Polylang isn't always used in a multilingual site. It can be used for a multi country site (you could have the same locale for two or more countries and not necessarily use sub locale).
This is of course quite an edge case issue but I think it's worth to be noticed and should be fixed in a future major release because it would introduce a BC issue.
The text was updated successfully, but these errors were encountered: