Category translations are not applied in the "Tree Cascade Dropdown" question
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 58/100
Línea de trabajo
Start by comparing the Tree Cascade Dropdown question with the standard dropdown question for ticket categories, then trace how category labels are loaded for the initial tree and subsequent selections. The fix is complete when translated labels appear at every tree level, including a selectable root, in the logged-in user's language.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Code of Conduct
- I agree to follow this project's Code of Conduct
Is there an existing issue for this?
- I have searched the existing issues
GLPI Version
11.0.8
Plugin version
1.3.0
Bug description
Description
In a form using a "Tree Cascade Dropdown" question bound to ticket categories, the labels listed in the dropdowns are always displayed in their original language — the one used when the categories were created — regardless of the language of the logged-in user.
The translations entered in GLPI for those categories are ignored.
Environment
- advancedforms plugin: 1.3.0
- GLPI: 11.0.x
- Question type: Tree Cascade Dropdown
- Selected item type: Ticket categories
Expected result
The dropdowns display the labels translated into the user's language ("Hardware"), at every level of the tree — the same way a standard dropdown question already does.
Actual result
The dropdowns display the original labels ("Matériel"). Every level is affected: the first level as well as the subsequent levels loaded as the user makes a selection. The root of the tree, when made selectable, is affected too.
Relevant log output
Page URL
No response
Steps To reproduce
No response
Your GLPI setup information
No response
Anything else?
No response
- Lenguaje dominante
- PHP
- Estrellas
- 4
- Forks
- 4
- Merge medio
- 7 d 7 h
- PR fusionados (30 d)
- 3
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pluginsGLPI/advancedforms
-
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
pluginsGLPI/advancedforms#34 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
pluginsGLPI/advancedforms#29 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
pluginsGLPI/advancedforms#28 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
pluginsGLPI/advancedforms#27 ·
-
Fatal Compile Error: Class GlpiPlugin\Advancedforms\Model\QuestionType\TreeCascadeDropdownQuestion Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
pluginsGLPI/advancedforms#24 · 1 comentario ·
Todos los issues de pluginsGLPI/advancedforms
Issues similares
-
priority: p3
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
nextcloud/fulltextsearch#1011 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
phpstan/phpstan-doctrine#794 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Automattic/static-site-importer#1767 ·