Forum Discussion
Thanks ChiaraS
This specific error message is related to the same topic but applies only for anonymous users. And it's kind of expected as not all languages coming in browser settings are supported. But we can improve the logic so there won't be error messages like this in the log.
Unfortunately the problem we have is related to authenticated users and that bit of code is not executed for them.
Cheers,
.M
I see... I would try to use the user.id instead of self and use restadmin to see if it makes a difference:
<#assign update_lang_setting = restadmin("/users/id/${user.id?c}/profiles/name/language/set?value=${language}") />
- miikka9 years agoMaven
Just tried this but looks like it makes no difference unfortunately. The weird thing is that we haven't touched this code in months and it suddenly started to cause issues. But will keep on troubleshooting :smileyhappy:
- ChiaraS9 years agoLithium Alumni (Retired)
hi miikka
i tried this on another 16.7 instance and works as expected, so the problem is related to some other logic failing inside the common init section.
- miikka9 years agoMaven
Thanks ChiaraS.
And I agree, the API call itself should be trivial and should work as expected.
We haven't changed the related code in several months so I was thinking about it could be because of some other changes (Freemarker updates, object updates etc) which would make the code work differently now as the problems have surfaced.
Another explanation could be horizontal scaling so that the information gets updated in the DB but then there's a delay to propagate the change between DB instances.
Will continue investigating, any pointers are still welcome :smileyhappy:
Related Content
- 3 months ago
- 2 years ago