Hi @karlemilnikka, thanks for highlighting these.
Whilst we will require community translations for many languages to be available to our customers, we do have plans to translate the strings within the Login Security standalone plugin, which would in turn make these strings translatable in the Login Security module of Wordfence itself. I’ve found a ticket for this to be included in a not-too-distant update, but I am unable to provide exact milestones or possible delivery dates here on the forums.
I have passed your request on to the development team as each request for a feature can strengthen its case for inclusion in the plugin.
Thanks,
Peter.
This is just a quick update to confirm that the issue persists in Wordfence 7.9.2. It wasn’t supposed to be addressed with the update according to the changelog. This comment is just to inform bypassing readers.
Thanks @karlemilnikka for the update,
As with this topic, marking “resolved” on bug/feature requests doesn’t mean we believe the work to be complete, but as we can’t provide updates with ongoing development, it means we have passed it on to the development team (and it’s been viewed/acknowledged). This status does not affect how searchable a topic is for other users looking up the same information.
Changelog: https://wordpress.org/plugins/wordfence/#developers
Blog: https://www.wordfence.com/blog/
Thanks,
Peter.
Oh. That’s unfortunate, but I understand.
@wfpeter I mark this topic as unresolved again since the Wordfence 2.10.0 update was supposed to address this bug (according to the changelog).
The issue is addressed with the release of today’s Wordfence 7.10.1. Thank you.
