Hi @inoxys, thanks for reaching out.
I’ve run some tests and Wordfence isn’t blocking “Say What?” and I was able to successfully translate some Wordfence plugin strings so the likelihood is an incorrectly set text change (or the text you’re trying to change can’t be translated), or a conflict with another plugin that I don’t have.
If you want to check for a conflict, enable Wordfence and “Say What?” on their own to see if you’re able to change what you need. If you can, then reenable your other plugins until it stops working to find the source of the problem. This test may also need to be done with disabling your theme and instead reverting to a default like Twenty Twenty-Four in certain circumstances. However, this test would still fail if your original text change was incorrect, so I’ll explain my test which could be easily replicated.
In WordPress > Tools > Text changes, I decided that I wanted to change the screen reader text strings for “opens in new tab” to “?bner i ny fane”, which appears in the text domain “wordfence” as required by the Say What? documentation on changing a string.
As they suggest, I viewed the source of a page – in this case Wordfence’s lib/IPTrafList.php – and took note of the following code on line 24 to get that information:
<?php esc_html_e('opens in new tab', 'wordfence') ?>
After saving the change, I viewed the Wordfence > All Options page, right-clicked and inspected one of the grey “?” inline help icons, which showed the change in the live version of the page:
<span class="screen-reader-text"> (?bner i ny fane)</span>
If you have issues translating a different plugin, you’d need to reach out to support for that plugin or “Say What?” itself to see if they can assist.
Many thanks,
Peter.
