Welcome, Guest
Username: Password: Remember me

TOPIC: token attribute mixed-up

token attribute mixed-up 1 year 2 months ago #95977

  • ricardo
  • ricardo's Avatar
  • OFFLINE
  • Expert Lime
  • Posts: 110
  • Thank you received: 1
  • Karma: 0
I'm using Version 2.00+ Build 130428

I set up a token list and added a new field attribute_1. The new field was "January 2013" or "August 2012"

I set up an invitation like this:

invitationemail.PNG


However, some people have emailed to me saying that date is not correct. For example, the date for this person is August 2013,

tokenlist_2013-05-14.PNG


but his email shows January 2013.

invitationtruncated.PNG




Other people simply did not get the date:


invitationnodate.PNG


Has anybody else had the same problem?
Last Edit: 1 year 2 months ago by ricardo. Reason: wrong pic
The administrator has disabled public write access.

token attribute mixed-up 11 months 4 days ago #99380

  • papacico
  • papacico's Avatar
  • OFFLINE
  • Junior Lime
  • Posts: 20
  • Karma: 0
hello Ricardo,

yes i have the same problem the {token:attribute_1} is not returning the value from the token table,

did you already solved this problem? Could you please share the solution?

Thank you bye
The administrator has disabled public write access.

token attribute mixed-up 11 months 3 days ago #99400

  • DenisChenu
  • DenisChenu's Avatar
  • OFFLINE
  • Moderator Lime
  • Posts: 6236
  • Thank you received: 794
  • Karma: 238
If this happen with last version too, please report the bug.

But i think i see a fix for that some week ago.

Denis
The administrator has disabled public write access.

token attribute mixed-up 11 months 2 days ago #99441

  • FHemmes
  • FHemmes's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 10
  • Thank you received: 1
  • Karma: 0
Hello ricardo, papacico,

I had the same problem some time ago. The email invitations would sometimes load the right tokens, sometimes the wrong ones, and sometimes none at all.

What made the difference for me was using the field replacement tags without the word 'TOKEN' in them. So use {ATTRIBUTE_1} instead of {TOKEN:ATTRIBUTE_1}. Include 'TOKEN' only in the field replacement tags you build into the survey itself.
This solved the problem for me. You can find my thread on this problem here: www.limesurvey.org/en/forum/design-issue...butes-in-invitations

There is also a page in the manual related to replacement field tags that has information on this here: manual.limesurvey.org/Tokens#Emailing

I hope this solves your problem.

Best,
FH
The administrator has disabled public write access.
The following user(s) said Thank You: papacico

token attribute mixed-up 11 months 2 days ago #99457

  • DenisChenu
  • DenisChenu's Avatar
  • OFFLINE
  • Moderator Lime
  • Posts: 6236
  • Thank you received: 794
  • Karma: 238
DenisChenu wrote:
If this happen with last version too, please report the bug.
The administrator has disabled public write access.
The following user(s) said Thank You: papacico

token attribute mixed-up 11 months 1 day ago #99502

  • papacico
  • papacico's Avatar
  • OFFLINE
  • Junior Lime
  • Posts: 20
  • Karma: 0
thank you Fhemmes and Denis the issue is solved using {ATTRIBUTE_1}

kind regards
The administrator has disabled public write access.
Moderators: ITEd
Time to create page: 0.139 seconds
Donation Image