| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Prevent people from registering via your disallowed comment keys. | You have to log in to add a translation. | Details |
Original untranslated
Prevent people from registering via your disallowed comment keys.
You have to log in to edit this translation. Meta |
|||
| ↑ | Ban Hammer | You have to log in to add a translation. | Details |
Original untranslatedMeta |
|||
| I believe so. | You have to log in to add a translation. | Details | |
Original untranslatedMeta |
|||
| <strong>Single Site (Traditional) Install</strong> | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Single Site (Traditional) Install</strong>
CommentFound in installation paragraph. You have to log in to edit this translation. Meta |
|||
| No. Since WordPress itself doesn't list rejected comments, the rejected users are similarly lost forever. | You have to log in to add a translation. | Details | |
Original untranslated
No. Since WordPress itself doesn't list rejected comments, the rejected users are similarly lost forever.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| If I change the Blocklist via Ban Hammer, will it change the Disallowed Comment Keys? | You have to log in to add a translation. | Details | |
Original untranslated
If I change the Blocklist via Ban Hammer, will it change the Disallowed Comment Keys?
CommentFound in faq header. You have to log in to edit this translation. Meta |
|||
| This plugin does not track data outside of what WordPress already collects. It utilizes the submitted email address to validate the domain and compares it to the list of prohibited domains and emails. No additional data is processed. | You have to log in to add a translation. | Details | |
Original untranslated
This plugin does not track data outside of what WordPress already collects. It utilizes the submitted email address to validate the domain and compares it to the list of prohibited domains and emails. No additional data is processed.
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
| On a network instance, there's a network wide setting for banned emails and domains. This means you only have <em>one</em> place to update and maintain your blocked list. When a listed user attempts to register, they get a customizable message that they cannot register. | You have to log in to add a translation. | Details | |
Original untranslated
On a network instance, there's a network wide setting for banned emails and domains. This means you only have <em>one</em> place to update and maintain your blocked list. When a listed user attempts to register, they get a customizable message that they cannot register.
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
| On a single install of WordPress, instead of using its own database table, Ban Hammer pulls from your list of prohibited emails from the Disallowed Comment Keys feature, native to WordPress. Since emails never equal IP addresses, it simply skips over and ignores them. | You have to log in to add a translation. | Details | |
Original untranslated
On a single install of WordPress, instead of using its own database table, Ban Hammer pulls from your list of prohibited emails from the Disallowed Comment Keys feature, native to WordPress. Since emails never equal IP addresses, it simply skips over and ignores them.
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
| <a href="https://github.com/Ipstenu/ban-hammer/wiki">Wiki</a> | You have to log in to add a translation. | Details | |
Original untranslated
<a href="https://github.com/Ipstenu/ban-hammer/wiki">Wiki</a>
CommentFound in description list item. You have to log in to edit this translation. Meta |
|||
| <a href="https://github.com/Ipstenu/ban-hammer/">Development</a> | You have to log in to add a translation. | Details | |
Original untranslated
<a href="https://github.com/Ipstenu/ban-hammer/">Development</a>
CommentFound in description list item. You have to log in to edit this translation. Meta |
|||
| Privacy Policy | You have to log in to add a translation. | Details | |
Original untranslatedMeta |
|||
| <a href="https://ko-fi.com/A236CEN/">Donate</a> | You have to log in to add a translation. | Details | |
Original untranslated
<a href="https://ko-fi.com/A236CEN/">Donate</a>
CommentFound in description list item. You have to log in to edit this translation. Meta |
|||
| If you want to block everyone from all subdomains (like <code>joe@bar.example.com</code>) then you can block <code>.example.com</code> and that will block all the subdomains. | You have to log in to add a translation. | Details | |
Original untranslated
If you want to block everyone from all subdomains (like <code>joe@bar.example.com</code>) then you can block <code>.example.com</code> and that will block all the subdomains.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Yes but not wildcards. If you put in <code>viagra</code> for example, you will block <code>viagrajones@gmail.com</code> <em>and</em> <code>john@viagra.com</code> so please use this carefully. If you put in <code>cookie</code> then you'll block <code>cookiemonster@sesamestreet.edu</code> and everyone would be sad. | You have to log in to add a translation. | Details | |
Original untranslated
Yes but not wildcards. If you put in <code>viagra</code> for example, you will block <code>viagrajones@gmail.com</code> <em>and</em> <code>john@viagra.com</code> so please use this carefully. If you put in <code>cookie</code> then you'll block <code>cookiemonster@sesamestreet.edu</code> and everyone would be sad.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
Export as
Comment
Short description.