I have an interesting problem - it might just be lack of knowledge, but it has me stumped!

The SMTP provider we use has started to add footers to our emails unless we have an unsubscribe link that matches their specification. Unfortunately, this is in the form of a regular expression, which Limesurvey doesn't recognise, which obviously breaks the optout link!

Original format:
<a href="{OPTOUTURL}">unsubscribe</a>.

Required format:
<a href="{unsubscribe:{OPTOUTURL}}">unsubscribe</a>.


Does anyone have any ideas how to get aorund this conundrum, for example to pass curly braces as text rather than as an expression?

Any advice greatly appreciated

If you insert a space after the opening brace and before the closing brace, Expression Manager shouldn't parse them.

I'm not sure whether the SMTP provider will recognize this but try:

Thanks Tony

Unfortunately, it looks like they don't parse it, but it was a good idea nonetheless.

What a silly little problem, but I suspect it might be intractable.

Cheers

Hi, about
are replaced by . Then you mus use
Maybe you can try

I don't think that will solve it - the issue is that the SMTP provider needs to see a tag enclosed in curly braces but EM is trying to parse those braces.

Yes, I can confirm that Limesurvey sees both:

or

as curly braces that it tries (unsuccesfully) to decode.


There seems to be no way to pass the curly braces as simple text without Limesurvey pricking up its ears and taking an interest (unlike for example Excel, where you can pass a wildcard character 'as is' by surrounding it by two other wildcards), at least no way I have been able to find via google!

With a push in the right direction from Tony and Denis, I think I might have sorted it - hurrah!

I ended up just trying it with simple escaped brackets on the open and close, which Ididn't expect to work, but it did:

Thanks to you both!

That's a good tip to know.

Arg,

Expression manager of limesurvey replace {html_entity_decode(&#123;)} by { and redo the it after ... Must fix this issue ! But \{unsubscribe:@@OPTOUTURL@@\} seems great too.

Maybe manual must be updated ...