• If you must publish email addresses, phone numbers, and other data frequently harvested by spammers, this is the best tool WordPress has for keeping the spammers at bay. Rather than activating the plugin to work on all content and widgets, just use the shortcode to selectively encode the content you wish to protect.

    If you activate the plugin to automatically filter all content, including widgets, this is probably needless overhead and may break some forms. Being able to specify exception pages would be nice, but that is not yet a feature.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Pi Zi

    (@freelancephp)

    Thanks Dan.

    You’re right. This form bug is on the list for the next release. But I’m also in the middle of a complete code refactor. So it might take a few weeks.

    Thread Starter Dan Knauss

    (@dpknauss)

    That’s great news.

    For years I’ve had email encoder bundle on the short list of “must install” plugins, especially for client’s sites where a high level of “protecting people from themselves” is needed.

    Some time I’d like to repeat tests that were done almost 10 years ago to evaluate the relative effectiveness of the different methods of encoding email addresses. What was shown back then is that the conversion to hex/html entities was not very effective at all and worse even than the old “jim [at] bob [dot] com” method. My guess is that by now most spam harvesters look for this and eat it right up. The javascript methods may be the only worthwhile approach to the problem.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Consistently useful’ is closed to new replies.