Problem with {TOKEN} values

More
4 years 10 months ago #89043 by Loco
Loco created the topic: Problem with {TOKEN} values
Hi,

I have a weird probleme here.

Using latest release (Version 2.00+ Build 121121) with closed survey and multiple token uses.

So here is what happens:

In invitation and reminder email passing {FIRSTNAME}, {LASTNAME} and {USESLEFT} values works perfectly (bit it won't pass value of {TOKEN:FIRSTNAME}, {TOKEN:LASTNAME}, {TOKEN:USESLEFT).

But in basic admin notification, advanced admin notification and confirmation emails values are only passed if I use {TOKEN:FIRSTNAME} and {TOKEN:LASTNAME}. Value {TOKEN:USESLEFT} doesn't work at all, neither does {USESLEFT} (big problem for me).

Also, passing values of {TOKEN:FIRSTNAME} and {TOKEN:LASTNAME} in question group description work normally, but I cannot get {TOKNEN:USESLEFT}, nor {USESLEFT} values. even bigger problem for me.


So, my question is, is this a bug or I'm just very dumb and missing something.
Thanks

Please Log in to join the conversation.

More
4 years 10 months ago #89047 by Loco
Loco replied the topic: Problem with {TOKEN} values
is there any way arround this? maybe some javascript reading token table and USESLEFT value directly, bypassing Expression Manager or something?

Please Log in to join the conversation.

More
4 years 10 months ago #89100 by tomscher
tomscher replied the topic: Problem with {TOKEN} values
Does the bug occur if you are using the INSERTANS function?

Please Log in to join the conversation.

More
4 years 10 months ago - 4 years 10 months ago #89107 by Loco
Loco replied the topic: Problem with {TOKEN} values
INSERTANS works fine.

Also, I have noticed that when I open suvey in limesurvey administration sometimes TOKEN:ATTRIBUTE_CPDB_1 is marked as undefined variable (red rectangle and letters) although it works fine in survey, and TOKEN:USESLEFT is marked with normal brown letters (but never works in survey - marked as undefined variable).

sometimes it is other way arround with this two variables.

TOKEN:FIRSTNAME and TOKEN:LASTNAME are always marked properly and work fine.
Last Edit: 4 years 10 months ago by Loco.

Please Log in to join the conversation.

More
4 years 10 months ago #89119 by DenisChenu
DenisChenu replied the topic: Problem with {TOKEN} values

Loco wrote: but I cannot get {TOKNEN:USESLEFT}, nor {USESLEFT} values

This work in 1.92, please fill a bug report.

(with a lss file and a csv tokens file).

Denis

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand (or search sondages pro).
An error happen ? Before make a new topic : remind the Debug mode .

Please Log in to join the conversation.

More
4 years 10 months ago #89122 by Loco
Loco replied the topic: Problem with {TOKEN} values
Thanks

Please Log in to join the conversation.

More
4 years 10 months ago #89128 by Loco
Loco replied the topic: Problem with {TOKEN} values

DenisChenu wrote: This work in 1.92


I can confirm that it works perfectly in 1.92. Just tried it. Thanks again.

Please Log in to join the conversation.

More
4 years 10 months ago #89136 by DenisChenu
DenisChenu replied the topic: Problem with {TOKEN} values

Loco wrote:

DenisChenu wrote: This work in 1.92


I can confirm that it works perfectly in 1.92.

DenisChenu wrote: please fill a bug report.

And leave the link of the bug report here (with the number).

Denis

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand (or search sondages pro).
An error happen ? Before make a new topic : remind the Debug mode .

Please Log in to join the conversation.

More
4 years 10 months ago #89206 by Loco
Loco replied the topic: Problem with {TOKEN} values

DenisChenu wrote: And leave the link of the bug report here (with the number)


bugs.limesurvey.org/view.php?id=6966

Please Log in to join the conversation.

Start now!

Just create your account and start using Limesurvey today.

Register now