Plugin: MD Spam Me Not, alternative to using {encode} for hiding or masking email addresses

Thanks mdesign, works like a charm!

Thanks, Cocoaholic. You were nice enough to add a title attribute to the plugin, so I incorporated that and put out version 1.0.2, available in the first post.

/me claps three hands.

Well done, both you guys!

Looks useful. Thanks as lot.

Hey, thanks for this!

I had my own php function for this sort of thing, but it was not working when I set my template to parse PHP on INPUT… Your plugin saved me a bit of dev time!

Keep up the great work mdesign! 😊

Cheers, M

Perfect, just what I was looking for!

This almost works for me. Was wondering if it’ll work in weblog fields (custom or otherwise)?

.angie

It should work, if you wrap the field you’re outputting with allow_eecode (another plugin). For example, if you have a huge body area that might have a few emails in there, instead of just putting

{body}

on your template, wrap that with:

{exp:allow_eecode}{body}{/exp:allow_eecode}

Then, anytime you’re using spammenot in that body field, it should get parsed correctly.

Thanks, mdesign - a nice contribution indeed.

And just noticed, you made this a while ago. Good to find it 😉.

Kind regards, Clive

This works great!

Any way of adding a “message body” parameter in the future would make it even better.

Thanks very much!

How would you envision using the message body? Like this:

{exp:spammenot email="you@email.com" mode="1" 
title="My Title" class="nocion email" subject="EE Inquiry" 
text="Email Ryan for more info."}If you have text that should go in the message body, 
it should go in here (between opening/closing tag), and we might have less trouble 
with weird characters here like ' or ", among others.{/exp:spammenot}

or like this:

{exp:spammenot email="you@email.com" mode="1" 
title="My Title" class="nocion email" subject="EE Inquiry" 
text="Email Ryan for more info." message_body="If you have text that should go in the 
message body, it should go in here right in a parameter), but we might have trouble 
with weird characters here like \\' or \\", among others - you might have to escape them."}

I feel like the first way would be the way to go, in case you had a long message that might have a bunch of tricky characters in it.

I’d gladly use either method but I suppose the first one is more straightforward (without having to escape certain characters).

Unfortunately, I’ve found that [as of version 1.0.3 - 15 September 2007] this plugin does not work with entries or custom weblog fields that use Textile formatting, but it does work with Markdown and/or SmartyPants’ text filters.

What happens with Textile is that the anchor code is output, but the e-mail address is not filled in so the code becomes:

<a href="mailto:"></a>

Markdown doesn’t seem to have a problem understanding the SpamMeNot syntax and outputs the code correctly:

<a href="mailto:user@domain.com">user@domain.com</a>

Unfortunately, I’ve found that [as of version 1.0.3 - 15 September 2007] this plugin does not work with entries or custom weblog fields that use Textile formatting…the anchor code is output, but the e-mail address is not filled it so the code becomes

<code><a href="mailto">

Have you tried it with single quotes, and with the most basic parameter(s)? I found that EE’s native {encode} doesn’t work with Textile either (in my experience) unless you don’t use any quotes.