search

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.
http://www.magento.com
Open Software License 3.0
11.48k stars 9.29k forks source link

Translate messages on password strength #5509

Closed rorteg closed 7 years ago

rorteg commented 8 years ago

Steps to reproduce

  1. Install Magento 2.1
  2. Try to translate the messages on password strength (Translate inline or source)

    Expected result

  3. Translated.

    Actual result

  4. Not translated.
captura de tela 2016-07-06 as 18 06 24

Thanks.

juanitopons commented 7 years ago

@orlangur a quite awful solution. But as you mentioned, I don't see any other way of doing it. Thanks !

mamutawa commented 7 years ago

I Still having this issue with 2.1.8

magento-team commented 7 years ago

Internal ticket to track issue progress: MAGETWO-72250

andidhouse commented 7 years ago

hmmm.. @magento-team two internal tickets to track the issue process of this one?

Internal ticket to track issue progress: MAGETWO-71380 and now Internal ticket to track issue progress: MAGETWO-72250

This is reported over 14 month now and not fixed...

orlangur commented 7 years ago

@andidhouse, there are two mistakes in your comment

  1. MAGETWO-71380 was to track PR which is already delivered to develop
  2. Missed the "reopened this on Jun 9" part in your conclusion about 14 months
andidhouse commented 7 years ago

@orlangur i do not get it - magento makes out a philosophy of bug reporting and tracking. Never seen a platform where it is so complex --> report a bug --> create a internal ticket --> close the ticket --> reopen it again --> deliver it to XY branch etc. etc.

Could you guys not just simply fix the bugs in the new version? It is so time consuming for all which are in the process... Never seen a worst bug tracking and bug fixing workflow 👎

orlangur commented 7 years ago

@andidhouse you are right that some processes, like issue processing on GitHub and 2.1.x fixes backporting with or without Community involvement, are not established/nontransparent yet. The things started to change somewhere around https://community.magento.com/t5/Magento-DevBlog/Update-on-Developer-Experience-Initiatives/ba-p/59704 and of course situation with bugs is not something that can change within days or weeks.

Consider current situation as an inherited tech debt which will, no doubt, be eliminated. By the way, duration of its resolution depends not only on Magento but on amount of Community enthusiasts, like you and me, doing the right things.

Don't try to draw conclusions on state of things as of 12-18 months ago and keep up the good work on raising important issues 👍

andidhouse commented 7 years ago

@orlangur i agree that it takes time to change things - and i also spoke to the m2 management team about it. The "problem" in my mind is not that m2 is not a good system. The problem is that there are way too many bugs - and this since the beginning. The m2 management team agreed to change something here over 1 year ago - but i can not see such things.

Example:

A while ago (i think it was 2.1.7 or 2.1.6) a new magneto version was released. So we all expected here to be some major bugs to be fixed - and hoped for a lot of other bugs to be fixed too. In fact the release was a security? release or something and then, again, in the new versions coming new functions are implemented?

I am not shure what sense it makes to include new functions (which cause new bugs at the moment) when there are such major bugs in the system which are not fixed.

In my opinion this is a bad management. The normal workflow (and i think all developers confirm this) is 1. get rid of ALL the major bugs 2. then think about some new functions to implement.

And this goes on and on and on since the beginning of m2. Instead of working lets say 6 month on all GitHub bugs reported the m2 management decides to "live" with major bugs and implement some new functions. And this is exactly what is the problem in first place in my view.

magento-engcom-team commented 7 years ago

@rorteg, thank you for your report. The issue is already fixed in 2.2.0