queXML

quexmlPDF.php in limesurvey outputs weird short free text fields in exported PDF

Asked by Jakub Cerveny

Hello,

I am not sure if this is the correct thread to report this as the bug might be in limesurvey, but anyway:

I created a survey using limesurvey with a couple of short free text fields. I set the character limit for all of them in the web interface. Then I tried to export the quexml PDF via limesurvey, but the resulting PDF/xml seemed to ignore this and instead it generated a long and very narrow blank text field (see attached image, questions A7, A8, A9).

http://localhost.sk/~br/quexmlpdf.png

I also noticed that the resulting generated .xml file for the survey through the export had for the respective question set the <format> as follows:

 <format>longtext</format>

I then decided to change this to <format>text</format> and use https://quexmltools.acspri.org.au/quexml/ to generate the pdf and banding, which produced a correct PDF, where the respective text input fields were composed of three separate boxes next to each other (if the character limit was set to three for that specific question).

Did I miss something in the limesurvey settings or is this possibly a bug?

I am using the latest stable version of limesurvey, php 7.2.6, Apache 2.4.33.

Thanks,

Jakub

Question information

Language:
English Edit question
Status:
Solved
For:
queXML Edit question
Assignee:
No assignee Edit question
Solved by:
Adam Zammit
Solved:
Last query:
Last reply:
Revision history for this message
Best Adam Zammit (adamzammit) said : 		#1

Hi Jakub,

The default export to a queXML file from Limesurvey makes all text based fields "longtext". This was a decision made to avoid potential difficulties for people not familiar with queXML.

There isn't a setting to change this in Limesurvey. The method to use would be as you described - export to queXML , then use the queXML tools we provide, or use your own copy of the queXMLPDF class to generate your PDF's.

Adam

Revision history for this message
Jakub Cerveny (jakubc) said : 		#2

OK, thanks!

Revision history for this message
Jakub Cerveny (jakubc) said : 		#3

Thanks Adam Zammit, that solved my question.