Incomplete translations in Backend and Frontend - Magento 2.4.3

[vertic4l]

Preconditions (*)

1. Upgraded from Magento 2.4.1 to 2.4.3

Steps to reproduce (*)

1. set admin user locale to german

Expected result (*)

1. Backend is fully translated as it was with Magento 2.4.1

Actual result (*)

1. Backend is partially translated

---

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @vertic4l. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[mrtuvn]

Can you share screenshot with un-translated parts ?

[vertic4l]

[vertic4l]

Current js-translation.json for the backend with Magento 2.4.3

and here the old js-translation.json from Magento 2.4.1

Over 200+ entries vs 17...

[vertic4l]

@mrtuvn Same issue exists for the frontend as well. there are also just a few translations instead of 200+

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[maksymz]

Hi, @vertic4l !

Don't think this issue is directly related to #31804. I've just checked the translation in clean Magento 2.4.3 without language packs. I have added a translation for one of the phrases from your previous file and it was successfully added to the js-translation.json file. After that I added the following phrases:

• jQuery.mage.__('You have item changes')
• jQuery.mage.__("Test phrase to be 'translated");

Phrases were translated as expected. Untranslated phrases are not added to the file.
The phrase $.mage.__("We don't recognize this file extension.") comes from the JS code defined in the phtml file, so not sure if translation will work for it.

Are you sure the language pack used for the website is compatible with Magento 2.4.3 and it was successfully installed? Try moving the translation to the core file just to see whether the translations work this way or not. Create a file as it does not exist by default - /vendor/magento/language-de_de/de_DE.csv. This is for the test purpose only.

[vertic4l]

Hi @maksymz,

u are right, while upgrading to 2.4.3, i've lost the language pack within the composer.json somehow.
Thanks for pointing me in the right direction.