Category translations are not applied in the "Tree Cascade Dropdown" question
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- PHP
- Stars
- 4
- Forks
- 4
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pluginsGLPI/advancedforms
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
pluginsGLPI/advancedforms#34 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pluginsGLPI/advancedforms#29 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
pluginsGLPI/advancedforms#28 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
pluginsGLPI/advancedforms#27 ·
-
Fatal Compile Error: Class GlpiPlugin\Advancedforms\Model\QuestionType\TreeCascadeDropdownQuestion Open
Difficulty 3/5 1-2 days Newbie friendliness 52/100
pluginsGLPI/advancedforms#24 · 1 comment ·
All issues in pluginsGLPI/advancedforms
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
phpstan/phpstan-doctrine#794 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Automattic/static-site-importer#1767 ·