choosing site language AFTER logging in?
I noticed that when you are not logged, you can only see an elgg website in the default language chosen by admin. Wouldn't it be better if a user could choose the language BEFORE registering? How can he know if there is even the possibility to choose his own language OR understand terms and conditions, for example? Is there something I'm not considering?
- rjcalifornia@rjcalifornia
rjcalifornia - 0 likes
- Gerard@gkanters
Gerard - 0 likes
- andreaconsole@andreaconsole
andreaconsole - 0 likes
- Steve Clay@steve_clay
Steve Clay - 0 likes
- Nikolai Shcherbin@rivervanrain
Nikolai Shcherbin - 0 likes
- andreaconsole@andreaconsole
andreaconsole - 0 likes
- Nikolai Shcherbin@rivervanrain
Nikolai Shcherbin - 0 likes
- andreaconsole@andreaconsole
andreaconsole - 0 likes
- andreaconsole@andreaconsole
andreaconsole - 0 likes
- Nikolai Shcherbin@rivervanrain
Nikolai Shcherbin - 0 likes
You must log in to post replies.hmmm that's actually a good suggestion. You could redirect the user to the user settings page on first log in to let him choose his language
Rodolfo Hernandez
Arvixe/Elgg Community Liaison
Detect language based on browser language and switch langugae based on that.
Yes, but how? Do I need a plugin just for this?
I could also prepare a landing page where the guest can select his language and then pass this value to elgg by url: is that possible?
You may want to submit an issue at GitHub. Allowing language set logged out is a good case to consider.
@andreaconsole Did you tried http://community.elgg.org/plugins/384977/2.0/language-selector ?
Hi RvR thank you for the suggestion! I tried it, but I could not make it work: I switched off my theme and enabled the selector from plugin administration panel, but nothing happened to the header
@andreaconsole
If you don't use your own theme then activate 'Show language selector in header?' option in the plugin' settings.
Just edited my answer before reading yours... As I said, nothing happens, and I don't have any strange plugin activated...
I found that setting Minimum language completeness (e.g. 30) is mandatory. Now the plugin works perfectly! Thanks again.
Thanks for debugging ;)