PHP code inside the EMAIL template, how do I accomplish that? Unicode domain to IDN ASCII

Hi All

Stumbled upon this old post.

I want to add the following PHP code to an email template I have.

The code convert an unicode domain name domain to an IDNA ASCII-compatible format.

When I add the code to the template I just get an error, so I suspect I am doing it wrongly.

{php}
echo idn_to_ascii('$service_domain');
{/php}

I have pasted an example below.

<?php

echo idn_to_ascii('täst.de'); 

?>

Gives the output : xn--tst-qla.de

I look forward to hear from you.

- Tim

Hi TIm,

I can see two potential issues with this...

1. in order for idn_to_ascii to work, you will likely have to enable 'intl' in your PHP settings.

2. as it's just a PHP function, you should be able to call it directly in Smarty without the need for {php} tags... e.g, either of the following should work and give the same output...

php = {php}echo idn_to_ascii('ჰელო.გე');{/php}
smarty = {idn_to_ascii('ჰელო.გე')}

... and given the option of using either, go with Smarty... though bear in mind that you will need to update your Smarty Security Policy to cover it's use in the email templates.

Hi Brian

Thanks for the input, didn't see it due to missing notifications of new posts on my threads

I will look at it and see if I can get it to work

- Tim

Hi Brian

To understand the Smarty Security Policy, I would need to add the following to my configuration file to be able to use the idn_to_ascii within the email templates.

// Smarty custom email based template policy:
$smarty_security_policy = array(
   'mail' => array(
       'php_functions' => array(
           'idn_to_ascii',
       ),
   ),
);

- Tim

wouldn't it be idn_to_utf8 ?

because you want to change for xn-etc to täst.de

Hi Brian

Not in this case.

The email template hold the correct domain name, such as täst.de but it doesn't show the IDN name and I just want to show the client what the IDN domain is as well.

I can't tell them that mail will work as brian@täst.de it needs to show brian@xn-etc.de.

- Tim

I stand corrected!

i'm sure i'm involved in two different threads on this topic - one using idn_to_utf8 and this one... so many threads, they blur together after a while!