View Issue Details

IDProjectCategoryView StatusLast Update
13581Bug reports[All Projects] Print Viewpublic2018-09-14 02:00
ReporterblockaAssigned Toadamzammit 
Status closedResolutionwon't fix 
Product Version3.6.x 
Target VersionFixed in Version 
Summary13581: Survey place holders not processed in queXMLPDF

When I use EM type fields or token attributes in survey text, they are not processed when rendering the queXMLPDF file (accessed via the Individual Responses table set of icons -- or elsewhere when the queXMLPDF is used to render a completed response).

I would expect that LS placeholder variables would be replaced with their actual values. For example, we use a couple of custom token attributes, and display them in the welcome text. In the PDF, I see the names of the placeholder fields “{TOKEN:ATTRIBUTE_1} and {TOKEN:ATTRIBUTE_2}” instead of their associated values. We'd like their stored values (not their labels, but the associated value) to be rendered in the PDF output.

TagsNo tags attached.
Complete LimeSurvey version number (& build)2.73.0 b171219 (but confirmed in latest LS 3 release as well)
I will donate to the project if issue is resolvedNo
Database & DB-VersionmySQL 5.6.37
Operating System (Server)CentOs
Webserver software & versionApache
PHP Version7.0.x


has duplicate 14027 closedadamzammit Qid-token not substituted in quexml pdf export 




2018-09-14 01:58

developer   ~49028

I think my original response to this has disappeared.

I don't think this should be an upstream Limesurvey feature, as it destroys the archival nature of a queXML export (i.e. each respondent could get a different queXML PDF output, which also means queXF will not be able to process it properly).

If you want to try this - you can patch Limesurvey with a branch I have created here:

Here is the patch against Limesurvey master:

Issue History

Date Modified Username Field Change
2018-04-09 16:55 blocka New Issue
2018-04-10 15:13 c_schmitz Assigned To => adamzammit
2018-04-10 15:13 c_schmitz Status new => assigned
2018-09-14 01:58 adamzammit Note Added: 49028
2018-09-14 01:59 adamzammit Status assigned => closed
2018-09-14 01:59 adamzammit Resolution open => won't fix
2018-09-14 02:00 adamzammit Relationship added has duplicate 14027