Thread

Somehow the global variable {encode} is not rendering on EE 2.5.3.

It does work inside a template but not as part of a channel entry.

I tried to change the preferences of the channel but unfortunately no result. See screenshot attached.

Can someone please help me?

Thanks 😊

{encode="[email protected]" title="[email protected]"}

http://ellislab.com/expressionengine/user-guide/templates/globals/single_variables.html#encode

Hi titm0use,

I’m unable to reproduce, the encoded email address appears fine for me in 2.5.3 as well as our latest, 2.5.5. There is a known issue of encoded email addresses not working in the forums, but it should work fine inside of a channel entry.

What does the entry output instead of the encoded email address?

Kevin

We had this happen with EE 2.5.2. The issue was the related to a WYSIWYG field specifically. But also related to how ExpressionEngine now handles encode.  It was converting all the curly brackets to html_entities, which means they did get parsed.

We solved by switching to using BBCode for encoding. This required find/replace across entries, but basically we searched for…

{encode="[email protected]" title="[email protected]"}

then replaced with

[email="[email protected]"][email protected][/email]

The find/replace code was a bit more complicated, because it required multiple passes for different email combinations for example some people used. But we tested and played with in BBEdit until we got it working, then backed up the database and ran it using EE Find/Replace tool.

{encode="[email protected]" title="[email protected]"}
{encode="[email protected]"} .(JavaScript must be enabled to view this email address){/encode}
{encode="[email protected]" title="[email protected]"}

There are probably other options you can use as well, such as modify the WYSIWYG add-on/field_type. Use a different WYSIWYG field_type, one that offers its own {encode} option, etc., or lastly, if you turn on ‘automatic conversion’ EE will encode all email addresses.

This wasn’t really an option for us, because auto-conversion doesn’t create proper urls. In fact if EE separated out the auto-conversion into two separate options: (1) auto-convert emails, and (2) auto-convert urls this would be much better. For accessibility and standards compliance we always include titles with our <a > and auto-convert doesn’t.

We had this happen with EE 2.5.2. The issue was the related to a WYSIWYG field specifically. But also related to how ExpressionEngine now handles encode.  It was converting all the curly brackets to html_entities, which means they did get parsed.

We solved by switching to using BBCode for encoding. This required find/replace across entries, but basically we searched for…

{encode="[email protected]" title="[email protected]"}

then replaced with

[email="[email protected]"][email protected][/email]

 

Thanks for thinking with me on this issue.

I tried the BBCode version and it worked but when you click on the link the e-mail that is composed by your e-mail client isn’t using the e-mail address that you would think it would pass through. Do you have any idea?

Sorry, I was just typing from memory this morning, I should have provided the link to the BBCode reference chart. I probably entered something wrong. Here’s the code from the BBCode page:

[email][email protected][/email]

or

[[email protected]]click here to email[/email]

the UserGuide link is here.

Thanks a lot! It works!!!!! 😊