Actions

Difference between revisions of "General FAQ"

From LimeSurvey Manual

(Marked this version for translation)
 
(113 intermediate revisions by 10 users not shown)
Line 1: Line 1:
 
<languages /> <translate>
 
<languages /> <translate>
 +
  
 
<!--T:1-->
 
<!--T:1-->
 
__TOC__
 
__TOC__
 +
 +
 +
<!--T:84-->
 +
{{Note|The following answers have been provided by the LimeSurvey user community. In case you do not understand something or you are unsure about what you have to do next, you can address your question(s) to the rest of community members: https://limesurvey.org/forums. For professional help, please check our list of authorized partners: https://limesurvey.com.}}
 +
  
 
=Getting started= <!--T:2-->
 
=Getting started= <!--T:2-->
 +
  
 
<!--T:3-->
 
<!--T:3-->
If you don't want to read half the manual to get a feeling what can be done with Limesurvey we recommend to watch some videos (see below).
+
If you don't want to read half the manual to get a feeling what can be done with LimeSurvey, we recommend you to watch some YouTube video tutorials:
 +
 
 +
<!--T:85-->
 +
*[https://www.youtube.com/watch?v=oyoq14XpkwA How to set up an account and survey installation]
 +
*[https://www.youtube.com/watch?v=7134QebOQzY Question type - Array]
 +
*[https://www.youtube.com/watch?v=aeb93vAe7R4 Assessments]
 +
*[https://www.youtube.com/watch?v=s5OOzDoPjIU Placeholder fields]
 +
*[https://www.youtube.com/watch?v=7N4xUQMWbJY Radio list]
 +
*[https://www.youtube.com/watch?v=UI01hwrsiVk Copy/import survey]
 +
*[https://www.youtube.com/watch?v=QEHyH1YbNEQ Import question]
 +
 
 +
 
 +
<!--T:86-->
 +
{{Note|If you know any good video out there, do not hesitate to share it with us.}}
  
<!--T:4-->
 
After that the [[Creating surveys - Introduction]] manual page might be a good start.
 
  
 
==I need a quick introduction for LimeSurvey== <!--T:5-->
 
==I need a quick introduction for LimeSurvey== <!--T:5-->
  
<!--T:6-->
 
For a first start have a look at our very basic [[LimeSurvey Video-Tutorial]].
 
  
<!--T:7-->
+
<!--T:87-->
There is [http://vimeo.com/4951738 another tutorial] which shows you how to get started with using Lime Survey to conduct online surveys. In [http://vimeo.com/4951738 this video] we'll create our first survey, deliver it to a user and then view the submitted results.
+
For a quick text introduction to LimeSurvey, check the following two links:
 +
 
 +
<!--T:88-->
 +
*[[Quick start guide - LimeSurvey 2.50+|LimeSurvey 2.50+]]
 +
*[[Quick start guide - LimeSurvey 3.0+|Limesurvey 3+]]
  
<!--T:8-->
 
There are some '''more videos on YouTube''':
 
  
<!--T:9-->
+
<!--T:89-->
'''''Limesurvey:'''''
+
{{Alert|We are working at the moment on introductory videos to LimeSurvey.}}
*[http://www.youtube.com/watch?v=96WdtqDmRVw Planning a survey]
 
*[http://www.youtube.com/watch?v=6GH-S3YAHRg Creating a survey]
 
*[http://www.youtube.com/watch?v=61p1Yre4GFM Entering questions]
 
*[http://www.youtube.com/watch?v=5eiZHw9mjDg Using label sets]
 
*[http://www.youtube.com/watch?v=5fI9Fyk5UCk Exporting data from LimeSurvey]
 
  
<!--T:10-->
 
'''''Old PHP-surveyor videos:'''''
 
*[http://www.youtube.com/watch?v=c8OiA0bv8Rk Getting to the phpsurveyors Admin Pages]
 
*[http://www.youtube.com/watch?v=KOq45Val3v8 Creating a new group in a survey]
 
*[http://www.youtube.com/watch?v=bXGQeP8f7kQ Creating a new question for phpsurveyor]
 
*[http://www.youtube.com/watch?v=1mzZ3KCaGAc Testing a newly created/modified Survey]
 
*[http://www.youtube.com/watch?v=6Y2L23y6bps Add respondent]
 
*[http://www.youtube.com/watch?v=NcnK5YsfB8g Emailing to the respondents]
 
  
 
=Survey design and layout= <!--T:11-->
 
=Survey design and layout= <!--T:11-->
  
==How can I remove index.php from the URL path to get a shorter URL==
 
If you want to use fancy URLs and so not have /index.php in every URL please edit /application/config/config.php and change
 
  
 +
==How can I remove index.php from the URL path to get a shorter URL== <!--T:90-->
 +
 +
 +
<!--T:64-->
 +
If you want to use fancy URLs (not have /index.php in every URL), please edit /application/config/config.php and change
 +
 +
<!--T:65-->
 
<syntaxhighlight lang="php" enclose="div">'showScriptName' => true,</syntaxhighlight>
 
<syntaxhighlight lang="php" enclose="div">'showScriptName' => true,</syntaxhighlight>
  
 +
<!--T:66-->
 
to
 
to
  
 +
<!--T:67-->
 
<syntaxhighlight lang="php" enclose="div">'showScriptName' => false,</syntaxhighlight>
 
<syntaxhighlight lang="php" enclose="div">'showScriptName' => false,</syntaxhighlight>
  
For this to work properly you must use an Apache webserver with a properly installed mod_rewrite module.
+
<!--T:68-->
 +
For this to work properly, you must use an Apache webserver with a properly installed mod_rewrite module.
 +
 
 +
<!--T:69-->
 +
If you are using the [http://nginx.com/products/ Nginx] http server (with php running via FastCGI) and want to use the ''''urlFormat' => 'path'''' setting (see config.php), consider the following Nginx website configuration:
 +
 
 +
<!--T:70-->
 +
<syntaxhighlight lang="apache">server {
 +
    set $host_path "/PATH/TO/LIMESURVEY";
 +
    server_name  YOUR.SERVER.FQDN;
 +
    root /PATH/TO/LIMESURVEY;
 +
    charset utf-8;
 +
    try_files $uri $uri/ /index.php?r=$uri&$args;
 +
    #Disallow reading inside php script directory, see issue with debug > 1 on note
 +
    location ~ ^/(application|protected|framework|themes/\w+/views) {
 +
        deny  all;
 +
    }
 +
    #Disallow direct read user upload files
 +
    location ~ ^/upload/surveys/.*/fu_[a-z0-9]*$ {
 +
        return 444;
 +
    }
 +
    #Disallow uploaded potential executable files in upload directory
 +
    location ~* /upload/.*\.(pl|cgi|py|pyc|pyo|phtml|sh|lua|php|php3|php4|php5|php6|pcgi|pcgi3|pcgi4|pcgi5|pcgi6|icn)$ {
 +
        return 444;
 +
    }
 +
    #avoid processing of calls to unexisting static files by yii
 +
    location ~ \.(js|css|png|jpg|gif|swf|ico|pdf|mov|fla|zip|rar)$ {
 +
        try_files $uri =404;
 +
    }
 +
    location ~ \.php$ {
 +
        fastcgi_split_path_info  ^(.+\.php)(.*)$;
 +
        try_files $uri index.php;
 +
        fastcgi_pass  127.0.0.1:9000; # Change this to match your settings
 +
        fastcgi_index index.php;
 +
        include fastcgi_params;
 +
        fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
 +
        fastcgi_param  SCRIPT_NAME      $fastcgi_script_name;
 +
    }
 +
}</syntaxhighlight>
 +
 
 +
<!--T:91-->
 +
{{Note|This disables access to files inside application. Some JavaScript and CSS files located within the application have to be readable with debug > 0. You can force the usage of the asset manager when the debug mode is enabled with <code><nowiki>'use_asset_manager' => 1,</nowiki></code> in your config file (or remove <code><nowiki>application</nowiki></code> from the directory list</code>).}}
 +
 
 +
<!--T:92-->
 +
The end result should look like this:
 +
 
 +
 
 +
<!--T:93-->
 +
<center>[[File:Remove index.php steps.png]]</center>
 +
 
  
 
==How do I get rid of the <span style='color:red'>*</span> (red asterisk) of mandatory questions?== <!--T:12-->
 
==How do I get rid of the <span style='color:red'>*</span> (red asterisk) of mandatory questions?== <!--T:12-->
 +
 +
 +
===Instructions for LimeSurvey 2=== <!--T:94-->
 +
  
 
<!--T:13-->
 
<!--T:13-->
In '''LimeSurvey Version 1.80 and above''' the red asterisk of mandatory questions is set within the template.css file ("asterisk" class). To hide it:
+
In LimeSurvey 2.x, the red asterisk of mandatory questions is set within the template.css file ("asterisk" class). To hide it:
 
*Open the template editor
 
*Open the template editor
 
*Create a copy of the template you wish to modify
 
*Create a copy of the template you wish to modify
Line 64: Line 129:
 
*Clear your browser cache so that the edited template.css is reloaded and not taken from cache.
 
*Clear your browser cache so that the edited template.css is reloaded and not taken from cache.
  
<!--T:14-->
 
In '''LimeSurvey Version 1.53''' the red asterisk of mandatory questions is set within the css "asterisk" class. To hide it:
 
*Open the template editor
 
*Select the template you wish to modify so that the asterisk doesn't show
 
*Select the "startpage.pstpl" file
 
*Add the css ".asterisk {display: none;}" into the css stylesheet area.
 
  
<!--T:15-->
+
===Instructions for LimeSurvey 3=== <!--T:95-->
'''Earlier Versions'''
+
 
*Open qanda.php in your text editor
+
 
*Search for the string "asterisk"
+
<!--T:96-->
*Comment out this line with two slashes "//" at the beginning of the line
+
The instructions are similar to the ones presented above for LimeSurvey 2.
*Example:
+
 
**original: $qtitle = '<span class=\'asterisk\'>'.$clang->gT('*').'</span>'.$qtitle;
+
<!--T:97-->
**modified: // $qtitle = '<span class=\'asterisk\'>'.$clang->gT('*').'</span>'.$qtitle;
+
* Access the desired theme. If it is a default theme, create a copy of it by clicking on the "extend" button.
 +
* Access the list of themes and click on the '''theme editor''' that corresponds to the newly created theme.
 +
* On the left side, you can visualise the corresponding CSS files of your theme.
 +
* Click on custom.css and add the following line:
 +
 
 +
<!--T:98-->
 +
<syntaxhighlight lang="css" enclose="div">.asterisk {display: none;}</syntaxhighlight>
 +
 
 +
 
 +
<!--T:99-->
 +
* Save the changes. The red asterisk that is usually displayed at the beginning of the question text is hidden.
 +
 
  
 
==How can I embed a flash file?== <!--T:16-->
 
==How can I embed a flash file?== <!--T:16-->
 +
  
 
<!--T:17-->
 
<!--T:17-->
First go to [[Global settings]] and deactivate the XSS-filter. Please also read up in the implications deactivating that filter. The following steps won't work if the filter is active.
+
First, go to [[Global settings]] and deactivate the XSS-filter. Please also read up the implications deactivating that filter has on your instance. The following steps will '''not''' work if the filter is active.
 
#Navigate to the place in your survey where you want insert your Flash file. This can be anywhere where you can use the integrated HTML editor, for example in questions, subquestions, answers, survey welcome/end text and many more.
 
#Navigate to the place in your survey where you want insert your Flash file. This can be anywhere where you can use the integrated HTML editor, for example in questions, subquestions, answers, survey welcome/end text and many more.
#Open the [http://docs.limesurvey.org/tiki-index.php?page=First+Login+%2F+You+user+preferences&structure;=English+Instructions+for+LimeSurvey#Popup:_The_normal_text_editor_is_used_but_the_HTML_editor_is_available_as_a_pop_up_option. full-screen editor mode] by clicking the 'LimeFitWin' button on the editor tool-bar.
+
#Open the [[First login - Your user preferences#Popup|full-screen editor mode]] by clicking the 'LimeFitWin' button on the editor tool-bar.
#On the full-screen editor tool-bar you will find a little button with a Flash symbol. Click on it. A dialog will open.
+
#On the full-screen editor tool-bar you will find a little button with a Flash symbol. Click on it. A dialog box will open.
#In this dialog you can give either the path to an existing Flash file somewhere OR you click the 'Browse server' button.
+
#In this box you can give either the path to an existing Flash file somewhere or you click the 'Browse server' button.
 
#If you clicked the 'Browse server' button you will be presented with a file browser and on the bottom an file upload field. Choose now an existing file or upload a file first.
 
#If you clicked the 'Browse server' button you will be presented with a file browser and on the bottom an file upload field. Choose now an existing file or upload a file first.
 +
  
 
<!--T:18-->
 
<!--T:18-->
 
That's it! If you find this description incomplete please update it accordingly.
 
That's it! If you find this description incomplete please update it accordingly.
  
==How to remove one of these texts from my survey== <!--T:19-->
 
  
==="There are X questions"=== <!--T:20-->
+
<!--T:100-->
 +
{{Alert|title=Attention|text=The steps to use it in LimeSurvey 3 are similar. However, we do not recommend our users to use flash files!}}
 +
 
 +
 
 +
==How do I create a survey which is open to everyone?== <!--T:25-->
 +
 
 +
 
 +
<!--T:101-->
 +
To create a survey that can be filled out by anyone, do not create a [[Survey participants|survey participants table]]! Share the survey link located on the [[Overview|overview panel]].
 +
 
 +
 
 +
==Public registration - mandatory fields== <!--T:102-->
 +
 
 +
 
 +
<!--T:103-->
 +
If you use a [[Survey participants|survey participants table]] and you also allow [[Participant_settings#Allow_public_registration|public registration]], then users will be prompted by the following message:
 +
 
 +
 
 +
<!--T:104-->
 +
<center>[[File:non-mandatory public reg.png]]</center>
 +
 
 +
 
 +
<!--T:105-->
 +
As it can be observed above, only the email field is mandatory.
 +
 
 +
<!--T:106-->
 +
To have all three fields marked as being mandatory, please edit your survey theme accordingly. If you use '''Fruity''', you have to go to the '''registration''' screen and see how the participants email field looks like:
 +
 
 +
<!--T:107-->
 +
<syntaxhighlight lang="twig">
 +
        {# Participants email #}
 +
        <div class='{{ aSurveyInfo.class.registerformcolrowc }} form-group row' {{ aSurveyInfo.attr.registerformcolrowc }}>
 +
            <label {{ aSurveyInfo.attr.registerformcolrowclabel }} class='{{ aSurveyInfo.class.registerformcolrowclabel }}  control-label'> {{ gT("Email address:") }} {{ include('./subviews/registration/required.twig') }}</label>
 +
            <div {{ aSurveyInfo.attr.registerformcolrowcdiv }}  >
 +
                {{ C.Html.textField('register_email', aSurveyInfo.sEmail, ({'id' : 'register_email','class' : 'form-control input-sm','required' : true})) }}
 +
            </div>
 +
        </div>
 +
</syntaxhighlight>
 +
 
 +
<!--T:108-->
 +
After that, make sure to edit the first name and last name fields correspondingly by adding the label: <syntaxhighlight lang="twig">{{ include('./subviews/registration/required.twig') }}</syntaxhighlight> and this line which makes the field mandatory to be filled out: <syntaxhighlight lang="twig">'required' : true</syntaxhighlight>
 +
 
 +
<!--T:109-->
 +
The edited file should look like this:
 +
 
 +
<!--T:110-->
 +
<syntaxhighlight lang="twig">
 +
        {# Participants first name #}
 +
        <div class='{{ aSurveyInfo.class.registerformcolrow }} form-group row' {{ aSurveyInfo.attr.registerformcolrow }}>
 +
            <label for='register_firstname' class='{{ aSurveyInfo.class.registerformcolrowlabel }} control-label '>{{ gT("First name:") }} {{ include('./subviews/registration/required.twig') }}</label> {# extra label #}
 +
            <div class="">
 +
                {{ C.Html.textField('register_firstname', aSurveyInfo.sFirstName, ({'id' : 'register_firstname','class' : 'form-control', 'required' : true})) }} {# mandatory field #}
 +
            </div>
 +
        </div>
 +
 
 +
        <!--T:111-->
 +
{# Participants last name #}
 +
        <div class='{{ aSurveyInfo.class.registerformcolrowb }} form-group row' {{ aSurveyInfo.attr.registerformcolrowb }}>
 +
            <label {{ aSurveyInfo.attr.registerformcolrowblabel }}  class='{{ aSurveyInfo.class.registerformcolrowblabel }} control-label '>{{ gT("Last name:") }} {{ include('./subviews/registration/required.twig') }}</label> {# extra label #}
 +
            <div {{ aSurveyInfo.attr.registerformcolrowbdiv }} >
 +
                {{ C.Html.textField('register_lastname', aSurveyInfo.sLastName, ({'id' : 'register_lastname', 'class' : 'form-control', 'required' : true})) }} {# mandatory field #}
 +
            </div>
 +
        </div>
 +
</syntaxhighlight>
 +
 
 +
 
 +
<!--T:112-->
 +
Now, the public registration page should look like this (all the fields being mandatory):
 +
 
 +
 
 +
<!--T:113-->
 +
<center>[[File:mandatory public reg.png]]</center>
 +
 
 +
 
 +
== Hiding the language switcher == <!--T:114-->
 +
 
 +
 
 +
<!--T:115-->
 +
The steps to hide both the language switchers (near the survey title and on the top-right side of the page) are described in our wiki section dedicated to [[Multilingual_survey#Hints_.26_tips|multilingual surveys]].
 +
 
 +
 
 +
== Hiding "Exit and clear survey" == <!--T:119-->
 +
 
 +
 
 +
<!--T:120-->
 +
In case you wish to hide the button "Exit and clear survey", you have to edit the nav_bar.twig file located inside your survey theme.
 +
 
 +
 
 +
<!--T:121-->
 +
<center>[[File:exit and clear survey pic.png]]</center>
  
==="A note on privacy..."=== <!--T:21-->
 
  
===question code=== <!--T:22-->
+
<!--T:122-->
 +
The line that needs to be removed (or commented out) is:
  
<!--T:23-->
+
<!--T:123-->
All these texts are inserted at the template you are using by [http://docs.limesurvey.org/tiki-index.php?page=Template+editor&structure;=English+Instructions+for+LimeSurvey#Replacements_Field_Strings placeholders]. You can easily remove them. Go to the [http://docs.limesurvey.org/tiki-index.php?page=Template+editor&structure;=English+Instructions+for+LimeSurvey Template Editor] and remove the {THEREAREXQUESTIONS} / {PRIVACYMESSAGE} / {QUESTION_CODE} placeholder(s).
+
<syntaxhighlight lang="twig">
 +
{{ include('./subviews/navigation/clearall_links.twig') }}
 +
</syntaxhighlight>
  
=Survey configuration= <!--T:24-->
 
  
==How do I create a survey which is open to everyone?== <!--T:25-->
+
<!--T:124-->
 +
<center>[[File:Hide exit and clear survey.png]]</center>
 +
 
 +
 
 +
<!--T:125-->
 +
Now, there is no option to exit and clear the survey.
  
<!--T:26-->
 
To make a survey public to everyone you should:
 
* not [http://docs.limesurvey.org/tiki-index.php?page=Tokens&structure;=English+Instructions+for+LimeSurvey#How_to_activate_tokens_ create a token table] (if there is one, drop it)
 
* at survey settings set "[http://docs.limesurvey.org/tiki-index.php?page=Creating+a+new+survey&structure;=English+Instructions+for+LimeSurvey#Publication_amp_Access_control Only users with tokens may enter the survey]" = no (old setting)
 
* at survey settings set "[http://docs.limesurvey.org/tiki-index.php?page=Creating+a+new+survey&structure;=English+Instructions+for+LimeSurvey#Publication_amp_Access_control allow public registration]" = no
 
* at survey settings set "[http://docs.limesurvey.org/tiki-index.php?page=Creating+a+new+survey&structure;=English+Instructions+for+LimeSurvey#Presentation_amp_Navigation list this survey publicly]"
 
  
<!--T:27-->
+
<!--T:126-->
Your survey should then be listed at the root page of your limesurvey installation. You can publish the link to the survey on your website/blog and everyone can take the survey without restrictions.
+
<center>[[File:no exit clear survey.png]]</center>
  
==How can I stop the system from sending confirmation emails== <!--T:28-->
 
  
<!--T:29-->
+
<!--T:127-->
If you are [http://docs.limesurvey.org/tiki-index.php?page=Tokens&structure;=English+Instructions+for+LimeSurvey#Email_settings using tokens] and a participant fills out the survey, a confirmation email is sent to his/her email address. If you don't want this message to be sent just delete the whole ''confirmation email'' subject and message. You have to [http://docs.limesurvey.org/tiki-index.php?page=First+Login+%2F+You+user+preferences&structure;=English+Instructions+for+LimeSurvey#X._Source_code_mode: switch to source code mode] to be able to delete all the text. Save the empty message and no confirmation emails should be sent anymore.
+
<div class="simplebox">[[File:help.png]] '''Note:''' This customization can be used when you create long surveys and require from your respondents to save and resume later the survey. Sometimes, the users tend to click the "Exit and clear survey" button which deletes the entry from the partially completed responses table.</div>
  
 
=Help, I accidentally...= <!--T:30-->
 
=Help, I accidentally...= <!--T:30-->
 +
  
 
==I forgot my admin password. How do I reset it?== <!--T:31-->
 
==I forgot my admin password. How do I reset it?== <!--T:31-->
# For version 1.47 to 1.53 only: Download [[Media:resetadminpw.php|this file]] and copy it to /<your limesurveydir>/admin/install/ .
+
 
# For version 1.7 or later: Restore your /<your limesurveydir>/admin/install/ directory from the download package
+
 
# Execute resetadminpw.php using your browser by pointing it to <syntaxhighlight lang="php" enclose="div">http://www.your_domain.com/your_limesurvey_dir/admin/install/resetadminpw.php</syntaxhighlight>
+
=== Version 2.x === <!--T:73-->
# After removing the /install directory again you should be able to login with $defaultuser (Default: admin) and $defaultpass (Default: password) set in config.php.
+
# Access to your server with a command line (ssh for example)
 +
# Ensure you have php command line access (see http://php.net/features.commandline.php).
 +
# Go to your LimeSurvey directory
 +
# Launch this command <code>php application/commands/starter.php resetpassword NEW_ADMIN_NAME NEW_ADMIN_PASS</code> or <code>php application/commands/console.php resetpassword NEW_ADMIN_NAME NEW_ADMIN_PASS</code><sup>The php can need complete directory access, example /usr/bin/php</sup>
 +
 
 +
 
 +
<!--T:116-->
 +
{{Alert|Title=Attention|text=Please note that this method will not work in LimeSurvey 3.x!}}
 +
 
 +
 
 +
===Version 2.x.x and newer with only FTP access=== <!--T:82-->
 +
 
 +
 
 +
<!--T:83-->
 +
See [https://gitlab.com/SondagesPro/coreAndTools/ResetPasswordController ResetPasswordController]
 +
 
 +
 
 +
=== Directly change the password in the database === <!--T:74-->
 +
If you have direct access to the Limesurvey database you can change the old password there by uploading the new password as SHA256 hash. You can [http://www.xorbin.com/tools/sha256-hash-calculator create the SHA256 hash of your password here].
 +
 
 +
<!--T:76-->
 +
For example, you can use this instruction to set password to password:
 +
<syntaxhighlight lang="sql" enclose="div">
 +
UPDATE lime_users SET password = 0x35653838343839386461323830343731353164306535366638646336323932373733363033643064366161626264643632613131656637323164313534326438 WHERE uid =1;
 +
</syntaxhighlight>
 +
Here with prefix to lime_ and database selected.
 +
 
  
 
==How can I restore data from a deactivated survey?== <!--T:32-->
 
==How can I restore data from a deactivated survey?== <!--T:32-->
 +
  
 
<!--T:33-->
 
<!--T:33-->
We recommend to always use the time-out option instead of deactivating a survey. If you closed your survey accidentally it is important that you don't change anything in the survey.
+
We recommend to always use the time-out option instead of deactivating a survey. '''If you closed your survey accidentally, it is important that you don't change anything in the survey!'''
  
 
<!--T:34-->
 
<!--T:34-->
 
Then, and only then the following steps will work:
 
Then, and only then the following steps will work:
 
#Activate your survey again
 
#Activate your survey again
#Go to the "Browse responses for this survey" menu.
+
#Select [[Responses]] from the survey toolbar.
#Click at the "Import answers from a deactivated survey table" button.
+
#Click on [[Import responses|Import]] and select the "Import answers from a deactivated survey table" menu entry.
 
#Choose your source table.
 
#Choose your source table.
#Click at the "Import responses" button.
+
#Click on the "Import" button located on the upper-right part of the screen.
 +
 
 +
 
 +
<!--T:117-->
 +
{{Note|To understand the difference between "expiry" and "deactivation", visit this following [https://manual.limesurvey.org/Closing_a_survey wiki section].}}
 +
 
  
 
==I deleted a question/question group/survey!== <!--T:35-->
 
==I deleted a question/question group/survey!== <!--T:35-->
 +
  
 
<!--T:36-->
 
<!--T:36-->
This is bad luck. If you delete it, it is really gone. In that case only a backup will help you (which of course you did regularly, didn't you?).
+
If you delete it, it is gone. Only a backup could help you recover it.
 +
 
 +
 
 +
<!--T:118-->
 +
{{Note|If you are a [https://limesurvey.org LimeSurvey GmbH] professional user, please open a support ticket and ask the team to provide you the backup associated to your account. '''Please note that this service is not free of charge!'''}}
 +
 
  
 
=Hard- and Software requirements= <!--T:37-->
 
=Hard- and Software requirements= <!--T:37-->
 +
  
 
<!--T:38-->
 
<!--T:38-->
For general requirements please refer to our [http://docs.limesurvey.org/tiki-index.php?page=Installation&structure;=English+Instructions+for+LimeSurvey#Make_sure_you_can_use_LimeSurvey_on_your_website installation instructions].
+
For general requirements please refer to our [[Installation#Make sure you can use LimeSurvey on your website|installation instructions]].
 +
 
  
 
==What limitations does LimeSurvey have...== <!--T:39-->
 
==What limitations does LimeSurvey have...== <!--T:39-->
 +
  
 
=== ...regarding speed=== <!--T:40-->
 
=== ...regarding speed=== <!--T:40-->
 +
  
 
<!--T:41-->
 
<!--T:41-->
There is no existing speed limit on LimeSurvey. It all depends on how fast your server and your connection is. If you expect a large number of users within a short time and you are not sure if your server can handle this check our forum for according topics about other users' experience.
+
There is no existing speed limit on LimeSurvey. Everything depends on how fast your server and your connection are. If you expect a large number of users within a short amount of time and you are not sure if your server can handle this, '''check our forum for similar topics!''' or '''contact an authorized LimeSurvey partner''': https://limesurvey.com.
  
 
=== ...regarding survey size=== <!--T:42-->
 
=== ...regarding survey size=== <!--T:42-->
 +
  
 
<!--T:43-->
 
<!--T:43-->
Note: 'Survey size' refers to the maximmum number of questions (and answers) in your survey - '''don't confuse this with the number of replies on your survey (there is no limitation on that)'''. Theoretically there would also be no limit on the maximum number of questions/answers in LimeSurvey. But the database engine you are using has several limits. The most important one is the limit on the number of fields(columns) in the result table.
+
Note: 'Survey size' refers to the maximum number of questions (and answers) in your survey - '''don't confuse this with the number of replies on your survey (there is no limitation on that)'''. Theoretically there would also be no limit on the maximum number of questions/answers in LimeSurvey. But the database engine you are using has several limits. The most important one is the limit on the number of fields(columns) in the result table.
 
*MySQL ISAM: The sum of the lengths of the VARCHAR and CHAR columns in a table may be up to 64KB.
 
*MySQL ISAM: The sum of the lengths of the VARCHAR and CHAR columns in a table may be up to 64KB.
 
*MySQL InnoDB: Maximum number of 1000 columns
 
*MySQL InnoDB: Maximum number of 1000 columns
 
*MS SQL Server 2000: Maximum number of 1024 columns
 
*MS SQL Server 2000: Maximum number of 1024 columns
 
*Postgres: Maximum number of 250-1600 columns depending on column types. The maximum number of columns can be quadrupled by increasing the default block size to 32k. See [[Installation FAQ]] and [http://www.postgresql.org/docs/faqs.FAQ.html#item4.4 PostgreSQL FAQ].
 
*Postgres: Maximum number of 250-1600 columns depending on column types. The maximum number of columns can be quadrupled by increasing the default block size to 32k. See [[Installation FAQ]] and [http://www.postgresql.org/docs/faqs.FAQ.html#item4.4 PostgreSQL FAQ].
 +
 +
<!--T:77-->
 +
{{Alert|title=Attention|text=Please think about what you do before you do it! An array of 10 x 10 items already costs you 100 columns. Rule of thumb: every item on the screen that can be filled in or selected costs one column!}}
  
 
<!--T:44-->
 
<!--T:44-->
The mySQL ISAM engine is the most tricky one (see [http://dev.mysql.com/doc/refman/5.0/en/column-count-limit.html mysql documentation for more information]). As it allows only up to 65,535 bytes per row and utf8 characters can require up to three bytes per character the maximum may be only 21,844 characters (but this depends on your DB encoding).
+
The mySQL ISAM engine is the most tricky one (see [http://dev.mysql.com/doc/refman/5.0/en/column-count-limit.html mysql documentation for more information]). As it allows only up to 65,535 bytes per row and utf8 characters, it can require up to three bytes per character. The maximum may be only 21,844 characters (but this depends on your DB encoding).
  
 
<!--T:45-->
 
<!--T:45-->
Line 181: Line 387:
  
 
==How to increase the maximum number of columns in PostgreSQL== <!--T:46-->
 
==How to increase the maximum number of columns in PostgreSQL== <!--T:46-->
 +
  
 
<!--T:47-->
 
<!--T:47-->
In case your survey contains too many questions you can define a different block size in PostgreSQL so it is possible to create more columns. This might be tricky because you have to recompile PostgreSQL and set BLCKSZ to a higher value, like 16kiB or 32kiB. Watch for the configuration option "--with-blocksize=BLOCKSIZE". For details see the archives of the PostgreSQL mailing list or ask there (pgsql-patches(at)postgresql(dot)org).
+
In case your survey contains too many questions, you can define a different block size in PostgreSQL to create more columns. This might be tricky because you have to recompile PostgreSQL and set BLCKSZ to a higher value, like 16kiB or 32kiB. Watch for the configuration option "--with-blocksize=BLOCKSIZE". For details see the archives of the PostgreSQL mailing list or ask there (pgsql-patches(at)postgresql(dot)org).
  
 
<!--T:48-->
 
<!--T:48-->
 
Instructions for Debian (thanks to Martin Pitt):
 
Instructions for Debian (thanks to Martin Pitt):
  
<!--T:49-->
+
</translate>
<syntaxhighlight lang="c" enclose="div">  
+
<syntaxhighlight lang="bash">sudo apt-get build-dep postgresql-8.3
sudo apt-get build-dep postgresql-8.3
 
 
apt-get source postgresql-8.3
 
apt-get source postgresql-8.3
 
cd postgresql-8.3-*
 
cd postgresql-8.3-*
Line 196: Line 402:
 
sensible-editor build-tree/postgresql-8.3.5/src/include/pg_config_manual.h
 
sensible-editor build-tree/postgresql-8.3.5/src/include/pg_config_manual.h
 
dpkg-buildpackage -us -uc -b -nc</syntaxhighlight>
 
dpkg-buildpackage -us -uc -b -nc</syntaxhighlight>
 +
<translate>
  
==Survey participants get kicked out to the Surveys List page part way through. What can I do?== <!--T:55-->
+
<!--T:75-->
 +
Note: '''the above could not be reproduced''' on Ubuntu 14.04 in August 2014. A patch is required (the configuration option is not enough). See (tested with PostgreSQL 9.3 on Linux):
 +
[[Instructions for increasing the maximum number of columns in PostgreSQL on Linux]]
  
<!--T:56-->
+
==Fatal error: Allowed memory size== <!--T:59-->
If you have a particularly long survey, and you find that your users can access a survey, and get part way through completing it, but then seem to get kicked out to the Surveys List page check your PHP settings. If your host is using the '''Suhosin extension for Apache''' it may be set to be too limiting on a couple of settings.
 
  
<!--T:57-->
 
For example the two settings "suhosin.post.max_vars" and "suhosin.request.max_vars" are both set to a value of 200 by default. Increase those settings both to 400 or higher so users can complete and submit long surveys.
 
 
<!--T:58-->
 
If you still have problems, try switching the module to simulation_mode (and so basically deactivate it), as the maximum value always depends on your particular survey.
 
 
==Fatal error: Allowed memory size== <!--T:59-->
 
  
 
<!--T:60-->
 
<!--T:60-->
Line 214: Line 415:
  
 
<!--T:61-->
 
<!--T:61-->
You can try to raise the limit by [http://docs.limesurvey.org/Optional+settings&structure;=English+Instructions+for+LimeSurvey#Resources adding an optional setting to Limesurvey's config file].
+
You can try to raise the limit by [[Optional settings#Resources|adding an optional setting]] to LimeSurvey's config file.
  
 
<!--T:62-->
 
<!--T:62-->
Please mind that such local settings by an application can always be overruled by global server settings. To increase the memory limit to 128M directly on your server you could try adding:
+
Please bear in mind that changes in the default settings of an application can always be overruled by global server settings. To increase the memory limit of your sever to 128M:
 
*memory_limit = 128M to your server's main php.ini file (recommended, if you have access)
 
*memory_limit = 128M to your server's main php.ini file (recommended, if you have access)
 
*memory_limit = 128M to a php.ini file in the LimeSurvey root
 
*memory_limit = 128M to a php.ini file in the LimeSurvey root
*php_value memory_limit 32M in a .htaccess file in the LimeSurvey root
+
*php_value memory_limit 32M in a .htaccess file located in the LimeSurvey root folder
*ini_set('memory_limit', '128M'); in your config.php
+
*" ini_set('memory_limit', '128M'); " in your config.php
 +
 
 +
=Specific configuration= <!--T:63-->
 +
 
 +
 
 +
<!--T:78-->
 +
Under certain circumstances, you need to update the LimeSurvey configuration in application/config/config.php
 +
 
 +
== IE 11 and Windows 7 / Windows 8 == <!--T:128-->
 +
 
 +
<!--T:129-->
 +
There is a known issue with the session with IE 11, that leads to users not being able to finish a survey.
 +
 
 +
<!--T:130-->
 +
It is solved by giving the session a unique name.
 +
 
 +
<!--T:131-->
 +
This is done by adding this to the config file.
 +
<syntaxhighlight lang="php" enclose="pre">
 +
      // Set the name of the session
 +
        'session' => array (
 +
            'sessionName' => "YOURUNIQUESESSIONNAME",
 +
        ),
 +
</syntaxhighlight>
 +
 
 +
== Two LimeSurvey instances on same domain == <!--T:79-->
 +
 
 +
 
 +
<!--T:80-->
 +
If you run 2 LimeSurvey instances on the same domain, but within different directories, you need to update the [[Optional_settings#Yii_settings|session configuration]].
  
=Email problems= <!--T:63-->
 
  
 +
<!--T:81-->
 +
For example, if you have example.org/ls1 and example.org/ls2, update the ls1 config file:
 +
<syntaxhighlight lang="php" enclose="pre">
 +
        'session' => array (
 +
            'cookieParams' => array(
 +
                    'path' => '/ls1',
 +
                ),
 +
            ),
 +
        'request' => array(
 +
            'csrfCookie' => array( 'path' => '/ls1' )
 +
        ),
 +
</syntaxhighlight>
 
</translate>
 
</translate>

Latest revision as of 18:09, 10 September 2019

Other languages:
Deutsch • ‎English • ‎español • ‎français • ‎日本語 • ‎Nederlands • ‎русский • ‎slovenščina • ‎svenska


Help.pngThe following answers have been provided by the LimeSurvey user community. In case you do not understand something or you are unsure about what you have to do next, you can address your question(s) to the rest of community members: https://limesurvey.org/forums. For professional help, please check our list of authorized partners: https://limesurvey.com.


Getting started

If you don't want to read half the manual to get a feeling what can be done with LimeSurvey, we recommend you to watch some YouTube video tutorials:


Help.pngIf you know any good video out there, do not hesitate to share it with us.


I need a quick introduction for LimeSurvey

For a quick text introduction to LimeSurvey, check the following two links:


Important.png
We are working at the moment on introductory videos to LimeSurvey.


Survey design and layout

How can I remove index.php from the URL path to get a shorter URL

If you want to use fancy URLs (not have /index.php in every URL), please edit /application/config/config.php and change

'showScriptName' => true,

to

'showScriptName' => false,

For this to work properly, you must use an Apache webserver with a properly installed mod_rewrite module.

If you are using the Nginx http server (with php running via FastCGI) and want to use the 'urlFormat' => 'path' setting (see config.php), consider the following Nginx website configuration:

server {
    set $host_path "/PATH/TO/LIMESURVEY";
    server_name  YOUR.SERVER.FQDN;
    root /PATH/TO/LIMESURVEY;
    charset utf-8;
    try_files $uri $uri/ /index.php?r=$uri&$args;
    #Disallow reading inside php script directory, see issue with debug > 1 on note
    location ~ ^/(application|protected|framework|themes/\w+/views) {
        deny  all;
    }
    #Disallow direct read user upload files
    location ~ ^/upload/surveys/.*/fu_[a-z0-9]*$ {
        return 444;
    }
    #Disallow uploaded potential executable files in upload directory
    location ~* /upload/.*\.(pl|cgi|py|pyc|pyo|phtml|sh|lua|php|php3|php4|php5|php6|pcgi|pcgi3|pcgi4|pcgi5|pcgi6|icn)$ {
        return 444;
    }
    #avoid processing of calls to unexisting static files by yii
    location ~ \.(js|css|png|jpg|gif|swf|ico|pdf|mov|fla|zip|rar)$ {
        try_files $uri =404;
    }
    location ~ \.php$ {
        fastcgi_split_path_info  ^(.+\.php)(.*)$;
        try_files $uri index.php;
        fastcgi_pass   127.0.0.1:9000; # Change this to match your settings
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
        fastcgi_param  SCRIPT_NAME      $fastcgi_script_name;
    }
}
Help.pngThis disables access to files inside application. Some JavaScript and CSS files located within the application have to be readable with debug > 0. You can force the usage of the asset manager when the debug mode is enabled with 'use_asset_manager' => 1, in your config file (or remove application from the directory list).

The end result should look like this:


Remove index.php steps.png


How do I get rid of the * (red asterisk) of mandatory questions?

Instructions for LimeSurvey 2

In LimeSurvey 2.x, the red asterisk of mandatory questions is set within the template.css file ("asterisk" class). To hide it:

  • Open the template editor
  • Create a copy of the template you wish to modify
  • Select the "template.css" file and search for the asterix class
  • Add the following line at the end of the asterix class".asterisk {display: none;}".
  • Save template.css
  • Clear your browser cache so that the edited template.css is reloaded and not taken from cache.


Instructions for LimeSurvey 3

The instructions are similar to the ones presented above for LimeSurvey 2.

  • Access the desired theme. If it is a default theme, create a copy of it by clicking on the "extend" button.
  • Access the list of themes and click on the theme editor that corresponds to the newly created theme.
  • On the left side, you can visualise the corresponding CSS files of your theme.
  • Click on custom.css and add the following line:
.asterisk {display: none;}


  • Save the changes. The red asterisk that is usually displayed at the beginning of the question text is hidden.


How can I embed a flash file?

First, go to Global settings and deactivate the XSS-filter. Please also read up the implications deactivating that filter has on your instance. The following steps will not work if the filter is active.

  1. Navigate to the place in your survey where you want insert your Flash file. This can be anywhere where you can use the integrated HTML editor, for example in questions, subquestions, answers, survey welcome/end text and many more.
  2. Open the full-screen editor mode by clicking the 'LimeFitWin' button on the editor tool-bar.
  3. On the full-screen editor tool-bar you will find a little button with a Flash symbol. Click on it. A dialog box will open.
  4. In this box you can give either the path to an existing Flash file somewhere or you click the 'Browse server' button.
  5. If you clicked the 'Browse server' button you will be presented with a file browser and on the bottom an file upload field. Choose now an existing file or upload a file first.


That's it! If you find this description incomplete please update it accordingly.


Important.png
Attention : The steps to use it in LimeSurvey 3 are similar. However, we do not recommend our users to use flash files!


How do I create a survey which is open to everyone?

To create a survey that can be filled out by anyone, do not create a survey participants table! Share the survey link located on the overview panel.


Public registration - mandatory fields

If you use a survey participants table and you also allow public registration, then users will be prompted by the following message:


Non-mandatory public reg.png


As it can be observed above, only the email field is mandatory.

To have all three fields marked as being mandatory, please edit your survey theme accordingly. If you use Fruity, you have to go to the registration screen and see how the participants email field looks like:

        {# Participants email #}
        <div class='{{ aSurveyInfo.class.registerformcolrowc }} form-group row' {{ aSurveyInfo.attr.registerformcolrowc }}>
            <label {{ aSurveyInfo.attr.registerformcolrowclabel }} class='{{ aSurveyInfo.class.registerformcolrowclabel }}  control-label'> {{ gT("Email address:") }} {{ include('./subviews/registration/required.twig') }}</label>
            <div {{ aSurveyInfo.attr.registerformcolrowcdiv }}  >
                {{ C.Html.textField('register_email', aSurveyInfo.sEmail, ({'id' : 'register_email','class' : 'form-control input-sm','required' : true})) }}
            </div>
        </div>

After that, make sure to edit the first name and last name fields correspondingly by adding the label:

{{ include('./subviews/registration/required.twig') }}

and this line which makes the field mandatory to be filled out:

'required' : true

The edited file should look like this:

        {# Participants first name #}
        <div class='{{ aSurveyInfo.class.registerformcolrow }} form-group row' {{ aSurveyInfo.attr.registerformcolrow }}>
            <label for='register_firstname' class='{{ aSurveyInfo.class.registerformcolrowlabel }} control-label '>{{ gT("First name:") }} {{ include('./subviews/registration/required.twig') }}</label> {# extra label #}
            <div class="">
                {{ C.Html.textField('register_firstname', aSurveyInfo.sFirstName, ({'id' : 'register_firstname','class' : 'form-control', 'required' : true})) }} {# mandatory field #}
            </div>
        </div>

        {# Participants last name #}
        <div class='{{ aSurveyInfo.class.registerformcolrowb }} form-group row' {{ aSurveyInfo.attr.registerformcolrowb }}>
            <label {{ aSurveyInfo.attr.registerformcolrowblabel }}  class='{{ aSurveyInfo.class.registerformcolrowblabel }} control-label '>{{ gT("Last name:") }} {{ include('./subviews/registration/required.twig') }}</label> {# extra label #}
            <div {{ aSurveyInfo.attr.registerformcolrowbdiv }} >
                {{ C.Html.textField('register_lastname', aSurveyInfo.sLastName, ({'id' : 'register_lastname', 'class' : 'form-control', 'required' : true})) }} {# mandatory field #}
            </div>
        </div>


Now, the public registration page should look like this (all the fields being mandatory):


Mandatory public reg.png


Hiding the language switcher

The steps to hide both the language switchers (near the survey title and on the top-right side of the page) are described in our wiki section dedicated to multilingual surveys.


Hiding "Exit and clear survey"

In case you wish to hide the button "Exit and clear survey", you have to edit the nav_bar.twig file located inside your survey theme.


Exit and clear survey pic.png


The line that needs to be removed (or commented out) is:

{{ include('./subviews/navigation/clearall_links.twig') }}


Hide exit and clear survey.png


Now, there is no option to exit and clear the survey.


No exit clear survey.png


Help.png Note: This customization can be used when you create long surveys and require from your respondents to save and resume later the survey. Sometimes, the users tend to click the "Exit and clear survey" button which deletes the entry from the partially completed responses table.

Help, I accidentally...

I forgot my admin password. How do I reset it?

Version 2.x

  1. Access to your server with a command line (ssh for example)
  2. Ensure you have php command line access (see http://php.net/features.commandline.php).
  3. Go to your LimeSurvey directory
  4. Launch this command php application/commands/starter.php resetpassword NEW_ADMIN_NAME NEW_ADMIN_PASS or php application/commands/console.php resetpassword NEW_ADMIN_NAME NEW_ADMIN_PASSThe php can need complete directory access, example /usr/bin/php


Important.png
Please note that this method will not work in LimeSurvey 3.x!


Version 2.x.x and newer with only FTP access

See ResetPasswordController


Directly change the password in the database

If you have direct access to the Limesurvey database you can change the old password there by uploading the new password as SHA256 hash. You can create the SHA256 hash of your password here.

For example, you can use this instruction to set password to password:

UPDATE lime_users SET password = 0x35653838343839386461323830343731353164306535366638646336323932373733363033643064366161626264643632613131656637323164313534326438 WHERE uid =1;

Here with prefix to lime_ and database selected.


How can I restore data from a deactivated survey?

We recommend to always use the time-out option instead of deactivating a survey. If you closed your survey accidentally, it is important that you don't change anything in the survey!

Then, and only then the following steps will work:

  1. Activate your survey again
  2. Select Responses from the survey toolbar.
  3. Click on Import and select the "Import answers from a deactivated survey table" menu entry.
  4. Choose your source table.
  5. Click on the "Import" button located on the upper-right part of the screen.


Help.pngTo understand the difference between "expiry" and "deactivation", visit this following wiki section.


I deleted a question/question group/survey!

If you delete it, it is gone. Only a backup could help you recover it.


Help.pngIf you are a LimeSurvey GmbH professional user, please open a support ticket and ask the team to provide you the backup associated to your account. Please note that this service is not free of charge!


Hard- and Software requirements

For general requirements please refer to our installation instructions.


What limitations does LimeSurvey have...

...regarding speed

There is no existing speed limit on LimeSurvey. Everything depends on how fast your server and your connection are. If you expect a large number of users within a short amount of time and you are not sure if your server can handle this, check our forum for similar topics! or contact an authorized LimeSurvey partner: https://limesurvey.com.

...regarding survey size

Note: 'Survey size' refers to the maximum number of questions (and answers) in your survey - don't confuse this with the number of replies on your survey (there is no limitation on that). Theoretically there would also be no limit on the maximum number of questions/answers in LimeSurvey. But the database engine you are using has several limits. The most important one is the limit on the number of fields(columns) in the result table.

  • MySQL ISAM: The sum of the lengths of the VARCHAR and CHAR columns in a table may be up to 64KB.
  • MySQL InnoDB: Maximum number of 1000 columns
  • MS SQL Server 2000: Maximum number of 1024 columns
  • Postgres: Maximum number of 250-1600 columns depending on column types. The maximum number of columns can be quadrupled by increasing the default block size to 32k. See Installation FAQ and PostgreSQL FAQ.
Important.png
Attention : Please think about what you do before you do it! An array of 10 x 10 items already costs you 100 columns. Rule of thumb: every item on the screen that can be filled in or selected costs one column!

The mySQL ISAM engine is the most tricky one (see mysql documentation for more information). As it allows only up to 65,535 bytes per row and utf8 characters, it can require up to three bytes per character. The maximum may be only 21,844 characters (but this depends on your DB encoding).

You can roughly calculate the size of your survey like this:

  • Every multiple numerical question: 20 chars for each answer
  • Every multiple choice & array question answers: 5 chars for each answer
  • Every other question type: 5 chars
  • Add 10% for the usual overhead

How to increase the maximum number of columns in PostgreSQL

In case your survey contains too many questions, you can define a different block size in PostgreSQL to create more columns. This might be tricky because you have to recompile PostgreSQL and set BLCKSZ to a higher value, like 16kiB or 32kiB. Watch for the configuration option "--with-blocksize=BLOCKSIZE". For details see the archives of the PostgreSQL mailing list or ask there (pgsql-patches(at)postgresql(dot)org).

Instructions for Debian (thanks to Martin Pitt):

sudo apt-get build-dep postgresql-8.3
apt-get source postgresql-8.3
cd postgresql-8.3-*
debian/rules patch
sensible-editor build-tree/postgresql-8.3.5/src/include/pg_config_manual.h
dpkg-buildpackage -us -uc -b -nc

Note: the above could not be reproduced on Ubuntu 14.04 in August 2014. A patch is required (the configuration option is not enough). See (tested with PostgreSQL 9.3 on Linux): Instructions for increasing the maximum number of columns in PostgreSQL on Linux

Fatal error: Allowed memory size

Depending on your server configuration you might run into memory problems being reported by an error like "Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 233472 bytes) in /path/to/htdocs/limesurvey/filename.php on line 7296".

You can try to raise the limit by adding an optional setting to LimeSurvey's config file.

Please bear in mind that changes in the default settings of an application can always be overruled by global server settings. To increase the memory limit of your sever to 128M:

  • memory_limit = 128M to your server's main php.ini file (recommended, if you have access)
  • memory_limit = 128M to a php.ini file in the LimeSurvey root
  • php_value memory_limit 32M in a .htaccess file located in the LimeSurvey root folder
  • " ini_set('memory_limit', '128M'); " in your config.php

Specific configuration

Under certain circumstances, you need to update the LimeSurvey configuration in application/config/config.php

IE 11 and Windows 7 / Windows 8

There is a known issue with the session with IE 11, that leads to users not being able to finish a survey.

It is solved by giving the session a unique name.

This is done by adding this to the config file.

       // Set the name of the session
        'session' => array (
            'sessionName' => "YOURUNIQUESESSIONNAME",
        ),

Two LimeSurvey instances on same domain

If you run 2 LimeSurvey instances on the same domain, but within different directories, you need to update the session configuration.


For example, if you have example.org/ls1 and example.org/ls2, update the ls1 config file:

        'session' => array (
            'cookieParams' => array(
                    'path' => '/ls1',
                ),
            ),
        'request' => array(
            'csrfCookie' => array( 'path' => '/ls1' )
        ),