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

Untranslatable string "Please enter the same value again." #5956

Closed
jernejh opened this issue Aug 3, 2016 · 11 comments
Closed

Untranslatable string "Please enter the same value again." #5956

jernejh opened this issue Aug 3, 2016 · 11 comments
Assignees
Labels
Area: Frontend bug report Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@jernejh
Copy link

jernejh commented Aug 3, 2016

Preconditions

Version: Magento 2.1

Steps to reproduce

  1. When creating new user account in the storefront, if a user does not enter the same password twice, this untranslatable string occurs.

Expected result

  1. The message Please enter the same value again. should be translatable, but is not - no such string was generated with magento i18n:collect-phrases tool

Actual result

capture

@grasdaggel
Copy link

This bug is existent as early of 2.0.6 and 2.0.4 at least.

@odubovyk odubovyk self-assigned this Aug 22, 2016
@magento-engcom-team magento-engcom-team added bug report Area: Frontend Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed labels Sep 11, 2017
@magento-engcom-team magento-engcom-team added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Sep 28, 2017
@magento-engcom-team
Copy link
Contributor

@jernejh, thank you for your report.
We've created internal ticket(s) MAGETWO-80318 to track progress on the issue.

@JeroenVanLeusden
Copy link
Member

I'm working on it #SQUASHTOBERFEST

@dan-advantec
Copy link

Thanks @JeroenVanLeusden - how did you get on with this? It still appears to be an issue in 2.2.0

@JeroenVanLeusden
Copy link
Member

@dan-advantec I see merging of the PR started earlier today. Once merged, it will be released in 2.2.1 or 2.2.2.

@magento-team
Copy link
Contributor

Internal ticket to track issue progress: MAGETWO-81970

@okorshenko
Copy link
Contributor

The issue has been fixed in 2.2-develop branch and will be available with 2.2.2 release soon

@sadon
Copy link

sadon commented Dec 28, 2017

I've reproduced it in 2.2.2

@LKarklins
Copy link

Reproduced in 2.2.8

@angelo983
Copy link
Member

Reproduced in 2.1.18

@zaheerbadi
Copy link

reproduced in 2.4 too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend bug report Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests