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
Bear with me on this one, as I'm not 100% sure if I fully understand what's happening. The problem is the site, configured with NL, EN, and FR languages, refused to save English. Dutch and French work fine. Dutch (NL) is the system-configured cultureKey.
In the Lingua service class' setContentTranslation() method it's trying to load the cultureKey from the context, and skip that language its values if it's the same. I guess as the primary language goes on the resource itself.
For some reason I haven't been able to decipher yet, that line is returning en for me. The cultureKey system setting is set to nl and the (only) context does not have a cultureKey setting. The only reason I can think of it may be using en for me is if it sniffed the browser, but is that supposed to affect the manager? If so that suggests a front-end language may affect what languages can be saved, which wouldn't be great.
Bear with me on this one, as I'm not 100% sure if I fully understand what's happening. The problem is the site, configured with NL, EN, and FR languages, refused to save English. Dutch and French work fine. Dutch (NL) is the system-configured cultureKey.
In the Lingua service class' setContentTranslation() method it's trying to load the cultureKey from the context, and skip that language its values if it's the same. I guess as the primary language goes on the resource itself.
For some reason I haven't been able to decipher yet, that line is returning
en
for me. ThecultureKey
system setting is set tonl
and the (only) context does not have a cultureKey setting. The only reason I can think of it may be usingen
for me is if it sniffed the browser, but is that supposed to affect the manager? If so that suggests a front-end language may affect what languages can be saved, which wouldn't be great.When changing:
to
it once again saves the English and seems to behave as it should. But I'm not sure if that truly is the way to fix it. Feedback would be welcome..
The text was updated successfully, but these errors were encountered: