# "Login by email" switches to incorrect strings when "hide email address" activated

**URL:** <https://meta.discourse.org/t/login-by-email-switches-to-incorrect-strings-when-hide-email-address-activated/143432>\
**Category:** Bug\
**Created:** [5 maart 2020 om 18:07 UTC](https://meta.discourse.org/t/login-by-email-switches-to-incorrect-strings-when-hide-email-address-activated/143432 "2020-03-05T18:07:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)\
**Post date:** [6 maart 2020 om 18:45 UTC](https://meta.discourse.org/t/login-by-email-switches-to-incorrect-strings-when-hide-email-address-activated/143432/3 "2020-03-06T18:45:31Z")

</div>

> [@codinghorror](#):
>
> But if we have the other copy we should be using it in this scenario @eviltrout

Sorry if this was confusing. The bug as perceived, is that when (and **only** when) `hide email address taken` is set active, **and** non-matching values are entered for email-based login:

Instead of displaying the intentionally-ambiguous **js.email\_login.complete\_email** and **js.email\_login.complete\_username** strings, it instead (mistakenly) displays a false positive using strings **js.email\_login.complete\_email\_found** and **js.email\_login.complete\_username\_found**.

If the site setting is disabled (default) it correctly displays “no match found” strings.

---

_[View the full topic](https://meta.discourse.org/t/login-by-email-switches-to-incorrect-strings-when-hide-email-address-activated/143432)._
