miikka
Maven
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: Using Quick Reply outside ForumMessage
thanks VarunGrazitti I'm working on a custom navigation where ideally I'd like to reuse the existing quick reply logic if possible. So I'll investigate if there's a feasible way of placing at least some of the code within Forum Message but if that starts to like a hack, then it's time for some custom development :smileyhappy: Might be easier just trying to tap into the existing event listeners and ajax calls while doing custom code for the UI bit. One other option is to use jQuery to tweak the markup but that sounds relatively hacky as well. Cheers, .M171Views0likes2CommentsUsing Quick Reply outside ForumMessage
Hi, has anybody tried and successfully used quick-reply-button and quick-reply outside the default location of Forum Message? I already tested just placing these in a custom location and obviously they do not work directly so maybe there's some little hack which for this? Cheers, .M219Views0likes4CommentsRe: Updating user profile language through REST API v1 now broken
Hi ChiaraS, yes, we are doing a redirect to a new page after the API call to save the changed language. And it more and more looks like it's related to some caching on some level, just need to understand where exactly.322Views0likes0CommentsRe: Updating user profile language through REST API v1 now broken
One interesting observation from our investigations, this could be somehow related to caching. As when you change language using one of the two dropdown menus, a URL like this will be called: https://community-stage.skype.com/?setlang=XX where XX is the identifier of the selected language, for example 'en', 'de', 'es' and so on. For authenticated users on our stage changing language does not really work at the moment but seems to work (could 100%) when you force the page to be loaded, for example: https://community-stage.skype.com/?setlang=es?ffdsdfsdfsdfsdf So I'm wondering whether the request gets cached and instead of actually executing the related business logic, a cached response is returned instead.353Views0likes2CommentsRe: Updating user profile language through REST API v1 now broken
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:355Views0likes3CommentsRe: Updating user profile language through REST API v1 now broken
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:348Views0likes5CommentsRe: Updating user profile language through REST API v1 now broken
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, .M318Views0likes7CommentsUpdating user profile language through REST API v1 now broken
Hi, we have been using this bit of code to change the language setting for a user: <#assign update_lang_setting = rest("/users/self/profiles/name/language/set?value=${language}") /> This has worked well up until version 16.5 but now it seems to be broken or at least not working reliably enough (it's used in the page initialization script so it's hard to see what goes wrong). So has something changed in 16.6 or in 16.7 which could cause this? Cheers, .M507Views0likes9Comments