Do you still have the problem in the latest version?

I will have to check it later this month, am currently out of the office.
I'll post back ASAP.

I have installed the recent (2.06) version of limesurvey on my local computer, and it seems to have the same problem still. It works when I send the email from the web interface, but no EXPIRY date when sending through RemoteControl.

I've been looking into the problem myself and have found the following solution:

The EXPIRY field was not included in the $fieldsarray in the emailTokens function (application/helpers/admin/token_helper.php)

The global options, including EXPIRY, are already parsed through ReplaceFields in the views when going through the Webinterface (e.g. see the code in application/views/admin/token/invite.php), before passing to the same emailTokens function later.

What is interesting to note here (a second problem for me) is that the function call to ReplaceFields in the views is used with the parameter bReplaceInsertans set to FALSE.

In my own example, the EXPIRY variable was wrapped inside a function to format it according to a specific pattern ({strftime('%e %B %Y', strtotime('{EXPIRY}'))}). EXPIRY here needs to be replaced first by calling ReplaceFields with $bReplaceInsertans to FALSE, or it will be lost.

To solve both problems i have added a diff to the most recent code (checked out 2.06 build 151018 with git):

• Added the field 'expiry' to the fieldarray from the Global survey data

• Run the subject & message of the mail to send through an extra call of ReplaceFields with bReplaceInsertans to FALSE
  (That way, wrapped insertans fields like my EXPIRY above will be parsed correctly too)
  This does not seem to interfere with the extra call to ReplaceFields when going through the WebInterface.

Hope that helps !

Why doing Replacefields(Replacefields($sSubject)) ?

You don't have to Replacefields 2 times.

It was mentioned in my previous note, and the reason of the whole problem:

It is called 2 times, but once with the bReplaceInsertans to FALSE and then with it set to TRUE. Doing this allows the INSERTANS fields to be parsed to.

Quote:

In my own example, the EXPIRY variable was wrapped inside a function to format it according to a specific pattern ({strftime('%e %B %Y', strtotime('{EXPIRY}'))}). EXPIRY here needs to be replaced first by calling ReplaceFields with $bReplaceInsertans to FALSE, or it will be lost.

You don't have to add the { inside an expression ....

{strftime('%e %B %Y', strtotime(EXPIRY))})

Musty work (and if not : must be fixed)

I'm afraid that does not work, and i wasn't expecting it to.
If you leave out the {...} around the EXPIRY string, how would the ExpressionManager be able to tell apart an ordinary string from an INSERTANS field ? it would need to read the whole string and see if it detects any fields that might be an INSERTANS ?

What if i wanted to use a function to concatenate a piece of text with the string 'EXPIRY' (or any other existing INSERTANS field for that matter) ? Then it would always replace the strings with their value counterparts, no ?

1st : strftime don't exist.

2nd : IN GUI too : EXPIRY is not replaced with EM.
(same for other var : SURVEYDESCITION, ADMINNAME etc ...)

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=16446

2.06

Version 2.50+ Build 140413 released