Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix translations on customer account page #164

Merged

Conversation

micka-fdz
Copy link
Contributor

Questions Answers
Description? This PR fixes customer account page translations
Type? bug fix
BC breaks? no
Deprecations? no
Fixed ticket? Fixes PrestaShop/PrestaShop#27942.
How to test? See issue

Copy link

@matthieu-rolland matthieu-rolland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your PR @micka-fdz 👍

can you explain how and why you generated these keys ?

@micka-fdz
Copy link
Contributor Author

micka-fdz commented Mar 17, 2022

Hi @matthieu-rolland.

Old version of this module (v1.1.0) have template files for both PS versions:

  • customerPersonalData16.tpl (translation key: customerpersonaldata16)
  • customerPersonalData17.tpl (translation key: customerpersonaldata17)

Today we just have one template file customerPersonalData.tpl (translation key: customerpersonaldata).

In my PR, I just removed translations with customerpersonaldata16 key and rename customerpersonaldata17 key to customerpersonaldata.

Copy link

@matthieu-rolland matthieu-rolland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your information

I'm not sure about renaming customerpersonaldata17 into customerpersonaldata, what if we add a new file for the next major (prestashop 8.0 ?)

@PrestaShop/prestashop-core-developers what do you guys think ? I'm not so familiar with this module

@micka-fdz
Copy link
Contributor Author

micka-fdz commented Mar 22, 2022

@matthieu-rolland module translation system works like that: translation key is equal to file name.

My PR just fixed translations for current template file. It's a common issue on this module.
If we add new file in the future, translation files will have to be regenerated.

Copy link

@matthieu-rolland matthieu-rolland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanx @micka-fdz, sorry for the misunderstanding 👍

Copy link
Contributor

@florine2623 florine2623 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @micka-fdz ,

Thanks for the PR !

Looking good to me.
Tested with multiple different languages, translation is always correct.

This is QA ✅

@Progi1984 Progi1984 added this to the 1.4.1 milestone Mar 24, 2022
@Progi1984 Progi1984 merged commit 88ed1f9 into PrestaShop:dev Mar 24, 2022
@Progi1984
Copy link
Member

Thanks @micka-fdz & @florine2623

@micka-fdz micka-fdz deleted the fix-translations-customer-account branch March 25, 2022 09:19
@matks matks mentioned this pull request Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing translations on psgdpr module
4 participants