Obfuscation of email via the [email]…[/email] shortcode syntax using built-in WordPress Codex functionality.
| Author: | Robert Peake (profile at wordpress.org) |
| WordPress version required: | 3.0.1 |
| WordPress version tested: | 5.8 |
| Plugin version: | 1.1.6 |
| Added to WordPress repository: | 20-09-2014 |
| Last updated: | 13-07-2021
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
| Rating, %: | 100 |
| Rated by: | 5 |
| Plugin URI: | https://wordpress.org/plugins/antispambot |
| Total downloads: | 7 916 |
| Active installs: | 800+ |
Click to start download
|
Obfuscation of email via the [email]...[/email] shortcode syntax using built-in WordPress Codex functionality.
Alternative variations:
[email]user@example.com?subject=foo+bar&body=baz[/email] creates a mailto: link with subject and body pre-populated[email nolink=1]user@example.com[/email] just displays the email without a link wrapping it[email linktext="click here"]user@example.com[/email] displays the text “click here” with a link to the email address
Screenshots
![Use the <code>[email]...[/email]</code> tag to wrap your email input](https://ps.w.org/antispambot/assets/screenshot-1.png?rev=993940)
Use the [email]...[/email] tag to wrap your email input
This will display as an email address wrapped in a mailto: hyperlink (i.e. clickable to open a mail client)
The source code used to render this involves randomly-encoded characters, making it more difficult for spambots to harvest
How does this work?
This plugin converts email addresses within the [email]...[/email] shortcodes using the built-in WordPress Codex antispambot() function. The function converts email address characters to HTML entities. It converts a random selection of characters each time, making it more difficult for spam-bots to “harvest” the email address programmatically.
Is it foolproof?
The only foolproof way to ensure email addresses do not get harvested from a web page is to not include them on the page in any form. However, the method created by the WordPress developers that we employ here should provide reasonable protection against all but the most concerted automatic-harvesting efforts.
ChangeLog
- 1.1.5 – Tested with WordPress 5.3
- 1.1.5 – Tested with WordPress 5.2
- 1.1.4 – Tested with WordPress 5.1
- 1.1.3 – Tested with WordPress 5.0
- 1.1.2 – Tested with WordPress 4.9.5
- 1.1. – Added support for ?subject= strings, nolink= shortcode attribute (just print) and linktext= shortcode attribute to specify link text
- 1.0 – upgraded to stable version after eight months in the wild
- 0.1-alpha – Initial release
