View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
14287 | Feature requests | Expression Manager | public | 2018-11-26 17:51 | 2018-11-27 19:08 |
Reporter | mad99 | Assigned To | DenisChenu | ||
Priority | none | Severity | feature | ||
Status | closed | Resolution | duplicate | ||
Summary | 14287: cosistent use of ATTRIBUTE_1 OR TOKEN:ATTRIBUTE_1 in email-template and text for survey. | ||||
Description | I'm quite sure it is more then a feature-request like holch ment: It is a design-bug at least and really hard to figure out, because also the lack of documentation (I guess)! Would be great if both would
Friendly regards | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Bug heat | 4 | ||||
Story point estimate | |||||
Users affected % | |||||
duplicate of | 14288 | closed | DenisChenu | Bug reports | TOKEN:ATTRIBUTE_INT: No output in email-template AND no Error in validate expression |
related to | 08683 | closed | DenisChenu | Bug reports | Unique custom token values fail to merge in invite/reminder emails |
TOKEN:ATTRIBUTE_X is empty during survey for anonymous survey. TOKEN:ATTRIBUTE_X is related to survey, ATTRIBUTE_X is related to token ONLY when sending email and reminder. Manual : https://manual.limesurvey.org/Email_templates#Email_placeholders |
|
Tkey are all private, NOT ANONYMOUS survey where I have problem with TOKEN:ATTRIBUTE_X. The TOKEN:ATTRIUBTE_X is filled with value (See Forum https://www.limesurvey.org/forum/design-issues/117048-email-template-if-statement-with-placeholder-token-does-not-work#177423) Line 5. |
|
I have add the Testpart for you above the current email-template for send to user: I don't know why, but know there is alltime an output in the sent email. Maybe various typos in all the tests. Unfortunatelly I overwrited the old email-template and have only the images left (also published in forum). At that time there was either no output/empty «», or it wasn't rendered «if(TOKEN:ATTRIBUTE_1 == 'DU', 'TEST-YES', 'TEST-NO')». In the current test, attached as lss-file there is everytime an output. But the "wrong" output «TEST-NO» althought the value in {TOKEN:ATTRIBUTE_1} is "DU", like in the {if}-statement for {ATTRIBUTE_1} where the output is right: «TEST-YES». Hope this will help |
|
The files |
|
You can report only ONE issue please ! |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2018-11-26 17:51 | mad99 | New Issue | |
2018-11-27 09:43 | DenisChenu | Note Added: 49793 | |
2018-11-27 09:43 | DenisChenu | Relationship added | related to 08683 |
2018-11-27 10:03 | mad99 | Note Added: 49795 | |
2018-11-27 10:57 | mad99 | Note Added: 49799 | |
2018-11-27 10:57 | mad99 | File Added: limesurvey_survey_279156_Kundenzufriedenheit nach Telefongespräch.lss | |
2018-11-27 10:57 | mad99 | File Added: limesurvey-DenisChenu-email-output.png | |
2018-11-27 10:57 | mad99 | File Added: limesurvey-DenisChenu-email-template.png | |
2018-11-27 10:57 | mad99 | File Added: limesurvey-DenisChenu-validate-expression.png | |
2018-11-27 10:57 | mad99 | Note Added: 49800 | |
2018-11-27 19:07 | DenisChenu | Note Added: 49811 | |
2018-11-27 19:07 | DenisChenu | Relationship added | duplicate of 14288 |
2018-11-27 19:08 | DenisChenu | Assigned To | => DenisChenu |
2018-11-27 19:08 | DenisChenu | Status | new => closed |
2018-11-27 19:08 | DenisChenu | Resolution | open => duplicate |