Async usage of elgg.echo fails to work correctly, if the logged in user has set another language than the English to be used. You will always get any language strings in English regardless what language is defined as site language and/or user language.
Is there any specific way to define an AMD module (i.e. a specific requirement) for elgg.echo to work correctly within AMD? I noticed that there are some open issues about this problem at github but I've failed to understand if there's at least any workaround implemented in 1.X / 2.X or not.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- iionly@iionly
iionly - 0 likes
You must log in to post replies.It seems to me it's a bug in Elgg 2 because it works on Elgg 1.10/1.11. Issue opened at https://github.com/Elgg/Elgg/issues/8958.