<languages />
__TOC__

=Allgemeines=

Das ComfortUpdate ist ein neues Feature seit Version 1.87. Mit Hilfe des ComfortUpdate können Sie Ihre LimeSurvey Installation mit nur wenigen Mauslick aus Ihrem Browser aktualisieren - statt des üblichen manuellen Updates.

Das ComfortUpdate ist momentan ein Service, der umsonst ist - aber ab einem noch nicht näher bestimmten Zeitpunkt in der Zukunft planen wir dafür ein geringes Entgelt zu nehmen.
=Voraussetzungen=

Ihre PHP-Installation muss mit Unterstützung für zlib kompiliert werden. Überprüfen Sie Ihre PHPInfo zu sehen, und/oder kontaktieren Sie Ihren Systemadministrator, um dies zu bestätigen (siehe auch [http://php.net/manual/de/book.zlib.php]).

Your server must be able to connect by SSL to update.limesurvey.org and update-data.limesurvey.org in order to use the ComfortUpdate tool. If you have problems with this and get error messages like

10060 could not connect to the host "update.limesurvey.org"
sollten Sie ihre Proxy / Firewall-Sicherheitseinstellungen bearbeiten oder Ihren Server-Administrator um Hilfe fragen.

=Anwendung von ComfortUpdate=

Das LimeSurvey ComfortUpdate kann auch mit aktiven Umfragen durchgeführt werden. Es ist nicht möglich damit vorhandenen Daten zu löschen oder zu zerstören. Allerdings sollte man im Hinterkopf behalten, dass dies eine Beta-Funktion ist und sicherzustellen, dass Sie Ihre Datenbank und Dateien gesichert haben, bevor Sie fortfahren.

*Öffnen Sie die Globale Einstellungen, wählen Sie die ersten Registerkarte und klicken Sie auf die Schaltfläche für "Updates"
*Es wird ein Update Link angezeigt, wenn eine neue Version von LimeSurvey vorhanden ist. Wenn nicht klicken Sie auf " Jetzt prüfen ", um zu sehen, ob ein neues Update verfügbar ist.
*Wenn ein Update gefunden wird, wird LimeSurvey ein Link angezeigen, damit Sie aktualisieren können. Klicken Sie auf diesen Link um die Aktualisierung zu starten.
* LimeSurvey überprüft jetzt das Installations-Verzeichnis auf entsprechende Berechtigungen, die eine Aktualisierung ermöglichen müssen. Eine Liste der vorgeschlagenen Änderungen werden angezeigt.
* Wenn es irgendwelche Probleme gibt , müssen Sie diese zuerst korrigieren, und dann gelangen Sie zum nächsten Schritt .
* Die ComfortUpdate wird nun ein Backup Ihrer Datenbank anlegen (wenn Sie MySQL verwenden ) und speichert Ihre alte Installationsdateien im Verzeichnis /tmp. Wenn Sie eine anderen Datenbanktyp verwenden, sollten Sie Ihre Datenbank manuell sichern, bevor Sie fortfahren. ComfortUpdate wird nun Ihre Installation auf die neueste Version aktualisieren, einschließlich der Aktualisierung der Datenbank.

=Bekannte Probleme=

==Leere Seite auf Schritt 3==

Wenn Sie eine leere Seite beiSchritt 3 bekommen, bedeutet es in der Regel, dass das Arbeitsspeicherlimit Ihrer PHP-Konfiguration zu niedrig eingestellt ist. Während dieses Schrittes versucht LimeSurvey, ein Datenbank-Backup und ein Datei-Backup (von Dateien, die ersetzt werden soll) zu erstellen.

==Verwendung eines Proxy-Servers für die Verbindung mit update.limesurvey.org==

Wenn Sie sich hinter einem Proxy befinden, müssen Sie möglicherweiseeinige Einstellungen anpassen, um das Komfort-Update zu nutzen. In LimeSurvey 2.05 größer als build 140404 können Sie die den Proxy-Server in der Konfigurationsdatei festgelegen (siehe https://manual.limesurvey.org/Optional_settings#General_settings).

Bei früheren Versionen müssen Sie die Datei http.php in Ihrer LimeSurvey-Installation anpassen. Werfen Sie mit Hilfe eines Texteditors einen Blick auf die Variablen in den ersten Zeilen der Datei und fügen ggf. die Daten Ihres Proxyserver hinzu.

Beispiel: Für eine Verbindung zu einem Proxy-Server 111.111.111.111 Port 1234 ohne Authentifizierung sollten Sie dies so setzen:
var $proxy_host_name="111.111.111.111";
var $proxy_host_port=1234;

Depending on your version, you will find the file in the /admin/classes/ folder or in /application/libraries/admin/http/. There are pre-coded variables within the file so only details of your proxy are needed. If your installation is running unusually slow, wrong proxy settings may be the cause.

2014-01-23T13:50:41Z

Mfaber: Update minimum date for new logic

<translate>

<languages />
<onlyinclude>

===Minimum date (date_min){{NewIn|2.05}} === 


'''Description'''


This question attribute can be used to set the minimum value for the date question. It applies to both, the popup-variant of the calendar and the dropdown fields.


'''Valid values'''


#'''Any date value in format YYYY-MM-DD''' (eg., 2013-08-24)
#'''Any year value'''
#'''Reference to another date/time question'''(eg., dateofbirth)
#'''Expressions''' With expressions, a minimum date can be dynamically calculated. For example, you can use a date from a previous answer + 3 days as a minimum for the present question by entering: date("Y-m-d H:i",strtotime(departuredate)+3*60*60*24).


</onlyinclude>


[[Category:Question Settings]][[Category:Advanced Question Settings]]

</translate>

Question type - Date/de

2014-01-23T13:38:40Z

Mfaber: Created page with "Mit diesem Fragetyp kann ein Datum, eine Uhrzeit oder eine Kombination von Datum und Uhrzeit erhoben werden. Datum und Uhrzeit können direkt eingegeben werden, aus einem Popu..."

<languages />

__TOC__

=Kurzbeschreibung=

<onlyinclude>{{#ifeq:{{{transcludesection|short_description}}}|short_description|Mit diesem Fragetyp kann ein Datum, eine Uhrzeit oder eine Kombination von Datum und Uhrzeit erhoben werden. Datum und Uhrzeit können direkt eingegeben werden, aus einem Popup-Kalender oder aus Drop-Down-Boxen ausgewählt werden. Zur Validierung können Minimal- und Maximaldaten festgelegt werden. Verschiedene Datums-und Zeitformate werden unterstützt. Einige Funktionen sind erst ab LimeSurvey Version 2.05+ verfügbar.

[[File:D_Date_DD.jpg]] [[File:datetime.jpg]] [[File:timepicker.jpg]]

}}</onlyinclude>
=Basis-Einstellungen=

{{QS:mandatory/de}}

{{QS:relevance/de}}

=Erweiterte Einstellungen=

{{QS:Reverse/de}}

{{QS:Random_group/de}}

{{QS:dropdown_dates/de}}

{{QS:Hidden/de}}

{{QS:dropdown_dates_year_min/de}}

{{QS:dropdown_dates_year_max/de}}

{{QS:date_min}}

{{QS:date_max}}

{{QS:em_validation_q}}

===Validation on date===
{{Alert||text=Dates in Limesurvey are saved as a string (text format).}}
<div class="boxed">To really be able to work (and calculate) with dates, these have to be converted to a number format. The function strtotime{{NewIn|2.0|b=130515}} , which calculates the number of seconds from the 1st January 1970 to a given date can be used for this. Using strtotime() one can for example enforce that only dates before "today" are entered using the following expression: strtotime(self)<=strtotime("now").
Or enforce that that only dates after a certain date can be entered: strtotime(self)>strtotime("2013-03-27")</div>

{{Alert|Please be aware that strtotime() works with a lot of different but not ALL date formats. Limesurvey's default date format (MM-DD-YYYY) does NOT work with strtotime(). Please set your survey to use one of the following date formats to avoid problems: YYYY-MM-DD, YYYY/MM/DD, DD.MM.YYYY, MM/DD/YYYY, DD-MM-YYYY.}}

{{QS:em_validation_q_tip}}

{{QS:Page_break}}

Translations:Question type - Date/25/de

2014-01-23T13:38:39Z

Mit diesem Fragetyp kann ein Datum, eine Uhrzeit oder eine Kombination von Datum und Uhrzeit erhoben werden. Datum und Uhrzeit können direkt eingegeben werden, aus einem Popup-Kalender oder aus Drop-Down-Boxen ausgewählt werden. Zur Validierung können Minimal- und Maximaldaten festgelegt werden. Verschiedene Datums-und Zeitformate werden unterstützt. Einige Funktionen sind erst ab LimeSurvey Version 2.05+ verfügbar.

Question type - Date/de

2014-01-23T13:35:13Z

Mfaber:

<languages />

__TOC__

=Kurzbeschreibung=

<onlyinclude>{{#ifeq:{{{transcludesection|short_description}}}|short_description|This question type can be used to ask for a certain date, for a time or a combination of date and time. Dates and times can be entered directly, chosen from a popup calendar or from drop-down boxes. For validation, minimum and maximum dates can be chosen. Various date and time formats are supported. Some of these features are only available from LimeSurvey version 2.05+.

[[File:D_Date_DD.jpg]] [[File:datetime.jpg]] [[File:timepicker.jpg]]

}}</onlyinclude>
=Basis-Einstellungen=

{{QS:mandatory/de}}

{{QS:relevance/de}}

=Erweiterte Einstellungen=

{{QS:Reverse/de}}

{{QS:Random_group/de}}

{{QS:dropdown_dates/de}}

{{QS:Hidden/de}}

{{QS:dropdown_dates_year_min/de}}

{{QS:dropdown_dates_year_max/de}}

{{QS:date_min}}

{{QS:date_max}}

{{QS:em_validation_q}}

===Validation on date===
{{Alert||text=Dates in Limesurvey are saved as a string (text format).}}
<div class="boxed">To really be able to work (and calculate) with dates, these have to be converted to a number format. The function strtotime{{NewIn|2.0|b=130515}} , which calculates the number of seconds from the 1st January 1970 to a given date can be used for this. Using strtotime() one can for example enforce that only dates before "today" are entered using the following expression: strtotime(self)<=strtotime("now").
Or enforce that that only dates after a certain date can be entered: strtotime(self)>strtotime("2013-03-27")</div>

{{Alert|Please be aware that strtotime() works with a lot of different but not ALL date formats. Limesurvey's default date format (MM-DD-YYYY) does NOT work with strtotime(). Please set your survey to use one of the following date formats to avoid problems: YYYY-MM-DD, YYYY/MM/DD, DD.MM.YYYY, MM/DD/YYYY, DD-MM-YYYY.}}

{{QS:em_validation_q_tip}}

{{QS:Page_break}}

Translations:Question type - Date/4/de

2014-01-23T13:35:12Z

Mfaber:

[[File:D_Date_DD.jpg]] [[File:datetime.jpg]] [[File:timepicker.jpg]]

QS:Relevance

2014-01-23T13:17:15Z

Mfaber: Added a description of what relevance actually is.

<translate>

<languages />
<onlyinclude>

===Relevance equation=== 


{{FeatureStarting|v=1.92}}


'''Description'''


If the value of the relevance equation is "1" or "true", the question is "relevant" in the survey context, i.e. it is shown to the survey participant. If not, the question is hidden. All questions let you specify a relevance equation. Relevance is the successor to conditions and supports much more complex conditional logic.


'''Syntax Highlighting'''


Whenever you save the relevance equation, it will be evaluated and syntax-highlighted. Any errors will be color coded so that you can quickly detect and fix them.


'''Valid values'''


Any equation, using [[Expression Manager|Expression Manager]] syntax, without surrounding curly braces.


'''Examples'''


Here are good examples of [[Expression Manager HowTos#Syntax Highlighting|syntax highlighting]]


</onlyinclude>
[[Category:Question Settings]][[Category:Core Question Settings]]
</translate>

Question type - Date

2014-01-23T13:10:09Z

Mfaber: Removed "default value"...there is no such field in date/time question

<languages />
<translate>


__TOC__

=Short description= 

</translate>
<onlyinclude>{{#ifeq:{{{transcludesection|short_description}}}|short_description|<translate>

This question type can be used to ask for a certain date, for a time or a combination of date and time. Dates and times can be entered directly, chosen from a popup calendar or from drop-down boxes. For validation, minimum and maximum dates can be chosen. Various date and time formats are supported. Some of these features are only available from LimeSurvey version 2.05+.


[[File:D_Date_DD.jpg]]
[[File:datetime.jpg]]
[[File:timepicker.jpg]]

</translate>
}}</onlyinclude><translate>

=Core settings= 


{{QS:mandatory}}


{{QS:relevance}}

=Advanced settings= 


{{QS:Reverse}}


{{QS:Random_group}}


{{QS:dropdown_dates}}


{{QS:Hidden}}


{{QS:dropdown_dates_year_min}}


{{QS:dropdown_dates_year_max}}


{{QS:date_min}}


{{QS:date_max}}


{{QS:em_validation_q}}

===Validation on date=== 
{{Alert||text=Dates in Limesurvey are saved as a string (text format).}}
<div class="boxed">To really be able to work (and calculate) with dates, these have to be converted to a number format. The function strtotime{{NewIn|2.0|b=130515}} , which calculates the number of seconds from the 1st January 1970 to a given date can be used for this. Using strtotime() one can for example enforce that only dates before "today" are entered using the following expression: strtotime(self)<=strtotime("now").
Or enforce that that only dates after a certain date can be entered: strtotime(self)>strtotime("2013-03-27")</div>


{{Alert|Please be aware that strtotime() works with a lot of different but not ALL date formats. Limesurvey's default date format (MM-DD-YYYY) does NOT work with strtotime(). Please set your survey to use one of the following date formats to avoid problems: YYYY-MM-DD, YYYY/MM/DD, DD.MM.YYYY, MM/DD/YYYY, DD-MM-YYYY.}}


{{QS:em_validation_q_tip}}


{{QS:Page_break}}

</translate>

Question type - Date

2014-01-23T13:07:30Z

Mfaber: Feature overview of date/time question in short description

<languages />
<translate>


__TOC__

=Short description= 

</translate>
<onlyinclude>{{#ifeq:{{{transcludesection|short_description}}}|short_description|<translate>

This question type can be used to ask for a certain date, for a time or a combination of date and time. Dates and times can be entered directly, chosen from a popup calendar or from drop-down boxes. For validation, minimum and maximum dates can be chosen. Various date and time formats are supported. Some of these features are only available from LimeSurvey version 2.05+.


[[File:D_Date_DD.jpg]]
[[File:datetime.jpg]]
[[File:timepicker.jpg]]

</translate>
}}</onlyinclude><translate>

=Core settings= 


{{QS:mandatory}}


{{QS:defaults}}


{{QS:relevance}}

=Advanced settings= 


{{QS:Reverse}}


{{QS:Random_group}}


{{QS:dropdown_dates}}


{{QS:Hidden}}


{{QS:dropdown_dates_year_min}}


{{QS:dropdown_dates_year_max}}


{{QS:date_min}}


{{QS:date_max}}


{{QS:em_validation_q}}

===Validation on date=== 
{{Alert||text=Dates in Limesurvey are saved as a string (text format).}}
<div class="boxed">To really be able to work (and calculate) with dates, these have to be converted to a number format. The function strtotime{{NewIn|2.0|b=130515}} , which calculates the number of seconds from the 1st January 1970 to a given date can be used for this. Using strtotime() one can for example enforce that only dates before "today" are entered using the following expression: strtotime(self)<=strtotime("now").
Or enforce that that only dates after a certain date can be entered: strtotime(self)>strtotime("2013-03-27")</div>


{{Alert|Please be aware that strtotime() works with a lot of different but not ALL date formats. Limesurvey's default date format (MM-DD-YYYY) does NOT work with strtotime(). Please set your survey to use one of the following date formats to avoid problems: YYYY-MM-DD, YYYY/MM/DD, DD.MM.YYYY, MM/DD/YYYY, DD-MM-YYYY.}}


{{QS:em_validation_q_tip}}


{{QS:Page_break}}

</translate>

File:Timepicker.jpg

2014-01-23T13:05:31Z

Mfaber: Choosing a time using the timepicker in LimeSurvey

Choosing a time using the timepicker in LimeSurvey

File:Datetime.jpg

2014-01-23T13:04:49Z

Mfaber: Datetimepicker in Limesurvey

Datetimepicker in Limesurvey

Changing an active survey

2014-01-23T09:51:45Z

Mfaber: Instructions for using the new vvimport/vvexport for changing an active survey

<languages />

<translate>

= Changing an active survey= 


While a survey is active, it is not possible to add or remove questions or answers, or to change the type of the question. However, it is still possible to:


* Modify the text of a question (for example to correct typos or whatever)
* Modify the attributes of a question (for example to include it in the public statistics, insist on a particular number of answers for a multiple options question or whatever).


To make more complicated changes, you need to use the import/export facilities described in the next section.

= Changing an active survey by import and export= 


If you find you need to add or remove questions or answers or a combination of these, LimeSurvey has functions called "VV-Import" and "VV-Export" that can be used to move all the results from one survey across to another survey.


VV-Import and VV-Export can also be used to combine survey results when the same survey has been run on more than one server.


The method for using VV-Import and VV-Export is as follows:
* Create a new survey and copy the structure of the original one. If necessary modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _old_ survey
* Perform the VV-Import into the _new_ survey

In older Versions of LimeSurvey (<2.05+) you need to apply a method involving some manual handling of data files:
* Export the structure of the original survey. Then import that file as a new survey, and - if necessary - modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _new_ survey (we'll call this the 'first export')
* Perform a VV-Export from the _old_ survey (we'll call this the 'second export')
* Cut the two top rows from the first export and insert them as the top two rows in the second export.
* While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.
* Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)
* Save it all as a Tab-Delimited file
* Perform the VV-Import into the _new_ survey


Exporting the survey structure is done in the survey toolbar. The VV-Import and VV-Export buttons are found in the "Browse responses" page of an active survey.

= Tricks= 
* When '''rearranging columns''' switch column ids ( row 2) instead of all content columns (3-end)
* '''Rename vv files''' as .txt and excel will open them correctly (save as unicode and rename)
* To '''change the survey title''' go to your admin section and click the 'edit survey' button you will be presented with a screen where you can edit your survey details. On the first Edit Survey - Step 1 of 2 page, click the 'Save and continue' button at the bottom of the page and you will get the screen you need to change the title.
</translate>

Workarounds: Question design, layout and templating

2013-11-01T12:17:19Z

Mfaber: correction of a typo

This section more or less deals with styling your survey, adjusting the layout and setting up special question types. You can find '''similar information''' at these pages:
* [[The template editor]]
* [[Workarounds: Manipulating a survey at runtime using Javascript]]
* [[Workarounds: Survey behaviour]].

<div class="simplebox"><center><br />'''Please keep in mind that these workarounds are not official LimeSurvey extensions - they are solutions that users have created for themselves.<br /><span style='color:#EE0000,#FFFFFF'>Therefore LimeSurvey can't offer guarantees or support for these solutions.</span><br />If you have questions, please contact the users that, thankfully, shared their solutions with the community.'''<br /><br /></center></div>

__TOC__

= Get rid of the quetstion mark (help.gif)=

''Tested with: 1.80+ (6536)''

To get rid of the question mark symbol that LimeSurvey displays at the end of a question, you can either upload an empty help.gif into the template folder (as discussed in the forum) or you can use the Template editor: Open the ''template.css'' of your template and search for ''div.questionhelp img'', then add a ''visibility:hidden;''

It will look something like this:

<syntaxhighlight lang="php" enclose="div">

div.questionhelp img

{

margin:5px;

visibility:hidden;

}

</syntaxhighlight>

You can also '''replace the image''' by following [[The template editor#Replacing the help icon|these instructions]].

=Require users to check a box agreeing to privacy statement before registering for a survey=

If you need to have users positively acknowledge a privacy statement before submitting a registration form, the following will help you do this.

It involves a minor modification to common.php in versions up to 1.85. Later versions may not require this.

Edit common.php and look for the line (at approximately line 3014)

<syntaxhighlight lang="php" enclose="div">$registerform .= "<tr><td></td><td>
<input class='submit' type='submit' value='".$clang->gT("Continue")."' />"
</syntaxhighlight>

and change it to:

<syntaxhighlight lang="php" enclose="div">$registerform .= "<tr><td></td><td>
<input id='registercontinue' class='submit' type='submit' value='".$clang->gT("Continue")."' />"
</syntaxhighlight>

Then save common.php. This gives you DOM access to the "continue" button on the register form, but will have no other practical effect or change to LimeSurvey's operations.

Next, you need to edit the template you are using (see the documentation on the Template editor if you don't know how to do this).

In the template editor, open the screen "Register page" and select the file "register.pstpl"

There are two modifications you need to make to this file. The first is to add the following code after the line that says ''{REGISTERFORM}''.

<syntaxhighlight lang="php" enclose="div"><script type='text/javascript'>

</script></syntaxhighlight>

This code disables the "Continue" button so that nobody can process the registration form until they've clicked the checkbox.

The second modification to make is to be done between the lines {REGISTERMESSAGE2} and {REGISTERFORM}. Add:

<syntaxhighlight lang="php" enclose="div"><center>
<label> Accept
<input type='radio'
name="privacy"
value="YES"
onChange="if(this.checked) {
document.getElementById('registercontinue').disabled=false;
}" />
</label>
<label>I don't accept
<input type='radio'
name="privacy"
value="NO"
CHECKED
onChange="if(this.checked) {
document.getElementById('registercontinue').disabled=true;
}" />
</label>
</center></syntaxhighlight>

Then the users will have to agree to whatever text you replace "Do you agree to privacy stuff?" before they continue on and register.

(Thanks to ''Pippo_Jedi'' for helping work this out)

=Different progress indicator=

==Version 1.87 and later:==

Add the following to the end of template.js. It will find the progress value and insert it into the element following the progress bar.

It should be pointed out that I had to introduce a delay in firing the function because the progress value is not calculated until after template.js is called. The delay is set at 1/10 of a second but you may be able to reduce that.

<syntaxhighlight lang="php" enclose="div">

// Display progress value

function setProgValue() {

var progress = $('#progressbar').attr('aria-valuenow');

$('#progress-post').text(progress+'%').show();

}

$(document).ready(function(){

$('#progress-post').hide();

setTimeout('setProgValue()',100);

});

</syntaxhighlight>

If you want to hide the "0%" before the progress bar, add the following to the end of template.css:

<syntaxhighlight lang="php" enclose="div">
#progress-pre {

display: none;

}

</syntaxhighlight>

=Delete unwanted gaps in question title=

''Tested with: ''

When copying data (questions, answers, ...) from MS Word or other applications into the editor there might occur some gaps in the question title.

There are two solutions to this:
# Use popup mode and manually delete unwanting extra html tags (requires html knowledge).
# Disable paste word feature: Tweak your limesurvey-config.js file in limesurvey/admin/scripts/fckeditor.26 and set the following option to true:

<syntaxhighlight lang="php" enclose="div">FCKConfig.ForcePasteAsPlainText = true ;</syntaxhighlight>

After that clear you browser cache and try again.

=How to change the <font-size> tags using CSS=

''This workaround was deleted because it is outdated. Such changes can be done by [[The template editor#Styling questions with CSS|adjusting template.css]] of your template.

=Question type variation: Scale with bars (one and two sided)=

''Tested with: ''

Some methodogical issues to think about: Very often a common scale as 1 to 5 or -2 to +2 fits all needs, as the shown subject is clearly defined as positive or negative. As soon as you would reduce the influence from the question and scale on the respondent, you will need something neutral to determine tendences, emphases and so on.

So I put up a new variation of the one and two sided array question:

ttp://www.limesurvey.org/images/fbfiles/images/example_bar_scale.jpg

In my example the left side reads "strategical planning" and the right side "operative business". None of these are purely negative or positive, so the bars only show in which direction the balancing point moves.

To realize a question as shown above just do as follows:

Set up as many bars as you will need (in my example there are four different bars in total) with a graphic program like PAINT .NET, GIMP or similar ones (yes, you may also use commercial software like Photoshop). To prevent the bars from looking twitchy, designate the size in advance. I did one bar 60x15 px, one 45x15px, one 30x15px and at last 15x15px. Save them as PNG, JPG or GIF.
# Create a new label set within Lime. Call it whatever you like.
# Enter a code number at first, then press the pencil symbol to enter the editor.
#Press the "Insert / edit image" button and upload the bar you want to insert with the FCK upload tool. Then choose the uploaded picture, save and leave the FCK editor.
#The row in the lable editor now shows an <img>-tag which refers to your bar picture.
#Repeat the above described steps as often as needed to build up your bar scale.

=Doing a Likert Scale=

''Tested with: ''

A Likert Scale is a special type of the Semantic Differential question where several item shall be rated on different scales, each marked at the beginning and at the end with opposite statements. See example:

http://www.limesurvey.org/images/fbfiles/images/lickert.jpg

To do this in LimeSurvey just follow these steps:
#Create a label set with values from 0 to 7 (for the classic Likert Scale - feel free to choose other ranges).
#Create a new question and choose Array (Flexible Labels) as question type.
#Assign the Likert Scale label set to this question.
#Enter your answers as follows:

<syntaxhighlight lang="php" enclose="div"><DIV style="white-space: nowrap;">ITEM statement1|statement2</div></syntaxhighlight>

The white-space style is to avoid line breaks which would ruin the whole scale. feel free to insert non-breakable spaces between the ITEM and statement1 to define the margin between these to strings.

=Alternate background colour of questions=

''Tested with: 1.85+ (7191)''

To alternate the background colour of questions, open the ''template.css'' of your template with the Template Editor or a text editor and modify the ''Question styles'' section to include the following style.

<syntaxhighlight lang="php" enclose="div">

div#question2 td.questiontext,

div#question4 td.questiontext,

div#question6 td.questiontext {

background-color: #E0EBF8;

}

</syntaxhighlight>

Be sure to apply the style to all of the questions you would like modified using their question IDs (''question2, question4, question6'' in this case). Question IDs are displayed when creating or editing questions - see below:

[[File:qid_1_493x173.gif]]

Here the question ID is #question80 .

=Embedding audio in questions=

''Tested with: 1.85+ (7191), IE 7, FireFox 3''

Audio clips can be embedded in most question text or answer text. In this example, using the default template, I've embedded clips into the answers of an '''''Array (Yes/No/Uncertain)''''' question to ask respondents how they feel about some sounds. The resulting question will look like this.

[[File:audioTest_595x202.gif]]

It's accomplished by placing the following code in each of the answers.

<syntaxhighlight lang="php" enclose="div">

<embed height="20" width="128" autostart="false" controls="console"

loop="true" volume="50" src="{TEMPLATEURL}audio_1.mp3"></embed>

</syntaxhighlight>

Some notes about the code:
*The ''audio_1.mp3'' part will be different for each answer (it's the audio file name).
*In this case the audio files are residing in the template folder being used for this survey (that's where ''{TEMPLATEURL}'' points to) but they can be placed anywhere if you use an absolute URL in the ''src'' parameter - something like ''src="http://mysite.com/audio/audio_1.mp3"''
*If the audio file doesn't exist where the ''src'' parameter indicates, the player will not appear.
*You'll need to insert the code into the answers using the source screen - click on "Edit answers", click the pencil beside the text box, click "Source" in the pop-up, enter the code and save it with the little diskette icon.
*You may need to turn off the XSS filter - see the documentation for [http://docs.limesurvey.org/tiki-index.php?page=Global+settings&structure;=English+Instructions+for+LimeSurvey#Security Global settings].

Although the above example places the audio in the answer text of the question, the same principles can be used to place it in the question text itself. Something like this perhaps.

[[File:audioTest_595x154.gif]]

=Hiding inputs of a "Multiple options with comments" question=

Tested with: 1.85+ (7253), IE 6/7, FireFox 3.0, Safari 3.2, Chrome 2.0

There may be times when you want to hide some of the input boxes of a '''''Multiple options with comments''''' question as in the image below.

[[File:hidden_inputs_541x168.gif]]

This can be accomplished with CSS (see [[The template editor#Styling questions with CSS|Styling questions in LimeSurvey 1.8]]). For each input that you want to hide, add the following style to your template.css file:

<syntaxhighlight lang="css" enclose="div">
#answer11111X22X33Acomment {
display: none;
}
</syntaxhighlight>
Where 11111 is your survey ID, 22 is your group ID, 33 is your question ID and A is the answer code.

Note that you will still see columns for the hidden inputs in your data but they will be empty.

=Multiple question types in array=

''Tested with: 1.90 - 1.92+, IE 7/8/9, Firefox 13, Safari 5, Chrome 10''

'''Note: sample survey works in 2.00+ but code is different from example below. Make sure to use the right code. Copy paste the script from the sample survey and adapt.'''

[[Media:limesurvey_survey_62584.lss|Download the sample survey]]

This workaround allows you to present multiple question types in what appears to be an array - as depicted in the image below and [http://www.partnersinc.biz/surveys//index.php?sid=62584&newtest=Y&lang=en demonstrated here] (download the sample survey - [[Media:limesurvey_survey_62584.lss|limesurvey_survey_62584.lss]]). This example uses the default template but should be adaptable to any template using divisions for question containers.

[[File:inline_questions_700x228.png]]

Basically what we do is take groups of questions (5 in this case), wrap them in a division and make them line up nicely horizontally and vertically. The width of the survey is also fixed to prevent wrapping issues. We do this with a JavaScript/jQuery function that inserts the necessary wrappers and then modifies styles so everything behaves properly. The top row is 5 boilerplate questions with the "column headers" as question text (the first just has a blank space). The following rows are a boilerplate with the "row headers" followed by 4 assorted questions.

It should be noted that using conditions on these questions may result in unexpected behavior. If a question is hidden by conditions, the question(s) to the right of it will move over to take its place.

Implementation is as follows:
#Create your questions keeping in mind how they will lay out when grouped into rows (in this example - boilerplate, yes/no, short text, numeric, dropdown, and repeat).
#In the source of the first boilerplate question add the function below (see [http://manual.limesurvey.org/wiki/Workarounds:_Manipulating_a_survey_at_runtime_using_Javascript#How_to_use_Script_.28eg._JavaScript_etc..29_in_LimeSurvey.3F How to use script]).
#Modify the number of rows, number of columns and the start placement in the function call (line 6) as required (the example uses 4 rows and 5 columns and the "array" starts with the third question on the page).

The code may look intimidating at first but it's actually fairly simple. I've laid it out as sequentially as possible and purposely used few shortcuts and many comments to make it easier to follow.

Notes:
*If you use question types other than boilerplate, short text, list dropdown, numeric or yes-no, you'll need to add to the last section of code, where it hides the question text and formats the inputs for display this way.
*Any extra questions on the page should follow this grid of questions, not precede them.
* If you use boilerplate as question type you should add after:
<syntaxhighlight lang="javascript" enclose="div">
// Hide the question text elements in non-boilerplate questions
$('div.questionCell td.questiontext').parent().hide();
</syntaxhighlight>
the following 2 lines
<syntaxhighlight lang="javascript" enclose="div">
//repair boilerplate questioncells
$('div.boilerplate td.questiontext').parent().show();
</syntaxhighlight>

Javascript code:
<syntaxhighlight lang="javascript" enclose="div">
<script type="text/javascript" charset="utf-8">
$(document).ready(function() {
// Call the "sideBySide" function with number of rows, columns and start position
sideBySide(4, 5, 3);
});

function sideBySide(rows, columns, startQuestion) {

/*********** Display multiple questions side by side ***********/

if ($('div.qRow1').length == 0) {
var rowNum = 0;
var colNum = 1;
var rowList = new Array();

//////// Add question classes for later use ////////

// Loop through all questions and add row and column specific classes
$('div[id<div class="simplebox">="question"]').each(function(i) {
if(i >= (startQuestion-1) && rowNum < rows) { // This IF condition only needed if there are questions before or following the "inline" questions
$(this).addClass('qRow'+rowNum+'').addClass('qCol'+colNum+'').addClass('inlineQuestion');
if(rowNum == 0 && colNum > 1) {
$(this).addClass('columnLabel');
}

if(rowNum > 0 && colNum == 1) {
$(this).addClass('rowLabel');
}
else if(rowNum > 0 && colNum > 1) {
$(this).addClass('questionCell');
}

if(colNum == columns) {
rowList.push('qRow'+rowNum+'');
rowNum++;
colNum = 1;
}
else {
colNum++;
}
}
else {
$(this).addClass('normalQuestion');
}
});

//////// Survey layout manipulation ////////

// Fix the width of the survey
$('table.outerframe').css({
'width': '900px'
});

// Wrap each "row" in a wrapper div
$(rowList).each(function(i) {
$('.'+this+'').wrapAll('<div id="inlineWrapper'+i+'" class="inlineRow" />');
});

// Style the wrapper divs
$('.inlineRow').css({
'width': '850px',
'margin': '0 auto 0 auto',
'clear': 'both'
});

$( '.inlineRow:first' ).css({
'margin-top': '10px'
});

// Get all the questions to sit politely side by side
$( '.inlineQuestion' ).css({
'float': 'left',
'height':'41px',
'overflow':'hidden',
'margin-bottom': '-8px'
});
$( '.inlineQuestion .questionhelp' ).hide();
$( '.inlineQuestion .survey-question-help' ).parent().hide();

// A little space under the last row
$( '.inlineRow:last .inlineQuestion' ).css({
'margin-bottom': '10px'
});

// Any questions not displayed inline (this is only needed if there are questions following the "inline" questions)
$( '.normalQuestion' ).css({
'clear': 'both'
});

//////// Column manipulation ////////

// Set the column widths - can be set individually if necessary
// Must add up to less than 100%
$( '.qCol1' ).css({
'width': '12%'
});

$( '.qCol2, .qCol3, .qCol4, .qCol5' ).css({
'width': '22%'
});

//////// Question manipulation ////////

// Hide the answer element in boilerplate questions
$( 'div.boilerplate td.answer' ).parent().hide();

// Hide the question text elements in non-boilerplate questions
$('div.questionCell td.questiontext').parent().hide();

// Push the question tables to 100%
$( 'div.inlineRow table' ).css({
'width': '100%'
});

// Get everything to line up nicely vertically
$( '.inlineQuestion td.questiontext, .inlineQuestion td.answer p' ).css({
'text-align': 'center'
});

// Adjust cell heights so everything lines up nicely horizontally
$( '.inlineQuestion td.answer, .inlineQuestion td.questiontext' ).css({
'height':'35px',
'overflow':'hidden',
'padding':'0.5em'
});
$( '#inlineWrapper0 .inlineQuestion' ).css({ 'height':'50px' });
$( '#inlineWrapper0 td.questiontext' ).css({
'height':'50px'
});

// Yes-no question styles
$( 'div.yes-no ul' ).css({
'text-align': 'center',
'font-size': '90%',
'margin': '0',
'padding-bottom': '5px'
});
$( 'div.yes-no li' ).css({
'padding-right': '1.5em'
});
$( 'div.yes-no td.answer' ).css({
'padding-bottom': '0'
});

// Short-text question styles
$( 'div.text-short input' ).css({
'width': '125px',
'margin-left': '0'
});

// Numeric question styles
$( 'div.numeric input' ).css({
'width': '125px',
'margin-left': '0'
});
$( 'div.numeric p.tip' ).css({
'display': 'none'
});

// Get rid of the margins around select boxes
$( 'p.question' ).css({ 'margin':'0' });
}
}
</script>
</syntaxhighlight>
<br /><br />

=Star Rating System=

''Tested with: 1.85+ (7557), IE 6/7, FireFox 3.0, Safari 3.2,''

This workaround uses the [http://www.fyneworks.com/jquery/star-rating/ jQuery Star Rating Plugin] to display a series of stars that are used to generate a rating value. This value is then passed to either a hidden numeric input question or a hidden list radio question. Both methods are outlined below - use one or both depending on whether you want to use [Assessments|assessments].

The plugin uses a series of radio inputs to generate the stars (more about these below). It allows the use of whole or partial stars as shown in [http://www.partnersinc.biz/surveys//index.php?sid=47586&newtest=Y&lang=en this demo] and the image below.

[[File:star_rating_700x324.png]]

==Star Rating System Using Numeric Input Question==

Use this method if you would like your rating data to be collected as a numeric value and don't want to use [[Assessments|LimeSurvey assessments]] - it's a little easier to implement. There is a demo [http://www.partnersinc.biz/surveys//index.php?sid=47586&newtest=Y&lang=en here] (first question).

'''Implementation is as follows:'''
#Turn off ''$filterxsshtml'' to allow insertion of JavaScript in the questions. (See [[Optional settings#Security|documentation here]])
#[http://www.fyneworks.com/jquery/star-rating/ Download the plugin] and place the following included files in your template folder:
##jquery.MetaData.js
##jquery.rating.css
##jquery.rating.js
##delete.gif
##star.gif
#In the <head> section of your startpage.pstpl, add the following code to link to the files.

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" src="{TEMPLATEURL}jquery.rating.js" charset="utf-8"></script>

<script type="text/javascript" src="{TEMPLATEURL}jquery.MetaData.js" charset="utf-8"></script>

<link rel="stylesheet" type="text/css" href="{TEMPLATEURL}jquery.rating.css" />

</syntaxhighlight>

5. Create a numeric input question and then in the source of the question add as many radio inputs as star segments. For example, if you would like 5 stars, each with half-segments (as in the demo Q1), you would need 10 radio inputs and that would give rating values from 1-10.

Don't confuse these inputs with the actual question, they are just for the plugin's use.

At this point your question source code should look something like below. Make sure that all inputs have the same name. Each input must have the same title as value and these must be sequential. Don't worry about how all of this looks in the WSYSWYG editor - the plugin is going to hide these inputs and replace them with stars.

<syntaxhighlight lang="php" enclose="div">

Q1 - Some question text here.<br /><br />

<div id="starContainer">

<input type="radio" class="star { split:2 }" title="1" value="1" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="2" value="2" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="3" value="3" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="4" value="4" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="5" value="5" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="6" value="6" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="7" value="7" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="8" value="8" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="9" value="9" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="10" value="10" name="q1Rate" />

</div>

</syntaxhighlight>

6. A note on split stars. The stars in the above example are split in half by the ''{ split:2 }'' metadata. So if you don't want split stars, your inputs would look like:

'''<input type="radio" class="star" title="1" value="1" name="q1Rate" />'''

And stars split into third-segments would look like:

'''<input type="radio" class="star { split:3 }" title="1" value="1" name="q1Rate" />'''

7. Finally, in the source of the question add the following function after your inputs. (See [[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|How to use script here]])

Some notes on the code:
*Replace "SSSSS", "GG", "QQ" in the function call at the end with the survey ID, group ID and question ID respectively.
*The code will hide the numeric input and pass the rating values into it as they are changed. If the rating is canceled the numeric input is nullified. If a respondent navigates away from the page then returns the code "remembers" the previous rating and displays the stars accordingly.
*If you want to apply it to more numeric questions on the same page simply add more calls with the appropriate IDs. (eg. handleRatingNumeric(11111, 22, 1); handleRatingNumeric(11111, 22, 2); ...) .

Code:

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" charset="utf-8">

$(document).ready(function() {

function handleRatingNumeric (sID, gID, qID) {

// Hide the numeric input

$('#question' + qID + ' td.answer').parent().hide();

// Get a previous rating (if any) and use it to initialize the star display

var rating = $('#answer' + sID + 'X' + gID + 'X' + qID + '').val();

if ( rating != '' ) {

$('#question' + qID + ' input.star').rating('select', rating);

}

// Listener on the star rating cancel element

$('#question' + qID + ' div.rating-cancel').click(function(event) {

// Nullify the rating if the Cancel element is clicked

rating = '';

$('#answer' + sID + 'X' + gID + 'X' + qID + '').val(rating);

});

// Listener on the star rating elements

$('#question' + qID + ' div.star-rating').click(function(event) {

// Find the value of the highest clicked star and pass it into the text input

$('#question' + qID + ' div.star-rating-on').each(function(i) {

rating = $(this).children('a').html( );

});

$('#answer' + sID + 'X' + gID + 'X' + qID + '').val(rating);

});

}

// Call the function for the numeric question

handleRatingNumeric (SSSSS, GG, QQ);

});

</script>

</syntaxhighlight>

==Star Rating System Using List (Radio) Question==

Use this method if you would like to use [[Assessments|assessments]]. There is a demo [http://www.partnersinc.biz/surveys//index.php?sid=47586&newtest=Y&lang=en here] (second question).

'''Implementation is as follows:'''

1. Turn off ''$filterxsshtml'' to allow insertion of JavaScript in the questions. (See [[Optional settings#Security|documentation here]])

2. Set up the template to use custom onload functions. (See the [[Workarounds: Manipulating a survey at runtime using Javascript#Custom onload function|workaround here]])

3. [http://www.fyneworks.com/jquery/star-rating/ Download the plugin] and place the following included files in your template folder:
*jquery.MetaData.js
*jquery.rating.css
*jquery.rating.js
*delete.gif
*star.gif

4. In the <head> section of your startpage.pstpl, add the following code to link to the files.

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" src="{TEMPLATEURL}jquery.rating.js" charset="utf-8"></script>

<script type="text/javascript" src="{TEMPLATEURL}jquery.MetaData.js" charset="utf-8"></script>

<link rel="stylesheet" type="text/css" href="{TEMPLATEURL}jquery.rating.css" />

</syntaxhighlight>

5. Create a list (radio) question with the same amount of sequentially numbered answers as star ratings. For example, if you want 5 whole-stars, you would create 5 answers, as in the image below, and this would give you ratings from 1-5. Note that the "Codes" and "Answers" must be sequential numbers.

[[File:star_rating_700x156_v2.png]]

6. In the list (radio) question, set the [[Advanced question settings|hide_tip]] question attribute to 1

7. In the source of the question add as many radio inputs as star segments. So 5 whole-stars (as in the demo Q2), would need 5 radio inputs.

Don't confuse these inputs with the actual question, they are just for the plugin's use.

At this point your question source code should look something like below. Make sure that all inputs have the same name. Each input must have the same title as value and these must be sequential. Don't worry about how all of this looks in the WSYSWYG editor - the plugin is going to hide these inputs and replace them with stars.

<syntaxhighlight lang="php" enclose="div">

Q2 - Some question text here.<br /><br />

<div id="starContainer">

<input type="radio" class="star" title="1" value="1" name="q2Rate" />

<input type="radio" class="star" title="2" value="2" name="q2Rate" />

<input type="radio" class="star" title="3" value="3" name="q2Rate" />

<input type="radio" class="star" title="4" value="4" name="q2Rate" />

<input type="radio" class="star" title="5" value="5" name="q2Rate" />

</div>

</syntaxhighlight>

8. A note on split stars. The stars in the above example are whole-stars. If you want them split you need to add metadata to the class - something like ''{ split:2 }''. So if you want half-stars your inputs would look like:

'''<input type="radio" class="star { split:2 }" title="1" value="1" name="q1Rate" />'''

And stars split into third-segments would look like:

'''<input type="radio" class="star { split:3 }" title="1" value="1" name="q1Rate" />'''

9. Finally, in the source of the question add the following function after your inputs. (See [http://docs.limesurvey.org/tiki-index.php?page=Workarounds&structure;=English+Instructions+for+LimeSurvey#How_to_use_Script_eg._JavaScript_etc._ How to use script here])

Some notes on the code:
*Replace "SSSSS", "GG", "QQ" in the function call at the end with the survey ID, group ID and question ID respectively.
*The code will hide the question radio buttons and toggle them as the rating values are changed. If the rating is canceled all question inputs are unchecked. If a respondent navigates away from the page then returns the code "remembers" the previous rating and displays the stars accordingly.
*If you want to apply it to more numeric questions on the same page simply add more calls with the appropriate IDs. (eg. handleRatingRadio(11111, 22, 1); handleRatingRadio(11111, 22, 2); ...) .

Onload code:

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" charset="utf-8">

$(document).ready(function() {

function handleRatingRadio (sID, gID, qID) {

// Hide the radio input

$('#question' + qID + ' td.answer').parent().hide();

// Get a previous rating (if any) and use it to initialize the star display

var rating = $('#question' + qID + ' input.radio[checked=true]').attr('value');

//if ( rating != '' ) {

if ( rating ) {

$('#question' + qID + ' input.star').rating('select', rating);

}

// Listener on the star rating cancel element

$('#question' + qID + ' div.rating-cancel').click(function(event) {

// Nullify the rating if the Cancel element is clicked

rating = '';

$('#question' + qID + ' input.radio').attr('checked', false);

});

// Listener on the star rating elements

$('#question' + qID + ' div.star-rating').click(function(event) {

// Find the value of the highest clicked star and pass it into the text input

$('#question' + qID + ' div.star-rating-on').each(function(i) {

rating = $(this).children('a').html( );

});

$('#question' + qID + ' input.radio[value=' + rating + ']').attr('checked', true);

});

}

// Call the function for the radio question

handleRatingRadio (SSSSS, GG, QQ);

});

</script></syntaxhighlight>

=Variable column widths in array=

''Tested with: 1.85+ (7557), IE 6/7, Firefox 3.0, Safari 3.2''

This workaround allows you to define all column widths of an array question - as shown in the image below and [http://www.partnersinc.biz/surveys//index.php?sid=26842&newtest=Y&lang=en demonstrated here]. This example uses the default template shipped with 7557 but should be adaptable to any template.

[[File:array_widths_701x226.gif]]

We use a function to remove all of the widths imposed by the core code and then insert our own.

'''Implementation is as follows:'''
#Turn off ''$filterxsshtml'' to allow insertion of JavaScript in the questions (see [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings&structure;=English+Instructions+for+LimeSurvey#Filtering_dangerous_HTML_tags_in_survey_objects documentation here]).
#Create the array question.
#In the source of the array question add the following script (see [[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|How to use script here]]).
#Replace all instances of QQ with the question ID.
#In the third section of code, adjust the widths and add/remove columns as necessary. This example is for an array with a question text column followed by 3 answer columns as shown above.
#In the final section adjust the question text alignment to your liking

Onload code

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" charset="utf-8">

$(document).ready(function() {

// Get rid of all the widths that the API imposes

$( 'div#questionQQ table.question col' ).attr('width', '');

$( 'div#questionQQ table.question thead td' ).attr('width', '');

// Define a width for the question table so we can do so for its children

// NOTE: Keep this to 95% or less so IE will behave

$( 'div#questionQQ table.question' ).attr('width', '95%');

// Define the column widths

// Add or remove columns and adjust widths as necessary but widths should add up to 100%

// NOTE: Columns must be sequentially numbered starting at 0 - eg, td:eq(0), td:eq(1), td:eq(2).....

$( 'div#questionQQ table.question tbody th:eq(0)' ).css({ 'width':'10%' }); // Answer text column

$( 'div#questionQQ table.question tbody td:eq(0)' ).css({ 'width':'50%' }); // First answer column

$( 'div#questionQQ table.question tbody td:eq(1)' ).css({ 'width':'20%' }); // Second answer column

$( 'div#questionQQ table.question tbody td:eq(2)' ).css({ 'width':'20%' }); // Third answer column

// Push the text input widths to 95% of their parent containers

$( 'div#questionQQ table.question input[type="text"]' ).css({ 'width':'95%' });

// Align the answer text - feel free to experiment

$( 'div#questionQQ table.question tbody th' ).css({'text-align':'center'});

});

</script></syntaxhighlight>

=Use images for radio buttons and checkboxes=

''Tested with: LimeSurvey 1.92/2.0, using IE 9, FireFox 13, Chrome 16, Safari 5''

This workaround uses an adaptation of the jQuery imagetick.js plugin to replace the default radio buttons and checkboxes with images as pictured below:

[[File:images.png]]

This adaptation will work in the following question types:
*Array
*Array by column
*Array dual scale
*Array (5 point choice)
*Array (10 point choice)
*Array (Increase-Same-Decrease)
*Array (Yes-No-Uncertain)
*Gender
*Yes-No
*Multiple choice
*Multiple choice with comments
*5 point choice
*List (Radio)
*List with comment

==LimeSurvey 1.92 and earlier implementation==
#[[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|Set up your survey to use JavaScript]].
#Download [[Media:imagetick_lime_v1.3.zip|this modified version of the plugin]].
#Extract all files and place them in your template directory.
#Add the following line to the <head> element in your startpage.pstpl '''BEFORE''' the call for template.js:<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" src="{TEMPLATEURL}imagetick_lime.js"></script></syntaxhighlight>
#Add the following to the source of a question or the group description<syntaxhighlight lang="javascript" enclose="div"><script type="text/javascript" charset="utf-8">

$(document).ready(function(){

var templatePath = $('head link[href*="template.css"]').attr('href').replace(/template.css/, '');

// Apply images to radios
$('input[type="radio"]').imageTick({

// Image to use as a selected state of the radio
tick_image_path: templatePath+"radio.gif",
// Image to use as a non-selected state
no_tick_image_path: templatePath+"no_radio.gif",
// Class to apply to all radio images that are dynamically created
image_tick_class: "radios"
});

// Apply images to checkboxes
$('input[type="checkbox"]').imageTick({

// Image to use as a selected state of the checkbox
tick_image_path: templatePath+"check.gif",
// Image to use as a non-selected state
no_tick_image_path: templatePath+"no_check.gif",
// Class to apply to all checkbox images that are dynamically created
image_tick_class: "checkboxes"
});
});

</script></syntaxhighlight>
#You can also call the imagetick function from template.js. Skip the last step above and add the following to the end of template.js. Replace "yourTemplateName" with your template directory name.<syntaxhighlight lang="javascript" enclose="div">$(document).ready(function(){

var templatePath = $('head link[href*="template.css"]').attr('href').replace(/template.css/, '');

// Apply images to radios
$('input[type="radio"]').imageTick({

// Image to use as a selected state of the radio
tick_image_path: templatePath+"radio.gif",
// Image to use as a non-selected state
no_tick_image_path: templatePath+"no_radio.gif",
// Class to apply to all radio images that are dynamically created
image_tick_class: "radios"
});

// Apply images to checkboxes
$('input[type="checkbox"]').imageTick({

// Image to use as a selected state of the checkbox
tick_image_path: templatePath+"check.gif",
// Image to use as a non-selected state
no_tick_image_path: templatePath+"no_check.gif",
// Class to apply to all checkbox images that are dynamically created
image_tick_class: "checkboxes"
});
});</syntaxhighlight>
<br />
If you want to apply it to only one question on a page use selector (where QQ is the question ID)<syntaxhighlight lang="php" enclose="div">$('#questionQQ input[type="radio"]')</syntaxhighlight>
<br />
If you want to apply it to a single radio button in a question (to maybe have different images for each option) use selector (where SSSSS is the survey ID, GG is the group ID, QQ is the question ID, AA is the answer code)<syntaxhighlight lang="php" enclose="div">$("input#answerSSSSSXGGXQQAA")</syntaxhighlight>
<br />

==LimeSurvey 2.0 and later implementation==

Follow the instructions above with these changes:
#Download [[Media:Imagetick_lime_v2.1.zip|this modified version of the plugin for 2.0 and up]] instead of the one mentioned above and add all contained files to your template directory.
#Add these lines to the <head> element in your startpage.pstpl instead of the one above:<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" src="{TEMPLATEURL}imagetick_lime_2.js"></script>

<link rel="stylesheet" type="text/css" href="{TEMPLATEURL}imagetick_lime_2.css" /></syntaxhighlight>

Thanks to Jordan Boesch for the original plugin.

=Changing the position and layout of an individual question using "question code"=

''Tested with: 1.87+ (6536)''

To use this very flexible workaround you first have to apply a minor change to the question.pstpl of the used template.

<syntaxhighlight lang="php" enclose="div">

<div class="survey-question">

<div class="survey-question-text">

</syntaxhighlight>

needs to be changed to

<syntaxhighlight lang="php" enclose="div">

<div class="survey-question" id="{QUESTION_CODE}">

<div class="survey-question-text" id="{QUESTION_CODE}" >

</syntaxhighlight>

this change won't change anything in the layout and can be left in the template even if you don't need this workaround. It's just a means to have a handle to actually change individual questions.

You can then use a code such as the following in the question text to make question specific format changes. "SAMPLE" needs to be replaced with the concerning question code and javascript has to be allowed ([[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|older versions of limesurvey]], under global settings for newer versions).

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" charset="utf-8">

document.getElementById('SAMPLE').style.borderTop= "0px";

document.getElementById('SAMPLE').style.marginTop= "-62px";

document.getElementById('SAMPLE').style.marginLeft= "30px";

</script>

</syntaxhighlight>

This sample code will hide the border at the top of the question, will move the whole question up by 62px and to the right by 30px. Using this workaround you can change a whole a lot of things concerning format and positions of a specific question without changing all the questions. A (German) list of all the allowed options can be found [http://de.selfhtml.org/javascript/objekte/style.htm#style_eigenschaften here].

=Create MaxDiff question type=

''Tested with: 1.87+ (8518), IE 6/7/8, Firefox 3.6, Safari 3.2''

This workaround uses JavaScript to convert an '''''Array (flexible labels) by column''''' question into a [http://en.wikipedia.org/wiki/MaxDiff MaxDiff] question type.

[[File:max_diff_596x253.gif]]

There is a demo [http://www.partnersinc.biz/surveys//index.php?sid=29191&newtest=Y&lang=en here] and implementation is as follows.
#[[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|Set up your survey to use JavaScript]].
#Create an '''''Array (flexible labels) by column''''' question with 2 "answers" - these will be the left and right columns.
#Assign a label set to the question - these will be the labels in the center column.
#Place the following script in the source of the question or in the group description.
#In line 5, replace "QQ" with the ID of the question and modify the message to your needs.
#Adjust the styles in lines 15-18 as required.

The script moves the question columns into the MaxDiff configuration and alerts the user if they select the same option for both max and min columns.

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" charset="utf-8">

$(document).ready(function(){

maxDiff(QQ, 'You cannot select this answer twice.');

function maxDiff(qID, msg) {

// Move the cells around

$('#question'+qID+' table.question col:eq(1)').prependTo('colgroup.col-responses');

$('#question'+qID+' table.question thead tr:eq(0) th:eq(0)').prependTo('#question'+qID+' table.question thead tr:eq(0)');

$('#question'+qID+' table.question tbody tr').each(function(i){

$('td:eq(0)', this).prependTo(this);

});

// Style stuff

$('#question'+qID+' table.question col.odd').css({ 'background-color':'transparent' });

$('#question'+qID+' table.question tbody th').css({ 'text-align':'center' });

$('#question'+qID+' table.question tbody tr:even td, #question'+qID+' table.question tbody tr:even th').css({ 'background-color':'#F1F1F1' });

$('#question'+qID+' table.question tbody tr:odd td, #question'+qID+' table.question tbody tr:odd th').css({ 'background-color':'#FCFCFC' });

// Prevent clicking twice in the same row

$('#question'+qID+' input.radio').mousedown(function () {

var clickRow = $(this).parents('tr:eq(0)');

if ($('input.radio:checked', clickRow).length > 0) {

alert (msg);

return false;

}

});

$('#question'+qID+' table.question tbody td').mousedown(function () {

var clickRow = $(this).parents('tr:eq(0)');

if ($('input.radio:checked', clickRow).length > 0) {

alert (msg);

return false;

}

});

}

});

</script>

</syntaxhighlight>

=Load SVG Code From Drawing Tool=

This workaround uses JavaScript/jQuery to load a drawing tool and store the results in a huge-text question. The details are outlined in the [[Workarounds: Manipulating a survey at runtime using Javascript#Load SVG Code From Drawing Tool|JavaScript section of the workarounds]].

=Minimum or Maximum Date in Datepicker=

''Tested with: 1.90, IE 7/8, Firefox 3.6, Safari 3.2''

'''Please note: From version 2.05 beta6, you can set the minimum and maximum date for the date picker directly in the advanced question attributes of the date/time question.'''

You can set the minimum or maximum selectible date in a datepicker as follows

[[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|Set up your survey to use JavaScript]] and add the following to the source of the date question text or help. Replace "QQ" with the date question ID.

For a minimum date of April 15, 2010:<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" charset="utf-8">

$(document).ready(function() {

var qID = QQ;

$('#question'+qID+' .popupdate').datepicker( 'option', 'minDate', new Date(2010, 4-1, 15) );

});

</script>

</syntaxhighlight>

For a minimum date of the current date (today):<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" charset="utf-8">

$(document).ready(function() {

var qID = QQ;

$('#question'+qID+' .popupdate').datepicker( 'option', 'minDate', new Date() );

});

</script>

</syntaxhighlight>

For a maximum date of May 10, 2015:<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" charset="utf-8">

$(document).ready(function() {

var qID = QQ;

$('#question'+qID+' .popupdate').datepicker( 'option', 'maxDate', new Date(2015, 5-1, 10) );

});

</script>

</syntaxhighlight>

More details here - http://jqueryui.com/demos/datepicker/#option-minDate

=Evaluative Space Grid (ESG)=

''Tested with: 1.91, IE 7/8, Firefox 3.6, Safari 3.2''

The evaluative space grid (ESG) is a two-dimensional grid that provides a single-item measure of positivity and negativity (Larsen et al, 2009). See [http://leeds-faculty.colorado.edu/mcgrawp/pdf/larsen.norris.mcgraw.hawkley.cacioppo.2009.pdf page 4 of this PDF].

This can be accomplished using a multiple-numeric question, some simple HTML and a little JavaScript.

A table can be shown in the question. When a respondent clicks a grid cell in the table JavaScript loads the coordinates of the cell into the multiple-numeric question inputs.

[[File:space_grid.png]]<br /><br />
#Create a Multiple Numeric question with two sub-questions labelled "X" and "Y".
#Add the following HTML to the source of the question to create the table:<syntaxhighlight lang="html4strict" enclose="div">
<table class="spaceGrid">
<tr>
<td rowspan="5" class="yAxisLabel">How NEGATIVE<br>
do you feel about<br>
the stimulus?</td>
<td class="yLabel">Extremely</td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
</tr>
<tr>
<td class="yLabel">Quite a bit</td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
</tr>
<tr>
<td class="yLabel">Moderately</td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
</tr>
<tr>
<td class="yLabel">Slightly</td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
</tr>
<tr>
<td class="yLabel">Not at all</td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
</tr>
<tr>
<td class="blankCell"></td>
<td class="blankCell"></td>
<td class="xLabel">Not at all</td>
<td class="xLabel"><span class="yLabel">Slightly</span></td>
<td class="xLabel"><span class="yLabel">Moderately</span></td>
<td class="xLabel"><span class="yLabel">Quite a bit</span></td>
<td class="xLabel"><span class="yLabel">Extremely</span></td>
</tr>
<tr>
<td class="blankCell"></td>
<td class="blankCell"></td>
<td colspan="5" class="xAxisLabel">How POSITIVE do you feel about the stimulus?</td>
</tr>
</table>
</syntaxhighlight><br /><br />
#Add the following styles to the end of your template.css file:<syntaxhighlight lang="css" enclose="div">
.spaceGrid {
border: 0 none;
border-collapse: collapse;
}

.spaceGrid td {
padding: 0 3px;
text-align: center !important;
border: 0 none;
}

td.xAxisLabel {
padding-top: 10px;
}

td.yAxisLabel {
padding-right: 10px;
width: 125px;
}

td.xLabel {
height: 20px;
font-weight: normal;
}

td.yLabel {
text-align: right !important;
font-weight: normal;
}

td.gridCell {
width: 70px;
height: 70px;
border: 1px solid #666666;
background-color: #FFFFFF;
cursor: pointer;
}

td.checkedCell {
background-color: #66FF00;
}
</syntaxhighlight><br /><br />
#Add the following to the end of your template.js file:<syntaxhighlight lang="javascript" enclose="div">
$(document).ready(function() {

// Listener on the grid cells
$('.gridCell').click(function(){

// Define some vars
var parentQ = $(this).parents('div[id</div>="question"]:eq(0)');
var parentTable = $(this).parents('table.spaceGrid:eq(0)');
var parentRow = $(this).parent();
var numGridCell = $('.gridCell').length;
var numCols = $('.gridCell', parentRow).length;
var numRows = numGridCell/numCols;

// Add class to checked cell
$('.checkedCell', parentQ).removeClass('checkedCell');
$(this).addClass('checkedCell');

// Find the cell coordinates
var reverseRowIndex = (numRows - $('tr', parentTable).index($(parentRow)));
var colIndex = $('.gridCell', parentRow).index($(this)) + 1;

// Load coordinates into inputs
$('input.text:eq(0)', parentQ).val(colIndex);
$('input.text:eq(1)', parentQ).val(reverseRowIndex);
});

});
</syntaxhighlight><br /><br />
The script should automatically handle different grid sizes.

=Slider Highlighting=

''Tested with: 1.91, IE 7/8, Firefox 3.6, Safari 3.2''

You may want to highlight a slider after it has been moved/changed to allow respondents to easily see which slider sub-questions have been answered.

[[File:Capture.PNG]]<br /><br />
#Add the following to the end of '''template.js''':<syntaxhighlight lang="javascript" enclose="div">
$('html').bind('slidecreate', function(event, ui) {
$('.slider_callout').each(function(i){
if($(this).text().length > 0) {
$(this).parents('li:eq(0)').addClass('changedSlider');
}
});
});

$(document).ready(function() {
$('.ui-slider-horizontal').bind('slidechange', function(event, ui) {
$(this).parents('li:eq(0)').addClass('changedSlider');
});
});
</syntaxhighlight><br /><br />
#Add something like the following to the end of '''template.css''' (these styles are for the default template and would need to be modified for other templates):<syntaxhighlight lang="css" enclose="div">
.numeric-multi .answer li {
border-bottom: 5px solid #FFFFFF;
}

.numeric-multi .answer li label {
background-color: #FFFFFF;
}

.numeric-multi .answer li div.multinum-slider {
margin: 1.5em 0.5em 0.2em 0;
padding-left: 0.5em;
}

.ui-slider-1 {
margin-bottom: 10px;
}

.changedSlider {
background-color: #99FFFF;
}
</syntaxhighlight>
<br /><br />

=Sliders in Array-Numbers or Array-Dual-Scale-Numbers=

''Tested with: 1.91, IE 7/8/9, Firefox 3/7, Safari 5, Chrome 15''

This workaround will replace the dropdowns in '''''array-numbers''''' or '''''array-dual-scale-numbers''''' questions with sliders. The sliders will automatically have the same minimum, maximum and steps that you set in the advanced question settings.

[[File:custom_sliders_1.png]]<br /><br />
There is a [http://www.partnersinc.biz/surveys//index.php?sid=66653&newtest=Y&lang=en '''demo here'''].<br /><br />
#[[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|Set up your survey to use JavaScript]].
#Create your array-numbers or array-dual-scale-numbers question.
#Add the following to the source of the question. Replace "QQ" with the array question ID. (NOTE: In 1.92 or newer, you can replace "QQ" with "{QID}")<syntaxhighlight lang="javascript" enclose="div">
<script type="text/javascript" charset="utf-8">

$(document).ready(function() {

insertSlider (QQ);

function insertSlider (qID) {

$('#question'+qID+' select').each(function(i, el){

// Hide the dropdown
$(el).hide();

var id = $(el).attr('id').replace(/#/g,'-');

// Some dropdown values
var currentVal = Number($('option:selected', el).val());
var firstVal = Number($('option[value!=""]:first', el).val());
var secondVal = Number($('option[value!=""]:first', el).next('option').val());
var lastVal = Number($('option[value!=""]:last', el).val());

// Insert a container for the slider
var container = $('<div class="customSliderWrapper"></div>').insertAfter(el);

// Insert a callout
var callout = $('<div id="callOut-'+id+'" class="customCallout"></div>').appendTo(container).text($('option:selected', el).val());

// Initiate the slider
var slider = $('<div id="slider-'+id+'" class="customSlider"></div>').appendTo(container).slider({
min: firstVal,
max: lastVal,
range: 'min',
value: currentVal,
step: secondVal - firstVal,
slide: function( event, ui ) {
$('option[value="'+ui.value+'"]', el).attr('selected', 'selected');
function updateCustomCallout() {
$('#callOut-'+id).text($('option:selected', el).val()).css({ 'left': $('#slider-'+id+' .ui-slider-handle').css('left') });
}
// Delay updating the callout because it was picking up the last postion of the slider
setTimeout(updateCustomCallout, 10);
}
});

// Change the slider if the dropdown is changed
// (not required if dropdown is hidden)
$(el).change(function() {
slider.slider('value', Number($('option:selected', el).val()));
$('#callOut-'+id).text($('option:selected', el).val());
});

// Set a value as soon as the slider handle is clicked
$('#slider-'+id+' .ui-slider-handle').mousedown(function() {
$('option[value="'+slider.slider('value')+'"]', el).attr('selected', 'selected');
$('#callOut-'+id).text(slider.slider('value'));
});
});
}
});
</script></syntaxhighlight><br /><br />
#Add something like the following to the end of '''template.css''' (these styles are for the default template and may need to be modified for other templates):<syntaxhighlight lang="css" enclose="div">
table.innerframe {
width:850px;
}

.array-multi-flexi table.question {
width:90%;
}

.customCallout {
position: absolute;
top: 0;
left: 0;
width: 50px;
height: 1.75em;
text-align: left;
font-weight: bold;
margin: 0 0 0 -0.3em;
}

.customSliderWrapper {
position: relative;
margin: 0 10px;
padding-top: 1.75em;
}
</syntaxhighlight>
<br /><br />

=Vertical Sliders=

''Tested with: 1.92+, 2.00+, IE 9, Firefox 13, Chrome 19''

This workaround uses a custom jQuery plugin to apply vertical sliders to multiple-numeric questions. You can download a sample template here (with the plugin in template.js) - [[Media:default_vertical_sliders.zip|vertical slider template]] - and a sample survey here - [[Media:demo_vertical_sliders.lss|vertical slider survey]].

[[File:verticalsliders_1.jpg]]<br /><br />
# Create your multi-numeric question(s). Do NOT use any of the slider advanced settings.<br /><br />
#Add the following to the end of template.js. Replace "QQ" (line 5) with the question ID and adjust the options in the function call as desired. Repeat the call as many times as you need for more questions<syntaxhighlight lang="javascript" enclose="div">$(document).ready(function(){

// Call the vertical slider plugin with the question ID
// Edit options here as desired
$('#questionQQ').lsVerticalSlider({
minValue :0, // Minimum value (default 0)
maxValue :200, // Maximum value (default 100)
startValue :100, // Start value (default null)
step :10, // Slider increments (default 1)
height :100, // Height of slider in pixels (default 200)
recordStart :true, // Record the start value? (default no)
showMin :true, // Show minimum value? (default no)
showMax :true // Show maximum value? (default no)
});
});

// NO EDITING REQUIRED BELOW HERE
// A jQuery plugin to convert multiple-numeric questions to vertical sliders
(function( $ ){
$.fn.lsVerticalSlider = function(options) {

// The defaults, extended and modified with any passed in the function call
var opts = $.extend( {
minValue :0,
maxValue :100,
startValue :'',
step :1,
height :150,
recordStart :false,
showMin :false,
showMax :false
}, options);

return this.each(function() {

var $this = $(this);

// Some classes for the question and sub-questions
$this.addClass('vertical-slider-question');
$('li:[id<div class="simplebox">="javatbd"]', $this).addClass('vertical-slider-sub-question');

// Loop through the sub-questions
$('li:[id</div>="javatbd"]', $this).each(function(i){
var itemID = $(this).attr('id').replace(/javatbd/, '');

// Check for pre-existing answer
if($('#answer'+itemID).val() != '') {
opts.startValue = $('#answer'+itemID).val();
}

// Insert the slider elements
$('#answer'+itemID).after(
'<div class="vertical-slider-max-min" style="height:'+(opts.height+2)+'px;"> \
<div class="vertical-slider-max"></div> \
<div class="vertical-slider-min"></div> \
</div> \
<div id="vertical-slider-'+itemID+'" class="vertical-slider" style="height:'+opts.height+'px;"></div> \
<div class="vertical-slider-callout-wrapper" style="height:'+(opts.height+2)+'px;"> \
<div class="vertical-slider-callout" id="slider-callout-'+itemID+'"></div> \
</div>'
);

// Show min/max if option is set
if(opts.showMax) {
$('.vertical-slider-max', $this).text(opts.maxValue);
}

if(opts.showMin) {
$('.vertical-slider-min', $this).text(opts.minValue);
}

// Initiate the slider
$('#vertical-slider-'+itemID).slider({
orientation: 'vertical',
range: 'min',
min: opts.minValue,
max: opts.maxValue,
value: opts.startValue,
step: opts.step,
slide: function(event, ui) {
$('#answer'+itemID).val(ui.value);
$('#slider-callout-'+itemID).text(ui.value);
setTimeout(function() {
$('#slider-callout-'+itemID).css({ 'bottom':$('#vertical-slider-'+itemID+' .ui-slider-handle').css('bottom') }).show();
}, 10);
},
create: function(event, ui) {
// Initial values and positions
if($('#answer'+itemID).val() != '') { // Pre-existing answer
$('#slider-callout-'+itemID).text(opts.startValue);
}
else if(opts.recordStart) { // Record the start value (if option is set)
$('#answer'+itemID).val(opts.startValue);
$('#slider-callout-'+itemID).text(opts.startValue);
}
else {
$('#slider-callout-'+itemID).hide();
}
$('#slider-callout-'+itemID).css({ 'bottom':$('#vertical-slider-'+itemID+' .ui-slider-handle').css('bottom') });
}
});
});
});
};
})( jQuery );</syntaxhighlight><br /><br />
#Add the following to the end of template.css (these styles are for the default template):<syntaxhighlight lang="css" enclose="div">/* Vertical slider styles and overrides */
.vertical-slider-question p.tip {
display: none;
}

.vertical-slider-sub-question {
float: left;
margin: 0 3em 0 0 !important;
}

.vertical-slider-question label {
display: block;
padding: 0 0 0.75em 0 !important;
}

.vertical-slider-question span.input {
padding: 0.3em 0 0 0;
display: block;
}

.vertical-slider-question input.text {
display: none;
}

.vertical-slider {
float: left;
border-radius: 4px;
}

.vertical-slider-question .ui-slider-handle {
top: auto;
border-radius: 4px;
}

.vertical-slider-max-min,
.vertical-slider-callout-wrapper {
float: left;
position: relative;
}

.vertical-slider-callout-wrapper {
min-width: 3em;
}

.vertical-slider-max-min {
margin-right: 0.5em;
}

.vertical-slider-max,
.vertical-slider-min {
font-size: 0.8em;
color:#666666;
line-height: 1;
}

.vertical-slider-max {
margin-top: -0.5em;
}

.vertical-slider-min {
position: absolute;
right: 0;
bottom: 0;
margin-bottom: -0.5em;
}

.vertical-slider-callout {
position: absolute;
top: auto;
margin: 0 0 -0.6em 0.5em;
padding: 0.1em;
font-size: 0.9em;
color:#000000;
line-height: 1;
background: #F8F8FF;
border: 1px solid #D2E0F2;
border-radius: 4px;
}</syntaxhighlight>
<br /><br />

=Range Slider=

''Tested with: 1.92+, 2.00+, IE 9, Firefox 13, Chrome 19''

This workaround uses a custom jQuery plugin to insert a jQuery UI range slider into a multi-numeric question and automatically populate that question's inputs with the range min and max values. You can download a sample template here - [[Media:Demo_Range_Slider.zip|range slider template]] - and a sample survey here - [[Media:Limesurvey_survey_range_slider.lss|range slider survey]].

[[File:Range_slider.jpg]]<br /><br />
The plugin handles:
*previous answers
*slider max/min
*range min start
*range max start
*range span min
*slider step
*slider width
*record the start values
*show slider max and min<br /><br />
Requirements:
*LimeSurvey 1.92 or newer
*A multiple-numeric question with two sub-questions<br /><br />
# Create your multi-numeric question. Do NOT use any of the slider advanced settings.<br /><br />
#Add the following to the end of template.js.<syntaxhighlight lang="javascript" enclose="div">// A jQuery plugin to display a range slider in LimeSurvey
(function( $ ){

$.fn.lsRangeSlider = function(options) {

// The defaults, extended and modified with any passed in the function call
var opts = $.extend( {
range :true,
sliderMin :0,
sliderMax :100,
rangeStartMin :'',
rangeStartMax :'',
minRangeSpan :0,
step :1,
width :250,
recordStart :false,
showMin :false,
showMax :false
}, options);

return this.each(function() {

if($(this).hasClass('numeric-multi') && $('input.text', this).length == 2) {

// Define some vars
var $this = $(this);
var qID = $(this).attr('id').split('question')[1];
var rangeMinInput = $('input.text:eq(0)', $this);
var rangeMaxInput = $('input.text:eq(1)', $this);

// Some classes for the question and sub-questions
$this.addClass('range-slider-question');

// Check for pre-existing answer
if($(rangeMinInput).val() != '' && $(rangeMinInput).val() != '') {
opts.rangeStartMin = $(rangeMinInput).val();
opts.rangeStartMax = $(rangeMaxInput).val();
}

// Insert the slider elements
$('.subquestions-list', $this).before(
'<div class="range-slider-wrapper"> \
<div class="range-slider-min"></div> \
<div id="range-slider-'+qID+'" class="range-slider" style="width:'+opts.width+'px;"> \
<div class="range-slider-callout" id="slider-callout-min-'+qID+'"></div> \
<div class="range-slider-callout" id="slider-callout-max-'+qID+'"></div> \
</div> \
<div class="range-slider-max"></div> \
<div style="clear:both;"></div> \
</div>'
);

// Show min/max if option is set
if(opts.showMax) {
$('.range-slider-max', $this).text(opts.sliderMax);
}
if(opts.showMin) {
$('.range-slider-min', $this).text(opts.sliderMin);
}

// Initiate the slider
var rangeMin;
var rangeMax;
if(opts.rangeStartMin == '' || opts.rangeStartMin < opts.sliderMin || opts.rangeStartMin > opts.rangeStartMax) {
rangeMin = opts.sliderMin+((opts.sliderMax-opts.sliderMin)*0.3333);
}
else {
rangeMin = opts.rangeStartMin;
}
if(opts.rangeStartMax == '' || opts.rangeStartMax > opts.sliderMax || opts.rangeStartMax < opts.rangeStartMin) {
rangeMax = opts.sliderMin+((opts.sliderMax-opts.sliderMin)*0.6667);
}
else {
rangeMax = opts.rangeStartMax;
}
$('#range-slider-'+qID).slider({
range: true,
min: opts.sliderMin,
max: opts.sliderMax,
values: [ rangeMin, rangeMax ],
step: opts.step,
slide: function(event, ui) {
if((ui.values[1] - ui.values[0]) < opts.minRangeSpan) {
return false; // Nothing happens if less than minRangeSpan
}
$(rangeMinInput).val(ui.values[0]);
$(rangeMaxInput).val(ui.values[1]);
$('#slider-callout-min-'+qID).text(ui.values[0]);
$('#slider-callout-max-'+qID).text(ui.values[1]);
setTimeout(function() {
$('#slider-callout-min-'+qID).css({ 'left':$('.ui-slider-handle:eq(0)', $this).position().left - $('#slider-callout-min-'+qID).outerWidth() - ($('.ui-slider-handle:eq(1)', $this).outerWidth()/2)+'px' }).show();
$('#slider-callout-max-'+qID).css({ 'left':($('.ui-slider-handle:eq(1)', $this).position().left)+($('.ui-slider-handle:eq(1)', $this).outerWidth()/2)+'px' }).show();
}, 10);
},
create: function(event, ui) {
// Initial values and positions
if($(rangeMinInput).val() != '' && $(rangeMaxInput).val() != '') { // Pre-existing answer
$('#slider-callout-min-'+qID).text(opts.rangeStartMin);
$('#slider-callout-max-'+qID).text(opts.rangeStartMax);
}
else if(opts.recordStart && opts.rangeStartMin && opts.rangeStartMin && $(rangeMinInput).val() == '' && $(rangeMaxInput).val() == '') { // Record the start value (if option is set)
$(rangeMinInput).val(opts.rangeStartMin);
$(rangeMaxInput).val(opts.rangeStartMax);
$('#slider-callout-min-'+qID).text(opts.rangeStartMin);
$('#slider-callout-max-'+qID).text(opts.rangeStartMax);
}
else {
$('.range-slider-callout', $this).hide();
}
$('#slider-callout-min-'+qID).css({ 'left':$('.ui-slider-handle:eq(0)', $this).position().left - $('#slider-callout-min-'+qID).outerWidth() - ($('.ui-slider-handle:eq(1)', $this).outerWidth()/2)+'px' });
$('#slider-callout-max-'+qID).css({ 'left':($('.ui-slider-handle:eq(1)', $this).position().left)+($('.ui-slider-handle:eq(1)', $this).outerWidth()/2)+'px' });
}
});
}
});

};
})( jQuery );
</syntaxhighlight><br /><br />
#Add the following to the end of template.css (these styles are for the default template but easily modified for others):<syntaxhighlight lang="css" enclose="div">
.range-slider-question p.tip,
.range-slider-question .subquestions-list {
display: none;
}

.range-slider-wrapper {
clear: both;
margin: 10px 0;
padding-top: 20px;
}

.range-slider,
.range-slider-max,
.range-slider-min {
float: left;
position: relative;
}

.range-slider-max,
.range-slider-min {
font-size: 0.8em;
color:#666666;
line-height: 1.20;
}

.range-slider-min {
margin-right: 5px;
}

.range-slider-max {
margin-left: 5px;
}

.range-slider-question .ui-slider-handle {
top: -4px;
border-radius: 4px;
}

.range-slider-callout {
position: absolute;
top: -30px;
margin: 0;
min-width: 1.3em;
padding: 0.1em;
font-size: 0.9em;
color:#000000;
line-height: 1;
text-align: center;
background: #F8F8FF;
border: 1px solid #D2E0F2;
border-radius: 4px;
}
</syntaxhighlight><br /><br />
#Then, add something like this to the source of your question to apply the plugin with some custom option settings (I think the comments explain the options adequately)<syntaxhighlight lang="javascript" enclose="div">
<script type="text/javascript" charset="utf-8">
$(document).ready(function(){

$('#question{QID}').lsRangeSlider({
sliderMin :0, // Minimum slider value (default 0)
sliderMax :100, // Maximum slider value (default 100)
rangeStartMin :20, // Minimum range handle start value
rangeStartMax :80, // Maximum range handle start value
minRangeSpan :5, // Minimum allowed range span
step :1, // Slider increments (default 1)
width :400, // Width of slider in pixels (default 250)
recordStart :true, // Record the start value? (default no)
showMin :true, // Show slider minimum value? (default no)
showMax :true // Show slider maximum value? (default no)
});

});
</script>
</syntaxhighlight><br /><br />
#Or, to apply the plugin with the default option settings<syntaxhighlight lang="javascript" enclose="div">
<script type="text/javascript" charset="utf-8">
$(document).ready(function(){

$('#question{QID}').lsRangeSlider();

});
</script>
</syntaxhighlight>
<br /><br />

=Split your sample into legs (cells) that see slightly different wording and media=

Sometimes you may need to test candidate A vs candidate B or brand 1 vs brand 2 … vs brand n. Typically in such cases the phrasing of the questionnaire is identical except for the brand (candidate) and some logo/media. Rather than create several questionnaires it is best to control survey logic by assigning respondents to different groups and showing them different versions of the questionnaire.

The logical engine in the current version (1.91) does not support this but you can still do it using the attribute fields in the token table. The instructions below are not really a workaround, but more of a translation of conditional logic to database questionnaire logic.

This works for closed surveys. If your survey is not closed you may want to consider ways to create automatically tokens for each respondent like: "Create token on the fly and Edit completed survey": http://bugs.limesurvey.org/view.php?id=2982

'''Case A: you need different text for each version'''

Step 1: you create a tokens table adding attribute fields for each variation you need: [[Tokens#User-defined attribute fields|User defined attribute fields]]. For example you may store in attribute_1 the name of the candidate, in attribute_2 the name of the party etc.

Step 2 You export the structure of your tokens database and populate it with the relevant values for the attribute fields. Then import it back

Example:

http://img502.imageshack.us/img502/7425/58d0ff2c68d74366a81e6f7.png

Please use the instructions here: [[Tokens#Importing/exporting tokens|importing and exporting tokens]], and pay attention because this can be error-prone.

Step 3

When creating a question use the insert replacement field icon http://img502.imageshack.us/img502/540/81a6c17d49f04f88bd52e72.png to insert your proper keyword.

This is it. The overall process is quite simple once you get the hang of using tokens, but the database can be space-consuming if you are running on limited resources.

'''Case B: you need to run different media, from public hosting websites.'''

The process is just like in case A, just that you will populate the attribute field with unique identifiers for the media.

See below an example on how to embed a youtube video

<syntaxhighlight lang="php" enclose="div"><iframe allowfullscreen="" frameborder="0" height="349" src="http://www.youtube.com/embed/'''{TOKEN:ATTRIBUTE_5}'''?rel=0&modestbranding=1&loop=0&controls=0&autoplay=1&rel=0&showinfo=0&showsearch=0&iv_load_policy=o" width="560"></iframe></syntaxhighlight>

If you embed images you will want to make sure that the hotlinks for your pictures only differ by the image ID. IF not, you may use a larger portion, or maybe even the entire URL as your unique identifier. As said before, please consider how much space you are allowed for your databases.

'''Case C: you want to run media from your server, which is organized in relevant folders'''

For this scenario I will assume your media is organized as follows

Project folder ...leg folder (for each leg) ... media (1 to n). You can use a FTP client to upload this structure to you LS installation.

In this case you only need to store the <leg folder> into the tokens table and then use this info to build your embed tag. This may free a significant amount of space,

For example if you have the data as below...

http://img534.imageshack.us/img534/8967/a62e6ff48476492c8795f79.png

… then your embed for the party logo will look somewhere along these lines:

<syntaxhighlight lang="php" enclose="div"><img src="[path to project folder]/'''{TOKEN:ATTRIBUTE_3}'''/logo1.png" alt="'''{TOKEN:ATTRIBUTE_2}'''"></syntaxhighlight>

The alt tag is, of course, optional.
***

You can match and mix all 3 cases as it suites you best. You need to be a little careful when you work with tokens and embed tags, but it will save you from using intricate and error-prone survey logic or from duplicating surveys endlessly.

=Limit the language options dropdown on the list surveys page=

<div class="simplebox">Note: This feature is implemented in Version 2.0</div>

This solution allows you to define (in config.php) a comma-delimited list of languages you want in the dropdown. It is not optimized (it loads all the languages and then unsets everything you don't want), but is fairly easy to implement.

<syntaxhighlight lang="php" enclose="div">

$supportedLanguagesKeys = 'en,vi';

</syntaxhighlight>

Filter out everything except the your selected languages (if defined).

<syntaxhighlight lang="php" enclose="div">

// if $supportedLanguagesKeys is defined in config, filter

if (!empty($GLOBALS['supportedLanguagesKeys']))

foreach (array_keys($supportedLanguages) as $lang) {

if (!in_array($lang, explode(',', $GLOBALS['supportedLanguagesKeys']))) {

unset($supportedLanguages[$lang]);

}

}

</syntaxhighlight>

Now only my languages, plus the base language, is displayed. To get rid of the redundant base language, do the following

<syntaxhighlight lang="php" enclose="div">
#

} elseif (!isset($surveyid))

{

global $defaultlang, $baselang;

$htmlcode = "<select name=\"select\" class='languagechanger' onchange=\"javascript:window.location=this.value\">\n";
# REMOVE THE NEXT LINE OR COMMENT IT OUT)

$htmlcode .= "<option value=\"$relativeurl/index.php?lang=". $defaultlang ."$tokenparam\">".getLanguageNameFromCode($defaultlang,false)."</option>\n";

foreach(getlanguagedata() as $key=>$val)

{

$htmlcode .= "\t<option value=\"$relativeurl/index.php?lang=".$key."$tokenparam\" ";

if ($key == $baselang) $htmlcode .= " selected='selected'"; /* ADD THIS TO SET SELECTION */

$htmlcode .= ">".getLanguageNameFromCode($key,false)."</option>\n";

}

$htmlcode .= "</select>\n";

</syntaxhighlight>

Basically it just pre-selects the base language from the list.

QS:Date max

2013-10-19T21:58:51Z

Mfaber: update feature: no more curly braces in date min/max fields

<translate>

<languages />
<onlyinclude>

===Maximum date (date_max){{NewIn|2.05}} === 


'''Description'''


This question attribute can be used to set the maximum value for the calendar question. It applies to both, the popup-variant of the calendar and the dropdown fields. However, for the dropdown fields, only the year is used as a maximum.


'''Valid values'''


#'''Any date value in format YYYY-MM-DD''' (eg., 2013-08-24)
#'''Any year value'''
#'''Reference to another date/time question''' (eg., dateofbirth)
#'''Expressions''', work on a following page, not on the same: E.g, You can use a date from a previous answer + 365 days as a maximum for the present question by entering: date("Y-m-d",strtotime(departuredate)+365*60*60*24). The question with the code 'departuredate' has to be on a previous page in the survey (either in a different group in group by group mode or use question by question mode).


</onlyinclude>


[[Category:Question Settings]][[Category:Advanced Question Settings]]

</translate>

QS:Date min

2013-10-19T21:56:54Z

Mfaber: update feature: no more curly braces in date min/max fields

<translate>

<languages />
<onlyinclude>

===Minimum date (date_min){{NewIn|2.05}} === 


'''Description'''


This question attribute can be used to set the minimum value for the calendar question. It applies to both, the popup-variant of the calendar and the dropdown fields. However, for the dropdown fields, only the year is used as a minimum.


'''Valid values'''


#'''Any date value in format YYYY-MM-DD''' (eg., 2013-08-24)
#'''Any year value'''
#'''Reference to another date/time question'''(eg., dateofbirth)
#'''Expressions''', work on a following page, not on the same: E.g, You can use a date from a previous answer + 3 days as a minimum for the present question by entering: date("Y-m-d",strtotime(departuredate)+3*60*60*24). The question with the code 'departuredate' has to be on a previous page in the survey (either in a different group in group by group mode or use question by question mode).


</onlyinclude>


[[Category:Question Settings]][[Category:Advanced Question Settings]]

</translate>

Exporting results

2013-10-16T20:00:49Z

Mfaber: stata export: add LS version info

<languages /> <translate>

__TOC__


Once your survey is active you can start browsing responses and export them. To get to the survey response overview click...


[[File:browse_results.png]]

=Export to application (Excel/.csv)= 


On top of the browse responses page several export options are listed, beginning with ''export to CSV/application''.


[[File:export2.png]]


When exporting results to an application there are several filter options which are separated into:
*'''General'''
** Set a range like export records X to Y
** Set to export all records OR completed records only OR incomplete records only
*'''Questions'''
** Set how the heading should look like: Abbreviated heading OR full headings OR question codes
** Convert spaces in question text to underscores
*'''Answers'''
** You can either export full answers or convert answer codes Y and N to a defined variable
*'''Format'''
** Microsoft Word (latin charset)
** Microsoft Excel (all charsets)
** CSV File (all charsets)
** PDF
*'''Column Control'''
** Set which answers should be exported. All answers in this list are represented by their [[SGQA identifier|SGQA identifier]]
** Set which '''''token''''' data should be exported. This option is only available if your survey is '''''not anonymous'''''!


[[File:export_tokens.png]]

=SPSS Export= 

==General== 


To export your response data to SPSS go to Responses & Statistics section and click the icon to export to SPSS.


[[File:spss_toolbar.png]]

==Export and filter data== 


When exporting data to SPSS there are two filter options. You can select '''which data''' should be selected (''all records/completed records only/incompleted records only'') and for '''which SPSS version''' the export files will be used (''prior version 16/16 or up'').


SPSS export includes two files:
# a syntax file (''survey_xxxx_SPSS_syntax_file.sps'')
# and a data file (''survey_xxxx_SPSS_data_file.dat'').


After having downloaded these files you can open them using a raw text editor like notepad to take a look how the exported data looks like. The syntax file holds the commands that should be run to import the data. It is like a programming language inside SPSS. The data file contains a comma separated file with all data. If you just import this data as csv via a wizard you loose information about questions, labelsets etc. so we don't do that.

==Import data in SPSS== 


Place the two files in the same folder on your drive (example: ''c:\data\survey_xxxx_SPSS_syntax_file.sps'' and ''c:\data\survey_xxxx_SPSS_data_file.dat'')


We have two options now:


1. When using Windows use the explorer to browse to the folder used above. If SPSS is connected to the .sps file extension you can just open the file by double clicking it:


[[File:spss_explorer-screenshot.jpg]]


Now you can just choose Run->All from the opened window and after some time have your output dataset that you can save as a normal .sav file.


2. Sometimes the easy solution above does not work. Then you can proceed as follows:
* Open SPSS
* Choose File->Open->Syntax
* Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps
* Now the syntax opens.
* Change the line that reads ''/FILE='survey_xxxx_SPSS_data_file.dat' '' to include the path where the files are: ''/FILE='c:\data\survey_xxxx_SPSS_data_file.dat' ''
* Now mark the whole command text and choose Run->All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc.

=R Export= 


Feel free to add more information if you have some!


The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is closely linked to the SPSS export in LimeSurvey. Instructions on how to import your dataset in R:
#Download the syntax file and the data file.
#Store both files in R work listing (use ''getwd()'' and ''setwd()'' in R command window to set and indicate).
#Enter ''source("Surveydata_syntax.R", encoding = "UTF-8")'' in R command window.

=STATA-xml Export= 

<div class="simplebox">This option is available from version 2.05</div>

STATA is a commercial data analysis and statistical software package.

This export routine was created to facilitate rapid analysis of data collected with LimeSurvey. It creates an XML-file in STATAs proprietary format, which can be imported independent of the platform STATA is run on. Using this format offeres several advantages over importing plain CSV files:
*Data sets are fully labelled including variable labels (question, subquestion) and value labels (answers, if applicable).
*Dates are already transformed to STATAs internal date format and thus can directly be used to calculate difference between days etc.
*Variable names are, if necessary, converted to a STATA compatible format.
*Data formats of variables (string, integer, float, etc.) are already set according to the underlying data. (No more numbers encoded as strings :) ).

'''Howto load the file in STATA:
In STATA's menu, click on File, Import, xml-data. Choose browse to navigate to your exported file and click 'OK'. That should be it.
If you prefer STATA's binary .dta files, you can just save your data again in this format.
'''

Be aware: Due to a limitation in STATA's data format, the string length has a maximum of 244 characters. Everything > 244 characters is not exported.

=VVExport ([[File:exportvv.png]]) and VVImport ([[File:importvv.png]])= 


Once you've begun collecting responses, there may be occasions where you need to be able to directly edit and modify large quantities of data from your responses table, where a spreadsheet tool may be more useful.


VVExport (the "VV" stands for vertical verification) allow you to export your responses table into a .csv file. So long as the general structure of the file remains intact, you can then edit values within it, and the import the file again into your responses table using the "VVImport" feature.


Things you should be aware of:
* If you want to import responses using "VVImport" make sure to check whether the responses should be added to the existing responses or all responses should be overwritten.
* If you are trying to import responses from a different yet identical (e.g. identical questions/answers from another survey) make sure you are using the correct vv file and that the first two lines of the .csv-file are correct.
* If you import a survey to your LimeSurvey installation the SID will (if possible) not change. The group id and question id however might change. So you might have to adjust the first two heading lines to match the new group id/question id. See '''Adjusting vv file headings'''

==Exporting a VV survey file== 


[[File:limesurveyExportVVen.jpg]]


When you choose to export responses using VVExport you will be given the option to choose which survey to be exported, whether you want to export all responses or complete responses only or incomplete responses only. The file extension allows you to choose which extension the exported file will have. For easy use .csv should be chosen.


A 'vv survey file' allows you to import the responses to a survey when the question/answer combinations have changed. Effectively this allows you to add or remove questions in an active survey.


Clicking on "Export a VV survey file" will then produce a tab delimited file that can be opened by Excel or similar style spreadsheet program. The first two rows of the spreadsheet are the column labels. The first row is a "human readable" column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response.


You should not modify the first two rows of this spreadsheet if you want to be able to "import" the data back into LimeSurvey at a later point.

==Editing a VV survey file== 


When a vv file has been successfully exported you can use a spreadsheet tool like Microsoft Excel or alternatives to open and edit the file. If you have to choose the column seperator use "Tabulator". If you are using mutated vowels (like ä, ö or ü in the german language) make sure you use "UTF-8" as used character set.


If you are using Microsoft Excel to edit the exported vv file, you should know that excel destroys the original data structure of the file. This causes an error when you try to re-import the edited vv file.


But there is a workaround which allows you to edit the file with excel and import it without problems, as one of our users found out (see "Importing a VV survey file")


As mentioned before the first two rows of the vv file are headers so you should not change them. There are different use cases for importing a vv file so we will differentiate between adding new responses to a survey and overwriting all responses of the survey.


example (structure of a vv file):


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


</syntaxhighlight>

===Adding new responses to the existing responses of a survey=== 


If you want to add new responses to the survey you can delete every row past row two (the both headers should not be deleted) and add the new responses using one response for each row. You can add the responses by entering them manually or copy/paste the reponses from e.g. another vv file (be carefull to add the responses only and not the header.)


'''Example'''


Step 1: Open file


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


</syntaxhighlight>


Step 2: Delete old answers


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


</syntaxhighlight>


Step 3: Add new answers


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


17 10.11.11 12:44 3 de 4


18 24.11.11 14:53 3 de 2


</syntaxhighlight>


You can then import the survey, make sure not to override the existing responses (see "Importing a VV survey file").

===Overwriting all responses of the survey=== 


If you want to overwrite all responses of the survey you can just add the new responses to the end of the file. As mentoined in "Adding new responses to the existing responses of a survey" you can either enter them manually or copy/paste them from another vv file.


'''example'''


Step 1: Open file


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


</syntaxhighlight>


Step 2: Add new answers (at the end of the document)


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


17 10.11.11 12:44 3 de 4


18 24.11.11 14:53 3 de 2


</syntaxhighlight>


You can then import the survey, make sure to override the existing responses (see "Importing a VV survey file").

===Adjusting vv file headings=== 


When importing a survey it might happen that the survey id stays the same while the group and question ids change. In order to import the survey results you have to adjust the headings of the vv file. How to import a new survey and the survey results will be explained below.


'''example'''


Step 1: Import the new survey


Step 2: Activate the new survey


Step 3: Export the "empty" results of the new survey as vv file


Step 4: Open the "empty" vv file (new SGQA: 46492X<span style='color:#F00'>45</span>X<span style='color:#F00'>3269</span>)


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X45X3269


</syntaxhighlight>


Step 5: Copy the first two lines/rows from the "empty" vv file


Step 6: Open the exported vv file from the old LimeSurvey installation (old SGQA: 46492X<span style='color:#F00'>40</span>X<span style='color:#F00'>1991</span>)


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


</syntaxhighlight>


Step 7: Paste the new headings (copied two lines/rows) into the first two lines/rows of the old vv export file (now the SGQA should be 46492X<span style='color:#F00'>45</span>X<span style='color:#F00'>3269</span>)


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X45X3269


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


</syntaxhighlight>


You can now import the vv file and the headings are correct.

==Importing a VV survey file== 


[[File:LimeSurveyImportVVen.jpg]]


As long as the first two lines are intact, you can then import the data in your vv survey file back into an active LimeSurvey survey.


If you used Microsoft Excel to edit the exported vv file, the data structure of this file may be corrupted, so LimeSurvey is not able to import the edited file. You can try the following workaround to get the import working without an error:
*Open your exported vv file in Excel and do your changes (I guess you already did that)
*Save it as tab-separated text file (It creates a new file with the extension .txt)
*Do another "clean" vv export from LimeSurvey
*Open this new exported vv file with a texteditor like notepad or something else (I used textwrangler on mac)
*Press CTRL + A to mark all of the content and delete it
*Open the Excel edited vv file (the tab separated .txt file) with a texteditor and press CTRL + A to mark all of the content
*Press CTRL + C to copy the content and paste it into the new (now empty) vv file
*Press CTRL + S to save the file as it is (as .csv)
*Now try to import this file


Then, from the browse screen, choose the "Import a VV Survey file" icon.


The "Import a VV Survey File" screen needs you to choose the "vvexport" file you are importing. If you choose to "Exclude Record IDs" the records will be imported and brand new Record ID's will be generated for them (use this option for the use case "Adding new responses to the existing responses of a survey"). If you un-check this box, then the original record id's will be imported (use this option for the use case "Overwriting all responses of the survey").


There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries.
*Report an error (and skip the new record).
*Renumber the new record
*Replace the existing record (uses this for the use case "Overwriting all responses of the survey")

=Other export options= 

==Export a single response== 


If you want to export an individual response, you can do it in 3 ways:


1. Login to limesurvey admin backend, choose your survey, goto "Edit survey settings" -> "Notification and data management" and make sure you receive basic email notifications.


Every time someone has completed a survey, you will receive an email with a link: "Click the following link to see the individual response"


This will take you to a page with a button above the data saying "Export this response"


2. Login to limesurvey admin backend, choose your survey and "Browse responses for this survey". Click on "Display responses" and the id number you want to export in the left column. Then you can click on "Export this survey" above the data.


3. Login to limesurvey admin backend, choose your survey and "Export results to application". In the last field above "Export data" you can choose which entry you want to export.

==Match responses from different surveys== 


If you want to track survey responses for particular individuals over time, LimeSurvey can help you do that. A possible use case is to track group responses before and after the group takes a particular seminar.


The steps to implementing this are as follows:


1. Create the survey


2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey:


a - Click on the icon General settings.


b - Then under the Tokens tab select "No" for Anonymized responses.


3. Activate the survey.


When you activate the survey, click on the "switch to closed-access mode" button to create the token table:


[[File:switch_to_closed.png]]


4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ).


5. Export the survey results and make sure you include the token information.


To export click ''browse results''...


[[File:browse_results.png]]


...and then ''export'':


[[File:export2.png]]


Remember to choose one or more elements from the token table to associate with the survey responses:


[[File:export_tokens.png]]


6. When you run the survey again, which can easily be done by copying the survey and tokens table using export/import, just repeat the steps, and make sure the same query is used to build the csv token import file.

=Problems & Solutions= 

==Excel== 

===Modifying responses in Excel prior to Import=== 


In order to make multiple changes to responses, you may choose to Export and open a file in Excel. Make changes to the data (other than the top lines) and then save as a .txt file. If you save as .csv, Excel uses comma-delimits which will not import into LimeSurvey. By saving as a .txt file, Excel saves as a tab-delimited file which imports back into LimeSurvey.

===Edit .csv with Excel=== 


In general '''''we do not recommend to use Excel to edit the exported .csv files''''' because Excel does some changes to the internal data structure which results in a failing import. If you nevertheless want to use Excel you have to set the seperator for Excel to a comma in System Control (Windows Systems):


System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,

===Workaround to edit .csv files with Excel=== 


Using Excel for editing questions can prevent you from being able to re-import them. But editing is the way to go if you have more than 5 or so options or ranking options, want to use Excel capabilities like sorting, etc.


This is a partial workaround that seems to work in 1.82-essentially, only use Excel on the part of the file that is the data:
* Export a question similar to what you would like to reuse as .csv file
* Open the CSV file in a rawtext editor
* Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.
* Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish
* Save the file as Excel CSV, which will likely have no quotes.
* Open this file in the editor, and Select All, Copy
* Go back to the file you opened with the rawtext editor
* Paste over the answers there
* Save AS, with a different name, maybe one that you can remember for reuse
* Import this file.

===Excel - export limited to 255 columns=== 


Due to limitations in Excel (versions lower and equal to 2003), LimeSurvey can export only 255 columns at the same time. Microsoft has proposed a [http://support.microsoft.com/kb/272729/en-us workaround as a VB macro].


Although newer spreadsheets (Excel >= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can't export more than 255 columns.


Two workarounds are however possible, use one of the following solutions:
* Either export to CSV and import in your spreadsheet
* Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results

===Excel/.csv - export fails=== 


If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.

==CSV== 

===CSV defaults to 255 columns=== 


When exporting large surveys the GUI by default limits the export to the first 255 columns. To work around this, simply mark all data sets for export.

==SPSS export== 

===General steps=== 


To import the LimeSurvey response data please use the following steps:
#Click on the 'Export to SPSS' icon.
#From the select boxes select which responses you want to export and your SPSS version.
#Download both files, the .sps (SPSS syntax command file) and .dat file (data file)
#Open the .sps file with SPSS by opening SPSS, then select 'Choose another type of file' and select the downloaded .sps file.
#Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with '/FILE=...'
#Edit that line and adjust the path so it points to your .dat file. Example: Your *.dat file is in c:\temp so set this line to /FILE='c:\temp\survey_(xxxx)_SPSS_data_file.dat'
#Now select all commands inside the editor by pressing CTRL-A.
#From the SPSS menu select Run/All.
#Be patient, it will take some time to import all data and labels. Check the status bar for the progress.
#Done!

===Possible error messages in SPSS=== 

====ERROR. command name:Get Data==== 


If you receive the error message ''ERROR. command name:Get Data. 2267 Unexpected Token missing.'' please edit the forth line of your syntax file so it points to the absolute path of the data file like


<div class="simplebox">C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat</div>

====Error: "Text value unmappable in the current server locale"==== 


This error can happen if you try to open an exported syntax file in SPSS 16. The solution is to force SPSS to interpret the syntax file as unicode.


<div class="simplebox">Open SPSS. Go to Edit > Options > Character encoding for data and syntax. Change the option to "unicode".</div>


LimeSurvey data can now be exported to SPSS 16 without any problem.

===Define the scale to use for your variable=== 


It is possible to override the default scale used for a variable by setting the question attribute [[Advanced question settings#scale_export|scale_export]] to the appropriate value.

==VV Export/Import== 

===VV - Problems with vv import=== 


If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine.

==Other problems and solutions== 

===Copying responses into a different survey (using tokens)=== 
# Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.
# Export the responses from the old survey, including tokens, open in Excel.
# Use this data to create an Excel worksheet for the standard token file import (eg. Firstname, Lastname, Token, Email address, Email status (OK), Language (En)). Save as .csv and import tokens to the new survey in LimeSurvey.
# In Excel, copy the response fields from the old survey responses that you want in the new survey (including token) into the appropriate Excel column of the new survey format.
# Save as .txt file.
# Use VVImport to import the new data into the new survey.
# Possible import errors include date format - some system date fields do not allow a NULL value, some do. If the date looks okay but gives an error, use the Excel cell format "2009-12-01".
</translate>

Exporting results

2013-10-16T19:47:02Z

Mfaber: Add STATA export

<languages /> <translate>

__TOC__


Once your survey is active you can start browsing responses and export them. To get to the survey response overview click...


[[File:browse_results.png]]

=Export to application (Excel/.csv)= 


On top of the browse responses page several export options are listed, beginning with ''export to CSV/application''.


[[File:export2.png]]


When exporting results to an application there are several filter options which are separated into:
*'''General'''
** Set a range like export records X to Y
** Set to export all records OR completed records only OR incomplete records only
*'''Questions'''
** Set how the heading should look like: Abbreviated heading OR full headings OR question codes
** Convert spaces in question text to underscores
*'''Answers'''
** You can either export full answers or convert answer codes Y and N to a defined variable
*'''Format'''
** Microsoft Word (latin charset)
** Microsoft Excel (all charsets)
** CSV File (all charsets)
** PDF
*'''Column Control'''
** Set which answers should be exported. All answers in this list are represented by their [[SGQA identifier|SGQA identifier]]
** Set which '''''token''''' data should be exported. This option is only available if your survey is '''''not anonymous'''''!


[[File:export_tokens.png]]

=SPSS Export= 

==General== 


To export your response data to SPSS go to Responses & Statistics section and click the icon to export to SPSS.


[[File:spss_toolbar.png]]

==Export and filter data== 


When exporting data to SPSS there are two filter options. You can select '''which data''' should be selected (''all records/completed records only/incompleted records only'') and for '''which SPSS version''' the export files will be used (''prior version 16/16 or up'').


SPSS export includes two files:
# a syntax file (''survey_xxxx_SPSS_syntax_file.sps'')
# and a data file (''survey_xxxx_SPSS_data_file.dat'').


After having downloaded these files you can open them using a raw text editor like notepad to take a look how the exported data looks like. The syntax file holds the commands that should be run to import the data. It is like a programming language inside SPSS. The data file contains a comma separated file with all data. If you just import this data as csv via a wizard you loose information about questions, labelsets etc. so we don't do that.

==Import data in SPSS== 


Place the two files in the same folder on your drive (example: ''c:\data\survey_xxxx_SPSS_syntax_file.sps'' and ''c:\data\survey_xxxx_SPSS_data_file.dat'')


We have two options now:


1. When using Windows use the explorer to browse to the folder used above. If SPSS is connected to the .sps file extension you can just open the file by double clicking it:


[[File:spss_explorer-screenshot.jpg]]


Now you can just choose Run->All from the opened window and after some time have your output dataset that you can save as a normal .sav file.


2. Sometimes the easy solution above does not work. Then you can proceed as follows:
* Open SPSS
* Choose File->Open->Syntax
* Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps
* Now the syntax opens.
* Change the line that reads ''/FILE='survey_xxxx_SPSS_data_file.dat' '' to include the path where the files are: ''/FILE='c:\data\survey_xxxx_SPSS_data_file.dat' ''
* Now mark the whole command text and choose Run->All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc.

=R Export= 


Feel free to add more information if you have some!


The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is closely linked to the SPSS export in LimeSurvey. Instructions on how to import your dataset in R:
#Download the syntax file and the data file.
#Store both files in R work listing (use ''getwd()'' and ''setwd()'' in R command window to set and indicate).
#Enter ''source("Surveydata_syntax.R", encoding = "UTF-8")'' in R command window.

=STATA-xml Export= 

STATA is a commercial data analysis and statistical software package.

This export routine was created to facilitate rapid analysis of data collected with LimeSurvey. It creates an XML-file in STATAs proprietary format, which can be imported independent of the platform STATA is run on. Using this format offeres several advantages over importing plain CSV files:
*Data sets are fully labelled including variable labels (question, subquestion) and value labels (answers, if applicable).
*Dates are already transformed to STATAs internal date format and thus can directly be used to calculate difference between days etc.
*Variable names are, if necessary, converted to a STATA compatible format.
*Data formats of variables (string, integer, float, etc.) are already set according to the underlying data. (No more numbers encoded as strings :) ).

'''Howto load the file in STATA:
In STATA's menu, click on File, Import, xml-data. Choose browse to navigate to your exported file and click 'OK'. That should be it.
If you prefer STATA's binary .dta files, you can just save your data again in this format.
'''

Be aware: Due to a limitation in STATA's data format, the string length has a maximum of 244 characters. Everything > 244 characters is not exported.

=VVExport ([[File:exportvv.png]]) and VVImport ([[File:importvv.png]])= 


Once you've begun collecting responses, there may be occasions where you need to be able to directly edit and modify large quantities of data from your responses table, where a spreadsheet tool may be more useful.


VVExport (the "VV" stands for vertical verification) allow you to export your responses table into a .csv file. So long as the general structure of the file remains intact, you can then edit values within it, and the import the file again into your responses table using the "VVImport" feature.


Things you should be aware of:
* If you want to import responses using "VVImport" make sure to check whether the responses should be added to the existing responses or all responses should be overwritten.
* If you are trying to import responses from a different yet identical (e.g. identical questions/answers from another survey) make sure you are using the correct vv file and that the first two lines of the .csv-file are correct.
* If you import a survey to your LimeSurvey installation the SID will (if possible) not change. The group id and question id however might change. So you might have to adjust the first two heading lines to match the new group id/question id. See '''Adjusting vv file headings'''

==Exporting a VV survey file== 


[[File:limesurveyExportVVen.jpg]]


When you choose to export responses using VVExport you will be given the option to choose which survey to be exported, whether you want to export all responses or complete responses only or incomplete responses only. The file extension allows you to choose which extension the exported file will have. For easy use .csv should be chosen.


A 'vv survey file' allows you to import the responses to a survey when the question/answer combinations have changed. Effectively this allows you to add or remove questions in an active survey.


Clicking on "Export a VV survey file" will then produce a tab delimited file that can be opened by Excel or similar style spreadsheet program. The first two rows of the spreadsheet are the column labels. The first row is a "human readable" column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response.


You should not modify the first two rows of this spreadsheet if you want to be able to "import" the data back into LimeSurvey at a later point.

==Editing a VV survey file== 


When a vv file has been successfully exported you can use a spreadsheet tool like Microsoft Excel or alternatives to open and edit the file. If you have to choose the column seperator use "Tabulator". If you are using mutated vowels (like ä, ö or ü in the german language) make sure you use "UTF-8" as used character set.


If you are using Microsoft Excel to edit the exported vv file, you should know that excel destroys the original data structure of the file. This causes an error when you try to re-import the edited vv file.


But there is a workaround which allows you to edit the file with excel and import it without problems, as one of our users found out (see "Importing a VV survey file")


As mentioned before the first two rows of the vv file are headers so you should not change them. There are different use cases for importing a vv file so we will differentiate between adding new responses to a survey and overwriting all responses of the survey.


example (structure of a vv file):


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


</syntaxhighlight>

===Adding new responses to the existing responses of a survey=== 


If you want to add new responses to the survey you can delete every row past row two (the both headers should not be deleted) and add the new responses using one response for each row. You can add the responses by entering them manually or copy/paste the reponses from e.g. another vv file (be carefull to add the responses only and not the header.)


'''Example'''


Step 1: Open file


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


</syntaxhighlight>


Step 2: Delete old answers


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


</syntaxhighlight>


Step 3: Add new answers


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


17 10.11.11 12:44 3 de 4


18 24.11.11 14:53 3 de 2


</syntaxhighlight>


You can then import the survey, make sure not to override the existing responses (see "Importing a VV survey file").

===Overwriting all responses of the survey=== 


If you want to overwrite all responses of the survey you can just add the new responses to the end of the file. As mentoined in "Adding new responses to the existing responses of a survey" you can either enter them manually or copy/paste them from another vv file.


'''example'''


Step 1: Open file


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


</syntaxhighlight>


Step 2: Add new answers (at the end of the document)


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


17 10.11.11 12:44 3 de 4


18 24.11.11 14:53 3 de 2


</syntaxhighlight>


You can then import the survey, make sure to override the existing responses (see "Importing a VV survey file").

===Adjusting vv file headings=== 


When importing a survey it might happen that the survey id stays the same while the group and question ids change. In order to import the survey results you have to adjust the headings of the vv file. How to import a new survey and the survey results will be explained below.


'''example'''


Step 1: Import the new survey


Step 2: Activate the new survey


Step 3: Export the "empty" results of the new survey as vv file


Step 4: Open the "empty" vv file (new SGQA: 46492X<span style='color:#F00'>45</span>X<span style='color:#F00'>3269</span>)


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X45X3269


</syntaxhighlight>


Step 5: Copy the first two lines/rows from the "empty" vv file


Step 6: Open the exported vv file from the old LimeSurvey installation (old SGQA: 46492X<span style='color:#F00'>40</span>X<span style='color:#F00'>1991</span>)


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X40X1991


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


</syntaxhighlight>


Step 7: Paste the new headings (copied two lines/rows) into the first two lines/rows of the old vv export file (now the SGQA should be 46492X<span style='color:#F00'>45</span>X<span style='color:#F00'>3269</span>)


<syntaxhighlight lang="php" enclose="div">


Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)


id submitdate lastpage startlanguage token 46492X45X3269


183 09.11.11 11:44 3 de 4


184 09.11.11 11:53 3 de 2


190 09.11.11 11:44 3 de 1


</syntaxhighlight>


You can now import the vv file and the headings are correct.

==Importing a VV survey file== 


[[File:LimeSurveyImportVVen.jpg]]


As long as the first two lines are intact, you can then import the data in your vv survey file back into an active LimeSurvey survey.


If you used Microsoft Excel to edit the exported vv file, the data structure of this file may be corrupted, so LimeSurvey is not able to import the edited file. You can try the following workaround to get the import working without an error:
*Open your exported vv file in Excel and do your changes (I guess you already did that)
*Save it as tab-separated text file (It creates a new file with the extension .txt)
*Do another "clean" vv export from LimeSurvey
*Open this new exported vv file with a texteditor like notepad or something else (I used textwrangler on mac)
*Press CTRL + A to mark all of the content and delete it
*Open the Excel edited vv file (the tab separated .txt file) with a texteditor and press CTRL + A to mark all of the content
*Press CTRL + C to copy the content and paste it into the new (now empty) vv file
*Press CTRL + S to save the file as it is (as .csv)
*Now try to import this file


Then, from the browse screen, choose the "Import a VV Survey file" icon.


The "Import a VV Survey File" screen needs you to choose the "vvexport" file you are importing. If you choose to "Exclude Record IDs" the records will be imported and brand new Record ID's will be generated for them (use this option for the use case "Adding new responses to the existing responses of a survey"). If you un-check this box, then the original record id's will be imported (use this option for the use case "Overwriting all responses of the survey").


There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries.
*Report an error (and skip the new record).
*Renumber the new record
*Replace the existing record (uses this for the use case "Overwriting all responses of the survey")

=Other export options= 

==Export a single response== 


If you want to export an individual response, you can do it in 3 ways:


1. Login to limesurvey admin backend, choose your survey, goto "Edit survey settings" -> "Notification and data management" and make sure you receive basic email notifications.


Every time someone has completed a survey, you will receive an email with a link: "Click the following link to see the individual response"


This will take you to a page with a button above the data saying "Export this response"


2. Login to limesurvey admin backend, choose your survey and "Browse responses for this survey". Click on "Display responses" and the id number you want to export in the left column. Then you can click on "Export this survey" above the data.


3. Login to limesurvey admin backend, choose your survey and "Export results to application". In the last field above "Export data" you can choose which entry you want to export.

==Match responses from different surveys== 


If you want to track survey responses for particular individuals over time, LimeSurvey can help you do that. A possible use case is to track group responses before and after the group takes a particular seminar.


The steps to implementing this are as follows:


1. Create the survey


2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey:


a - Click on the icon General settings.


b - Then under the Tokens tab select "No" for Anonymized responses.


3. Activate the survey.


When you activate the survey, click on the "switch to closed-access mode" button to create the token table:


[[File:switch_to_closed.png]]


4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ).


5. Export the survey results and make sure you include the token information.


To export click ''browse results''...


[[File:browse_results.png]]


...and then ''export'':


[[File:export2.png]]


Remember to choose one or more elements from the token table to associate with the survey responses:


[[File:export_tokens.png]]


6. When you run the survey again, which can easily be done by copying the survey and tokens table using export/import, just repeat the steps, and make sure the same query is used to build the csv token import file.

=Problems & Solutions= 

==Excel== 

===Modifying responses in Excel prior to Import=== 


In order to make multiple changes to responses, you may choose to Export and open a file in Excel. Make changes to the data (other than the top lines) and then save as a .txt file. If you save as .csv, Excel uses comma-delimits which will not import into LimeSurvey. By saving as a .txt file, Excel saves as a tab-delimited file which imports back into LimeSurvey.

===Edit .csv with Excel=== 


In general '''''we do not recommend to use Excel to edit the exported .csv files''''' because Excel does some changes to the internal data structure which results in a failing import. If you nevertheless want to use Excel you have to set the seperator for Excel to a comma in System Control (Windows Systems):


System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,

===Workaround to edit .csv files with Excel=== 


Using Excel for editing questions can prevent you from being able to re-import them. But editing is the way to go if you have more than 5 or so options or ranking options, want to use Excel capabilities like sorting, etc.


This is a partial workaround that seems to work in 1.82-essentially, only use Excel on the part of the file that is the data:
* Export a question similar to what you would like to reuse as .csv file
* Open the CSV file in a rawtext editor
* Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.
* Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish
* Save the file as Excel CSV, which will likely have no quotes.
* Open this file in the editor, and Select All, Copy
* Go back to the file you opened with the rawtext editor
* Paste over the answers there
* Save AS, with a different name, maybe one that you can remember for reuse
* Import this file.

===Excel - export limited to 255 columns=== 


Due to limitations in Excel (versions lower and equal to 2003), LimeSurvey can export only 255 columns at the same time. Microsoft has proposed a [http://support.microsoft.com/kb/272729/en-us workaround as a VB macro].


Although newer spreadsheets (Excel >= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can't export more than 255 columns.


Two workarounds are however possible, use one of the following solutions:
* Either export to CSV and import in your spreadsheet
* Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results

===Excel/.csv - export fails=== 


If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.

==CSV== 

===CSV defaults to 255 columns=== 


When exporting large surveys the GUI by default limits the export to the first 255 columns. To work around this, simply mark all data sets for export.

==SPSS export== 

===General steps=== 


To import the LimeSurvey response data please use the following steps:
#Click on the 'Export to SPSS' icon.
#From the select boxes select which responses you want to export and your SPSS version.
#Download both files, the .sps (SPSS syntax command file) and .dat file (data file)
#Open the .sps file with SPSS by opening SPSS, then select 'Choose another type of file' and select the downloaded .sps file.
#Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with '/FILE=...'
#Edit that line and adjust the path so it points to your .dat file. Example: Your *.dat file is in c:\temp so set this line to /FILE='c:\temp\survey_(xxxx)_SPSS_data_file.dat'
#Now select all commands inside the editor by pressing CTRL-A.
#From the SPSS menu select Run/All.
#Be patient, it will take some time to import all data and labels. Check the status bar for the progress.
#Done!

===Possible error messages in SPSS=== 

====ERROR. command name:Get Data==== 


If you receive the error message ''ERROR. command name:Get Data. 2267 Unexpected Token missing.'' please edit the forth line of your syntax file so it points to the absolute path of the data file like


<div class="simplebox">C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat</div>

====Error: "Text value unmappable in the current server locale"==== 


This error can happen if you try to open an exported syntax file in SPSS 16. The solution is to force SPSS to interpret the syntax file as unicode.


<div class="simplebox">Open SPSS. Go to Edit > Options > Character encoding for data and syntax. Change the option to "unicode".</div>


LimeSurvey data can now be exported to SPSS 16 without any problem.

===Define the scale to use for your variable=== 


It is possible to override the default scale used for a variable by setting the question attribute [[Advanced question settings#scale_export|scale_export]] to the appropriate value.

==VV Export/Import== 

===VV - Problems with vv import=== 


If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine.

==Other problems and solutions== 

===Copying responses into a different survey (using tokens)=== 
# Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.
# Export the responses from the old survey, including tokens, open in Excel.
# Use this data to create an Excel worksheet for the standard token file import (eg. Firstname, Lastname, Token, Email address, Email status (OK), Language (En)). Save as .csv and import tokens to the new survey in LimeSurvey.
# In Excel, copy the response fields from the old survey responses that you want in the new survey (including token) into the appropriate Excel column of the new survey format.
# Save as .txt file.
# Use VVImport to import the new data into the new survey.
# Possible import errors include date format - some system date fields do not allow a NULL value, some do. If the date looks okay but gives an error, use the Excel cell format "2009-12-01".
</translate>

Workarounds: Question design, layout and templating

2013-08-17T20:08:31Z

Mfaber: Workaround not needed for setting min/max date from 2.05 beta6 (new feature)

This section more or less deals with styling your survey, adjusting the layout and setting up special question types. You can find '''similar information''' at these pages:
* [[The template editor]]
* [[Workarounds: Manipulating a survey at runtime using Javascript]]
* [[Workarounds: Survey behaviour]].

<div class="simplebox"><center><br />'''Please keep in mind that these workarounds are not official LimeSurvey extensions - they are solutions that users have created for themselves.<br /><span style='color:#EE0000,#FFFFFF'>Therefore LimeSurvey can't offer guarantees or support for these solutions.</span><br />If you have questions, please contact the users that, thankfully, shared their solutions with the community.'''<br /><br /></center></div>

__TOC__

=Getting rid of the question mark symbol (help.gif)=

''Tested with: 1.80+ (6536)''

To get rid of the question mark symbol that LimeSurvey displays at the end of a question, you can either upload an empty help.gif into the template folder (as discussed in the forum) or you can use the Template editor: Open the ''template.css'' of your template and search for ''div.questionhelp img'', then add a ''visibility:hidden;''

It will look something like this:

<syntaxhighlight lang="php" enclose="div">

div.questionhelp img

{

margin:5px;

visibility:hidden;

}

</syntaxhighlight>

You can also '''replace the image''' by following [[The template editor#Replacing the help icon|these instructions]].

=Require users to check a box agreeing to privacy statement before registering for a survey=

If you need to have users positively acknowledge a privacy statement before submitting a registration form, the following will help you do this.

It involves a minor modification to common.php in versions up to 1.85. Later versions may not require this.

Edit common.php and look for the line (at approximately line 3014)

<syntaxhighlight lang="php" enclose="div">$registerform .= "<tr><td></td><td>

<input class='submit' type='submit' value='".$clang->gT("Continue")."' />"

</syntaxhighlight>

and change it to:

<syntaxhighlight lang="php" enclose="div">$registerform .= "<tr><td></td><td>

<input id='registercontinue' class='submit' type='submit' value='".$clang->gT("Continue")."' />"

</syntaxhighlight>

Then save common.php. This gives you DOM access to the "continue" button on the register form, but will have no other practical effect or change to LimeSurvey's operations.

Next, you need to edit the template you are using (see the documentation on the Template editor if you don't know how to do this).

In the template editor, open the screen "Register page" and select the file "register.pstpl"

There are two modifications you need to make to this file. The first is to add the following code after the line that says ''{REGISTERFORM}''.

<syntaxhighlight lang="php" enclose="div"><script type='text/javascript'>

</script></syntaxhighlight>

This code disables the "Continue" button so that nobody can process the registration form until they've clicked the checkbox.

The second modification to make is to be done between the lines {REGISTERMESSAGE2} and {REGISTERFORM}. Add:

<syntaxhighlight lang="php" enclose="div"><center>

<label> Accept

<input type='radio'

name="privacy"

value="YES"

onChange="if(this.checked) {

document.getElementById('registercontinue').disabled=false;

}" />

</label>

<label>I don't accept

<input type='radio'

name="privacy"

value="NO"

CHECKED

onChange="if(this.checked) {

document.getElementById('registercontinue').disabled=true;

}" />

</label>

</center></syntaxhighlight>

Then the users will have to agree to whatever text you replace "Do you agree to privacy stuff?" before they continue on and register.

(Thanks to ''Pippo_Jedi'' for helping work this out)

=Different progress indicator=

==Version 1.87 and later:==

Add the following to the end of template.js. It will find the progress value and insert it into the element following the progress bar.

It should be pointed out that I had to introduce a delay in firing the function because the progress value is not calculated until after template.js is called. The delay is set at 1/10 of a second but you may be able to reduce that.

<syntaxhighlight lang="php" enclose="div">

// Display progress value

function setProgValue() {

var progress = $('#progressbar').attr('aria-valuenow');

$('#progress-post').text(progress+'%').show();

}

$(document).ready(function(){

$('#progress-post').hide();

setTimeout('setProgValue()',100);

});

</syntaxhighlight>

If you want to hide the "0%" before the progress bar, add the following to the end of template.css:

<syntaxhighlight lang="php" enclose="div">
#progress-pre {

display: none;

}

</syntaxhighlight>

=Delete unwanted gaps in question title=

''Tested with: ''

When copying data (questions, answers, ...) from MS Word or other applications into the editor there might occur some gaps in the question title.

There are two solutions to this:
# Use popup mode and manually delete unwanting extra html tags (requires html knowledge).
# Disable paste word feature: Tweak your limesurvey-config.js file in limesurvey/admin/scripts/fckeditor.26 and set the following option to true:

<syntaxhighlight lang="php" enclose="div">FCKConfig.ForcePasteAsPlainText = true ;</syntaxhighlight>

After that clear you browser cache and try again.

=How to change the <font-size> tags using CSS=

''This workaround was deleted because it is outdated. Such changes can be done by [[The template editor#Styling questions with CSS|adjusting template.css]] of your template.

=Question type variation: Scale with bars (one and two sided)=

''Tested with: ''

Some methodogical issues to think about: Very often a common scale as 1 to 5 or -2 to +2 fits all needs, as the shown subject is clearly defined as positive or negative. As soon as you would reduce the influence from the question and scale on the respondent, you will need something neutral to determine tendences, emphases and so on.

So I put up a new variation of the one and two sided array question:

ttp://www.limesurvey.org/images/fbfiles/images/example_bar_scale.jpg

In my example the left side reads "strategical planning" and the right side "operative business". None of these are purely negative or positive, so the bars only show in which direction the balancing point moves.

To realize a question as shown above just do as follows:

Set up as many bars as you will need (in my example there are four different bars in total) with a graphic program like PAINT .NET, GIMP or similar ones (yes, you may also use commercial software like Photoshop). To prevent the bars from looking twitchy, designate the size in advance. I did one bar 60x15 px, one 45x15px, one 30x15px and at last 15x15px. Save them as PNG, JPG or GIF.
# Create a new label set within Lime. Call it whatever you like.
# Enter a code number at first, then press the pencil symbol to enter the editor.
#Press the "Insert / edit image" button and upload the bar you want to insert with the FCK upload tool. Then choose the uploaded picture, save and leave the FCK editor.
#The row in the lable editor now shows an <img>-tag which refers to your bar picture.
#Repeat the above described steps as often as needed to build up your bar scale.

=Doing a Likert Scale=

''Tested with: ''

A Likert Scale is a special type of the Semantic Differential question where several item shall be rated on different scales, each marked at the beginning and at the end with opposite statements. See example:

http://www.limesurvey.org/images/fbfiles/images/lickert.jpg

To do this in LimeSurvey just follow these steps:
#Create a label set with values from 0 to 7 (for the classic Likert Scale - feel free to choose other ranges).
#Create a new question and choose Array (Flexible Labels) as question type.
#Assign the Likert Scale label set to this question.
#Enter your answers as follows:

<syntaxhighlight lang="php" enclose="div"><DIV style="white-space: nowrap;">ITEM statement1|statement2</div></syntaxhighlight>

The white-space style is to avoid line breaks which would ruin the whole scale. feel free to insert non-breakable spaces between the ITEM and statement1 to define the margin between these to strings.

=Alternate background colour of questions=

''Tested with: 1.85+ (7191)''

To alternate the background colour of questions, open the ''template.css'' of your template with the Template Editor or a text editor and modify the ''Question styles'' section to include the following style.

<syntaxhighlight lang="php" enclose="div">

div#question2 td.questiontext,

div#question4 td.questiontext,

div#question6 td.questiontext {

background-color: #E0EBF8;

}

</syntaxhighlight>

Be sure to apply the style to all of the questions you would like modified using their question IDs (''question2, question4, question6'' in this case). Question IDs are displayed when creating or editing questions - see below:

[[File:qid_1_493x173.gif]]

Here the question ID is #question80 .

=Embedding audio in questions=

''Tested with: 1.85+ (7191), IE 7, FireFox 3''

Audio clips can be embedded in most question text or answer text. In this example, using the default template, I've embedded clips into the answers of an '''''Array (Yes/No/Uncertain)''''' question to ask respondents how they feel about some sounds. The resulting question will look like this.

[[File:audioTest_595x202.gif]]

It's accomplished by placing the following code in each of the answers.

<syntaxhighlight lang="php" enclose="div">

<embed height="20" width="128" autostart="false" controls="console"

loop="true" volume="50" src="{TEMPLATEURL}audio_1.mp3"></embed>

</syntaxhighlight>

Some notes about the code:
*The ''audio_1.mp3'' part will be different for each answer (it's the audio file name).
*In this case the audio files are residing in the template folder being used for this survey (that's where ''{TEMPLATEURL}'' points to) but they can be placed anywhere if you use an absolute URL in the ''src'' parameter - something like ''src="http://mysite.com/audio/audio_1.mp3"''
*If the audio file doesn't exist where the ''src'' parameter indicates, the player will not appear.
*You'll need to insert the code into the answers using the source screen - click on "Edit answers", click the pencil beside the text box, click "Source" in the pop-up, enter the code and save it with the little diskette icon.
*You may need to turn off the XSS filter - see the documentation for [http://docs.limesurvey.org/tiki-index.php?page=Global+settings&structure;=English+Instructions+for+LimeSurvey#Security Global settings].

Although the above example places the audio in the answer text of the question, the same principles can be used to place it in the question text itself. Something like this perhaps.

[[File:audioTest_595x154.gif]]

=Hiding inputs of a "Multiple options with comments" question=

Tested with: 1.85+ (7253), IE 6/7, FireFox 3.0, Safari 3.2, Chrome 2.0

There may be times when you want to hide some of the input boxes of a '''''Multiple options with comments''''' question as in the image below.

[[File:hidden_inputs_541x168.gif]]

This can be accomplished with CSS (see [[The template editor#Styling questions with CSS|Styling questions in LimeSurvey 1.8]]). For each input that you want to hide, add the following style to your template.css file:

<syntaxhighlight lang="css" enclose="div">
#answer11111X22X33Acomment {
display: none;
}
</syntaxhighlight>
Where 11111 is your survey ID, 22 is your group ID, 33 is your question ID and A is the answer code.

Note that you will still see columns for the hidden inputs in your data but they will be empty.

=Multiple question types in array=

''Tested with: 1.90 - 1.92+, IE 7/8/9, Firefox 13, Safari 5, Chrome 10''

'''Note: sample survey works in 2.00+ but code is different from example below. Make sure to use the right code. Copy paste the script from the sample survey adn adapt.'''

[[Media:limesurvey_survey_62584.lss|Download the sample survey]]

This workaround allows you to present multiple question types in what appears to be an array - as depicted in the image below and [http://www.partnersinc.biz/surveys//index.php?sid=62584&newtest=Y&lang=en demonstrated here] (download the sample survey - [[Media:limesurvey_survey_62584.lss|limesurvey_survey_62584.lss]]). This example uses the default template but should be adaptable to any template using divisions for question containers.

[[File:inline_questions_700x228.png]]

Basically what we do is take groups of questions (5 in this case), wrap them in a division and make them line up nicely horizontally and vertically. The width of the survey is also fixed to prevent wrapping issues. We do this with a JavaScript/jQuery function that inserts the necessary wrappers and then modifies styles so everything behaves properly. The top row is 5 boilerplate questions with the "column headers" as question text (the first just has a blank space). The following rows are a boilerplate with the "row headers" followed by 4 assorted questions.

It should be noted that using conditions on these questions may result in unexpected behavior. If a question is hidden by conditions, the question(s) to the right of it will move over to take its place.

Implementation is as follows:
#Create your questions keeping in mind how they will lay out when grouped into rows (in this example - boilerplate, yes/no, short text, numeric, dropdown, and repeat).
#In the source of the first boilerplate question add the function below (see [http://manual.limesurvey.org/wiki/Workarounds:_Manipulating_a_survey_at_runtime_using_Javascript#How_to_use_Script_.28eg._JavaScript_etc..29_in_LimeSurvey.3F How to use script]).
#Modify the number of rows, number of columns and the start placement in the function call (line 6) as required (the example uses 4 rows and 5 columns and the "array" starts with the third question on the page).

The code may look intimidating at first but it's actually fairly simple. I've laid it out as sequentially as possible and purposely used few shortcuts and many comments to make it easier to follow.

Notes:
*If you use question types other than boilerplate, short text, list dropdown, numeric or yes-no, you'll need to add to the last section of code, where it hides the question text and formats the inputs for display this way.
*Any extra questions on the page should follow this grid of questions, not precede them.

Javascript code:
<syntaxhighlight lang="javascript" enclose="div">
<script type="text/javascript" charset="utf-8">
$(document).ready(function() {
// Call the "sideBySide" function with number of rows, columns and start position
sideBySide(4, 5, 3);
});

function sideBySide(rows, columns, startQuestion) {

/*********** Display multiple questions side by side ***********/

if ($('div.qRow1').length == 0) {
var rowNum = 0;
var colNum = 1;
var rowList = new Array();

//////// Add question classes for later use ////////

// Loop through all questions and add row and column specific classes
$('div[id<div class="simplebox">="question"]').each(function(i) {
if(i >= (startQuestion-1) && rowNum < rows) { // This IF condition only needed if there are questions before or following the "inline" questions
$(this).addClass('qRow'+rowNum+'').addClass('qCol'+colNum+'').addClass('inlineQuestion');
if(rowNum == 0 && colNum > 1) {
$(this).addClass('columnLabel');
}

if(rowNum > 0 && colNum == 1) {
$(this).addClass('rowLabel');
}
else if(rowNum > 0 && colNum > 1) {
$(this).addClass('questionCell');
}

if(colNum == columns) {
rowList.push('qRow'+rowNum+'');
rowNum++;
colNum = 1;
}
else {
colNum++;
}
}
else {
$(this).addClass('normalQuestion');
}
});

//////// Survey layout manipulation ////////

// Fix the width of the survey
$('table.outerframe').css({
'width': '900px'
});

// Wrap each "row" in a wrapper div
$(rowList).each(function(i) {
$('.'+this+'').wrapAll('<div id="inlineWrapper'+i+'" class="inlineRow" />');
});

// Style the wrapper divs
$('.inlineRow').css({
'width': '850px',
'margin': '0 auto 0 auto',
'clear': 'both'
});

$( '.inlineRow:first' ).css({
'margin-top': '10px'
});

// Get all the questions to sit politely side by side
$( '.inlineQuestion' ).css({
'float': 'left',
'height':'41px',
'overflow':'hidden',
'margin-bottom': '-8px'
});
$( '.inlineQuestion .questionhelp' ).hide();
$( '.inlineQuestion .survey-question-help' ).parent().hide();

// A little space under the last row
$( '.inlineRow:last .inlineQuestion' ).css({
'margin-bottom': '10px'
});

// Any questions not displayed inline (this is only needed if there are questions following the "inline" questions)
$( '.normalQuestion' ).css({
'clear': 'both'
});

//////// Column manipulation ////////

// Set the column widths - can be set individually if necessary
// Must add up to less than 100%
$( '.qCol1' ).css({
'width': '12%'
});

$( '.qCol2, .qCol3, .qCol4, .qCol5' ).css({
'width': '22%'
});

//////// Question manipulation ////////

// Hide the answer element in boilerplate questions
$( 'div.boilerplate td.answer' ).parent().hide();

// Hide the question text elements in non-boilerplate questions
$('div.questionCell td.questiontext').parent().hide();

// Push the question tables to 100%
$( 'div.inlineRow table' ).css({
'width': '100%'
});

// Get everything to line up nicely vertically
$( '.inlineQuestion td.questiontext, .inlineQuestion td.answer p' ).css({
'text-align': 'center'
});

// Adjust cell heights so everything lines up nicely horizontally
$( '.inlineQuestion td.answer, .inlineQuestion td.questiontext' ).css({
'height':'35px',
'overflow':'hidden',
'padding':'0.5em'
});
$( '#inlineWrapper0 .inlineQuestion' ).css({ 'height':'50px' });
$( '#inlineWrapper0 td.questiontext' ).css({
'height':'50px'
});

// Yes-no question styles
$( 'div.yes-no ul' ).css({
'text-align': 'center',
'font-size': '90%',
'margin': '0',
'padding-bottom': '5px'
});
$( 'div.yes-no li' ).css({
'padding-right': '1.5em'
});
$( 'div.yes-no td.answer' ).css({
'padding-bottom': '0'
});

// Short-text question styles
$( 'div.text-short input' ).css({
'width': '125px',
'margin-left': '0'
});

// Numeric question styles
$( 'div.numeric input' ).css({
'width': '125px',
'margin-left': '0'
});
$( 'div.numeric p.tip' ).css({
'display': 'none'
});

// Get rid of the margins around select boxes
$( 'p.question' ).css({ 'margin':'0' });
}
}
</script>
</syntaxhighlight>
<br /><br />

=Star Rating System=

''Tested with: 1.85+ (7557), IE 6/7, FireFox 3.0, Safari 3.2,''

This workaround uses the [http://www.fyneworks.com/jquery/star-rating/ jQuery Star Rating Plugin] to display a series of stars that are used to generate a rating value. This value is then passed to either a hidden numeric input question or a hidden list radio question. Both methods are outlined below - use one or both depending on whether you want to use [Assessments|assessments].

The plugin uses a series of radio inputs to generate the stars (more about these below). It allows the use of whole or partial stars as shown in [http://www.partnersinc.biz/surveys//index.php?sid=47586&newtest=Y&lang=en this demo] and the image below.

[[File:star_rating_700x324.png]]

==Star Rating System Using Numeric Input Question==

Use this method if you would like your rating data to be collected as a numeric value and don't want to use [[Assessments|LimeSurvey assessments]] - it's a little easier to implement. There is a demo [http://www.partnersinc.biz/surveys//index.php?sid=47586&newtest=Y&lang=en here] (first question).

'''Implementation is as follows:'''
#Turn off ''$filterxsshtml'' to allow insertion of JavaScript in the questions. (See [[Optional settings#Security|documentation here]])
#[http://www.fyneworks.com/jquery/star-rating/ Download the plugin] and place the following included files in your template folder:
##jquery.MetaData.js
##jquery.rating.css
##jquery.rating.js
##delete.gif
##star.gif
#In the <head> section of your startpage.pstpl, add the following code to link to the files.

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" src="{TEMPLATEURL}jquery.rating.js" charset="utf-8"></script>

<script type="text/javascript" src="{TEMPLATEURL}jquery.MetaData.js" charset="utf-8"></script>

<link rel="stylesheet" type="text/css" href="{TEMPLATEURL}jquery.rating.css" />

</syntaxhighlight>

5. Create a numeric input question and then in the source of the question add as many radio inputs as star segments. For example, if you would like 5 stars, each with half-segments (as in the demo Q1), you would need 10 radio inputs and that would give rating values from 1-10.

Don't confuse these inputs with the actual question, they are just for the plugin's use.

At this point your question source code should look something like below. Make sure that all inputs have the same name. Each input must have the same title as value and these must be sequential. Don't worry about how all of this looks in the WSYSWYG editor - the plugin is going to hide these inputs and replace them with stars.

<syntaxhighlight lang="php" enclose="div">

Q1 - Some question text here.<br /><br />

<div id="starContainer">

<input type="radio" class="star { split:2 }" title="1" value="1" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="2" value="2" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="3" value="3" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="4" value="4" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="5" value="5" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="6" value="6" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="7" value="7" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="8" value="8" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="9" value="9" name="q1Rate" />

<input type="radio" class="star { split:2 }" title="10" value="10" name="q1Rate" />

</div>

</syntaxhighlight>

6. A note on split stars. The stars in the above example are split in half by the ''{ split:2 }'' metadata. So if you don't want split stars, your inputs would look like:

'''<input type="radio" class="star" title="1" value="1" name="q1Rate" />'''

And stars split into third-segments would look like:

'''<input type="radio" class="star { split:3 }" title="1" value="1" name="q1Rate" />'''

7. Finally, in the source of the question add the following function after your inputs. (See [[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|How to use script here]])

Some notes on the code:
*Replace "SSSSS", "GG", "QQ" in the function call at the end with the survey ID, group ID and question ID respectively.
*The code will hide the numeric input and pass the rating values into it as they are changed. If the rating is canceled the numeric input is nullified. If a respondent navigates away from the page then returns the code "remembers" the previous rating and displays the stars accordingly.
*If you want to apply it to more numeric questions on the same page simply add more calls with the appropriate IDs. (eg. handleRatingNumeric(11111, 22, 1); handleRatingNumeric(11111, 22, 2); ...) .

Code:

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" charset="utf-8">

$(document).ready(function() {

function handleRatingNumeric (sID, gID, qID) {

// Hide the numeric input

$('#question' + qID + ' td.answer').parent().hide();

// Get a previous rating (if any) and use it to initialize the star display

var rating = $('#answer' + sID + 'X' + gID + 'X' + qID + '').val();

if ( rating != '' ) {

$('#question' + qID + ' input.star').rating('select', rating);

}

// Listener on the star rating cancel element

$('#question' + qID + ' div.rating-cancel').click(function(event) {

// Nullify the rating if the Cancel element is clicked

rating = '';

$('#answer' + sID + 'X' + gID + 'X' + qID + '').val(rating);

});

// Listener on the star rating elements

$('#question' + qID + ' div.star-rating').click(function(event) {

// Find the value of the highest clicked star and pass it into the text input

$('#question' + qID + ' div.star-rating-on').each(function(i) {

rating = $(this).children('a').html( );

});

$('#answer' + sID + 'X' + gID + 'X' + qID + '').val(rating);

});

}

// Call the function for the numeric question

handleRatingNumeric (SSSSS, GG, QQ);

});

</script>

</syntaxhighlight>

==Star Rating System Using List (Radio) Question==

Use this method if you would like to use [[Assessments|assessments]]. There is a demo [http://www.partnersinc.biz/surveys//index.php?sid=47586&newtest=Y&lang=en here] (second question).

'''Implementation is as follows:'''

1. Turn off ''$filterxsshtml'' to allow insertion of JavaScript in the questions. (See [[Optional settings#Security|documentation here]])

2. Set up the template to use custom onload functions. (See the [[Workarounds: Manipulating a survey at runtime using Javascript#Custom onload function|workaround here]])

3. [http://www.fyneworks.com/jquery/star-rating/ Download the plugin] and place the following included files in your template folder:
*jquery.MetaData.js
*jquery.rating.css
*jquery.rating.js
*delete.gif
*star.gif

4. In the <head> section of your startpage.pstpl, add the following code to link to the files.

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" src="{TEMPLATEURL}jquery.rating.js" charset="utf-8"></script>

<script type="text/javascript" src="{TEMPLATEURL}jquery.MetaData.js" charset="utf-8"></script>

<link rel="stylesheet" type="text/css" href="{TEMPLATEURL}jquery.rating.css" />

</syntaxhighlight>

5. Create a list (radio) question with the same amount of sequentially numbered answers as star ratings. For example, if you want 5 whole-stars, you would create 5 answers, as in the image below, and this would give you ratings from 1-5. Note that the "Codes" and "Answers" must be sequential numbers.

[[File:star_rating_700x156_v2.png]]

6. In the list (radio) question, set the [[Advanced question settings|hide_tip]] question attribute to 1

7. In the source of the question add as many radio inputs as star segments. So 5 whole-stars (as in the demo Q2), would need 5 radio inputs.

Don't confuse these inputs with the actual question, they are just for the plugin's use.

At this point your question source code should look something like below. Make sure that all inputs have the same name. Each input must have the same title as value and these must be sequential. Don't worry about how all of this looks in the WSYSWYG editor - the plugin is going to hide these inputs and replace them with stars.

<syntaxhighlight lang="php" enclose="div">

Q2 - Some question text here.<br /><br />

<div id="starContainer">

<input type="radio" class="star" title="1" value="1" name="q2Rate" />

<input type="radio" class="star" title="2" value="2" name="q2Rate" />

<input type="radio" class="star" title="3" value="3" name="q2Rate" />

<input type="radio" class="star" title="4" value="4" name="q2Rate" />

<input type="radio" class="star" title="5" value="5" name="q2Rate" />

</div>

</syntaxhighlight>

8. A note on split stars. The stars in the above example are whole-stars. If you want them split you need to add metadata to the class - something like ''{ split:2 }''. So if you want half-stars your inputs would look like:

'''<input type="radio" class="star { split:2 }" title="1" value="1" name="q1Rate" />'''

And stars split into third-segments would look like:

'''<input type="radio" class="star { split:3 }" title="1" value="1" name="q1Rate" />'''

9. Finally, in the source of the question add the following function after your inputs. (See [http://docs.limesurvey.org/tiki-index.php?page=Workarounds&structure;=English+Instructions+for+LimeSurvey#How_to_use_Script_eg._JavaScript_etc._ How to use script here])

Some notes on the code:
*Replace "SSSSS", "GG", "QQ" in the function call at the end with the survey ID, group ID and question ID respectively.
*The code will hide the question radio buttons and toggle them as the rating values are changed. If the rating is canceled all question inputs are unchecked. If a respondent navigates away from the page then returns the code "remembers" the previous rating and displays the stars accordingly.
*If you want to apply it to more numeric questions on the same page simply add more calls with the appropriate IDs. (eg. handleRatingRadio(11111, 22, 1); handleRatingRadio(11111, 22, 2); ...) .

Onload code:

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" charset="utf-8">

$(document).ready(function() {

function handleRatingRadio (sID, gID, qID) {

// Hide the radio input

$('#question' + qID + ' td.answer').parent().hide();

// Get a previous rating (if any) and use it to initialize the star display

var rating = $('#question' + qID + ' input.radio[checked=true]').attr('value');

//if ( rating != '' ) {

if ( rating ) {

$('#question' + qID + ' input.star').rating('select', rating);

}

// Listener on the star rating cancel element

$('#question' + qID + ' div.rating-cancel').click(function(event) {

// Nullify the rating if the Cancel element is clicked

rating = '';

$('#question' + qID + ' input.radio').attr('checked', false);

});

// Listener on the star rating elements

$('#question' + qID + ' div.star-rating').click(function(event) {

// Find the value of the highest clicked star and pass it into the text input

$('#question' + qID + ' div.star-rating-on').each(function(i) {

rating = $(this).children('a').html( );

});

$('#question' + qID + ' input.radio[value=' + rating + ']').attr('checked', true);

});

}

// Call the function for the radio question

handleRatingRadio (SSSSS, GG, QQ);

});

</script></syntaxhighlight>

=Variable column widths in array=

''Tested with: 1.85+ (7557), IE 6/7, Firefox 3.0, Safari 3.2''

This workaround allows you to define all column widths of an array question - as shown in the image below and [http://www.partnersinc.biz/surveys//index.php?sid=26842&newtest=Y&lang=en demonstrated here]. This example uses the default template shipped with 7557 but should be adaptable to any template.

[[File:array_widths_701x226.gif]]

We use a function to remove all of the widths imposed by the core code and then insert our own.

'''Implementation is as follows:'''
#Turn off ''$filterxsshtml'' to allow insertion of JavaScript in the questions (see [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings&structure;=English+Instructions+for+LimeSurvey#Filtering_dangerous_HTML_tags_in_survey_objects documentation here]).
#Create the array question.
#In the source of the array question add the following script (see [[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|How to use script here]]).
#Replace all instances of QQ with the question ID.
#In the third section of code, adjust the widths and add/remove columns as necessary. This example is for an array with a question text column followed by 3 answer columns as shown above.
#In the final section adjust the question text alignment to your liking

Onload code

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" charset="utf-8">

$(document).ready(function() {

// Get rid of all the widths that the API imposes

$( 'div#questionQQ table.question col' ).attr('width', '');

$( 'div#questionQQ table.question thead td' ).attr('width', '');

// Define a width for the question table so we can do so for its children

// NOTE: Keep this to 95% or less so IE will behave

$( 'div#questionQQ table.question' ).attr('width', '95%');

// Define the column widths

// Add or remove columns and adjust widths as necessary but widths should add up to 100%

// NOTE: Columns must be sequentially numbered starting at 0 - eg, td:eq(0), td:eq(1), td:eq(2).....

$( 'div#questionQQ table.question tbody th:eq(0)' ).css({ 'width':'10%' }); // Answer text column

$( 'div#questionQQ table.question tbody td:eq(0)' ).css({ 'width':'50%' }); // First answer column

$( 'div#questionQQ table.question tbody td:eq(1)' ).css({ 'width':'20%' }); // Second answer column

$( 'div#questionQQ table.question tbody td:eq(2)' ).css({ 'width':'20%' }); // Third answer column

// Push the text input widths to 95% of their parent containers

$( 'div#questionQQ table.question input[type="text"]' ).css({ 'width':'95%' });

// Align the answer text - feel free to experiment

$( 'div#questionQQ table.question tbody th' ).css({'text-align':'center'});

});

</script></syntaxhighlight>

=Use images for radio buttons and checkboxes=

''Tested with: LimeSurvey 1.92/2.0, using IE 9, FireFox 13, Chrome 16, Safari 5''

This workaround uses an adaptation of the jQuery imagetick.js plugin to replace the default radio buttons and checkboxes with images as pictured below:

[[File:images.png]]

This adaptation will work in the following question types:
*Array
*Array by column
*Array dual scale
*Array (5 point choice)
*Array (10 point choice)
*Array (Increase-Same-Decrease)
*Array (Yes-No-Uncertain)
*Gender
*Yes-No
*Multiple choice
*Multiple choice with comments
*5 point choice
*List (Radio)
*List with comment

==LimeSurvey 1.92 and earlier implementation==
#[[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|Set up your survey to use JavaScript]].
#Download [[Media:imagetick_lime_v1.3.zip|this modified version of the plugin]].
#Extract all files and place them in your template directory.
#Add the following line to the <head> element in your startpage.pstpl '''BEFORE''' the call for template.js:<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" src="{TEMPLATEURL}imagetick_lime.js"></script></syntaxhighlight>
#Add the following to the source of a question or the group description<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" charset="utf-8">

$(document).ready(function(){

var templatePath = $('head link[href*="template.css"]').attr('href').replace(/template.css/, '');

// Apply images to radios

$('input[type="radio"]').imageTick({

// Image to use as a selected state of the radio

tick_image_path: templatePath+"radio.gif",

// Image to use as a non-selected state

no_tick_image_path: templatePath+"no_radio.gif",

// Class to apply to all radio images that are dynamically created

image_tick_class: "radios"

});

// Apply images to checkboxes

$('input[type="checkbox"]').imageTick({

// Image to use as a selected state of the checkbox

tick_image_path: templatePath+"check.gif",

// Image to use as a non-selected state

no_tick_image_path: templatePath+"no_check.gif",

// Class to apply to all checkbox images that are dynamically created

image_tick_class: "checkboxes"

});

});

</script></syntaxhighlight>

You can also call the imagetick function from template.js. Skip the last step above and add the following to the end of template.js. Replace "yourTemplateName" with your template directory name.<syntaxhighlight lang="php" enclose="div">$(document).ready(function(){

var templatePath = $('head link[href*="template.css"]').attr('href').replace(/template.css/, '');

// Apply images to radios

$('input[type="radio"]').imageTick({

// Image to use as a selected state of the radio

tick_image_path: templatePath+"radio.gif",

// Image to use as a non-selected state

no_tick_image_path: templatePath+"no_radio.gif",

// Class to apply to all radio images that are dynamically created

image_tick_class: "radios"

});

// Apply images to checkboxes

$('input[type="checkbox"]').imageTick({

// Image to use as a selected state of the checkbox

tick_image_path: templatePath+"check.gif",

// Image to use as a non-selected state

no_tick_image_path: templatePath+"no_check.gif",

// Class to apply to all checkbox images that are dynamically created

image_tick_class: "checkboxes"

});

}); </syntaxhighlight>

If you want to apply it to only one question on a page use selector (where QQ is the question ID)<syntaxhighlight lang="php" enclose="div">$('#questionQQ input[type="radio"]')</syntaxhighlight>

If you want to apply it to a single radio button in a question (to maybe have different images for each option) use selector (where SSSSS is the survey ID, GG is the group ID, QQ is the question ID, AA is the answer code)<syntaxhighlight lang="php" enclose="div">$("input#answerSSSSSXGGXQQAA")</syntaxhighlight>

==LimeSurvey 2.0 and later implementation==

Follow the instructions above with these changes:
#Download [[Media:imagetick_lime_v2.zip|this modified version of the plugin for 2.0 and up]] instead of the one mentioned above and add all contained files to your template directory.
#Add these lines to the <head> element in your startpage.pstpl instead of the one above:<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" src="{TEMPLATEURL}imagetick_lime_2.js"></script>

<link rel="stylesheet" type="text/css" href="{TEMPLATEURL}imagetick_lime_2.css" /></syntaxhighlight>

Thanks to Jordan Boesch for the original plugin.

=Changing the position an layout of an individual question using "question code"=

''Tested with: 1.87+ (6536)''

To use this very flexible workaround you first have to apply a minor change to the question.pstpl of the used template.

<syntaxhighlight lang="php" enclose="div">

<div class="survey-question">

<div class="survey-question-text">

</syntaxhighlight>

needs to be changed to

<syntaxhighlight lang="php" enclose="div">

<div class="survey-question" id="{QUESTION_CODE}">

<div class="survey-question-text" id="{QUESTION_CODE}" >

</syntaxhighlight>

this change won't change anything in the layout and can be left in the template even if you don't need this workaround. It's just a means to have a handle to actually change individual questions.

You can then use a code such as the following in the question text to make question specific format changes. "SAMPLE" needs to be replaced with the concerning question code and javascript has to be allowed ([[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|older versions of limesurvey]], under global settings for newer versions).

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" charset="utf-8">

document.getElementById('SAMPLE').style.borderTop= "0px";

document.getElementById('SAMPLE').style.marginTop= "-62px";

document.getElementById('SAMPLE').style.marginLeft= "30px";

</script>

</syntaxhighlight>

This sample code will hide the border at the top of the question, will move the whole question up by 62px and to the right by 30px. Using this workaround you can change a whole a lot of things concerning format and positions of a specific question without changing all the questions. A (German) list of all the allowed options can be found [http://de.selfhtml.org/javascript/objekte/style.htm#style_eigenschaften here].

=Create MaxDiff question type=

''Tested with: 1.87+ (8518), IE 6/7/8, Firefox 3.6, Safari 3.2''

This workaround uses JavaScript to convert an '''''Array (flexible labels) by column''''' question into a [http://en.wikipedia.org/wiki/MaxDiff MaxDiff] question type.

[[File:max_diff_596x253.gif]]

There is a demo [http://www.partnersinc.biz/surveys//index.php?sid=29191&newtest=Y&lang=en here] and implementation is as follows.
#[[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|Set up your survey to use JavaScript]].
#Create an '''''Array (flexible labels) by column''''' question with 2 "answers" - these will be the left and right columns.
#Assign a label set to the question - these will be the labels in the center column.
#Place the following script in the source of the question or in the group description.
#In line 5, replace "QQ" with the ID of the question and modify the message to your needs.
#Adjust the styles in lines 15-18 as required.

The script moves the question columns into the MaxDiff configuration and alerts the user if they select the same option for both max and min columns.

<syntaxhighlight lang="php" enclose="div">

<script type="text/javascript" charset="utf-8">

$(document).ready(function(){

maxDiff(QQ, 'You cannot select this answer twice.');

function maxDiff(qID, msg) {

// Move the cells around

$('#question'+qID+' table.question col:eq(1)').prependTo('colgroup.col-responses');

$('#question'+qID+' table.question thead tr:eq(0) th:eq(0)').prependTo('#question'+qID+' table.question thead tr:eq(0)');

$('#question'+qID+' table.question tbody tr').each(function(i){

$('td:eq(0)', this).prependTo(this);

});

// Style stuff

$('#question'+qID+' table.question col.odd').css({ 'background-color':'transparent' });

$('#question'+qID+' table.question tbody th').css({ 'text-align':'center' });

$('#question'+qID+' table.question tbody tr:even td, #question'+qID+' table.question tbody tr:even th').css({ 'background-color':'#F1F1F1' });

$('#question'+qID+' table.question tbody tr:odd td, #question'+qID+' table.question tbody tr:odd th').css({ 'background-color':'#FCFCFC' });

// Prevent clicking twice in the same row

$('#question'+qID+' input.radio').mousedown(function () {

var clickRow = $(this).parents('tr:eq(0)');

if ($('input.radio:checked', clickRow).length > 0) {

alert (msg);

return false;

}

});

$('#question'+qID+' table.question tbody td').mousedown(function () {

var clickRow = $(this).parents('tr:eq(0)');

if ($('input.radio:checked', clickRow).length > 0) {

alert (msg);

return false;

}

});

}

});

</script>

</syntaxhighlight>

=Load SVG Code From Drawing Tool=

This workaround uses JavaScript/jQuery to load a drawing tool and store the results in a huge-text question. The details are outlined in the [[Workarounds: Manipulating a survey at runtime using Javascript#Load SVG Code From Drawing Tool|JavaScript section of the workarounds]].

=Minimum or Maximum Date in Datepicker=

''Tested with: 1.90, IE 7/8, Firefox 3.6, Safari 3.2''

'''Please note: From version 2.05 beta6, you can set the minimum and maximum date for the date picker directly in the advanced question attributes of the date/time question.'''

You can set the minimum or maximum selectible date in a datepicker as follows

[[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|Set up your survey to use JavaScript]] and add the following to the source of the date question text or help. Replace "QQ" with the date question ID.

For a minimum date of April 15, 2010:<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" charset="utf-8">

$(document).ready(function() {

var qID = QQ;

$('#question'+qID+' .popupdate').datepicker( 'option', 'minDate', new Date(2010, 4-1, 15) );

});

</script>

</syntaxhighlight>

For a minimum date of the current date (today):<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" charset="utf-8">

$(document).ready(function() {

var qID = QQ;

$('#question'+qID+' .popupdate').datepicker( 'option', 'minDate', new Date() );

});

</script>

</syntaxhighlight>

For a maximum date of May 10, 2015:<syntaxhighlight lang="php" enclose="div"><script type="text/javascript" charset="utf-8">

$(document).ready(function() {

var qID = QQ;

$('#question'+qID+' .popupdate').datepicker( 'option', 'maxDate', new Date(2015, 5-1, 10) );

});

</script>

</syntaxhighlight>

More details here - http://jqueryui.com/demos/datepicker/#option-minDate

=Evaluative Space Grid (ESG)=

''Tested with: 1.91, IE 7/8, Firefox 3.6, Safari 3.2''

The evaluative space grid (ESG) is a two-dimensional grid that provides a single-item measure of positivity and negativity (Larsen et al, 2009). See [http://leeds-faculty.colorado.edu/mcgrawp/pdf/larsen.norris.mcgraw.hawkley.cacioppo.2009.pdf page 4 of this PDF].

This can be accomplished using a multiple-numeric question, some simple HTML and a little JavaScript.

A table can be shown in the question. When a respondent clicks a grid cell in the table JavaScript loads the coordinates of the cell into the multiple-numeric question inputs.

[[File:space_grid.png]]<br /><br />
#Create a Multiple Numeric question with two sub-questions labelled "X" and "Y".
#Add the following HTML to the source of the question to create the table:<syntaxhighlight lang="html4strict" enclose="div">
<table class="spaceGrid">
<tr>
<td rowspan="5" class="yAxisLabel">How NEGATIVE<br>
do you feel about<br>
the stimulus?</td>
<td class="yLabel">Extremely</td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
</tr>
<tr>
<td class="yLabel">Quite a bit</td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
</tr>
<tr>
<td class="yLabel">Moderately</td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
</tr>
<tr>
<td class="yLabel">Slightly</td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
</tr>
<tr>
<td class="yLabel">Not at all</td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
<td class="gridCell"></td>
</tr>
<tr>
<td class="blankCell"></td>
<td class="blankCell"></td>
<td class="xLabel">Not at all</td>
<td class="xLabel"><span class="yLabel">Slightly</span></td>
<td class="xLabel"><span class="yLabel">Moderately</span></td>
<td class="xLabel"><span class="yLabel">Quite a bit</span></td>
<td class="xLabel"><span class="yLabel">Extremely</span></td>
</tr>
<tr>
<td class="blankCell"></td>
<td class="blankCell"></td>
<td colspan="5" class="xAxisLabel">How POSITIVE do you feel about the stimulus?</td>
</tr>
</table>
</syntaxhighlight><br /><br />
#Add the following styles to the end of your template.css file:<syntaxhighlight lang="css" enclose="div">
.spaceGrid {
border: 0 none;
border-collapse: collapse;
}

.spaceGrid td {
padding: 0 3px;
text-align: center !important;
border: 0 none;
}

td.xAxisLabel {
padding-top: 10px;
}

td.yAxisLabel {
padding-right: 10px;
width: 125px;
}

td.xLabel {
height: 20px;
font-weight: normal;
}

td.yLabel {
text-align: right !important;
font-weight: normal;
}

td.gridCell {
width: 70px;
height: 70px;
border: 1px solid #666666;
background-color: #FFFFFF;
cursor: pointer;
}

td.checkedCell {
background-color: #66FF00;
}
</syntaxhighlight><br /><br />
#Add the following to the end of your template.js file:<syntaxhighlight lang="javascript" enclose="div">
$(document).ready(function() {

// Listener on the grid cells
$('.gridCell').click(function(){

// Define some vars
var parentQ = $(this).parents('div[id</div>="question"]:eq(0)');
var parentTable = $(this).parents('table.spaceGrid:eq(0)');
var parentRow = $(this).parent();
var numGridCell = $('.gridCell').length;
var numCols = $('.gridCell', parentRow).length;
var numRows = numGridCell/numCols;

// Add class to checked cell
$('.checkedCell', parentQ).removeClass('checkedCell');
$(this).addClass('checkedCell');

// Find the cell coordinates
var reverseRowIndex = (numRows - $('tr', parentTable).index($(parentRow)));
var colIndex = $('.gridCell', parentRow).index($(this)) + 1;

// Load coordinates into inputs
$('input.text:eq(0)', parentQ).val(colIndex);
$('input.text:eq(1)', parentQ).val(reverseRowIndex);
});

});
</syntaxhighlight><br /><br />
The script should automatically handle different grid sizes.

=Slider Highlighting=

''Tested with: 1.91, IE 7/8, Firefox 3.6, Safari 3.2''

You may want to highlight a slider after it has been moved/changed to allow respondents to easily see which slider sub-questions have been answered.

[[File:Capture.PNG]]<br /><br />
#Add the following to the end of '''template.js''':<syntaxhighlight lang="javascript" enclose="div">
$('html').bind('slidecreate', function(event, ui) {
$('.slider_callout').each(function(i){
if($(this).text().length > 0) {
$(this).parents('li:eq(0)').addClass('changedSlider');
}
});
});

$(document).ready(function() {
$('.ui-slider-horizontal').bind('slidechange', function(event, ui) {
$(this).parents('li:eq(0)').addClass('changedSlider');
});
});
</syntaxhighlight><br /><br />
#Add something like the following to the end of '''template.css''' (these styles are for the default template and would need to be modified for other templates):<syntaxhighlight lang="css" enclose="div">
.numeric-multi .answer li {
border-bottom: 5px solid #FFFFFF;
}

.numeric-multi .answer li label {
background-color: #FFFFFF;
}

.numeric-multi .answer li div.multinum-slider {
margin: 1.5em 0.5em 0.2em 0;
padding-left: 0.5em;
}

.ui-slider-1 {
margin-bottom: 10px;
}

.changedSlider {
background-color: #99FFFF;
}
</syntaxhighlight>
<br /><br />

=Sliders in Array-Numbers or Array-Dual-Scale-Numbers=

''Tested with: 1.91, IE 7/8/9, Firefox 3/7, Safari 5, Chrome 15''

This workaround will replace the dropdowns in '''''array-numbers''''' or '''''array-dual-scale-numbers''''' questions with sliders. The sliders will automatically have the same minimum, maximum and steps that you set in the advanced question settings.

[[File:custom_sliders_1.png]]<br /><br />
There is a [http://www.partnersinc.biz/surveys//index.php?sid=66653&newtest=Y&lang=en '''demo here'''].<br /><br />
#[[Workarounds: Manipulating a survey at runtime using Javascript#How to use Script (eg. JavaScript etc.) in LimeSurvey?|Set up your survey to use JavaScript]].
#Create your array-numbers or array-dual-scale-numbers question.
#Add the following to the source of the question. Replace "QQ" with the array question ID. (NOTE: In 1.92 or newer, you can replace "QQ" with "{QID}")<syntaxhighlight lang="javascript" enclose="div">
<script type="text/javascript" charset="utf-8">

$(document).ready(function() {

insertSlider (QQ);

function insertSlider (qID) {

$('#question'+qID+' select').each(function(i, el){

// Hide the dropdown
$(el).hide();

var id = $(el).attr('id').replace(/#/g,'-');

// Some dropdown values
var currentVal = Number($('option:selected', el).val());
var firstVal = Number($('option[value!=""]:first', el).val());
var secondVal = Number($('option[value!=""]:first', el).next('option').val());
var lastVal = Number($('option[value!=""]:last', el).val());

// Insert a container for the slider
var container = $('<div class="customSliderWrapper"></div>').insertAfter(el);

// Insert a callout
var callout = $('<div id="callOut-'+id+'" class="customCallout"></div>').appendTo(container).text($('option:selected', el).val());

// Initiate the slider
var slider = $('<div id="slider-'+id+'" class="customSlider"></div>').appendTo(container).slider({
min: firstVal,
max: lastVal,
range: 'min',
value: currentVal,
step: secondVal - firstVal,
slide: function( event, ui ) {
$('option[value="'+ui.value+'"]', el).attr('selected', 'selected');
function updateCustomCallout() {
$('#callOut-'+id).text($('option:selected', el).val()).css({ 'left': $('#slider-'+id+' .ui-slider-handle').css('left') });
}
// Delay updating the callout because it was picking up the last postion of the slider
setTimeout(updateCustomCallout, 10);
}
});

// Change the slider if the dropdown is changed
// (not required if dropdown is hidden)
$(el).change(function() {
slider.slider('value', Number($('option:selected', el).val()));
$('#callOut-'+id).text($('option:selected', el).val());
});

// Set a value as soon as the slider handle is clicked
$('#slider-'+id+' .ui-slider-handle').mousedown(function() {
$('option[value="'+slider.slider('value')+'"]', el).attr('selected', 'selected');
$('#callOut-'+id).text(slider.slider('value'));
});
});
}
});
</script></syntaxhighlight><br /><br />
#Add something like the following to the end of '''template.css''' (these styles are for the default template and may need to be modified for other templates):<syntaxhighlight lang="css" enclose="div">
table.innerframe {
width:850px;
}

.array-multi-flexi table.question {
width:90%;
}

.customCallout {
position: absolute;
top: 0;
left: 0;
width: 50px;
height: 1.75em;
text-align: left;
font-weight: bold;
margin: 0 0 0 -0.3em;
}

.customSliderWrapper {
position: relative;
margin: 0 10px;
padding-top: 1.75em;
}
</syntaxhighlight>
<br /><br />

=Vertical Sliders=

''Tested with: 1.92+, 2.00+, IE 9, Firefox 13, Chrome 19''

This workaround uses a custom jQuery plugin to apply vertical sliders to multiple-numeric questions. You can download a sample template here (with the plugin in template.js) - [[Media:default_vertical_sliders.zip|vertical slider template]] - and a sample survey here - [[Media:demo_vertical_sliders.lss|vertical slider survey]].

[[File:verticalsliders_1.jpg]]<br /><br />
# Create your multi-numeric question(s). Do NOT use any of the slider advanced settings.<br /><br />
#Add the following to the end of template.js. Replace "QQ" (line 5) with the question ID and adjust the options in the function call as desired. Repeat the call as many times as you need for more questions<syntaxhighlight lang="javascript" enclose="div">$(document).ready(function(){

// Call the vertical slider plugin with the question ID
// Edit options here as desired
$('#questionQQ').lsVerticalSlider({
minValue :0, // Minimum value (default 0)
maxValue :200, // Maximum value (default 100)
startValue :100, // Start value (default null)
step :10, // Slider increments (default 1)
height :100, // Height of slider in pixels (default 200)
recordStart :true, // Record the start value? (default no)
showMin :true, // Show minimum value? (default no)
showMax :true // Show maximum value? (default no)
});
});

// NO EDITING REQUIRED BELOW HERE
// A jQuery plugin to convert multiple-numeric questions to vertical sliders
(function( $ ){
$.fn.lsVerticalSlider = function(options) {

// The defaults, extended and modified with any passed in the function call
var opts = $.extend( {
minValue :0,
maxValue :100,
startValue :'',
step :1,
height :150,
recordStart :false,
showMin :false,
showMax :false
}, options);

return this.each(function() {

var $this = $(this);

// Some classes for the question and sub-questions
$this.addClass('vertical-slider-question');
$('li:[id<div class="simplebox">="javatbd"]', $this).addClass('vertical-slider-sub-question');

// Loop through the sub-questions
$('li:[id</div>="javatbd"]', $this).each(function(i){
var itemID = $(this).attr('id').replace(/javatbd/, '');

// Check for pre-existing answer
if($('#answer'+itemID).val() != '') {
opts.startValue = $('#answer'+itemID).val();
}

// Insert the slider elements
$('#answer'+itemID).after(
'<div class="vertical-slider-max-min" style="height:'+(opts.height+2)+'px;"> \
<div class="vertical-slider-max"></div> \
<div class="vertical-slider-min"></div> \
</div> \
<div id="vertical-slider-'+itemID+'" class="vertical-slider" style="height:'+opts.height+'px;"></div> \
<div class="vertical-slider-callout-wrapper" style="height:'+(opts.height+2)+'px;"> \
<div class="vertical-slider-callout" id="slider-callout-'+itemID+'"></div> \
</div>'
);

// Show min/max if option is set
if(opts.showMax) {
$('.vertical-slider-max', $this).text(opts.maxValue);
}

if(opts.showMin) {
$('.vertical-slider-min', $this).text(opts.minValue);
}

// Initiate the slider
$('#vertical-slider-'+itemID).slider({
orientation: 'vertical',
range: 'min',
min: opts.minValue,
max: opts.maxValue,
value: opts.startValue,
step: opts.step,
slide: function(event, ui) {
$('#answer'+itemID).val(ui.value);
$('#slider-callout-'+itemID).text(ui.value);
setTimeout(function() {
$('#slider-callout-'+itemID).css({ 'bottom':$('#vertical-slider-'+itemID+' .ui-slider-handle').css('bottom') }).show();
}, 10);
},
create: function(event, ui) {
// Initial values and positions
if($('#answer'+itemID).val() != '') { // Pre-existing answer
$('#slider-callout-'+itemID).text(opts.startValue);
}
else if(opts.recordStart) { // Record the start value (if option is set)
$('#answer'+itemID).val(opts.startValue);
$('#slider-callout-'+itemID).text(opts.startValue);
}
else {
$('#slider-callout-'+itemID).hide();
}
$('#slider-callout-'+itemID).css({ 'bottom':$('#vertical-slider-'+itemID+' .ui-slider-handle').css('bottom') });
}
});
});
});
};
})( jQuery );</syntaxhighlight><br /><br />
#Add the following to the end of template.css (these styles are for the default template):<syntaxhighlight lang="css" enclose="div">/* Vertical slider styles and overrides */
.vertical-slider-question p.tip {
display: none;
}

.vertical-slider-sub-question {
float: left;
margin: 0 3em 0 0 !important;
}

.vertical-slider-question label {
display: block;
padding: 0 0 0.75em 0 !important;
}

.vertical-slider-question span.input {
padding: 0.3em 0 0 0;
display: block;
}

.vertical-slider-question input.text {
display: none;
}

.vertical-slider {
float: left;
border-radius: 4px;
}

.vertical-slider-question .ui-slider-handle {
top: auto;
border-radius: 4px;
}

.vertical-slider-max-min,
.vertical-slider-callout-wrapper {
float: left;
position: relative;
}

.vertical-slider-callout-wrapper {
min-width: 3em;
}

.vertical-slider-max-min {
margin-right: 0.5em;
}

.vertical-slider-max,
.vertical-slider-min {
font-size: 0.8em;
color:#666666;
line-height: 1;
}

.vertical-slider-max {
margin-top: -0.5em;
}

.vertical-slider-min {
position: absolute;
right: 0;
bottom: 0;
margin-bottom: -0.5em;
}

.vertical-slider-callout {
position: absolute;
top: auto;
margin: 0 0 -0.6em 0.5em;
padding: 0.1em;
font-size: 0.9em;
color:#000000;
line-height: 1;
background: #F8F8FF;
border: 1px solid #D2E0F2;
border-radius: 4px;
}</syntaxhighlight>
<br /><br />

=Range Slider=

''Tested with: 1.92+, 2.00+, IE 9, Firefox 13, Chrome 19''

This workaround uses a custom jQuery plugin to insert a jQuery UI range slider into a multi-numeric question and automatically populate that question's inputs with the range min and max values. You can download a sample template here - [[Media:Demo_Range_Slider.zip|range slider template]] - and a sample survey here - [[Media:Limesurvey_survey_range_slider.lss|range slider survey]].

[[File:Range_slider.jpg]]<br /><br />
The plugin handles:
*previous answers
*slider max/min
*range min start
*range max start
*range span min
*slider step
*slider width
*record the start values
*show slider max and min<br /><br />
Requirements:
*LimeSurvey 1.92 or newer
*A multiple-numeric question with two sub-questions<br /><br />
# Create your multi-numeric question. Do NOT use any of the slider advanced settings.<br /><br />
#Add the following to the end of template.js.<syntaxhighlight lang="javascript" enclose="div">// A jQuery plugin to display a range slider in LimeSurvey
(function( $ ){

$.fn.lsRangeSlider = function(options) {

// The defaults, extended and modified with any passed in the function call
var opts = $.extend( {
range :true,
sliderMin :0,
sliderMax :100,
rangeStartMin :'',
rangeStartMax :'',
minRangeSpan :0,
step :1,
width :250,
recordStart :false,
showMin :false,
showMax :false
}, options);

return this.each(function() {

if($(this).hasClass('numeric-multi') && $('input.text', this).length == 2) {

// Define some vars
var $this = $(this);
var qID = $(this).attr('id').split('question')[1];
var rangeMinInput = $('input.text:eq(0)', $this);
var rangeMaxInput = $('input.text:eq(1)', $this);

// Some classes for the question and sub-questions
$this.addClass('range-slider-question');

// Check for pre-existing answer
if($(rangeMinInput).val() != '' && $(rangeMinInput).val() != '') {
opts.rangeStartMin = $(rangeMinInput).val();
opts.rangeStartMax = $(rangeMaxInput).val();
}

// Insert the slider elements
$('.subquestions-list', $this).before(
'<div class="range-slider-wrapper"> \
<div class="range-slider-min"></div> \
<div id="range-slider-'+qID+'" class="range-slider" style="width:'+opts.width+'px;"> \
<div class="range-slider-callout" id="slider-callout-min-'+qID+'"></div> \
<div class="range-slider-callout" id="slider-callout-max-'+qID+'"></div> \
</div> \
<div class="range-slider-max"></div> \
<div style="clear:both;"></div> \
</div>'
);

// Show min/max if option is set
if(opts.showMax) {
$('.range-slider-max', $this).text(opts.sliderMax);
}
if(opts.showMin) {
$('.range-slider-min', $this).text(opts.sliderMin);
}

// Initiate the slider
var rangeMin;
var rangeMax;
if(opts.rangeStartMin == '' || opts.rangeStartMin < opts.sliderMin || opts.rangeStartMin > opts.rangeStartMax) {
rangeMin = opts.sliderMin+((opts.sliderMax-opts.sliderMin)*0.3333);
}
else {
rangeMin = opts.rangeStartMin;
}
if(opts.rangeStartMax == '' || opts.rangeStartMax > opts.sliderMax || opts.rangeStartMax < opts.rangeStartMin) {
rangeMax = opts.sliderMin+((opts.sliderMax-opts.sliderMin)*0.6667);
}
else {
rangeMax = opts.rangeStartMax;
}
$('#range-slider-'+qID).slider({
range: true,
min: opts.sliderMin,
max: opts.sliderMax,
values: [ rangeMin, rangeMax ],
step: opts.step,
slide: function(event, ui) {
if((ui.values[1] - ui.values[0]) < opts.minRangeSpan) {
return false; // Nothing happens if less than minRangeSpan
}
$(rangeMinInput).val(ui.values[0]);
$(rangeMaxInput).val(ui.values[1]);
$('#slider-callout-min-'+qID).text(ui.values[0]);
$('#slider-callout-max-'+qID).text(ui.values[1]);
setTimeout(function() {
$('#slider-callout-min-'+qID).css({ 'left':$('.ui-slider-handle:eq(0)', $this).position().left - $('#slider-callout-min-'+qID).outerWidth() - ($('.ui-slider-handle:eq(1)', $this).outerWidth()/2)+'px' }).show();
$('#slider-callout-max-'+qID).css({ 'left':($('.ui-slider-handle:eq(1)', $this).position().left)+($('.ui-slider-handle:eq(1)', $this).outerWidth()/2)+'px' }).show();
}, 10);
},
create: function(event, ui) {
// Initial values and positions
if($(rangeMinInput).val() != '' && $(rangeMaxInput).val() != '') { // Pre-existing answer
$('#slider-callout-min-'+qID).text(opts.rangeStartMin);
$('#slider-callout-max-'+qID).text(opts.rangeStartMax);
}
else if(opts.recordStart && opts.rangeStartMin && opts.rangeStartMin && $(rangeMinInput).val() == '' && $(rangeMaxInput).val() == '') { // Record the start value (if option is set)
$(rangeMinInput).val(opts.rangeStartMin);
$(rangeMaxInput).val(opts.rangeStartMax);
$('#slider-callout-min-'+qID).text(opts.rangeStartMin);
$('#slider-callout-max-'+qID).text(opts.rangeStartMax);
}
else {
$('.range-slider-callout', $this).hide();
}
$('#slider-callout-min-'+qID).css({ 'left':$('.ui-slider-handle:eq(0)', $this).position().left - $('#slider-callout-min-'+qID).outerWidth() - ($('.ui-slider-handle:eq(1)', $this).outerWidth()/2)+'px' });
$('#slider-callout-max-'+qID).css({ 'left':($('.ui-slider-handle:eq(1)', $this).position().left)+($('.ui-slider-handle:eq(1)', $this).outerWidth()/2)+'px' });
}
});
}
});

};
})( jQuery );
</syntaxhighlight><br /><br />
#Add the following to the end of template.css (these styles are for the default template but easily modified for others):<syntaxhighlight lang="css" enclose="div">
.range-slider-question p.tip,
.range-slider-question .subquestions-list {
display: none;
}

.range-slider-wrapper {
clear: both;
margin: 10px 0;
padding-top: 20px;
}

.range-slider,
.range-slider-max,
.range-slider-min {
float: left;
position: relative;
}

.range-slider-max,
.range-slider-min {
font-size: 0.8em;
color:#666666;
line-height: 1.20;
}

.range-slider-min {
margin-right: 5px;
}

.range-slider-max {
margin-left: 5px;
}

.range-slider-question .ui-slider-handle {
top: -4px;
border-radius: 4px;
}

.range-slider-callout {
position: absolute;
top: -30px;
margin: 0;
min-width: 1.3em;
padding: 0.1em;
font-size: 0.9em;
color:#000000;
line-height: 1;
text-align: center;
background: #F8F8FF;
border: 1px solid #D2E0F2;
border-radius: 4px;
}
</syntaxhighlight><br /><br />
#Then, add something like this to the source of your question to apply the plugin with some custom option settings (I think the comments explain the options adequately)<syntaxhighlight lang="javascript" enclose="div">
<script type="text/javascript" charset="utf-8">
$(document).ready(function(){

$('#question{QID}').lsRangeSlider({
sliderMin :0, // Minimum slider value (default 0)
sliderMax :100, // Maximum slider value (default 100)
rangeStartMin :20, // Minimum range handle start value
rangeStartMax :80, // Maximum range handle start value
minRangeSpan :5, // Minimum allowed range span
step :1, // Slider increments (default 1)
width :400, // Width of slider in pixels (default 250)
recordStart :true, // Record the start value? (default no)
showMin :true, // Show slider minimum value? (default no)
showMax :true // Show slider maximum value? (default no)
});

});
</script>
</syntaxhighlight><br /><br />
#Or, to apply the plugin with the default option settings<syntaxhighlight lang="javascript" enclose="div">
<script type="text/javascript" charset="utf-8">
$(document).ready(function(){

$('#question{QID}').lsRangeSlider();

});
</script>
</syntaxhighlight>
<br /><br />

=Split your sample into legs (cells) that see slightly different wording and media=

Sometimes you may need to test candidate A vs candidate B or brand 1 vs brand 2 … vs brand n. Typically in such cases the phrasing of the questionnaire is identical except for the brand (candidate) and some logo/media. Rather than create several questionnaires it is best to control survey logic by assigning respondents to different groups and showing them different versions of the questionnaire.

The logical engine in the current version (1.91) does not support this but you can still do it using the attribute fields in the token table. The instructions below are not really a workaround, but more of a translation of conditional logic to database questionnaire logic.

This works for closed surveys. If your survey is not closed you may want to consider ways to create automatically tokens for each respondent like: "Create token on the fly and Edit completed survey": http://bugs.limesurvey.org/view.php?id=2982

'''Case A: you need different text for each version'''

Step 1: you create a tokens table adding attribute fields for each variation you need: [[Tokens#User-defined attribute fields|User defined attribute fields]]. For example you may store in attribute_1 the name of the candidate, in attribute_2 the name of the party etc.

Step 2 You export the structure of your tokens database and populate it with the relevant values for the attribute fields. Then import it back

Example:

http://img502.imageshack.us/img502/7425/58d0ff2c68d74366a81e6f7.png

Please use the instructions here: [[Tokens#Importing/exporting tokens|importing and exporting tokens]], and pay attention because this can be error-prone.

Step 3

When creating a question use the insert replacement field icon http://img502.imageshack.us/img502/540/81a6c17d49f04f88bd52e72.png to insert your proper keyword.

This is it. The overall process is quite simple once you get the hang of using tokens, but the database can be space-consuming if you are running on limited resources.

'''Case B: you need to run different media, from public hosting websites.'''

The process is just like in case A, just that you will populate the attribute field with unique identifiers for the media.

See below an example on how to embed a youtube video

<syntaxhighlight lang="php" enclose="div"><iframe allowfullscreen="" frameborder="0" height="349" src="http://www.youtube.com/embed/'''{TOKEN:ATTRIBUTE_5}'''?rel=0&modestbranding=1&loop=0&controls=0&autoplay=1&rel=0&showinfo=0&showsearch=0&iv_load_policy=o" width="560"></iframe></syntaxhighlight>

If you embed images you will want to make sure that the hotlinks for your pictures only differ by the image ID. IF not, you may use a larger portion, or maybe even the entire URL as your unique identifier. As said before, please consider how much space you are allowed for your databases.

'''Case C: you want to run media from your server, which is organized in relevant folders'''

For this scenario I will assume your media is organized as follows

Project folder ...leg folder (for each leg) ... media (1 to n). You can use a FTP client to upload this structure to you LS installation.

In this case you only need to store the <leg folder> into the tokens table and then use this info to build your embed tag. This may free a significant amount of space,

For example if you have the data as below...

http://img534.imageshack.us/img534/8967/a62e6ff48476492c8795f79.png

… then your embed for the party logo will look somewhere along these lines:

<syntaxhighlight lang="php" enclose="div"><img src="[path to project folder]/'''{TOKEN:ATTRIBUTE_3}'''/logo1.png" alt="'''{TOKEN:ATTRIBUTE_2}'''"></syntaxhighlight>

The alt tag is, of course, optional.
***

You can match and mix all 3 cases as it suites you best. You need to be a little careful when you work with tokens and embed tags, but it will save you from using intricate and error-prone survey logic or from duplicating surveys endlessly.

=Limit the language options dropdown on the list surveys page=

<div class="simplebox">Note: This feature is implemented in Version 2.0</div>

This solution allows you to define (in config.php) a comma-delimited list of languages you want in the dropdown. It is not optimized (it loads all the languages and then unsets everything you don't want), but is fairly easy to implement.

<syntaxhighlight lang="php" enclose="div">

$supportedLanguagesKeys = 'en,vi';

</syntaxhighlight>

Filter out everything except the your selected languages (if defined).

<syntaxhighlight lang="php" enclose="div">

// if $supportedLanguagesKeys is defined in config, filter

if (!empty($GLOBALS['supportedLanguagesKeys']))

foreach (array_keys($supportedLanguages) as $lang) {

if (!in_array($lang, explode(',', $GLOBALS['supportedLanguagesKeys']))) {

unset($supportedLanguages[$lang]);

}

}

</syntaxhighlight>

Now only my languages, plus the base language, is displayed. To get rid of the redundant base language, do the following

<syntaxhighlight lang="php" enclose="div">
#

} elseif (!isset($surveyid))

{

global $defaultlang, $baselang;

$htmlcode = "<select name=\"select\" class='languagechanger' onchange=\"javascript:window.location=this.value\">\n";
# REMOVE THE NEXT LINE OR COMMENT IT OUT)

$htmlcode .= "<option value=\"$relativeurl/index.php?lang=". $defaultlang ."$tokenparam\">".getLanguageNameFromCode($defaultlang,false)."</option>\n";

foreach(getlanguagedata() as $key=>$val)

{

$htmlcode .= "\t<option value=\"$relativeurl/index.php?lang=".$key."$tokenparam\" ";

if ($key == $baselang) $htmlcode .= " selected='selected'"; /* ADD THIS TO SET SELECTION */

$htmlcode .= ">".getLanguageNameFromCode($key,false)."</option>\n";

}

$htmlcode .= "</select>\n";

</syntaxhighlight>

Basically it just pre-selects the base language from the list.