Thanks for taking the time to look into this.

With English it works fine, the problem appears when using translations I guess, It happens with Spanish which I'm using for example.

6 days later

Correct, the same thing happens to me with the Spanish language

4 days later

I can confirm this is an issue with the es_ES.phar (Spanish — Spain) language pack in all versions of 1.16.x.

When that pack is installed as a secondary language, and the currently logged in user has selected it as their default language, the Profile page no longer works as expected.

For example, the Preferences and Signature tabs are not clickable, and the user cannot change their password or configure 2FA options.

Fortunately one can go back to Admin Panel> System and disable the Spanish pack. Once the currently logged in user is using English again (or any other language, as far as I can tell) everything works as expected.

2 months later

algonco

I still need to look into this. It’s on my list of things to review during our next cooldown.

Cheers.

    22 days later

    @AdrianC @pablopol24 @stevland @algonco

    I've finally found the issue. So the issue is that whomever accepted the translation for the Every %d minutes string in Spain Spanish language didn't review it well as it had an errant % character (ie. cada %d %minutos). I have accepted the correct version of Cada %d minutos so this issue will be addressed once we release new language pack builds (not set date for this at this time).

    Cheers.

      Hi:
      I modified and repacked the es_ES phar file, with the correction mentioned by @KevinTheJedi but the system does not allow to upload a PHAR file, so it is in ZIP format, just uncompress it.
      If you want to see the PAR file contents, you can use https://phar.scer.io/; seems legit enough and it does work.

      ** attachment removed by admin

        cavp76

        Please do not post custom builds of language packs. It is not verified and could cause issues. Providing instructions on how to accomplish what you did is the preferred option.

        Cheers.

            KevinTheJedi OK Kevin, sorry for the upload... the site I posted above allows anyone to decompress and compress a PHAR file, so it becomes very easy to correct that mistake you identified. Hope anyone with some issues can correct and use their own files.
            Best regards

              Just an update: there's an additional problem with the Spanish es_ES phar... even with the correction noted by Kevin it continues without working correctly as per @stevland and others confirmed... we'll just have to wait for the official correction.

              20 days later
              25 days later
              3 months later

              Hello, using es_AR.phar for me is not an option (we are using es_ES localization).
              I have tried to correct the es_ES.phar doing the following:

              • unpacking it with: php -r '$phar = new Phar("es_ES_new.phar"); $phar->extractTo("./temp/");'
              • editing the wrong file
              • packing it again with: php -r '$phar = new Phar("es_ES_mod.phar"); $phar->buildFromDirectory("./temp/");'
                But it seems .phar created is not good enough because it is not loaded. Am I doing something wrong?

                jdiaz

                You cannot repackage language packs appropriately by doing just that. We have a special packager that does some other things. You can look at the packager code on Github (within the core repo) and see how it packages language packs.

                Cheers.

                    I give up, it is impossible to me create a new phar... Extracting the .phar I got it to work executing the following command:

                    php -d phar.readonly=0 -r '$phar = new Phar("es_ES.phar"); $phar->extractTo("./es_ES");'; chmod 000 es_ES.phar;

                    And editing the affected file, may be somebody find it useful. (chmod 000 is to avoid osTicket to load es_ES.phar until it gets corrected).

                    4 months later

                    Still same issue in v1.17.3; any news on this? it is very frustrating since I'm the only sysadm in the platform and when my password expire I need to change the language in the database in order to be able to change the password...

                      santon

                      Issue been addressed since last release. You need to download the new language pack from our website.

                      Cheers.