1. In lists of objects (p.e. Users), translatable data appears only with internal value ([profileAdministrator]) instead of the translated value ('administrateur').
Not very sexy…
2. When any changes are made in a module for display, there is conflicts between new values or data in the module and recording in 'columnselector' values.
To avoid wrong display, I delete all lines for the concerned entities, so a new recording is done with good data and values (long life to PhpMyAdmin !
But it seems that something has not been provided for clean structural changes…
1. In lists of objects (p.e. Users), translatable data appears only with internal value ([profileAdministrator]) instead of the translated value ('administrateur').
Not very sexy…
It is because "profileAdministrator" is not included in lang.js file.
2. When any changes are made in a module for display, there is conflicts between new values or data in the module and recording in 'columnselector' values.
To avoid wrong display, I delete all lines for the concerned entities, so a new recording is done with good data and values (long life to PhpMyAdmin !
But it seems that something has not been provided for clean structural changes…
Yes, there is
In the fields selector list, click the "reset" button.
1. In lists of objects (p.e. Users), translatable data appears only with internal value ([profileAdministrator]) instead of the translated value ('administrateur').
Not very sexy…
It is because "profileAdministrator" is not included in lang.js file.
No, all values ARE in lang.js files. They comes right in the detail section when an element is selected.
The problem is only in the objects list (top part of the screen)
babynus wrote:
2. When any changes are made in a module for display, there is conflicts between new values or data in the module and recording in 'columnselector' values.
To avoid wrong display, I delete all lines for the concerned entities, so a new recording is done with good data and values (long life to PhpMyAdmin !
But it seems that something has not been provided for clean structural changes…
Yes, there is
In the fields selector list, click the "reset" button.
Where is that “fields selector list”? Not found on any screen, nor in the documentation…
But this has only for effect that "profileAdministrator" is replaced by "[profileAdministrator]", not by the language-translated value.
And what for fields having already a formatting, as colorNameFormatter ?
babynus wrote:
Where is that “fields selector list”? Not found on any screen, nor in the documentation…
Here :
Ah, O.K. Thanks !
I’ll go to bed less dumb, this evening.
But this has only for effect that "profileAdministrator" is replaced by "[profileAdministrator]", not by the language-translated value.
And what for fields having already a formatting, as colorNameFormatter ?
This is because [profileAdministrator] is not found in lang.js file by the javascript code
So you'll need to clean the browser cache to get the translation. Some times, cleaning the cache is not enough, and you may need to close the browser.
I sometimes had difficulties to retrieve the correct translations on javascript side.
Also concider cleaning "server side" cache.
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
Paramétrages de cookies
×
Cookies fonctionnels
Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.
Session
Veuillez vous connecter pour voir vos activités!
Autres cookies
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.