LimeSurvey Manual - User contributions [en]

General FAQ/ko

2024-07-12T07:54:02Z

Rhami: Created page with "에서 다음으로 편집하세요"

<languages />

__TOC__

{{참고|다음 답변은 LimeSurvey 사용자 커뮤니티에서 제공되었습니다. 이해하지 못하는 부분이 있거나 다음에 수행해야 할 작업이 확실하지 않은 경우에는 https://forums.limesurvey.org에서 커뮤니티 구성원에게 질문할 수 있습니다. 전문적인 도움이 필요하시면 공인 파트너 목록을 확인하세요: https://limesurvey.com.}}

<span id="Getting_started"></span>
=시작하기=

메뉴얼의 절반을 읽고도 LimeSurvey로 무엇을 할 수 있는지 감을 잡기 어렵다면, YouTube 튜토리얼 동영상 시청을 권장합니다.

*[https://www.youtube.com/watch?v=oyoq14XpkwA 계정 설정 및 설문조사 설치 방법]
*[https://www.youtube.com/watch?v=7134QebOQzY 문항 유형 - 배열]
*[https://www.youtube.com/watch?v=aeb93vAe7R4 평가(Assessments)]
*[https://www.youtube.com/watch?v=s5OOzDoPjIU 도움말 설정(Placeholder fields)]
*[https://www.youtube.com/watch?v=7N4xUQMWbJY 라디오 목록]
*[https://www.youtube.com/watch?v=UI01hwrsiVk 설문조사 복사/가져오기]
*[https://www.youtube.com/watch?v=QEHyH1YbNEQ 문항 가져오기]

{{참고|좋은 동영상을 알고 있다면 주저하지 말고 공유해 주세요.}}

<span id="I_need_a_quick_introduction_for_LimeSurvey"></span>
==LimeSurvey에 대한 간단한 소개가 필요합니다==

LimeSurvey에 대한 빠른 텍스트 소개를 보려면 다음 두 링크를 확인하세요.

*[[빠른 시작 가이드 - LimeSurvey 2.50+|LimeSurvey 2.50+]]
*[[빠른 시작 가이드 - LimeSurvey 3.0+|Limesurvey 3+]]

{{Alert|현재 LimeSurvey 소개 동영상을 제작 중입니다.}}

<span id="Survey_design_and_layout"></span>
=설문조사 디자인 및 레이아웃=

<span id="How_can_I_remove_index.php_from_the_URL_path_to_get_a_shorter_URL"></span>
==더 짧은 URL을 얻기 위해 어떻게 URL 경로에서 index.php를 제거할 수 있습니까?==

(모든 URL에 /index.php가 없는)멋진 URL을 사용하려면 /application/config/config.php를 편집하고 변경하세요.

<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>

에서 다음으로 편집하세요

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

이 기능이 제대로 작동하려면 mod_rewrite 모듈이 올바르게 설치된 Apache 웹서버를 사용해야 합니다.

<span id="With_nginx_webserver"></span>
===nginx 웹서버 사용하기===

[http://nginx.com/products/ Nginx] http 서버(FastCGI를 통해 실행되는 PHP 포함)를 사용하고 있고 ''''urlFormat' => 'path'''' 설정을 사용하려는 경우(config.php 참조), 다음 Nginx 웹사이트 구성을 고려하세요.

<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 /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;
}
}</syntaxhighlight>

{{Note|이 경우 애플리케이션 내부의 파일에 액세스 할 수 없습니다. 애플리케이션 내에 있는 일부 JavaScript 및 CSS 파일은 디버그 > 0으로 읽을 수 있어야 합니다. 구성 파일에서 <code><nowiki>'use_asset_manager' => 1,</nowiki></code> 로 디버그 모드를 활성화하면(또는 디렉토리 목록에서 <code><nowiki>application</nowiki></code>을 제거하면) 에셋 매니저의 사용을 강제할 수 있습니다.}}

최종 결과는 다음과 같아야 합니다.

<center>[[File:Remove index.php steps.png]]</center>

<span id="How_do_I_get_rid_of_the_*_(red_asterisk)_of_mandatory_questions?"></span>
==필수 질문의 <span style='color:red'>*</span> (빨간색 별표)는 어떻게 없애나요?==

<span id="Instructions_for_LimeSurvey_2"></span>
===LimeSurvey 2 지침===

LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면:
*템플릿 편집기를 엽니다
*수정하려는 템플릿의 복사본을 만듭니다
*"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다
*별표 클래스 끝에 다음 라인을 추가합니다".asterisk {display: none;}".
*template.css를 저장하세요
*브라우저 캐시를 지우면 편집한 template.css를 캐시에서 가져오지 않고 다시 로드됩니다.

<span id="Instructions_for_LimeSurvey_3"></span>
===LimeSurvey 3 지침===

위 지침은 LimeSurvey 2에 대해 위에 제시된 지침과 유사합니다.

* 원하는 테마에 접속하세요. 기본 테마인 경우 "확장" 버튼을 클릭하여 복사본을 만듭니다.
* 테마 목록에 접속하여 새로 생성된 테마에 해당하는 '''테마 편집기'''를 클릭합니다.
* 왼쪽에서는 테마에 해당하는 CSS 파일을 시각화할 수 있습니다.
* custom.css를 클릭하고 다음 줄을 추가합니다.

<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>

* 변경 사항을 저장합니다. 일반적으로 질문 텍스트 시작 부분에 표시되는 빨간색 별표가 숨겨져 있습니다.

<span id="How_can_I_embed_a_flash_file?"></span>
==플래시 파일을 어떻게 삽입하나요?==

먼저 [[Global settings]]로 이동하여 XSS 필터를 비활성화합니다. 필터 비활성화가 인스턴스에 미치는 영향도 읽어보세요. 필터가 활성화된 경우 다음 단계는 작동하지 '''않습니다'''.
#플래시 파일을 삽입하려는 설문조사 위치로 이동하세요. 예를 들어 질문, 하위 질문, 답변, 설문조사 시작/종료 텍스트 등 통합 HTML 편집기를 사용할 수 있는 곳이면 어디든 가능합니다.
#[[첫 번째 로그인 - 사용자 기본 설정#팝업|full- 화면 편집기 모드]] 편집기 도구 모음에서 'LimeFitWin' 버튼을 클릭하면 됩니다.
#전체 화면 편집기 도구 모음에는 플래시 기호가 있는 작은 버튼이 있습니다. 그것을 클릭하세요. 대화 상자가 열립니다.
#이 상자에서 기존 플래시 파일의 경로를 어딘가에 제공하거나 '서버 찾아보기' 버튼을 클릭할 수 있습니다.
#'서버 찾아보기' 버튼을 클릭하면 파일 브라우저와 하단에 파일 업로드 필드가 표시됩니다. 지금 기존 파일을 선택하거나 먼저 파일을 업로드하세요.

여기까지입니다! 이 설명이 불완전하다고 생각되시면 적절하게 업데이트 해주십시오.

{{Alert|title=Attention|text=LimeSurvey 3에서도 이의 사용 과정은 유사합니다. 그러나 플래시 파일을 사용하지 않는 것을 권장합니다!}}

<span id="How_do_I_create_a_survey_which_is_open_to_everyone?"></span>
==모든 사람에게 공개되는 설문조사를 만들려면 어떻게 해야 하나요?==

누구나 작성할 수 있는 설문조사를 만들려면 [[설문조사 참가자|설문조사 참가자 테이블]]을 생성하지 마세요! [[개요|개요 패널]]에 있는 설문조사 링크를 공유하세요.

<span id="Public_registration_-_mandatory_fields"></span>
==공개 등록하기 - 필수 항목==

[[설문 참가자|설문 참가자 테이블]]을 사용하고 [[Participant_settings#Allow_public_registration|공개 등록]]도 허용하는 경우 사용자에게 다음 메시지가 표시됩니다.

<center>[[File:non-mandatory public reg.png]]</center>

위와 같이, 이메일 필드만 필수 항목입니다.

세 가지 필드를 모두 필수 항목으로 표시하려면 그에 따라 설문조사 테마를 편집하세요. '''Fruity'''를 사용하는 경우 '''등록''' 화면으로 이동하여 참가자 이메일 필드가 어떻게 보이는지 확인해야 합니다.

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

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

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.

<center>[[File:exit and clear survey pic.png]]</center>

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.

<center>[[File:no exit clear survey.png]]</center>

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

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

=== Version 2.x ===
# 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>

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

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

For example, you can use this instruction to set password to password:
<syntaxhighlight lang="sql">
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?==

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:
#Activate your survey again
#Select [[Responses]] from the survey toolbar.
#Click on [[Import responses|Import]] and select the "Import answers from a deactivated survey table" menu entry.
#Choose your source table.
#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!==

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=

For general requirements please refer to our [[Installation#Make sure you can use LimeSurvey on your website|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. [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].

{{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, 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 [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].

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

<syntaxhighlight lang="bash">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</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):
[[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 [[Optional settings#Resources|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.
<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]].

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>

Translations:General FAQ/67/ko

2024-07-12T07:53:37Z

Rhami: Created page with "<syntaxhighlight lang="php">'showScriptName' => false,</syntaxhighlight>"

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

Translations:General FAQ/66/ko

2024-07-12T07:53:34Z

Rhami: Created page with "에서 다음으로 편집하세요"

에서 다음으로 편집하세요

Translations:General FAQ/65/ko

2024-07-12T07:53:14Z

Rhami: Created page with "<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>"

<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>

General FAQ/ko

2024-07-12T07:53:02Z

Rhami: Created page with "세 가지 필드를 모두 필수 항목으로 표시하려면 그에 따라 설문조사 테마를 편집하세요. '''Fruity'''를 사용하는 경우 '''등록''' 화면으로 이동하여 참가자 이메일 필드가 어떻게 보이는지 확인해야 합니다."

<languages />

__TOC__

{{참고|다음 답변은 LimeSurvey 사용자 커뮤니티에서 제공되었습니다. 이해하지 못하는 부분이 있거나 다음에 수행해야 할 작업이 확실하지 않은 경우에는 https://forums.limesurvey.org에서 커뮤니티 구성원에게 질문할 수 있습니다. 전문적인 도움이 필요하시면 공인 파트너 목록을 확인하세요: https://limesurvey.com.}}

<span id="Getting_started"></span>
=시작하기=

메뉴얼의 절반을 읽고도 LimeSurvey로 무엇을 할 수 있는지 감을 잡기 어렵다면, YouTube 튜토리얼 동영상 시청을 권장합니다.

*[https://www.youtube.com/watch?v=oyoq14XpkwA 계정 설정 및 설문조사 설치 방법]
*[https://www.youtube.com/watch?v=7134QebOQzY 문항 유형 - 배열]
*[https://www.youtube.com/watch?v=aeb93vAe7R4 평가(Assessments)]
*[https://www.youtube.com/watch?v=s5OOzDoPjIU 도움말 설정(Placeholder fields)]
*[https://www.youtube.com/watch?v=7N4xUQMWbJY 라디오 목록]
*[https://www.youtube.com/watch?v=UI01hwrsiVk 설문조사 복사/가져오기]
*[https://www.youtube.com/watch?v=QEHyH1YbNEQ 문항 가져오기]

{{참고|좋은 동영상을 알고 있다면 주저하지 말고 공유해 주세요.}}

<span id="I_need_a_quick_introduction_for_LimeSurvey"></span>
==LimeSurvey에 대한 간단한 소개가 필요합니다==

LimeSurvey에 대한 빠른 텍스트 소개를 보려면 다음 두 링크를 확인하세요.

*[[빠른 시작 가이드 - LimeSurvey 2.50+|LimeSurvey 2.50+]]
*[[빠른 시작 가이드 - LimeSurvey 3.0+|Limesurvey 3+]]

{{Alert|현재 LimeSurvey 소개 동영상을 제작 중입니다.}}

<span id="Survey_design_and_layout"></span>
=설문조사 디자인 및 레이아웃=

<span id="How_can_I_remove_index.php_from_the_URL_path_to_get_a_shorter_URL"></span>
==더 짧은 URL을 얻기 위해 어떻게 URL 경로에서 index.php를 제거할 수 있습니까?==

(모든 URL에 /index.php가 없는)멋진 URL을 사용하려면 /application/config/config.php를 편집하고 변경하세요.

<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>

to

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

이 기능이 제대로 작동하려면 mod_rewrite 모듈이 올바르게 설치된 Apache 웹서버를 사용해야 합니다.

<span id="With_nginx_webserver"></span>
===nginx 웹서버 사용하기===

[http://nginx.com/products/ Nginx] http 서버(FastCGI를 통해 실행되는 PHP 포함)를 사용하고 있고 ''''urlFormat' => 'path'''' 설정을 사용하려는 경우(config.php 참조), 다음 Nginx 웹사이트 구성을 고려하세요.

<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 /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;
}
}</syntaxhighlight>

{{Note|이 경우 애플리케이션 내부의 파일에 액세스 할 수 없습니다. 애플리케이션 내에 있는 일부 JavaScript 및 CSS 파일은 디버그 > 0으로 읽을 수 있어야 합니다. 구성 파일에서 <code><nowiki>'use_asset_manager' => 1,</nowiki></code> 로 디버그 모드를 활성화하면(또는 디렉토리 목록에서 <code><nowiki>application</nowiki></code>을 제거하면) 에셋 매니저의 사용을 강제할 수 있습니다.}}

최종 결과는 다음과 같아야 합니다.

<center>[[File:Remove index.php steps.png]]</center>

<span id="How_do_I_get_rid_of_the_*_(red_asterisk)_of_mandatory_questions?"></span>
==필수 질문의 <span style='color:red'>*</span> (빨간색 별표)는 어떻게 없애나요?==

<span id="Instructions_for_LimeSurvey_2"></span>
===LimeSurvey 2 지침===

LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면:
*템플릿 편집기를 엽니다
*수정하려는 템플릿의 복사본을 만듭니다
*"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다
*별표 클래스 끝에 다음 라인을 추가합니다".asterisk {display: none;}".
*template.css를 저장하세요
*브라우저 캐시를 지우면 편집한 template.css를 캐시에서 가져오지 않고 다시 로드됩니다.

<span id="Instructions_for_LimeSurvey_3"></span>
===LimeSurvey 3 지침===

위 지침은 LimeSurvey 2에 대해 위에 제시된 지침과 유사합니다.

* 원하는 테마에 접속하세요. 기본 테마인 경우 "확장" 버튼을 클릭하여 복사본을 만듭니다.
* 테마 목록에 접속하여 새로 생성된 테마에 해당하는 '''테마 편집기'''를 클릭합니다.
* 왼쪽에서는 테마에 해당하는 CSS 파일을 시각화할 수 있습니다.
* custom.css를 클릭하고 다음 줄을 추가합니다.

<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>

* 변경 사항을 저장합니다. 일반적으로 질문 텍스트 시작 부분에 표시되는 빨간색 별표가 숨겨져 있습니다.

<span id="How_can_I_embed_a_flash_file?"></span>
==플래시 파일을 어떻게 삽입하나요?==

먼저 [[Global settings]]로 이동하여 XSS 필터를 비활성화합니다. 필터 비활성화가 인스턴스에 미치는 영향도 읽어보세요. 필터가 활성화된 경우 다음 단계는 작동하지 '''않습니다'''.
#플래시 파일을 삽입하려는 설문조사 위치로 이동하세요. 예를 들어 질문, 하위 질문, 답변, 설문조사 시작/종료 텍스트 등 통합 HTML 편집기를 사용할 수 있는 곳이면 어디든 가능합니다.
#[[첫 번째 로그인 - 사용자 기본 설정#팝업|full- 화면 편집기 모드]] 편집기 도구 모음에서 'LimeFitWin' 버튼을 클릭하면 됩니다.
#전체 화면 편집기 도구 모음에는 플래시 기호가 있는 작은 버튼이 있습니다. 그것을 클릭하세요. 대화 상자가 열립니다.
#이 상자에서 기존 플래시 파일의 경로를 어딘가에 제공하거나 '서버 찾아보기' 버튼을 클릭할 수 있습니다.
#'서버 찾아보기' 버튼을 클릭하면 파일 브라우저와 하단에 파일 업로드 필드가 표시됩니다. 지금 기존 파일을 선택하거나 먼저 파일을 업로드하세요.

여기까지입니다! 이 설명이 불완전하다고 생각되시면 적절하게 업데이트 해주십시오.

{{Alert|title=Attention|text=LimeSurvey 3에서도 이의 사용 과정은 유사합니다. 그러나 플래시 파일을 사용하지 않는 것을 권장합니다!}}

<span id="How_do_I_create_a_survey_which_is_open_to_everyone?"></span>
==모든 사람에게 공개되는 설문조사를 만들려면 어떻게 해야 하나요?==

누구나 작성할 수 있는 설문조사를 만들려면 [[설문조사 참가자|설문조사 참가자 테이블]]을 생성하지 마세요! [[개요|개요 패널]]에 있는 설문조사 링크를 공유하세요.

<span id="Public_registration_-_mandatory_fields"></span>
==공개 등록하기 - 필수 항목==

[[설문 참가자|설문 참가자 테이블]]을 사용하고 [[Participant_settings#Allow_public_registration|공개 등록]]도 허용하는 경우 사용자에게 다음 메시지가 표시됩니다.

<center>[[File:non-mandatory public reg.png]]</center>

위와 같이, 이메일 필드만 필수 항목입니다.

세 가지 필드를 모두 필수 항목으로 표시하려면 그에 따라 설문조사 테마를 편집하세요. '''Fruity'''를 사용하는 경우 '''등록''' 화면으로 이동하여 참가자 이메일 필드가 어떻게 보이는지 확인해야 합니다.

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

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

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.

<center>[[File:exit and clear survey pic.png]]</center>

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.

<center>[[File:no exit clear survey.png]]</center>

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

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

=== Version 2.x ===
# 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>

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

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

For example, you can use this instruction to set password to password:
<syntaxhighlight lang="sql">
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?==

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:
#Activate your survey again
#Select [[Responses]] from the survey toolbar.
#Click on [[Import responses|Import]] and select the "Import answers from a deactivated survey table" menu entry.
#Choose your source table.
#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!==

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=

For general requirements please refer to our [[Installation#Make sure you can use LimeSurvey on your website|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. [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].

{{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, 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 [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].

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

<syntaxhighlight lang="bash">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</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):
[[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 [[Optional settings#Resources|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.
<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]].

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>

Translations:General FAQ/107/ko

2024-07-12T07:52:25Z

Rhami: Created page with "<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.registerformcolrowcdi..."

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

Translations:General FAQ/106/ko

2024-07-12T07:52:18Z

세 가지 필드를 모두 필수 항목으로 표시하려면 그에 따라 설문조사 테마를 편집하세요. '''Fruity'''를 사용하는 경우 '''등록''' 화면으로 이동하여 참가자 이메일 필드가 어떻게 보이는지 확인해야 합니다.

General FAQ/ko

2024-07-12T07:50:01Z

Rhami: Created page with "위와 같이, 이메일 필드만 필수 항목입니다."

<languages />

__TOC__

{{참고|다음 답변은 LimeSurvey 사용자 커뮤니티에서 제공되었습니다. 이해하지 못하는 부분이 있거나 다음에 수행해야 할 작업이 확실하지 않은 경우에는 https://forums.limesurvey.org에서 커뮤니티 구성원에게 질문할 수 있습니다. 전문적인 도움이 필요하시면 공인 파트너 목록을 확인하세요: https://limesurvey.com.}}

<span id="Getting_started"></span>
=시작하기=

메뉴얼의 절반을 읽고도 LimeSurvey로 무엇을 할 수 있는지 감을 잡기 어렵다면, YouTube 튜토리얼 동영상 시청을 권장합니다.

*[https://www.youtube.com/watch?v=oyoq14XpkwA 계정 설정 및 설문조사 설치 방법]
*[https://www.youtube.com/watch?v=7134QebOQzY 문항 유형 - 배열]
*[https://www.youtube.com/watch?v=aeb93vAe7R4 평가(Assessments)]
*[https://www.youtube.com/watch?v=s5OOzDoPjIU 도움말 설정(Placeholder fields)]
*[https://www.youtube.com/watch?v=7N4xUQMWbJY 라디오 목록]
*[https://www.youtube.com/watch?v=UI01hwrsiVk 설문조사 복사/가져오기]
*[https://www.youtube.com/watch?v=QEHyH1YbNEQ 문항 가져오기]

{{참고|좋은 동영상을 알고 있다면 주저하지 말고 공유해 주세요.}}

<span id="I_need_a_quick_introduction_for_LimeSurvey"></span>
==LimeSurvey에 대한 간단한 소개가 필요합니다==

LimeSurvey에 대한 빠른 텍스트 소개를 보려면 다음 두 링크를 확인하세요.

*[[빠른 시작 가이드 - LimeSurvey 2.50+|LimeSurvey 2.50+]]
*[[빠른 시작 가이드 - LimeSurvey 3.0+|Limesurvey 3+]]

{{Alert|현재 LimeSurvey 소개 동영상을 제작 중입니다.}}

<span id="Survey_design_and_layout"></span>
=설문조사 디자인 및 레이아웃=

<span id="How_can_I_remove_index.php_from_the_URL_path_to_get_a_shorter_URL"></span>
==더 짧은 URL을 얻기 위해 어떻게 URL 경로에서 index.php를 제거할 수 있습니까?==

(모든 URL에 /index.php가 없는)멋진 URL을 사용하려면 /application/config/config.php를 편집하고 변경하세요.

<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>

to

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

이 기능이 제대로 작동하려면 mod_rewrite 모듈이 올바르게 설치된 Apache 웹서버를 사용해야 합니다.

<span id="With_nginx_webserver"></span>
===nginx 웹서버 사용하기===

[http://nginx.com/products/ Nginx] http 서버(FastCGI를 통해 실행되는 PHP 포함)를 사용하고 있고 ''''urlFormat' => 'path'''' 설정을 사용하려는 경우(config.php 참조), 다음 Nginx 웹사이트 구성을 고려하세요.

<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 /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;
}
}</syntaxhighlight>

{{Note|이 경우 애플리케이션 내부의 파일에 액세스 할 수 없습니다. 애플리케이션 내에 있는 일부 JavaScript 및 CSS 파일은 디버그 > 0으로 읽을 수 있어야 합니다. 구성 파일에서 <code><nowiki>'use_asset_manager' => 1,</nowiki></code> 로 디버그 모드를 활성화하면(또는 디렉토리 목록에서 <code><nowiki>application</nowiki></code>을 제거하면) 에셋 매니저의 사용을 강제할 수 있습니다.}}

최종 결과는 다음과 같아야 합니다.

<center>[[File:Remove index.php steps.png]]</center>

<span id="How_do_I_get_rid_of_the_*_(red_asterisk)_of_mandatory_questions?"></span>
==필수 질문의 <span style='color:red'>*</span> (빨간색 별표)는 어떻게 없애나요?==

<span id="Instructions_for_LimeSurvey_2"></span>
===LimeSurvey 2 지침===

LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면:
*템플릿 편집기를 엽니다
*수정하려는 템플릿의 복사본을 만듭니다
*"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다
*별표 클래스 끝에 다음 라인을 추가합니다".asterisk {display: none;}".
*template.css를 저장하세요
*브라우저 캐시를 지우면 편집한 template.css를 캐시에서 가져오지 않고 다시 로드됩니다.

<span id="Instructions_for_LimeSurvey_3"></span>
===LimeSurvey 3 지침===

위 지침은 LimeSurvey 2에 대해 위에 제시된 지침과 유사합니다.

* 원하는 테마에 접속하세요. 기본 테마인 경우 "확장" 버튼을 클릭하여 복사본을 만듭니다.
* 테마 목록에 접속하여 새로 생성된 테마에 해당하는 '''테마 편집기'''를 클릭합니다.
* 왼쪽에서는 테마에 해당하는 CSS 파일을 시각화할 수 있습니다.
* custom.css를 클릭하고 다음 줄을 추가합니다.

<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>

* 변경 사항을 저장합니다. 일반적으로 질문 텍스트 시작 부분에 표시되는 빨간색 별표가 숨겨져 있습니다.

<span id="How_can_I_embed_a_flash_file?"></span>
==플래시 파일을 어떻게 삽입하나요?==

먼저 [[Global settings]]로 이동하여 XSS 필터를 비활성화합니다. 필터 비활성화가 인스턴스에 미치는 영향도 읽어보세요. 필터가 활성화된 경우 다음 단계는 작동하지 '''않습니다'''.
#플래시 파일을 삽입하려는 설문조사 위치로 이동하세요. 예를 들어 질문, 하위 질문, 답변, 설문조사 시작/종료 텍스트 등 통합 HTML 편집기를 사용할 수 있는 곳이면 어디든 가능합니다.
#[[첫 번째 로그인 - 사용자 기본 설정#팝업|full- 화면 편집기 모드]] 편집기 도구 모음에서 'LimeFitWin' 버튼을 클릭하면 됩니다.
#전체 화면 편집기 도구 모음에는 플래시 기호가 있는 작은 버튼이 있습니다. 그것을 클릭하세요. 대화 상자가 열립니다.
#이 상자에서 기존 플래시 파일의 경로를 어딘가에 제공하거나 '서버 찾아보기' 버튼을 클릭할 수 있습니다.
#'서버 찾아보기' 버튼을 클릭하면 파일 브라우저와 하단에 파일 업로드 필드가 표시됩니다. 지금 기존 파일을 선택하거나 먼저 파일을 업로드하세요.

여기까지입니다! 이 설명이 불완전하다고 생각되시면 적절하게 업데이트 해주십시오.

{{Alert|title=Attention|text=LimeSurvey 3에서도 이의 사용 과정은 유사합니다. 그러나 플래시 파일을 사용하지 않는 것을 권장합니다!}}

<span id="How_do_I_create_a_survey_which_is_open_to_everyone?"></span>
==모든 사람에게 공개되는 설문조사를 만들려면 어떻게 해야 하나요?==

누구나 작성할 수 있는 설문조사를 만들려면 [[설문조사 참가자|설문조사 참가자 테이블]]을 생성하지 마세요! [[개요|개요 패널]]에 있는 설문조사 링크를 공유하세요.

<span id="Public_registration_-_mandatory_fields"></span>
==공개 등록하기 - 필수 항목==

[[설문 참가자|설문 참가자 테이블]]을 사용하고 [[Participant_settings#Allow_public_registration|공개 등록]]도 허용하는 경우 사용자에게 다음 메시지가 표시됩니다.

<center>[[File:non-mandatory public reg.png]]</center>

위와 같이, 이메일 필드만 필수 항목입니다.

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

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

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.

<center>[[File:exit and clear survey pic.png]]</center>

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.

<center>[[File:no exit clear survey.png]]</center>

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

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

=== Version 2.x ===
# 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>

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

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

For example, you can use this instruction to set password to password:
<syntaxhighlight lang="sql">
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?==

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:
#Activate your survey again
#Select [[Responses]] from the survey toolbar.
#Click on [[Import responses|Import]] and select the "Import answers from a deactivated survey table" menu entry.
#Choose your source table.
#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!==

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=

For general requirements please refer to our [[Installation#Make sure you can use LimeSurvey on your website|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. [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].

{{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, 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 [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].

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

<syntaxhighlight lang="bash">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</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):
[[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 [[Optional settings#Resources|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.
<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]].

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>

Translations:General FAQ/105/ko

2024-07-12T07:49:28Z

Rhami: Created page with "위와 같이, 이메일 필드만 필수 항목입니다."

위와 같이, 이메일 필드만 필수 항목입니다.

General FAQ/ko

2024-07-12T07:48:01Z

Rhami: Created page with "<center>File:non-mandatory public reg.png</center>"

<languages />

__TOC__

{{참고|다음 답변은 LimeSurvey 사용자 커뮤니티에서 제공되었습니다. 이해하지 못하는 부분이 있거나 다음에 수행해야 할 작업이 확실하지 않은 경우에는 https://forums.limesurvey.org에서 커뮤니티 구성원에게 질문할 수 있습니다. 전문적인 도움이 필요하시면 공인 파트너 목록을 확인하세요: https://limesurvey.com.}}

<span id="Getting_started"></span>
=시작하기=

메뉴얼의 절반을 읽고도 LimeSurvey로 무엇을 할 수 있는지 감을 잡기 어렵다면, YouTube 튜토리얼 동영상 시청을 권장합니다.

*[https://www.youtube.com/watch?v=oyoq14XpkwA 계정 설정 및 설문조사 설치 방법]
*[https://www.youtube.com/watch?v=7134QebOQzY 문항 유형 - 배열]
*[https://www.youtube.com/watch?v=aeb93vAe7R4 평가(Assessments)]
*[https://www.youtube.com/watch?v=s5OOzDoPjIU 도움말 설정(Placeholder fields)]
*[https://www.youtube.com/watch?v=7N4xUQMWbJY 라디오 목록]
*[https://www.youtube.com/watch?v=UI01hwrsiVk 설문조사 복사/가져오기]
*[https://www.youtube.com/watch?v=QEHyH1YbNEQ 문항 가져오기]

{{참고|좋은 동영상을 알고 있다면 주저하지 말고 공유해 주세요.}}

<span id="I_need_a_quick_introduction_for_LimeSurvey"></span>
==LimeSurvey에 대한 간단한 소개가 필요합니다==

LimeSurvey에 대한 빠른 텍스트 소개를 보려면 다음 두 링크를 확인하세요.

*[[빠른 시작 가이드 - LimeSurvey 2.50+|LimeSurvey 2.50+]]
*[[빠른 시작 가이드 - LimeSurvey 3.0+|Limesurvey 3+]]

{{Alert|현재 LimeSurvey 소개 동영상을 제작 중입니다.}}

<span id="Survey_design_and_layout"></span>
=설문조사 디자인 및 레이아웃=

<span id="How_can_I_remove_index.php_from_the_URL_path_to_get_a_shorter_URL"></span>
==더 짧은 URL을 얻기 위해 어떻게 URL 경로에서 index.php를 제거할 수 있습니까?==

(모든 URL에 /index.php가 없는)멋진 URL을 사용하려면 /application/config/config.php를 편집하고 변경하세요.

<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>

to

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

이 기능이 제대로 작동하려면 mod_rewrite 모듈이 올바르게 설치된 Apache 웹서버를 사용해야 합니다.

<span id="With_nginx_webserver"></span>
===nginx 웹서버 사용하기===

[http://nginx.com/products/ Nginx] http 서버(FastCGI를 통해 실행되는 PHP 포함)를 사용하고 있고 ''''urlFormat' => 'path'''' 설정을 사용하려는 경우(config.php 참조), 다음 Nginx 웹사이트 구성을 고려하세요.

<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 /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;
}
}</syntaxhighlight>

{{Note|이 경우 애플리케이션 내부의 파일에 액세스 할 수 없습니다. 애플리케이션 내에 있는 일부 JavaScript 및 CSS 파일은 디버그 > 0으로 읽을 수 있어야 합니다. 구성 파일에서 <code><nowiki>'use_asset_manager' => 1,</nowiki></code> 로 디버그 모드를 활성화하면(또는 디렉토리 목록에서 <code><nowiki>application</nowiki></code>을 제거하면) 에셋 매니저의 사용을 강제할 수 있습니다.}}

최종 결과는 다음과 같아야 합니다.

<center>[[File:Remove index.php steps.png]]</center>

<span id="How_do_I_get_rid_of_the_*_(red_asterisk)_of_mandatory_questions?"></span>
==필수 질문의 <span style='color:red'>*</span> (빨간색 별표)는 어떻게 없애나요?==

<span id="Instructions_for_LimeSurvey_2"></span>
===LimeSurvey 2 지침===

LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면:
*템플릿 편집기를 엽니다
*수정하려는 템플릿의 복사본을 만듭니다
*"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다
*별표 클래스 끝에 다음 라인을 추가합니다".asterisk {display: none;}".
*template.css를 저장하세요
*브라우저 캐시를 지우면 편집한 template.css를 캐시에서 가져오지 않고 다시 로드됩니다.

<span id="Instructions_for_LimeSurvey_3"></span>
===LimeSurvey 3 지침===

위 지침은 LimeSurvey 2에 대해 위에 제시된 지침과 유사합니다.

* 원하는 테마에 접속하세요. 기본 테마인 경우 "확장" 버튼을 클릭하여 복사본을 만듭니다.
* 테마 목록에 접속하여 새로 생성된 테마에 해당하는 '''테마 편집기'''를 클릭합니다.
* 왼쪽에서는 테마에 해당하는 CSS 파일을 시각화할 수 있습니다.
* custom.css를 클릭하고 다음 줄을 추가합니다.

<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>

* 변경 사항을 저장합니다. 일반적으로 질문 텍스트 시작 부분에 표시되는 빨간색 별표가 숨겨져 있습니다.

<span id="How_can_I_embed_a_flash_file?"></span>
==플래시 파일을 어떻게 삽입하나요?==

먼저 [[Global settings]]로 이동하여 XSS 필터를 비활성화합니다. 필터 비활성화가 인스턴스에 미치는 영향도 읽어보세요. 필터가 활성화된 경우 다음 단계는 작동하지 '''않습니다'''.
#플래시 파일을 삽입하려는 설문조사 위치로 이동하세요. 예를 들어 질문, 하위 질문, 답변, 설문조사 시작/종료 텍스트 등 통합 HTML 편집기를 사용할 수 있는 곳이면 어디든 가능합니다.
#[[첫 번째 로그인 - 사용자 기본 설정#팝업|full- 화면 편집기 모드]] 편집기 도구 모음에서 'LimeFitWin' 버튼을 클릭하면 됩니다.
#전체 화면 편집기 도구 모음에는 플래시 기호가 있는 작은 버튼이 있습니다. 그것을 클릭하세요. 대화 상자가 열립니다.
#이 상자에서 기존 플래시 파일의 경로를 어딘가에 제공하거나 '서버 찾아보기' 버튼을 클릭할 수 있습니다.
#'서버 찾아보기' 버튼을 클릭하면 파일 브라우저와 하단에 파일 업로드 필드가 표시됩니다. 지금 기존 파일을 선택하거나 먼저 파일을 업로드하세요.

여기까지입니다! 이 설명이 불완전하다고 생각되시면 적절하게 업데이트 해주십시오.

{{Alert|title=Attention|text=LimeSurvey 3에서도 이의 사용 과정은 유사합니다. 그러나 플래시 파일을 사용하지 않는 것을 권장합니다!}}

<span id="How_do_I_create_a_survey_which_is_open_to_everyone?"></span>
==모든 사람에게 공개되는 설문조사를 만들려면 어떻게 해야 하나요?==

누구나 작성할 수 있는 설문조사를 만들려면 [[설문조사 참가자|설문조사 참가자 테이블]]을 생성하지 마세요! [[개요|개요 패널]]에 있는 설문조사 링크를 공유하세요.

<span id="Public_registration_-_mandatory_fields"></span>
==공개 등록하기 - 필수 항목==

[[설문 참가자|설문 참가자 테이블]]을 사용하고 [[Participant_settings#Allow_public_registration|공개 등록]]도 허용하는 경우 사용자에게 다음 메시지가 표시됩니다.

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

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

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.

<center>[[File:exit and clear survey pic.png]]</center>

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.

<center>[[File:no exit clear survey.png]]</center>

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

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

=== Version 2.x ===
# 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>

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

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

For example, you can use this instruction to set password to password:
<syntaxhighlight lang="sql">
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?==

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:
#Activate your survey again
#Select [[Responses]] from the survey toolbar.
#Click on [[Import responses|Import]] and select the "Import answers from a deactivated survey table" menu entry.
#Choose your source table.
#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!==

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=

For general requirements please refer to our [[Installation#Make sure you can use LimeSurvey on your website|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. [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].

{{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, 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 [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].

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

<syntaxhighlight lang="bash">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</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):
[[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 [[Optional settings#Resources|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.
<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]].

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>

Translations:General FAQ/104/ko

2024-07-12T07:47:29Z

Rhami: Created page with "<center>File:non-mandatory public reg.png</center>"

<center>[[File:non-mandatory public reg.png]]</center>

Translations:General FAQ/103/ko

2024-07-12T07:47:23Z

Rhami: Created page with "설문 참가자 테이블을 사용하고 공개 등록도 허용하는 경우 사용자에게 다음 메시지가 표시됩니다."

[[설문 참가자|설문 참가자 테이블]]을 사용하고 [[Participant_settings#Allow_public_registration|공개 등록]]도 허용하는 경우 사용자에게 다음 메시지가 표시됩니다.

Translations:General FAQ/102/ko

2024-07-12T07:47:09Z

Rhami: Created page with "==공개 등록하기 - 필수 항목=="

==공개 등록하기 - 필수 항목==

General FAQ/ko

2024-07-12T07:47:01Z

Rhami: Created page with "누구나 작성할 수 있는 설문조사를 만들려면 설문조사 참가자 테이블을 생성하지 마세요! 개요 패널에 있는 설문조사 링크를 공유하세요."

<languages />

__TOC__

{{참고|다음 답변은 LimeSurvey 사용자 커뮤니티에서 제공되었습니다. 이해하지 못하는 부분이 있거나 다음에 수행해야 할 작업이 확실하지 않은 경우에는 https://forums.limesurvey.org에서 커뮤니티 구성원에게 질문할 수 있습니다. 전문적인 도움이 필요하시면 공인 파트너 목록을 확인하세요: https://limesurvey.com.}}

<span id="Getting_started"></span>
=시작하기=

메뉴얼의 절반을 읽고도 LimeSurvey로 무엇을 할 수 있는지 감을 잡기 어렵다면, YouTube 튜토리얼 동영상 시청을 권장합니다.

*[https://www.youtube.com/watch?v=oyoq14XpkwA 계정 설정 및 설문조사 설치 방법]
*[https://www.youtube.com/watch?v=7134QebOQzY 문항 유형 - 배열]
*[https://www.youtube.com/watch?v=aeb93vAe7R4 평가(Assessments)]
*[https://www.youtube.com/watch?v=s5OOzDoPjIU 도움말 설정(Placeholder fields)]
*[https://www.youtube.com/watch?v=7N4xUQMWbJY 라디오 목록]
*[https://www.youtube.com/watch?v=UI01hwrsiVk 설문조사 복사/가져오기]
*[https://www.youtube.com/watch?v=QEHyH1YbNEQ 문항 가져오기]

{{참고|좋은 동영상을 알고 있다면 주저하지 말고 공유해 주세요.}}

<span id="I_need_a_quick_introduction_for_LimeSurvey"></span>
==LimeSurvey에 대한 간단한 소개가 필요합니다==

LimeSurvey에 대한 빠른 텍스트 소개를 보려면 다음 두 링크를 확인하세요.

*[[빠른 시작 가이드 - LimeSurvey 2.50+|LimeSurvey 2.50+]]
*[[빠른 시작 가이드 - LimeSurvey 3.0+|Limesurvey 3+]]

{{Alert|현재 LimeSurvey 소개 동영상을 제작 중입니다.}}

<span id="Survey_design_and_layout"></span>
=설문조사 디자인 및 레이아웃=

<span id="How_can_I_remove_index.php_from_the_URL_path_to_get_a_shorter_URL"></span>
==더 짧은 URL을 얻기 위해 어떻게 URL 경로에서 index.php를 제거할 수 있습니까?==

(모든 URL에 /index.php가 없는)멋진 URL을 사용하려면 /application/config/config.php를 편집하고 변경하세요.

<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>

to

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

이 기능이 제대로 작동하려면 mod_rewrite 모듈이 올바르게 설치된 Apache 웹서버를 사용해야 합니다.

<span id="With_nginx_webserver"></span>
===nginx 웹서버 사용하기===

[http://nginx.com/products/ Nginx] http 서버(FastCGI를 통해 실행되는 PHP 포함)를 사용하고 있고 ''''urlFormat' => 'path'''' 설정을 사용하려는 경우(config.php 참조), 다음 Nginx 웹사이트 구성을 고려하세요.

<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 /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;
}
}</syntaxhighlight>

{{Note|이 경우 애플리케이션 내부의 파일에 액세스 할 수 없습니다. 애플리케이션 내에 있는 일부 JavaScript 및 CSS 파일은 디버그 > 0으로 읽을 수 있어야 합니다. 구성 파일에서 <code><nowiki>'use_asset_manager' => 1,</nowiki></code> 로 디버그 모드를 활성화하면(또는 디렉토리 목록에서 <code><nowiki>application</nowiki></code>을 제거하면) 에셋 매니저의 사용을 강제할 수 있습니다.}}

최종 결과는 다음과 같아야 합니다.

<center>[[File:Remove index.php steps.png]]</center>

<span id="How_do_I_get_rid_of_the_*_(red_asterisk)_of_mandatory_questions?"></span>
==필수 질문의 <span style='color:red'>*</span> (빨간색 별표)는 어떻게 없애나요?==

<span id="Instructions_for_LimeSurvey_2"></span>
===LimeSurvey 2 지침===

LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면:
*템플릿 편집기를 엽니다
*수정하려는 템플릿의 복사본을 만듭니다
*"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다
*별표 클래스 끝에 다음 라인을 추가합니다".asterisk {display: none;}".
*template.css를 저장하세요
*브라우저 캐시를 지우면 편집한 template.css를 캐시에서 가져오지 않고 다시 로드됩니다.

<span id="Instructions_for_LimeSurvey_3"></span>
===LimeSurvey 3 지침===

위 지침은 LimeSurvey 2에 대해 위에 제시된 지침과 유사합니다.

* 원하는 테마에 접속하세요. 기본 테마인 경우 "확장" 버튼을 클릭하여 복사본을 만듭니다.
* 테마 목록에 접속하여 새로 생성된 테마에 해당하는 '''테마 편집기'''를 클릭합니다.
* 왼쪽에서는 테마에 해당하는 CSS 파일을 시각화할 수 있습니다.
* custom.css를 클릭하고 다음 줄을 추가합니다.

<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>

* 변경 사항을 저장합니다. 일반적으로 질문 텍스트 시작 부분에 표시되는 빨간색 별표가 숨겨져 있습니다.

<span id="How_can_I_embed_a_flash_file?"></span>
==플래시 파일을 어떻게 삽입하나요?==

먼저 [[Global settings]]로 이동하여 XSS 필터를 비활성화합니다. 필터 비활성화가 인스턴스에 미치는 영향도 읽어보세요. 필터가 활성화된 경우 다음 단계는 작동하지 '''않습니다'''.
#플래시 파일을 삽입하려는 설문조사 위치로 이동하세요. 예를 들어 질문, 하위 질문, 답변, 설문조사 시작/종료 텍스트 등 통합 HTML 편집기를 사용할 수 있는 곳이면 어디든 가능합니다.
#[[첫 번째 로그인 - 사용자 기본 설정#팝업|full- 화면 편집기 모드]] 편집기 도구 모음에서 'LimeFitWin' 버튼을 클릭하면 됩니다.
#전체 화면 편집기 도구 모음에는 플래시 기호가 있는 작은 버튼이 있습니다. 그것을 클릭하세요. 대화 상자가 열립니다.
#이 상자에서 기존 플래시 파일의 경로를 어딘가에 제공하거나 '서버 찾아보기' 버튼을 클릭할 수 있습니다.
#'서버 찾아보기' 버튼을 클릭하면 파일 브라우저와 하단에 파일 업로드 필드가 표시됩니다. 지금 기존 파일을 선택하거나 먼저 파일을 업로드하세요.

여기까지입니다! 이 설명이 불완전하다고 생각되시면 적절하게 업데이트 해주십시오.

{{Alert|title=Attention|text=LimeSurvey 3에서도 이의 사용 과정은 유사합니다. 그러나 플래시 파일을 사용하지 않는 것을 권장합니다!}}

<span id="How_do_I_create_a_survey_which_is_open_to_everyone?"></span>
==모든 사람에게 공개되는 설문조사를 만들려면 어떻게 해야 하나요?==

누구나 작성할 수 있는 설문조사를 만들려면 [[설문조사 참가자|설문조사 참가자 테이블]]을 생성하지 마세요! [[개요|개요 패널]]에 있는 설문조사 링크를 공유하세요.

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

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

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.

<center>[[File:exit and clear survey pic.png]]</center>

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.

<center>[[File:no exit clear survey.png]]</center>

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

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

=== Version 2.x ===
# 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>

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

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

For example, you can use this instruction to set password to password:
<syntaxhighlight lang="sql">
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?==

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:
#Activate your survey again
#Select [[Responses]] from the survey toolbar.
#Click on [[Import responses|Import]] and select the "Import answers from a deactivated survey table" menu entry.
#Choose your source table.
#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!==

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=

For general requirements please refer to our [[Installation#Make sure you can use LimeSurvey on your website|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. [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].

{{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, 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 [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].

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

<syntaxhighlight lang="bash">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</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):
[[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 [[Optional settings#Resources|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.
<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]].

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>

Translations:General FAQ/101/ko

Rhami: Created page with "먼저 Global settings로 이동하여 XSS 필터를 비활성화합니다. 필터 비활성화가 인스턴스에 미치는 영향도 읽어보세요. 필터가 활성화된 경우 다음 단계는 작동하지 '''않습니다'''. #플래시 파일을 삽입하려는 설문조사 위치로 이동하세요. 예를 들어 질문, 하위 질문, 답변, 설문조사 시작/종료 텍스트 등 통합 HTML 편집기를 사용할 수 있는 곳이면 어디든 가능합..."

<languages />

__TOC__

{{참고|다음 답변은 LimeSurvey 사용자 커뮤니티에서 제공되었습니다. 이해하지 못하는 부분이 있거나 다음에 수행해야 할 작업이 확실하지 않은 경우에는 https://forums.limesurvey.org에서 커뮤니티 구성원에게 질문할 수 있습니다. 전문적인 도움이 필요하시면 공인 파트너 목록을 확인하세요: https://limesurvey.com.}}

<span id="Getting_started"></span>
=시작하기=

메뉴얼의 절반을 읽고도 LimeSurvey로 무엇을 할 수 있는지 감을 잡기 어렵다면, YouTube 튜토리얼 동영상 시청을 권장합니다.

*[https://www.youtube.com/watch?v=oyoq14XpkwA 계정 설정 및 설문조사 설치 방법]
*[https://www.youtube.com/watch?v=7134QebOQzY 문항 유형 - 배열]
*[https://www.youtube.com/watch?v=aeb93vAe7R4 평가(Assessments)]
*[https://www.youtube.com/watch?v=s5OOzDoPjIU 도움말 설정(Placeholder fields)]
*[https://www.youtube.com/watch?v=7N4xUQMWbJY 라디오 목록]
*[https://www.youtube.com/watch?v=UI01hwrsiVk 설문조사 복사/가져오기]
*[https://www.youtube.com/watch?v=QEHyH1YbNEQ 문항 가져오기]

{{참고|좋은 동영상을 알고 있다면 주저하지 말고 공유해 주세요.}}

<span id="I_need_a_quick_introduction_for_LimeSurvey"></span>
==LimeSurvey에 대한 간단한 소개가 필요합니다==

LimeSurvey에 대한 빠른 텍스트 소개를 보려면 다음 두 링크를 확인하세요.

*[[빠른 시작 가이드 - LimeSurvey 2.50+|LimeSurvey 2.50+]]
*[[빠른 시작 가이드 - LimeSurvey 3.0+|Limesurvey 3+]]

{{Alert|현재 LimeSurvey 소개 동영상을 제작 중입니다.}}

<span id="Survey_design_and_layout"></span>
=설문조사 디자인 및 레이아웃=

<span id="How_can_I_remove_index.php_from_the_URL_path_to_get_a_shorter_URL"></span>
==더 짧은 URL을 얻기 위해 어떻게 URL 경로에서 index.php를 제거할 수 있습니까?==

(모든 URL에 /index.php가 없는)멋진 URL을 사용하려면 /application/config/config.php를 편집하고 변경하세요.

<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>

to

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

이 기능이 제대로 작동하려면 mod_rewrite 모듈이 올바르게 설치된 Apache 웹서버를 사용해야 합니다.

<span id="With_nginx_webserver"></span>
===nginx 웹서버 사용하기===

[http://nginx.com/products/ Nginx] http 서버(FastCGI를 통해 실행되는 PHP 포함)를 사용하고 있고 ''''urlFormat' => 'path'''' 설정을 사용하려는 경우(config.php 참조), 다음 Nginx 웹사이트 구성을 고려하세요.

<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 /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;
}
}</syntaxhighlight>

{{Note|이 경우 애플리케이션 내부의 파일에 액세스 할 수 없습니다. 애플리케이션 내에 있는 일부 JavaScript 및 CSS 파일은 디버그 > 0으로 읽을 수 있어야 합니다. 구성 파일에서 <code><nowiki>'use_asset_manager' => 1,</nowiki></code> 로 디버그 모드를 활성화하면(또는 디렉토리 목록에서 <code><nowiki>application</nowiki></code>을 제거하면) 에셋 매니저의 사용을 강제할 수 있습니다.}}

최종 결과는 다음과 같아야 합니다.

<center>[[File:Remove index.php steps.png]]</center>

<span id="How_do_I_get_rid_of_the_*_(red_asterisk)_of_mandatory_questions?"></span>
==필수 질문의 <span style='color:red'>*</span> (빨간색 별표)는 어떻게 없애나요?==

<span id="Instructions_for_LimeSurvey_2"></span>
===LimeSurvey 2 지침===

LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면:
*템플릿 편집기를 엽니다
*수정하려는 템플릿의 복사본을 만듭니다
*"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다
*별표 클래스 끝에 다음 라인을 추가합니다".asterisk {display: none;}".
*template.css를 저장하세요
*브라우저 캐시를 지우면 편집한 template.css를 캐시에서 가져오지 않고 다시 로드됩니다.

<span id="Instructions_for_LimeSurvey_3"></span>
===LimeSurvey 3 지침===

위 지침은 LimeSurvey 2에 대해 위에 제시된 지침과 유사합니다.

* 원하는 테마에 접속하세요. 기본 테마인 경우 "확장" 버튼을 클릭하여 복사본을 만듭니다.
* 테마 목록에 접속하여 새로 생성된 테마에 해당하는 '''테마 편집기'''를 클릭합니다.
* 왼쪽에서는 테마에 해당하는 CSS 파일을 시각화할 수 있습니다.
* custom.css를 클릭하고 다음 줄을 추가합니다.

<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>

* 변경 사항을 저장합니다. 일반적으로 질문 텍스트 시작 부분에 표시되는 빨간색 별표가 숨겨져 있습니다.

<span id="How_can_I_embed_a_flash_file?"></span>
==플래시 파일을 어떻게 삽입하나요?==

먼저 [[Global settings]]로 이동하여 XSS 필터를 비활성화합니다. 필터 비활성화가 인스턴스에 미치는 영향도 읽어보세요. 필터가 활성화된 경우 다음 단계는 작동하지 '''않습니다'''.
#플래시 파일을 삽입하려는 설문조사 위치로 이동하세요. 예를 들어 질문, 하위 질문, 답변, 설문조사 시작/종료 텍스트 등 통합 HTML 편집기를 사용할 수 있는 곳이면 어디든 가능합니다.
#[[첫 번째 로그인 - 사용자 기본 설정#팝업|full- 화면 편집기 모드]] 편집기 도구 모음에서 'LimeFitWin' 버튼을 클릭하면 됩니다.
#전체 화면 편집기 도구 모음에는 플래시 기호가 있는 작은 버튼이 있습니다. 그것을 클릭하세요. 대화 상자가 열립니다.
#이 상자에서 기존 플래시 파일의 경로를 어딘가에 제공하거나 '서버 찾아보기' 버튼을 클릭할 수 있습니다.
#'서버 찾아보기' 버튼을 클릭하면 파일 브라우저와 하단에 파일 업로드 필드가 표시됩니다. 지금 기존 파일을 선택하거나 먼저 파일을 업로드하세요.

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

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

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

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

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.

<center>[[File:exit and clear survey pic.png]]</center>

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.

<center>[[File:no exit clear survey.png]]</center>

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

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

=== Version 2.x ===
# 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>

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

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

For example, you can use this instruction to set password to password:
<syntaxhighlight lang="sql">
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?==

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:
#Activate your survey again
#Select [[Responses]] from the survey toolbar.
#Click on [[Import responses|Import]] and select the "Import answers from a deactivated survey table" menu entry.
#Choose your source table.
#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!==

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=

For general requirements please refer to our [[Installation#Make sure you can use LimeSurvey on your website|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. [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].

{{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, 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 [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].

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

<syntaxhighlight lang="bash">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</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):
[[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 [[Optional settings#Resources|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.
<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]].

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>

Translations:General FAQ/17/ko

2024-07-12T07:42:15Z

먼저 [[Global settings]]로 이동하여 XSS 필터를 비활성화합니다. 필터 비활성화가 인스턴스에 미치는 영향도 읽어보세요. 필터가 활성화된 경우 다음 단계는 작동하지 '''않습니다'''.
#플래시 파일을 삽입하려는 설문조사 위치로 이동하세요. 예를 들어 질문, 하위 질문, 답변, 설문조사 시작/종료 텍스트 등 통합 HTML 편집기를 사용할 수 있는 곳이면 어디든 가능합니다.
#[[첫 번째 로그인 - 사용자 기본 설정#팝업|full- 화면 편집기 모드]] 편집기 도구 모음에서 'LimeFitWin' 버튼을 클릭하면 됩니다.
#전체 화면 편집기 도구 모음에는 플래시 기호가 있는 작은 버튼이 있습니다. 그것을 클릭하세요. 대화 상자가 열립니다.
#이 상자에서 기존 플래시 파일의 경로를 어딘가에 제공하거나 '서버 찾아보기' 버튼을 클릭할 수 있습니다.
#'서버 찾아보기' 버튼을 클릭하면 파일 브라우저와 하단에 파일 업로드 필드가 표시됩니다. 지금 기존 파일을 선택하거나 먼저 파일을 업로드하세요.

General FAQ/ko

2024-07-12T07:13:02Z

Rhami: Created page with "<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>"

<languages />

__TOC__

{{참고|다음 답변은 LimeSurvey 사용자 커뮤니티에서 제공되었습니다. 이해하지 못하는 부분이 있거나 다음에 수행해야 할 작업이 확실하지 않은 경우에는 https://forums.limesurvey.org에서 커뮤니티 구성원에게 질문할 수 있습니다. 전문적인 도움이 필요하시면 공인 파트너 목록을 확인하세요: https://limesurvey.com.}}

<span id="Getting_started"></span>
=시작하기=

메뉴얼의 절반을 읽고도 LimeSurvey로 무엇을 할 수 있는지 감을 잡기 어렵다면, YouTube 튜토리얼 동영상 시청을 권장합니다.

*[https://www.youtube.com/watch?v=oyoq14XpkwA 계정 설정 및 설문조사 설치 방법]
*[https://www.youtube.com/watch?v=7134QebOQzY 문항 유형 - 배열]
*[https://www.youtube.com/watch?v=aeb93vAe7R4 평가(Assessments)]
*[https://www.youtube.com/watch?v=s5OOzDoPjIU 도움말 설정(Placeholder fields)]
*[https://www.youtube.com/watch?v=7N4xUQMWbJY 라디오 목록]
*[https://www.youtube.com/watch?v=UI01hwrsiVk 설문조사 복사/가져오기]
*[https://www.youtube.com/watch?v=QEHyH1YbNEQ 문항 가져오기]

{{참고|좋은 동영상을 알고 있다면 주저하지 말고 공유해 주세요.}}

<span id="I_need_a_quick_introduction_for_LimeSurvey"></span>
==LimeSurvey에 대한 간단한 소개가 필요합니다==

LimeSurvey에 대한 빠른 텍스트 소개를 보려면 다음 두 링크를 확인하세요.

*[[빠른 시작 가이드 - LimeSurvey 2.50+|LimeSurvey 2.50+]]
*[[빠른 시작 가이드 - LimeSurvey 3.0+|Limesurvey 3+]]

{{Alert|현재 LimeSurvey 소개 동영상을 제작 중입니다.}}

<span id="Survey_design_and_layout"></span>
=설문조사 디자인 및 레이아웃=

<span id="How_can_I_remove_index.php_from_the_URL_path_to_get_a_shorter_URL"></span>
==더 짧은 URL을 얻기 위해 어떻게 URL 경로에서 index.php를 제거할 수 있습니까?==

(모든 URL에 /index.php가 없는)멋진 URL을 사용하려면 /application/config/config.php를 편집하고 변경하세요.

<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>

to

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

이 기능이 제대로 작동하려면 mod_rewrite 모듈이 올바르게 설치된 Apache 웹서버를 사용해야 합니다.

<span id="With_nginx_webserver"></span>
===nginx 웹서버 사용하기===

[http://nginx.com/products/ Nginx] http 서버(FastCGI를 통해 실행되는 PHP 포함)를 사용하고 있고 ''''urlFormat' => 'path'''' 설정을 사용하려는 경우(config.php 참조), 다음 Nginx 웹사이트 구성을 고려하세요.

<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 /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;
}
}</syntaxhighlight>

{{Note|이 경우 애플리케이션 내부의 파일에 액세스 할 수 없습니다. 애플리케이션 내에 있는 일부 JavaScript 및 CSS 파일은 디버그 > 0으로 읽을 수 있어야 합니다. 구성 파일에서 <code><nowiki>'use_asset_manager' => 1,</nowiki></code> 로 디버그 모드를 활성화하면(또는 디렉토리 목록에서 <code><nowiki>application</nowiki></code>을 제거하면) 에셋 매니저의 사용을 강제할 수 있습니다.}}

최종 결과는 다음과 같아야 합니다.

<center>[[File:Remove index.php steps.png]]</center>

<span id="How_do_I_get_rid_of_the_*_(red_asterisk)_of_mandatory_questions?"></span>
==필수 질문의 <span style='color:red'>*</span> (빨간색 별표)는 어떻게 없애나요?==

<span id="Instructions_for_LimeSurvey_2"></span>
===LimeSurvey 2 지침===

LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면:
*템플릿 편집기를 엽니다
*수정하려는 템플릿의 복사본을 만듭니다
*"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다
*별표 클래스 끝에 다음 라인을 추가합니다".asterisk {display: none;}".
*template.css를 저장하세요
*브라우저 캐시를 지우면 편집한 template.css를 캐시에서 가져오지 않고 다시 로드됩니다.

<span id="Instructions_for_LimeSurvey_3"></span>
===LimeSurvey 3 지침===

위 지침은 LimeSurvey 2에 대해 위에 제시된 지침과 유사합니다.

* 원하는 테마에 접속하세요. 기본 테마인 경우 "확장" 버튼을 클릭하여 복사본을 만듭니다.
* 테마 목록에 접속하여 새로 생성된 테마에 해당하는 '''테마 편집기'''를 클릭합니다.
* 왼쪽에서는 테마에 해당하는 CSS 파일을 시각화할 수 있습니다.
* custom.css를 클릭하고 다음 줄을 추가합니다.

<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>

* 변경 사항을 저장합니다. 일반적으로 질문 텍스트 시작 부분에 표시되는 빨간색 별표가 숨겨져 있습니다.

<span id="How_can_I_embed_a_flash_file?"></span>
==플래시 파일을 어떻게 삽입하나요?==

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.
#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 box will open.
#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.

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

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

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

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

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.

<center>[[File:exit and clear survey pic.png]]</center>

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.

<center>[[File:no exit clear survey.png]]</center>

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

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

=== Version 2.x ===
# 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>

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

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

For example, you can use this instruction to set password to password:
<syntaxhighlight lang="sql">
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?==

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:
#Activate your survey again
#Select [[Responses]] from the survey toolbar.
#Click on [[Import responses|Import]] and select the "Import answers from a deactivated survey table" menu entry.
#Choose your source table.
#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!==

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=

For general requirements please refer to our [[Installation#Make sure you can use LimeSurvey on your website|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. [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].

{{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, 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 [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].

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

<syntaxhighlight lang="bash">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</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):
[[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 [[Optional settings#Resources|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.
<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]].

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>

Translations:General FAQ/16/ko

2024-07-12T07:12:57Z

Rhami: Created page with "==플래시 파일을 어떻게 삽입하나요?=="

==플래시 파일을 어떻게 삽입하나요?==

Translations:General FAQ/99/ko

2024-07-12T07:12:35Z

Rhami: Created page with "* 변경 사항을 저장합니다. 일반적으로 질문 텍스트 시작 부분에 표시되는 빨간색 별표가 숨겨져 있습니다."

* 변경 사항을 저장합니다. 일반적으로 질문 텍스트 시작 부분에 표시되는 빨간색 별표가 숨겨져 있습니다.

Translations:General FAQ/98/ko

2024-07-12T07:12:30Z

Rhami: Created page with "<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>"

<syntaxhighlight lang="css">.asterisk {display: none;}</syntaxhighlight>

Translations:General FAQ/97/ko

2024-07-12T07:12:24Z

Rhami: Created page with "* 원하는 테마에 접속하세요. 기본 테마인 경우 "확장" 버튼을 클릭하여 복사본을 만듭니다. * 테마 목록에 접속하여 새로 생성된 테마에 해당하는 '''테마 편집기'''를 클릭합니다. * 왼쪽에서는 테마에 해당하는 CSS 파일을 시각화할 수 있습니다. * custom.css를 클릭하고 다음 줄을 추가합니다."

* 원하는 테마에 접속하세요. 기본 테마인 경우 "확장" 버튼을 클릭하여 복사본을 만듭니다.
* 테마 목록에 접속하여 새로 생성된 테마에 해당하는 '''테마 편집기'''를 클릭합니다.
* 왼쪽에서는 테마에 해당하는 CSS 파일을 시각화할 수 있습니다.
* custom.css를 클릭하고 다음 줄을 추가합니다.

General FAQ/ko

2024-07-12T07:11:02Z

Rhami: Created page with "===LimeSurvey 3 지침==="

<languages />

__TOC__

{{참고|다음 답변은 LimeSurvey 사용자 커뮤니티에서 제공되었습니다. 이해하지 못하는 부분이 있거나 다음에 수행해야 할 작업이 확실하지 않은 경우에는 https://forums.limesurvey.org에서 커뮤니티 구성원에게 질문할 수 있습니다. 전문적인 도움이 필요하시면 공인 파트너 목록을 확인하세요: https://limesurvey.com.}}

<span id="Getting_started"></span>
=시작하기=

메뉴얼의 절반을 읽고도 LimeSurvey로 무엇을 할 수 있는지 감을 잡기 어렵다면, YouTube 튜토리얼 동영상 시청을 권장합니다.

*[https://www.youtube.com/watch?v=oyoq14XpkwA 계정 설정 및 설문조사 설치 방법]
*[https://www.youtube.com/watch?v=7134QebOQzY 문항 유형 - 배열]
*[https://www.youtube.com/watch?v=aeb93vAe7R4 평가(Assessments)]
*[https://www.youtube.com/watch?v=s5OOzDoPjIU 도움말 설정(Placeholder fields)]
*[https://www.youtube.com/watch?v=7N4xUQMWbJY 라디오 목록]
*[https://www.youtube.com/watch?v=UI01hwrsiVk 설문조사 복사/가져오기]
*[https://www.youtube.com/watch?v=QEHyH1YbNEQ 문항 가져오기]

{{참고|좋은 동영상을 알고 있다면 주저하지 말고 공유해 주세요.}}

<span id="I_need_a_quick_introduction_for_LimeSurvey"></span>
==LimeSurvey에 대한 간단한 소개가 필요합니다==

LimeSurvey에 대한 빠른 텍스트 소개를 보려면 다음 두 링크를 확인하세요.

*[[빠른 시작 가이드 - LimeSurvey 2.50+|LimeSurvey 2.50+]]
*[[빠른 시작 가이드 - LimeSurvey 3.0+|Limesurvey 3+]]

{{Alert|현재 LimeSurvey 소개 동영상을 제작 중입니다.}}

<span id="Survey_design_and_layout"></span>
=설문조사 디자인 및 레이아웃=

<span id="How_can_I_remove_index.php_from_the_URL_path_to_get_a_shorter_URL"></span>
==더 짧은 URL을 얻기 위해 어떻게 URL 경로에서 index.php를 제거할 수 있습니까?==

(모든 URL에 /index.php가 없는)멋진 URL을 사용하려면 /application/config/config.php를 편집하고 변경하세요.

<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>

to

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

이 기능이 제대로 작동하려면 mod_rewrite 모듈이 올바르게 설치된 Apache 웹서버를 사용해야 합니다.

<span id="With_nginx_webserver"></span>
===nginx 웹서버 사용하기===

[http://nginx.com/products/ Nginx] http 서버(FastCGI를 통해 실행되는 PHP 포함)를 사용하고 있고 ''''urlFormat' => 'path'''' 설정을 사용하려는 경우(config.php 참조), 다음 Nginx 웹사이트 구성을 고려하세요.

<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 /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;
}
}</syntaxhighlight>

{{Note|이 경우 애플리케이션 내부의 파일에 액세스 할 수 없습니다. 애플리케이션 내에 있는 일부 JavaScript 및 CSS 파일은 디버그 > 0으로 읽을 수 있어야 합니다. 구성 파일에서 <code><nowiki>'use_asset_manager' => 1,</nowiki></code> 로 디버그 모드를 활성화하면(또는 디렉토리 목록에서 <code><nowiki>application</nowiki></code>을 제거하면) 에셋 매니저의 사용을 강제할 수 있습니다.}}

최종 결과는 다음과 같아야 합니다.

<center>[[File:Remove index.php steps.png]]</center>

<span id="How_do_I_get_rid_of_the_*_(red_asterisk)_of_mandatory_questions?"></span>
==필수 질문의 <span style='color:red'>*</span> (빨간색 별표)는 어떻게 없애나요?==

<span id="Instructions_for_LimeSurvey_2"></span>
===LimeSurvey 2 지침===

LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면:
*템플릿 편집기를 엽니다
*수정하려는 템플릿의 복사본을 만듭니다
*"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다
*별표 클래스 끝에 다음 라인을 추가합니다".asterisk {display: none;}".
*template.css를 저장하세요
*브라우저 캐시를 지우면 편집한 template.css를 캐시에서 가져오지 않고 다시 로드됩니다.

<span id="Instructions_for_LimeSurvey_3"></span>
===LimeSurvey 3 지침===

위 지침은 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:

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

==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.
#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 [[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 box will open.
#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.

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

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

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

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

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.

<center>[[File:exit and clear survey pic.png]]</center>

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.

<center>[[File:no exit clear survey.png]]</center>

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

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

=== Version 2.x ===
# 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>

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

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

For example, you can use this instruction to set password to password:
<syntaxhighlight lang="sql">
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?==

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:
#Activate your survey again
#Select [[Responses]] from the survey toolbar.
#Click on [[Import responses|Import]] and select the "Import answers from a deactivated survey table" menu entry.
#Choose your source table.
#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!==

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=

For general requirements please refer to our [[Installation#Make sure you can use LimeSurvey on your website|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. [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].

{{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, 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 [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].

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

<syntaxhighlight lang="bash">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</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):
[[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 [[Optional settings#Resources|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.
<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]].

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>

Translations:General FAQ/96/ko

2024-07-12T07:10:46Z

Rhami: Created page with "위 지침은 LimeSurvey 2에 대해 위에 제시된 지침과 유사합니다."

위 지침은 LimeSurvey 2에 대해 위에 제시된 지침과 유사합니다.

Translations:General FAQ/95/ko

2024-07-12T07:10:20Z

Rhami: Created page with "===LimeSurvey 3 지침==="

===LimeSurvey 3 지침===

Translations:General FAQ/13/ko

2024-07-12T07:07:52Z

Rhami: Undo revision 378545 by Rhami (talk)

LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면:
*템플릿 편집기를 엽니다
*수정하려는 템플릿의 복사본을 만듭니다
*"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다
*별표 클래스 끝에 다음 라인을 추가합니다".asterisk {display: none;}".
*template.css를 저장하세요
*브라우저 캐시를 지우면 편집한 template.css를 캐시에서 가져오지 않고 다시 로드됩니다.

Translations:General FAQ/13/ko

2024-07-12T07:07:08Z

Rhami:

LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면:
*템플릿 편집기를 엽니다
*수정하려는 템플릿의 복사본을 만듭니다
*"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다
*Add the following line at the end of the asterix class".asterisk {display: none;}".
*template.css를 저장하세요
*브라우저 캐시를 지우면 편집한 template.css를 캐시에서 가져오지 않고 다시 로드됩니다.

General FAQ/ko

2024-07-12T07:06:02Z

Rhami: Created page with "LimeSurvey 2.x에서는 필수 질문의 빨간색 별표가 template.css file ("asterisk" class) 내에 설정됩니다. 이를 숨기려면: *템플릿 편집기를 엽니다 *수정하려는 템플릿의 복사본을 만듭니다 *"template.css" 파일을 선택하고 별표 클래스(asterix class)를 검색합니다 *별표 클래스 끝에 다음 라인을 추가합니다".asterisk {display: none;}". *template.css를 저장하세요 *브라우저 캐시를 지우..."

<languages />

__TOC__

{{참고|다음 답변은 LimeSurvey 사용자 커뮤니티에서 제공되었습니다. 이해하지 못하는 부분이 있거나 다음에 수행해야 할 작업이 확실하지 않은 경우에는 https://forums.limesurvey.org에서 커뮤니티 구성원에게 질문할 수 있습니다. 전문적인 도움이 필요하시면 공인 파트너 목록을 확인하세요: https://limesurvey.com.}}

<span id="Getting_started"></span>
=시작하기=

메뉴얼의 절반을 읽고도 LimeSurvey로 무엇을 할 수 있는지 감을 잡기 어렵다면, YouTube 튜토리얼 동영상 시청을 권장합니다.

*[https://www.youtube.com/watch?v=oyoq14XpkwA 계정 설정 및 설문조사 설치 방법]
*[https://www.youtube.com/watch?v=7134QebOQzY 문항 유형 - 배열]
*[https://www.youtube.com/watch?v=aeb93vAe7R4 평가(Assessments)]
*[https://www.youtube.com/watch?v=s5OOzDoPjIU 도움말 설정(Placeholder fields)]
*[https://www.youtube.com/watch?v=7N4xUQMWbJY 라디오 목록]
*[https://www.youtube.com/watch?v=UI01hwrsiVk 설문조사 복사/가져오기]
*[https://www.youtube.com/watch?v=QEHyH1YbNEQ 문항 가져오기]

{{참고|좋은 동영상을 알고 있다면 주저하지 말고 공유해 주세요.}}

<span id="I_need_a_quick_introduction_for_LimeSurvey"></span>
==LimeSurvey에 대한 간단한 소개가 필요합니다==

LimeSurvey에 대한 빠른 텍스트 소개를 보려면 다음 두 링크를 확인하세요.

*[[빠른 시작 가이드 - LimeSurvey 2.50+|LimeSurvey 2.50+]]
*[[빠른 시작 가이드 - LimeSurvey 3.0+|Limesurvey 3+]]

{{Alert|현재 LimeSurvey 소개 동영상을 제작 중입니다.}}

<span id="Survey_design_and_layout"></span>
=설문조사 디자인 및 레이아웃=

<span id="How_can_I_remove_index.php_from_the_URL_path_to_get_a_shorter_URL"></span>
==더 짧은 URL을 얻기 위해 어떻게 URL 경로에서 index.php를 제거할 수 있습니까?==

(모든 URL에 /index.php가 없는)멋진 URL을 사용하려면 /application/config/config.php를 편집하고 변경하세요.

<syntaxhighlight lang="php">'showScriptName' => true,</syntaxhighlight>

to

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

이 기능이 제대로 작동하려면 mod_rewrite 모듈이 올바르게 설치된 Apache 웹서버를 사용해야 합니다.

<span id="With_nginx_webserver"></span>
===nginx 웹서버 사용===

[http://nginx.com/products/ Nginx] http 서버(FastCGI를 통해 실행되는 PHP 포함)를 사용하고 있고 ''''urlFormat' => 'path'''' 설정을 사용하려는 경우(config.php 참조), 다음 Nginx 웹사이트 구성을 고려하세요.

<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 /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;
}
}</syntaxhighlight>

{{Note|이 경우 애플리케이션 내부 파일에 대한 액세스가 비활성화됩니다. 애플리케이션 내에 있는 일부 JavaScript 및 CSS 파일은 디버그 > 0으로 읽을 수 있어야 합니다. 다음을 사용하여 디버그 모드가 활성화되면 자산 관리자를 강제로 사용할 수 있습니다.<nowiki> <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>

==How do I get rid of the <span style='color:red'>*</span> (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:

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

==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.
#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 [[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 box will open.
#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.

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

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

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

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

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.

<center>[[File:exit and clear survey pic.png]]</center>

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.

<center>[[File:no exit clear survey.png]]</center>

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

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

=== Version 2.x ===
# 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>

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

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

For example, you can use this instruction to set password to password:
<syntaxhighlight lang="sql">
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?==

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:
#Activate your survey again
#Select [[Responses]] from the survey toolbar.
#Click on [[Import responses|Import]] and select the "Import answers from a deactivated survey table" menu entry.
#Choose your source table.
#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!==

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=

For general requirements please refer to our [[Installation#Make sure you can use LimeSurvey on your website|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. [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].

{{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, 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 [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].

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

<syntaxhighlight lang="bash">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</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):
[[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 [[Optional settings#Resources|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.
<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]].

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>