Bad label in the menu - version 2.9.0-beta 1

[mab18]

In stable version, label in the menu is (in FR ) "Formulaires", but in the 2.9.0 beta 1 this label is "Forms"

To Reproduce
Install in a FR installation the upgrade 2.9.0 B1

Expected behavior
The label in FR in the menu should be "Formulaires"

Screenshots

[btry]

Hi

I don't reproduce. Maybe there is a caching problem in translations (introduced in GLPI 9.4). Can you try to reset the cache then see if this solves the issue ?

[btry]

Hi

Did you try to reset the cache for translations of GLPI ?

[mab18]

Hi,
I try immediatly, sry 4 delay

[mab18]

It works with actual develop branch.
For me, it's corrected and without reset cache (maybe changes or reset since the time of creation of this issue).
Excellent, but what was the problem ? ;-)
Have a nice day, for me, it's ok with this release now.
Is there any difficults updates who should be tried In this Beta ?

[btry]

The develop branch is for versions 2.8.x. You reported the issue with versions 2.9 (currently support/2.9.0 branch). Then I expect that if you upgrade to 2.9.0-beta the bug will occur again.

I assume there were some changes in translations like a single localizable string converted to a single / plural one.

Is there any difficults updates who should be tried In this Beta ?

I don't understand your question. Do you want to know which parts of the plugin may contain bugs or regressions ?

[mab18]

Ouch...
I was right to precise this... Please, from what branch does I need to download the version (release beta, support 2.9 ?)?
LOL, if you knew where was bugs or regressions, I think it should be easy to correct them ;-)
NO, I speaking about specific tests about developpements made in this version ;-) .

[btry]

the versions 2.9.x (including beta) are un support/2.9.0 for now. When the 1st production release will be ready, this branch will merge in develop.

Bugs or regressions come from undiscovered bugs in previous releases and some new bugs may happen in new features or refactored code. I did an effort to increase automated tests, but there are still lot of them to write. Moreover UI is not automatically tested. A PoC is done but requires time to cover the whole UI.

So I have idea of where may be the bugs, but they are no discovered yet :) Here is the power of the community : build real life cases, more complex than those I build.

[mab18]

And already, you're doing a wonderful job.
I love free software because of that.
So, to test, does I need download from "release 2.9.0/beta.1" or "support/2.9.0" ? It's not clear for me and I am sorry about that.

[btry]

Ignore the branches release/xxxxx these exist only to build a release.

download the snapshot from support/2.9.0

• you will need to download and install composer: https://getcomposer.org
• run it from the folder of the plugin: composer install
• then run vendor/bin/robo build:fa-data

Once done, the development version of the plugin is ready to test

[mab18]

Merci to help me help you ;-)
I have bad news :



Reset does nothing.

[btry]

Ok, I think I found the problem. The above commit fixes it for me. Can you validate it ?

[mab18]

:-))

Excellent !
Comme j'aimerais savoir faire ça... je n'ai que de petites bases en PHP :-(

[btry]

Si vous connaissez bien le langage lui même, lancez vous ;). C'est dur au début, mais il n'y a pas de secret. C'est forgeant qu'on devient forgeron.