This is weird. Quip doesn't appear to have a language property, yet it has seven language files, including French. None of the lexicon->load() calls specify a language.
The lexicon uses the manager_language System Setting value when operating in the Manager and the cultureKey System Setting when operating in the front end.
If you create those two as Context Settings for each context, Quip may deliver the correct language for you. Let me know if it works. You'll have to clear the cache files (maybe manually) for it to take effect. You can use the CacheClear extra to clear the cache files quickly and easily.
.key
field type
namespace
name
Base URL base_url / Culture key cultureKey fr Site start site_start 1
Quote from: BobRay at Oct 29, 2018, 10:28 PMWhen i look at the snipest QuipLatestComments, I can see this line:This is weird. Quip doesn't appear to have a language property, yet it has seven language files, including French. None of the lexicon->load() calls specify a language.
The lexicon uses the manager_language System Setting value when operating in the Manager and the cultureKey System Setting when operating in the front end.
If you create those two as Context Settings for each context, Quip may deliver the correct language for you. Let me know if it works. You'll have to clear the cache files (maybe manually) for it to take effect. You can use the CacheClear extra to clear the cache files quickly and easily.
Dear Bobray,
Thank again for your reply, but I did not understand everything
You asked me to create a new context seting. But when I create one for web context, I did not understand which option, I have to select for
key
field type
namespace
name
As I confgiure Babel, for my web context, I already those
Base URL base_url / Culture key cultureKey fr Site start site_start 1
This what you asked me to check? I am a bit confused.
$quip->initialize($modx->context->get('key'))$quip->initialize($modx->context->get('cultureKey'))
Quote from: pierrot1010 at Oct 29, 2018, 10:45 PMQuote from: BobRay at Oct 29, 2018, 10:28 PMWhen i look at the snipest QuipLatestComments, I can see this line:This is weird. Quip doesn't appear to have a language property, yet it has seven language files, including French. None of the lexicon->load() calls specify a language.
The lexicon uses the manager_language System Setting value when operating in the Manager and the cultureKey System Setting when operating in the front end.
If you create those two as Context Settings for each context, Quip may deliver the correct language for you. Let me know if it works. You'll have to clear the cache files (maybe manually) for it to take effect. You can use the CacheClear extra to clear the cache files quickly and easily.
Dear Bobray,
Thank again for your reply, but I did not understand everything
You asked me to create a new context seting. But when I create one for web context, I did not understand which option, I have to select for
key
field type
namespace
name
As I confgiure Babel, for my web context, I already those
Base URL base_url / Culture key cultureKey fr Site start site_start 1
This what you asked me to check? I am a bit confused.
$quip->initialize($modx->context->get('key'))
Would it be an idea to change to
$quip->initialize($modx->context->get('cultureKey'))
manager_language System Setting value when operating in the Manager and the cultureKey System Setting
OK, I belived, I solved my problem.
I have a web site with two language: French and english.
The default language is french.
In context the key of french version (default) is : web
In context the key of english version is: en.
I went to
/core/componment/quip/lexicon/
and I duplicated the 'fr' folder and named it to web.
I uploaded the /core/componment/quip/lexicon/web/ folder and it's wokrs
Morever, when I go to Settings->Lexicons, for the quip namespace, I can see 'web' on the language field.
