• Resolved Nilo Velez

    (@nilovelez)


    WordFence has a default option that changes the default WP login errors to prevent and attacker form figuring out if a user exists in that site.

    The problem is that WordFence is not properly prepared for localization:
    https://translate.www.ads-software.com/locale/es/default/wp-plugins/wordfence

    and the notice shows up in English:

    The translation of that string to es_ES should be: “ERROR: El usuario o contrase?a que has introducido no son correctos. ?Olvidaste tu contrase?a?”

    Is there any way to contribute to the translation?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi Nilo,

    Thanks for your interest in having Wordfence translated into other languages, as Tim mentioned on this thread, internationalization is on our product road map and we hope to deliver this feature in the near future, it takes time to prepare the code base for a reliable translation process along with developing all other amazing security related features on the road map as well.

    We have a ticket opened regarding this “Login Error” message translation and I’ve updated it with your input here as well.

    Thanks.

    Thread Starter Nilo Velez

    (@nilovelez)

    I understand it’s a big deal to prepare all the WordFence codebase for localization, but having the front-end strings translated might be enough.

    There are only a few strings that regular users would ever see from WordFence, and the “login error” in this thread is also used for reducing the information a potential attacker can get.

    Sorry for my insistence, but you have to underderstand WordFence is the most used untranslatable plugin in the WordPress directory:
    https://wp-info.org/plugin-top120/

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Login Errors are not localized’ is closed to new replies.