Actions

General FAQ/sv: Difference between revisions

From LimeSurvey Manual

(Updating to match new version of source page)
(Updating to match new version of source page)
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<languages />  
<languages />  
__TOC__
__TOC__
{{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://forums.limesurvey.org. For professional help, please check our list of authorized partners: https://limesurvey.com.}}


=Att komma ig&aring;ng=
=Att komma ig&aring;ng=


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).


Efter det är manualsidan: [[Skapa enkäter &ndash; En introduktion]] förmodligen en bra start.
<div class="mw-translate-fuzzy">
Om du inte vill läsa halva manualen för att f&aring; en känsla över vad som kan &aring;stadkommas genom LimeSurvey rekommenderar vi dig att kolla p&aring; n&aring;gra filmer (se nedanför).
</div>
 
*[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]
 
 
{{Note|If you know any good video out there, do not hesitate to share it with us.}}
 


==Jag behöver en snabb introduktion till LimeSurvey==
==Jag behöver en snabb introduktion till LimeSurvey==


Om det är första g&aring;ngen, kolla p&aring; filmen [[LimeSurvey Video-Tutorial]], vilket är en väldigt grundläggande film.


Det finns [http://vimeo.com/4951738 en annan genomg&aring;ng] som visar dig hur kommer ig&aring;ng med att använda LimeSurvey för att skapa webbenkäter. I [http://vimeo.com/4951738 denna film] skapar vi v&aring;r första enkät, levererar den till en användare och sedan kollar över svaren.
For a quick text introduction to LimeSurvey, check the following two links:


Det finns '''ännu mer p&aring; YouTube''':
*[[Quick start guide - LimeSurvey 2.50+|LimeSurvey 2.50+]]
*[[Quick start guide - LimeSurvey 3.0+|Limesurvey 3+]]


'''''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]


'''''Äldre PHP-surveyor filmer:'''''
{{Alert|We are working at the moment on introductory videos to LimeSurvey.}}
*[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]


=Enkätdesign och enkätlayout=
=Enkätdesign och enkätlayout=


==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


<syntaxhighlight lang="php" enclose="div">'showScriptName' => true,</syntaxhighlight>
==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
 
<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>


to
to


<syntaxhighlight lang="php" enclose="div">'showScriptName' => false,</syntaxhighlight>
<syntaxhighlight lang="php">'showScriptName' => false,</syntaxhighlight>


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


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, consider the following Nginx site configuration:
===With nginx webserver===
 
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:


<syntaxhighlight lang="apache">server {
<syntaxhighlight lang="apache">server {
Line 51: Line 63:
     root /PATH/TO/LIMESURVEY;
     root /PATH/TO/LIMESURVEY;
     charset utf-8;
     charset utf-8;
     try_files $uri /index.php?$args;
     try_files $uri /index.php?$uri&$args;
     location ~ ^/(protected|framework|themes/\w+/views) {
    # Disallow reading inside php script directory, see issue with debug > 1 on note
     location ~ ^/(application|docs|framework|locale|protected|tests|themes/\w+/views) {
         deny  all;
         deny  all;
    }
    # Disallow reading inside runtime directory
    location ~ ^/tmp/runtime/ {
        deny  all;
    }
    # Allow access to well-known directory, different usage, for example ACME Challenge for Let's Encrypt
    location ~ /\.well-known {
        allow all;
    }
    # Deny all attempts to access hidden files
    # such as .htaccess, .htpasswd, .DS_Store (Mac).
        location ~ /\. {
        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
     #avoid processing of calls to unexisting static files by yii
Line 69: Line 104:
     }
     }
}</syntaxhighlight>
}</syntaxhighlight>
{{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>).}}
The end result should look like this:
<center>[[File:Remove index.php steps.png]]</center>


==Hur blir jag av med <span style='color:red'>*</span> (röd asterisk) p&aring; obligatoriska fr&aring;gor?==
==Hur blir jag av med <span style='color:red'>*</span> (röd asterisk) p&aring; obligatoriska fr&aring;gor?==


===Instructions for LimeSurvey 2===
<div class="mw-translate-fuzzy">
I '''LimeSurvey Version 1.80 och högre''' är den röda asterisken p&aring; obligatoriska fr&aring;gor definierade av template.css fil (klassen "asterisk"). För att gömma den:
I '''LimeSurvey Version 1.80 och högre''' är den röda asterisken p&aring; obligatoriska fr&aring;gor definierade av template.css fil (klassen "asterisk"). För att gömma den:
*Öppna mallhanteraren
*Öppna mallhanteraren
Line 79: Line 126:
*Spara template.css
*Spara template.css
*Rensa din webbläsares cache s&aring; att den redigerade filen blir laddat p&aring; nytt och inte bli inläst fr&aring;n cachen
*Rensa din webbläsares cache s&aring; att den redigerade filen blir laddat p&aring; nytt och inte bli inläst fr&aring;n cachen
</div>


I '''LimeSurvey Version 1.53''' är den röda asterisken p&aring; obligatoriska fr&aring;gor definierad i css-klassen "asterisk". För att dölja den:
*Öppna mallhanteraren
*Välj den mall du önskar att redigera
*Välj filen "startpage.pstpl"
*Addera ".asterisk {display: none;}" i css stylesheet


'''Tidigare Versioner'''
===Instructions for LimeSurvey 3===
*Öppna qanda.php I önskad textredigerare
 
*Sök efter strängen "asterisk"
 
*Kommentera  ut denna rad med tv&aring; stycken, // i början av raden
The instructions are similar to the ones presented above for LimeSurvey 2.
*Exempel:
 
**original: $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.
**redigerad: // $qtitle = '<span class=\'asterisk\'>'.$clang->gT('*').'</span>'.$qtitle;
* 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:
 
<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>
 
 
* Save the changes. The red asterisk that is usually displayed at the beginning of the question text is hidden.
 


==Hur kan jag inbädda en flashvideo?==
==Hur kan jag inbädda en flashvideo?==


<div class="mw-translate-fuzzy">
Först, g&aring; till [[Globala inställningar]] och avaktivera XSS-filter. Men läs p&aring; om de komplikationer som kan uppst&aring; när man inaktiverar det filtret. Följande steg kommer inte att fungera om inte filtret är inaktivt.
Först, g&aring; till [[Globala inställningar]] och avaktivera XSS-filter. Men läs p&aring; om de komplikationer som kan uppst&aring; när man inaktiverar det filtret. Följande steg kommer inte att fungera om inte filtret är inaktivt.
#Navigera till det ställe I din enkät där du vill placera din Flashvideo. Detta kan göras vart som helst där du kan använda den integrerade HTML redigeraren, till exempel i dina fr&aring;gor, subfr&aring;gor, svar, välkomstmeddelande/sluttext och mycket mer.
#Navigera till det ställe I din enkät där du vill placera din Flashvideo. Detta kan göras vart som helst där du kan använda den integrerade HTML redigeraren, till exempel i dina fr&aring;gor, subfr&aring;gor, svar, välkomstmeddelande/sluttext och mycket mer.
Line 102: Line 155:
#I denna dialog kan du antingen ange en sökväg till en redan existerande Flash-fil n&aring;gonstans ELLER s&aring; kan du klicka p&aring; knappen &rsquo;Bläddra i server&rsquo;.
#I denna dialog kan du antingen ange en sökväg till en redan existerande Flash-fil n&aring;gonstans ELLER s&aring; kan du klicka p&aring; knappen &rsquo;Bläddra i server&rsquo;.
#Om du klickade p&aring; knappen &rsquo;Bläddra i server&rsquo; kommer du att bli presenterad en filhanterare och i botten ett fält för uppladdning av filer. Välj  nu en redan existerande fil eller ladda upp den först.
#Om du klickade p&aring; knappen &rsquo;Bläddra i server&rsquo; kommer du att bli presenterad en filhanterare och i botten ett fält för uppladdning av filer. Välj  nu en redan existerande fil eller ladda upp den först.
</div>


Nu är det klart! Om du tycker att denna beskrivning saknar n&aring;got f&aring;r du gärna uppdatera den.
Nu är det klart! Om du tycker att denna beskrivning saknar n&aring;got f&aring;r du gärna uppdatera den.


==Hur man tar bort n&aring;gra av dessa texter fr&aring;n enkäten==


==="Den här enkäten inneh&aring;ller X fr&aring;gor"===
{{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!}}
 
 
==Hur skapar jag en enkät som är öppen för alla?==
 
 
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==
 
 
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:
 
 
<center>[[File:non-mandatory public reg.png]]</center>
 
 
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:
 
<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>
 
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>
 
The edited file should look like this:
 
<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>
 
        {# 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>
 
 
Now, the public registration page should look like this (all the fields being mandatory):
 
 
<center>[[File:mandatory public reg.png]]</center>
 
 
== Hiding the language switcher ==


===En kommentar om personuppgifter===


===fr&aring;gekod===
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]].


All these texts are inserted at the template you are using by [[The template editor#Replacements_Field_Strings|placeholders]]. You can easily remove them. Go to the [[The template editor|Template Editor]] and remove the {THEREAREXQUESTIONS} / {PRIVACYMESSAGE} / {QUESTION_CODE} placeholder(s).


=Enkät inställningar=
== Hiding "Exit and clear survey" ==


==Hur skapar jag en enkät som är öppen för alla?==


To make a survey public to everyone you should:
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.
* not [[Tokens#How_to_activate_tokens?|create a token table]] (if there is one, drop it)
 
* at survey settings set "[[Creating a new survey#Publication & access control|Only users with tokens may enter the survey]]" = no (old setting)
 
* at survey settings set "[[Creating a new survey#Tokens|Allow public registration]]" = no
<center>[[File:exit and clear survey pic.png]]</center>
* at survey settings set "[[Creating a new survey#Publication & access control|List survey publicly]]"
 
 
The line that needs to be removed (or commented out) is:
 
<syntaxhighlight lang="twig">
{{ include('./subviews/navigation/clearall_links.twig') }}
</syntaxhighlight>
 
 
<center>[[File:Hide exit and clear survey.png]]</center>
 
 
Now, there is no option to exit and clear the survey.
 


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==


If you are [[Tokens#Emails_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 [[First login - Your user preferences#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...=
=Help, I accidentally...=


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


=== version 2.00 ===
 
=== Version 2.x ===
# Access to your server with a command line (ssh for example)
# 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).
# Ensure you have php command line access (see http://php.net/features.commandline.php).
# Go to your limesurvey directory
# Go to your LimeSurvey directory
# Launch this command <code>php application/commands/starter.php resetpassword NEW_ADMIN_NAME NEW_ADMIN_PASS</code><sup>The php can need complete directory access, example /usr/bin/php</sup>
# 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>
 
 
{{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===


=== Directly change the password at the database ===
 
See [https://gitlab.com/SondagesPro/coreAndTools/ResetPasswordController 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 [http://www.xorbin.com/tools/sha256-hash-calculator create the SHA256 hash of your password here].
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].


For example, you can use this instruction to set password to password:
For example, you can use this instruction to set password to password:
<syntaxhighlight lang="sql" enclose="div">
<syntaxhighlight lang="sql">
UPDATE lime_users SET password = 0x35653838343839386461323830343731353164306535366638646336323932373733363033643064366161626264643632613131656637323164313534326438 WHERE uid =1;
UPDATE lime_users SET password = 0x35653838343839386461323830343731353164306535366638646336323932373733363033643064366161626264643632613131656637323164313534326438 WHERE uid =1;
</syntaxhighlight>
</syntaxhighlight>
Here with prefix to lime_ and database selected.
Here with prefix to lime_ and database selected.


=== version 1.47 to 1.53 only ===
# Download [[Media:resetadminpw.php|this file]] and copy it to /<your limesurveydir>/admin/install/ .


=== version 1.7 to 1.92 ===
==How can I restore data from a deactivated survey?==
# 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>
# After removing the /install directory again you should be able to login with $defaultuser (Default: admin) and $defaultpass (Default: password) set in config.php.


==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.
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:
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.
 
 
{{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!==
==I deleted a question/question group/survey!==


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.
 
 
{{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=
=Hard- and Software requirements=


For general requirements please refer to our [[Installation#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...==
==What limitations does LimeSurvey have...==


=== ...regarding speed===
=== ...regarding speed===


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===
=== ...regarding survey size===


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.
==== MySQL and MariaDB ====
 
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. [https://docs.microsoft.com/en-us/sql/sql-server/maximum-capacity-specifications-for-sql-server There are a maximum of 8,060 bytes for size one row], then even is survey can be activated, if you have a lot of text data : participant can not submit…
*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].


'''Take care here:''' 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!
{{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!}}


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).


You can roughly calculate the size of your survey like this:
You can roughly calculate the size of your survey like this:
Line 201: Line 346:
*Add 10% for the usual overhead
*Add 10% for the usual overhead


==How to increase the maximum number of columns in PostgreSQL==
==== With Microsoft SQL ====
 
There are no fixed limit on MSSQL. Some [https://docs.microsoft.com/en-us/sql/sql-server/maximum-capacity-specifications-for-sql-server?view=sql-server-ver15 information on microsoft website].
 
The 8,060 bytes per row can appear after activation when you want to browse response and data. You can export answer code and not answer text or try to export only some columns.
 
====With PostgreSQL====
 
When you try to export response : you can have SQLSTATE[54000] error. You can export some columns. See [https://forums.limesurvey.org/forum/french-forum/125447-erreur-sqlstate-54000 forum post].


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).
=====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):
Instructions for Debian (thanks to Martin Pitt):
Line 214: Line 370:
dpkg-buildpackage -us -uc -b -nc</syntaxhighlight>
dpkg-buildpackage -us -uc -b -nc</syntaxhighlight>


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):
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]]
[[Instructions for increasing the maximum number of columns in PostgreSQL on Linux]]


==Fatal error: Allowed memory size==
==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"''.
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"''.
Line 223: Line 380:
You can try to raise the limit by [[Optional settings#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.


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=
=Specific configuration=


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


== 2 limesurvey instance on same domain ==
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.
<syntaxhighlight lang="php" enclose="pre">
      // Set the name of the session
        'session' => array (
            'sessionName' => "YOURUNIQUESESSIONNAME",
        ),
</syntaxhighlight>
 
== 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 [[Optional_settings#Yii_settings|session configuration]].


With 2 limesurvey instance on same domain, but different directory, you need to update the [[Optional_settings#Yii_settings|session configuration]].


For example, if you have example.org/ls1 and example.org/ls2 : update the ls1 config file
For example, if you have example.org/ls1 and example.org/ls2, update the ls1 config file:
<syntaxhighlight lang="php" enclose="pre">
<syntaxhighlight lang="php" enclose="pre">
         'session' => array (
         'session' => array (

Latest revision as of 15:50, 28 March 2023


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://forums.limesurvey.org. For professional help, please check our list of authorized partners: https://limesurvey.com.


Att komma igång

Om du inte vill läsa halva manualen för att få en känsla över vad som kan åstadkommas genom LimeSurvey rekommenderar vi dig att kolla på några filmer (se nedanför).


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


Jag behöver en snabb introduktion till LimeSurvey

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


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



Enkätdesign och enkätlayout

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.

With nginx webserver

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 /index.php?$uri&$args;
    # Disallow reading inside php script directory, see issue with debug > 1 on note
    location ~ ^/(application|docs|framework|locale|protected|tests|themes/\w+/views) {
        deny  all;
    }
    # Disallow reading inside runtime directory
    location ~ ^/tmp/runtime/ {
        deny  all;
    }

    # Allow access to well-known directory, different usage, for example ACME Challenge for Let's Encrypt
    location ~ /\.well-known {
        allow all;
    }
    # Deny all attempts to access hidden files
    # such as .htaccess, .htpasswd, .DS_Store (Mac).
        location ~ /\. {
        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;
    }
}
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 'use_asset_manager' => 1, in your config file (or remove application from the directory list).

The end result should look like this:


Hur blir jag av med * (röd asterisk) på obligatoriska frågor?

Instructions for LimeSurvey 2

I LimeSurvey Version 1.80 och högre är den röda asterisken på obligatoriska frågor definierade av template.css fil (klassen "asterisk"). För att gömma den:

  • Öppna mallhanteraren
  • Skapa en kopia av mallen du vill redigera
  • Välj filen "template.css" och sök efter asteriskklassen
  • Lägg till följande rad i slutet av asteriskklassen ".asterisk {display: none;}"
  • Spara template.css
  • Rensa din webbläsares cache så att den redigerade filen blir laddat på nytt och inte bli inläst från cachen


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.


Hur kan jag inbädda en flashvideo?

Först, gå till Globala inställningar och avaktivera XSS-filter. Men läs på om de komplikationer som kan uppstå när man inaktiverar det filtret. Följande steg kommer inte att fungera om inte filtret är inaktivt.

  1. Navigera till det ställe I din enkät där du vill placera din Flashvideo. Detta kan göras vart som helst där du kan använda den integrerade HTML redigeraren, till exempel i dina frågor, subfrågor, svar, välkomstmeddelande/sluttext och mycket mer.
  2. Öppna redigeraren i fullskärmsläge genom att klicka på 'LimeFitWin' knappen, placerad i verktygsfältet.
  3. I fullskärmsläget hittar du en liten knapp med en Flash-symbol. Klicka på den. En dialog öppnas.
  4. I denna dialog kan du antingen ange en sökväg till en redan existerande Flash-fil någonstans ELLER så kan du klicka på knappen ’Bläddra i server’.
  5. Om du klickade på knappen ’Bläddra i server’ kommer du att bli presenterad en filhanterare och i botten ett fält för uppladdning av filer. Välj  nu en redan existerande fil eller ladda upp den först.


Nu är det klart! Om du tycker att denna beskrivning saknar något får du gärna uppdatera den.


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



Hur skapar jag en enkät som är öppen för alla?

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:



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):



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.



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

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



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



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


  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.


To 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.


If 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

MySQL and MariaDB

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. There are a maximum of 8,060 bytes for size one row, then even is survey can be activated, if you have a lot of text data : participant can not submit…
  • 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.
  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

With Microsoft SQL

There are no fixed limit on MSSQL. Some information on microsoft website.

The 8,060 bytes per row can appear after activation when you want to browse response and data. You can export answer code and not answer text or try to export only some columns.

With PostgreSQL

When you try to export response : you can have SQLSTATE[54000] error. You can export some columns. See forum post.

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' )
        ),