A user, 4ong, reported an issue with the interface language after accepting an invitation on Discourse. The interface language defaults to the Discourse default language (e.g., English) instead of maintaining the language detected from the browser or used in the invitation (e.g., French or Russian). 4ong considers this a bug, as it’s not user-friendly, especially in communities based on “invitations only” mode.
osioke asked for the Discourse version and a screen recording of the issue, which 4ong provided. osioke acknowledged the issue and stated that it would be looked into.
pmsuraj sees this as a feature request and proposes adding a site setting to save the user locale based on the browser/OS setting on signup. The issue is marked as pr-welcome, but the team doesn’t have the bandwidth to work on it at the moment.
4ong plans to look into the issue and potentially handle it. They also emphasize the importance of maintaining the interface language consistency, especially in multi-language communities, to avoid confusion and ensure a user-friendly experience.
If it’s a feature request - please move it to a best fit.
I consider this as a bug as it’s really not user friendly for communities based on “invitations only” mode.
@osioke may I ask you to take a brief look on this as well (this topic).
I’m not sure if it’s a bug or intentional functionality, but many users report related complications.
I’m sorry if that’s not your question - I don’t know who to address it to.
Thanks for the detailed report, Anatol. I see this as a feature request, but I do understand the confusion that a user encounters when seeing the site in one language as an anonymous user and another language once they are signed in.
We could use a site setting here that enables saving the user locale based on the browser/OS setting on signup. Currently, we only have the “set interface language for anonymous users from their web browser’s language headers” setting, which is clearly for non-authenticated users.
Marking this as pr-welcome, we don’t have bandwidth at the moment to take on this work, but happy to see it happen.
Ok - I will take a look if I will be able to handle this.
When user don’t know the default language - it can be quite complex for him to go and change the language back to his native.
In multi language communities invites often lead to some particular topic with initial how-to, welcome post…
And that topic (or even whole category) is usually formed in the language of the invitation.
So only interface language changes to default one. And it’s quite inconsistent and not user friendly in this case, imho.