Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: Insert token attributes in email doesn't work?

Insert token attributes in email doesn't work? 2 years 11 months ago #68039

  • lovepade
  • lovepade's Avatar
  • OFFLINE
  • Expert Lime
  • Posts: 93
  • Karma: 0
Hi guys

I've just sent my self a test invite for the next survey. I'm using token attributes in the invite mail.

The same tokens that work fine in the survey, doesn't work in the email though?

By that I mean that the email is sent in this form:
Subject: Hello {TOKEN:FIRSTNAME}

You graduated in {TOKEN:ATTRIBUTE_1}, please help us answer some questions.

{ADMINEMAIL}, {ADMINNAME}, {SURVEYURL} and {OPTOUTURL} works - i.e. those field are replaced. But all replacement fields in this form: {TOKEN:ATTRIBUTE_7} does not?

All fields have been inserted via the editor - so it's not a misspelling on my part.

I guess this is a bug report - but could it be something on my end?

Using: Version 1.91+ Build 11232

Sincerely
Andreas
The administrator has disabled public write access.

Re: Insert token attributes in email doesn't work? 2 years 11 months ago #68042

  • sp00ky
  • sp00ky's Avatar
  • OFFLINE
  • Junior Lime
  • Posts: 25
  • Thank you received: 2
  • Karma: 4
Last Edit: 2 years 11 months ago by sp00ky.
The administrator has disabled public write access.
The following user(s) said Thank You: DenisChenu

Re: Insert token attributes in email doesn't work? 2 years 11 months ago #68050

  • Mazi
  • Mazi's Avatar
  • OFFLINE
  • LimeSurvey Team
  • Posts: 5325
  • Thank you received: 296
  • Karma: 249
It works fine here at the latest version. I used this text for testing:
Dear {FIRSTNAME} {LASTNAME},

A1: {ATTRIBUTE_1} You have been invited to participate in a survey...

Did the editor add "TOKEN:" at the placeholders? Because I used the editor at the invitation email as well and the placeholders look different!?

Best regards/Beste Grüße,
Dr. Marcel Minke
(Limesurvey Head of Support)
Need Help? We offer professional Limesurvey support
Contact: marcel.minke(at)limesurvey.org'"
The administrator has disabled public write access.

Re: Insert token attributes in email doesn't work? 2 years 11 months ago #68055

  • lovepade
  • lovepade's Avatar
  • OFFLINE
  • Expert Lime
  • Posts: 93
  • Karma: 0
Yes I just checked that... It works without {TOKEN} - and yes the editor did insert those. BUT it might have done so with an earlier version of limesurvey. When I doubled checked it added the replacement fields without tokens.

Anyways - it works now - I am so sorry for the inconvenience. Guess I called for help a little to fast.

Congrats with the 2.0 alpha :-)
The administrator has disabled public write access.

Re: Insert token attributes in email doesn't work? 2 years 11 months ago #68057

  • Mazi
  • Mazi's Avatar
  • OFFLINE
  • LimeSurvey Team
  • Posts: 5325
  • Thank you received: 296
  • Karma: 249
Thanks for your feedback.

Can you try to find out at which version the editor used {TOKEN:...} for these placeholders. I think this should be backward compatibel in some way so we might need to do a little fixing.

Best regards/Beste Grüße,
Dr. Marcel Minke
(Limesurvey Head of Support)
Need Help? We offer professional Limesurvey support
Contact: marcel.minke(at)limesurvey.org'"
The administrator has disabled public write access.

Re: Insert token attributes in email doesn't work? 2 years 11 months ago #68063

  • lovepade
  • lovepade's Avatar
  • OFFLINE
  • Expert Lime
  • Posts: 93
  • Karma: 0
Well in the last backup I have, the version file reads:

$versionnumber = "1.91+";
$dbversionnumber = 146;
$buildnumber = '10859';

But to be honest I think I made at least one autoupdate without backing up (I knooooow).

Another thing: At some time I experienced some glitched inserting the replacement fields. I then disabled my adblocker, and the problem went away.

Sorry I can't be of more help.
The administrator has disabled public write access.

Re: Insert token attributes in email doesn't work? 2 years 11 months ago #68064

  • DenisChenu
  • DenisChenu's Avatar
  • OFFLINE
  • Moderator Lime
  • Posts: 6358
  • Thank you received: 824
  • Karma: 245
Yes, it seems to have two method:
{TOKEN:...} and {ATTRIBUTE_X} directly,

And it make very difficult to find the good method ...

Try the 2 method :)
The administrator has disabled public write access.

Re: Insert token attributes in email doesn't work? 2 years 8 months ago #71604

  • gskramer
  • gskramer's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 16
  • Karma: 0
As of version 1.91+, build 11804, there is still a small bug that pertains to the admin notification template only. In the other templates (invitation, reminder, etc.), it works to specify a token attribute as {ATTRIBUTE_N}; however, if you do this in the admin template, the substitution doesn't happen. You need to use {TOKEN:ATTRIBUTE_N} instead.
Last Edit: 2 years 8 months ago by gskramer.
The administrator has disabled public write access.

Re: Insert token attributes in email doesn't work? 2 years 8 months ago #71671

  • Mazi
  • Mazi's Avatar
  • OFFLINE
  • LimeSurvey Team
  • Posts: 5325
  • Thank you received: 296
  • Karma: 249
Please open a ticket at the bugtracker and...
  1. Give as much information as possible
  2. Attach your survey. You can mark your ticket "private" so that only the developers will be able to take a look at it.
  3. Provide step-by-step instructions how to reproduce the problem.
  4. If possible/helpful please provide screenshots

Afterwards please post the link to the bugtracker so we can follow the progress.

Best regards/Beste Grüße,
Dr. Marcel Minke
(Limesurvey Head of Support)
Need Help? We offer professional Limesurvey support
Contact: marcel.minke(at)limesurvey.org'"
The administrator has disabled public write access.

Re: Insert token attributes in email doesn't work? 2 years 8 months ago #71747

  • TMSWhite
  • TMSWhite's Avatar
  • OFFLINE
  • LimeSurvey Team
  • Posts: 759
  • Thank you received: 82
  • Karma: 36
I'm sure that's a replacements.php issue (e.g. part of the code isn't using it). What is the preferred naming? Since TOKEN:ATTRIBUTE_N is used in most substitutions, that would be my preference. If, however, there is a big installed base of surveys that use ATTRIBUTE_N, we should consider aliases. The problem is that ATTRIBUTE_N could clash with internal survey variables, but TOKEN:xxx never will.

Do please open a ticket and attach a sample survey so we can track getting this solved.

/Tom
Last Edit: 2 years 8 months ago by TMSWhite.
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Moderators: ITEd
Time to create page: 0.135 seconds
Donation Image