LimeSurvey Manual - User contributions [en]

Available third party plugins

2026-03-30T10:12:31Z

Tassoman: /* Other plugins */ duplicate removal

Some plugin are listed in the [https://account.limesurvey.org/limestore Limestore]. If you have a plugin you would like to share with the world, feel free to add it to this page.

== Authentication plugins ==

* [https://survey-consulting.com/product/extended-auth-ldap-limesurvey-plugin Free Auth LDAP Plugin]
* [https://survey-consulting.com/product/limesurvey-saml-plugin/ SAML SSO Plugin]
* [https://github.com/technowhizz/LimeSurvey-RegDomainRestricter Registration Email Domain Restrictor]
* [http://extensions.sondages.pro/authentification-by-wordpress/ Authentification by WordPress user]
* [https://github.com/univlorraine/limesurvey-cas CAS Authentication plugin for LimeSurvey]
* [https://github.com/atlet/LimeSurvey-ShibbolethAuth LimeSurvey Shibboleth auth plugin]
* [https://framagit.org/Animafac/limesurvey/limesurvey-rememberme LimeSurvey RememberMe plugin]

== Export and statistics plugins ==

* [http://extensions.sondages.pro/exportcompleteanswers/ exportCompleteAnswers : Complete New export system allowing export Answer code and answer text in CSV. Options is manageable by super admin.]
* [http://extensions.sondages.pro/triple-s-export/ exportTripleS : export in Triple-S XML2 or XML1.3 format survey structure and data.]
* [https://framagit.org/SondagePro-LimeSurvey-plugin/extendAdminStatitistics extendAdminStatitistics : rewriting of core statistics, actually put sub question in same table and graph]
* [https://github.com/reportico-web/limesurvey-reportico Reportico Reporting module for LimeSurvey]: generate charts,tables and statistics from survey data

== Public survey plugins ==
* [http://extensions.sondages.pro/hideemptycolumn-for-limesurvey/ hideEmptyColumn : A plugin to add a solution to hide column of array question type with ExpressionScript of LimeSurvey ]
* [http://extensions.sondages.pro/moreaccessibility/ moreAccessibility : some option to add accessibility to public survey] 2.6lts compatible onlmy, deprecated in 3.0
* [https://git.framasoft.org/Shnoulle/addQuestionCodeClass addQuestionCodeClass : add the question code at the question wrapper class]
* [https://framagit.org/SondagePro-LimeSurvey-plugin/radioToStarRating radioToStarRating : set any radio list to star rating system]
* [https://framagit.org/SondagePro-LimeSurvey-plugin/moveSomeAnswers moveSomeAnswers] : If using random_order attribute : allow to always move some answers at end.

== Data editing plugins ==
* [https://manual.limesurvey.org/MassAction_Plugin MassAction] : A plugin for faster survey editing by loading questions details into editable cells. Includes a search and replace feature.

== Email plugins ==

* [https://gitlab.com/SondagesPro/mailing/noMailToExample noMailToExample]
* [https://github.com/LimeSurvey/LimeSurvey/blob/develop/plugins/mailSenderToFrom/mailSenderToFrom.php mailSenderToFrom]
* [https://github.com/Xites/LS_mailDKIM mailDKIM]
* [https://github.com/Xites/LS_mailEmbedImages mailEmbedImages]
* [https://github.com/RegioneER/LsRerAntiphishing Anti Phishing Templates] this free software plugin, mandatory alters mail notifications templates, by displaying urls inside email messages.

== Other plugins ==

* [http://extensions.sondages.pro/recomputeexpression-for-limesurvey Recompute Expressions:] A Plugin for LimeSurvey to recompute expression in survey with already submitted survey. Allow to update some relevance too.
* [https://git.framasoft.org/SondagePro-LimeSurvey-plugin/showAdvancedSettings showAdvancedSettings:] Show advanced settings in question edit by default.
* [https://git.framasoft.org/SondagePro-LimeSurvey-plugin/replaceRegister replaceRegisterː] Extra option for Register, starting point for other plugin.
* [http://extensions.sondages.pro/fixmaxstep-for-question-index/ fixMaxStep : Fix question index for token answer persistence survey:] Example of usage : get the complete index when user come back to the survey.
* [http://extensions.sondages.pro/sendmailajax-all-email-in-one/ sendMailAjax : Send token email one by one with ajaxː] Allow to send all email in one click without restriction.
* [http://extensions.sondages.pro/mailing-management/sendmailcron sendMailCron: Automatically send invitations and reminders using cronjobsː] Automatically sends invitations and reminders in custom intervals. Extensive configuration and debugging options
* [https://github.com/SteveCohen/Piwik-for-Limesurvey Piwik-for-Limesurvey Piwik for LimeSurvey]: Plugs Piwik into LimeSurvey, so you can track your survey admin users and respondents.
* [https://github.com/SondagesPro/surveysModel Mark surveys as "Survey Model/Template"ː] Allow admins to mark a survey as "Survey Model", a kind of "master survey" or "survey template" which only users with appropriate rights are allowed to edit. The common user is only allowed to create copies based on such a survey template.
* [https://github.com/SondagesPro/LS-toolsDomDocument toolsDomDocumentː] a tools for anothers plugin
* [https://github.com/TonisOrmisson/limesurvey-url-templates UrlTemplateChangerː] Set respondent's interview template over an URL parameter.
* [https://github.com/evently-nl/zesthook ZestHookː] Makes it possible to send a Post request on every response submission. You can set the URL to post to, as well as several other options.
* [https://github.com/CEric-fr/limesurvey-rgpd Extension RGPD pour LimeSurvey] Each questionnaire owner is able to interact with these conditions of use via a new submenu added in the "questionnaire parameters" entitled: GDPR configuration.
* [https://github.com/projeto-cade-unb/Lime2Camunda Lime2Camunda] Plugin for integration with LimeSurvey with Camunda, which at the end of completing the survey it starts a process instance in Camunda submitting all questions and answers as process variables.
* [https://github.com/librecodecoop/lsTelegramNotify lsTelegramNotify]: Allows you to send after survey completed event to Telegram as text, PDF or CSV.
* [https://github.com/LibreCodeCoop/LSNextcloud LSNextcloud]: Save all survey responses and their attachments automatically to a folder in your Nextcloud.

== Example and demo plugins ==
* [https://framagit.org/SondagePro-LimeSurvey-plugin/extendRemoteControl extendRemoteControl] : Show how to add function to [[RemoteControl_2_API]], show how to create a new admin page too (usage of public function actionIndex() )

[[Category:Plugins]]

Available third party plugins

2026-03-30T10:09:58Z

Tassoman: added anti phishing plugin

Some plugin are listed in the [https://account.limesurvey.org/limestore Limestore]. If you have a plugin you would like to share with the world, feel free to add it to this page.

== Authentication plugins ==

* [https://survey-consulting.com/product/extended-auth-ldap-limesurvey-plugin Free Auth LDAP Plugin]
* [https://survey-consulting.com/product/limesurvey-saml-plugin/ SAML SSO Plugin]
* [https://github.com/technowhizz/LimeSurvey-RegDomainRestricter Registration Email Domain Restrictor]
* [http://extensions.sondages.pro/authentification-by-wordpress/ Authentification by WordPress user]
* [https://github.com/univlorraine/limesurvey-cas CAS Authentication plugin for LimeSurvey]
* [https://github.com/atlet/LimeSurvey-ShibbolethAuth LimeSurvey Shibboleth auth plugin]
* [https://framagit.org/Animafac/limesurvey/limesurvey-rememberme LimeSurvey RememberMe plugin]

== Export and statistics plugins ==

* [http://extensions.sondages.pro/exportcompleteanswers/ exportCompleteAnswers : Complete New export system allowing export Answer code and answer text in CSV. Options is manageable by super admin.]
* [http://extensions.sondages.pro/triple-s-export/ exportTripleS : export in Triple-S XML2 or XML1.3 format survey structure and data.]
* [https://framagit.org/SondagePro-LimeSurvey-plugin/extendAdminStatitistics extendAdminStatitistics : rewriting of core statistics, actually put sub question in same table and graph]
* [https://github.com/reportico-web/limesurvey-reportico Reportico Reporting module for LimeSurvey]: generate charts,tables and statistics from survey data

== Public survey plugins ==
* [http://extensions.sondages.pro/hideemptycolumn-for-limesurvey/ hideEmptyColumn : A plugin to add a solution to hide column of array question type with ExpressionScript of LimeSurvey ]
* [http://extensions.sondages.pro/moreaccessibility/ moreAccessibility : some option to add accessibility to public survey] 2.6lts compatible onlmy, deprecated in 3.0
* [https://git.framasoft.org/Shnoulle/addQuestionCodeClass addQuestionCodeClass : add the question code at the question wrapper class]
* [https://framagit.org/SondagePro-LimeSurvey-plugin/radioToStarRating radioToStarRating : set any radio list to star rating system]
* [https://framagit.org/SondagePro-LimeSurvey-plugin/moveSomeAnswers moveSomeAnswers] : If using random_order attribute : allow to always move some answers at end.

== Data editing plugins ==
* [https://manual.limesurvey.org/MassAction_Plugin MassAction] : A plugin for faster survey editing by loading questions details into editable cells. Includes a search and replace feature.

== Email plugins ==

* [https://gitlab.com/SondagesPro/mailing/noMailToExample noMailToExample]
* [https://github.com/LimeSurvey/LimeSurvey/blob/develop/plugins/mailSenderToFrom/mailSenderToFrom.php mailSenderToFrom]
* [https://github.com/Xites/LS_mailDKIM mailDKIM]
* [https://github.com/Xites/LS_mailEmbedImages mailEmbedImages]
* [https://github.com/RegioneER/LsRerAntiphishing Anti Phishing Templates] this free software plugin, mandatory alters mail notifications templates, by displaying urls inside email messages.

== Other plugins ==

* [http://extensions.sondages.pro/recomputeexpression-for-limesurvey Recompute Expressions:] A Plugin for LimeSurvey to recompute expression in survey with already submitted survey. Allow to update some relevance too.
* [https://git.framasoft.org/SondagePro-LimeSurvey-plugin/showAdvancedSettings showAdvancedSettings:] Show advanced settings in question edit by default.
* [https://git.framasoft.org/SondagePro-LimeSurvey-plugin/replaceRegister replaceRegisterː] Extra option for Register, starting point for other plugin.
* [http://extensions.sondages.pro/fixmaxstep-for-question-index/ fixMaxStep : Fix question index for token answer persistence survey:] Example of usage : get the complete index when user come back to the survey.
* [http://extensions.sondages.pro/sendmailajax-all-email-in-one/ sendMailAjax : Send token email one by one with ajaxː] Allow to send all email in one click without restriction.
* [http://extensions.sondages.pro/mailing-management/sendmailcron sendMailCron: Automatically send invitations and reminders using cronjobsː] Automatically sends invitations and reminders in custom intervals. Extensive configuration and debugging options
* [https://github.com/SteveCohen/Piwik-for-Limesurvey Piwik-for-Limesurvey Piwik for LimeSurvey]: Plugs Piwik into LimeSurvey, so you can track your survey admin users and respondents.
* [https://github.com/SondagesPro/surveysModel Mark surveys as "Survey Model/Template"ː] Allow admins to mark a survey as "Survey Model", a kind of "master survey" or "survey template" which only users with appropriate rights are allowed to edit. The common user is only allowed to create copies based on such a survey template.
* [https://github.com/SondagesPro/LS-toolsDomDocument toolsDomDocumentː] a tools for anothers plugin
* [https://github.com/TonisOrmisson/limesurvey-url-templates UrlTemplateChangerː] Set respondent's interview template over an URL parameter.
* [https://github.com/evently-nl/zesthook ZestHookː] Makes it possible to send a Post request on every response submission. You can set the URL to post to, as well as several other options.
* [https://github.com/CEric-fr/limesurvey-rgpd Extension RGPD pour LimeSurvey] Each questionnaire owner is able to interact with these conditions of use via a new submenu added in the "questionnaire parameters" entitled: GDPR configuration.
* [https://github.com/projeto-cade-unb/Lime2Camunda Lime2Camunda] Plugin for integration with LimeSurvey with Camunda, which at the end of completing the survey it starts a process instance in Camunda submitting all questions and answers as process variables.
* [https://github.com/LibreCodeCoop/LSNextcloud LSNextcloud] Allows you to send after survey completed event to Telegram as text, PDF or CSV.
* [https://github.com/librecodecoop/lsTelegramNotify lsTelegramNotify]: Allows you to send after survey completed event to Telegram as text, PDF or CSV.
* [https://github.com/LibreCodeCoop/LSNextcloud LSNextcloud]: Save all survey responses and their attachments automatically to a folder in your Nextcloud.

== Example and demo plugins ==
* [https://framagit.org/SondagePro-LimeSurvey-plugin/extendRemoteControl extendRemoteControl] : Show how to add function to [[RemoteControl_2_API]], show how to create a new admin page too (usage of public function actionIndex() )

[[Category:Plugins]]

Theme editor - Available Twig functions

2025-01-14T16:47:34Z

Tassoman: /* Image and file source */

== PHP included functions ==

* [http://php.net/array-flip array_flip]
* [http://php.net/array_intersect_key array_intersect_key]
* [http://php.net/str_replace str_replace]
* [http://php.net/intval intval]
* [http://php.net/empty empty]
* [http://php.net/reset reset]
* [http://php.net/in_array in_array]
* [http://php.net/array_search array_search]
* [http://php.net/isset isset]
* [http://php.net/sprintf sprintf]

== Specific function for LimeSurvey ==

=== Text update and management ===

==== flatString ====
Get html text and remove whole not clean string.
Parameters are
* the string to flatten
* a boolean encode html entities (default to false)

==== ellipsizeString ====
Get a flat and ellipsize string.
Parameters are
* the string to ellipsize
* an integer max length of the final string
* a float $position of the ellipsis in string (between 0 and 1), default to 1 mean the string is ellipsize at end.
* a string ellipsis string to shown in place of removed part, default to …

==== processString ====

Process ExpressionScript with any string with current page information, return a string.
Parameters are
* the string to be processed
* a boolean : return static string (or not), default to no.
* an integer : recursion (max) level to do, default to 3
* an array of string: replacement out of current expression know vars. The key is the value to be replaced, the value is the replacement.

=== Image and file source ===
Remember, by default SVG files are blacklisted for potential security issues. Before use inside your custom theme, you need to allow them inside the templates, by editing Advanced Config.

==== image() ====
Returns the HTML code needed for an image tag. Parameters are:
* The source of image, relative to theme directory (img/logo.png for example)
* alt attribute, useful for better accessibility
* array of extra html function (as array for twig : <code>{"class": "logo img-fluid"}</code>)
Not useful if you want display a SVG image, they are rendered differently, not by <code><img /></code> tag.

==== imageSrc() ====
Returns the dynamic path to a theme's image, obtained in the cache. Looks for parent's theme image, when not found in current theme.
* Image path relative to theme directory (img/mylogo.png for example)
* default value if image file was not found (img/default-avatar.png for example)
Can be used to render SVG. For example: <code><svg><use src="<nowiki>{{ imageSrc('img/logo.svg') }}</nowiki>" ></use></svg></code>

==== templateResourceUrl() ====

Create the dynamic source of a file, using parent theme if file are not found in current one.

* file path relative to theme directory
* default value if not found

=== Language management ===

==== gT ====

==== ngT ====

=== Get information ===

==== getConfig ====
Get the current config part for this instance of LimeSurvey for the parameter. Return the existing config, false if not set.

=== getPost ===
Get the current $_POST value for the parameter. Return the existing $_POST, null if not set.

==== getQuery ====
Get the current $_GET value for the parameter. Return the existing $_GET, null if not set.

==== getParam ====
Get the current $_PARAM value for the parameter. Returns the existing $_PARAM, null if not set.

=== Script and css management ===

* registerPublicCssFile
* registerTemplateCssFile
* registerGeneralScript
* registerTemplateScript
* registerScript
* registerPackage
* unregisterPackage
* registerCssFile
* registerScriptFile
* unregisterScriptFile
* unregisterScriptForAjax
* listCoreScripts
* listScriptFiles

=== Others ===

==== getAllTokenAnswers ====

== Adding a function ==

=== By updating config.php ===
You can add any PHP existing function easily in your config.php file. This is done by adding the function in twigRenderer.

<syntaxhighlight lang="php" enclose="pre">
'twigRenderer' => array(
'functions' => array(
'strlen' => 'strlen',
),
'sandboxConfig' => array(
'functions' => array(
'strlen',
),
),
),
</syntaxhighlight>

=== By extension ===

See [https://github.com/LimeSurvey/LimeSurvey/tree/master/upload/twig/extensions Custom Twig Extension for LimeSurvey]

[[Category:Theme]]
[[Category:Twig]]
[[Category:Development]]

Optional settings

2025-01-14T16:28:23Z

Tassoman: /* Allowed file upload */

<languages /> <translate>


__TOC__


The following section is addressed to those of you who would like to edit those configuration settings that could not be modified with the help of the GUI (Graphical User Interface) of the LimeSurvey installation. Please bear in mind that all the changes from the LimeSurvey root directory are done at your own risk. Nevertheless, in the case in which you are experiencing problems/need further guidance, join the [https://www.limesurvey.org/forum discussion forums] or the [irc://irc.freenode.net/limesurvey|IRC IRC channel] for help from the LimeSurvey community.

=Introduction= 


To modify the configuration settings of the installation, you have to edit the optional settings. They can be found in the /application/config/'''config-defaults.php''', which is located in the LimeSurvey root directory. The default settings of the standard installation can be found in config-defaults.php. Some of them can be overridden by using the [[Global settings|global settings]] dialog, while the others will have to be manually edited.


{{Alert|If you want to change these settings, please do not change them in config-defaults.php, but copy the particular setting/line to /application/config/'''config.php''' in <nowiki>'config'=>array( )</nowiki> and change it there. All the newly modified/introduced settings from the config.php file will override the default values from config-defaults.php.}}


When an upgrade occurs, only the config-defaults.php settings are changed. Therefore, editing the config.php file will save your customized settings.


To update/add the LimeSurvey settings in /application/'''config/config.php''', you have to update the config array:
<syntaxhighlight lang="php" enclose="pre">
'config'=>array(
'debug'=>0,
'debugsql'=>0,
'LimeSurveySetting'=>'New value', // Update default LimeSurvey config here
)
</syntaxhighlight>

=Yii settings= 


LimeSurvey uses the Yii framework, which has its own configuration parameters in application/config/'''internal.php''' and application/config/'''config.php''' file. You can also access some specific configuration settings of LimeSurvey via the Yii configuration.


Since config.php array is merged to the whole config, you can replace any Yii params in the config.php file.


The Yii specific settings are set in the components array:
<syntaxhighlight lang="php" enclose="pre">
'components' => array(
'db' => array(
....
),
'Specific settings'=>array(
....
),
),
</syntaxhighlight>


{{Note|For more information about the Yii framework, please access the [http://www.yiiframework.com/doc-2.0/guide-index.html following link.]}}

==Database settings== 
The database settings are written to config.php by the installer file when you install LimeSurvey for the first time. If needed, you can update this part of the config.php file. Please remember that you do this at your own risk!
See also the [http://www.yiiframework.com/doc/blog/1.1/en/prototype.database#establishing-database-connection Yii documentation] and please remember that LimeSurvey supports only the following types of database: mysql, pgsql, dblib, mssql, and sqlsrv.

==Session settings== 


You can set some session parameters in config.php (check the two examples from below). You can uncomment/add the part needed in config.php. See the [http://www.yiiframework.com/doc/api/1.1/CHttpSession Yii Documentation] for other settings.


{{Alert|If you need to update session settings to have multiple LimeSurvey instances running on the same server, check if you don't have to update [[Optional_settings#Request_settings|request settings]] for crsf cookie.}}

===Use table-based sessions=== 


LimeSurvey can use table-based sessions, you find a commented part on the default config.php generated file. To use table-based session, remove the // before each line.


<syntaxhighlight lang="php" enclose="pre">
'session' => array (
'class' => 'application.core.web.DbHttpSession',
'connectionID' => 'db',
'sessionTableName' => '{{sessions}}',
),
</syntaxhighlight>


{{Alert|Table-based sessions are currently not supported on MSSQL server.}}

===Other sessions update=== 


If you use SSL ('https') for your LimeSurvey installation, adding the following lines to your config.php will increase the security of the session:
<syntaxhighlight lang="php" enclose="pre"> // Set the cookie via SSL
'session' => array (
'cookieParams' => array(
'secure' => true, // use SSL for cookies
'httponly' => true // Cookies may not be used by other protocols - experimental
),
),
</syntaxhighlight>


If you want to fix the domain for a cookie, use the following syntax in config.php:
<syntaxhighlight lang="php" enclose="pre"> // Set the domain for cookie
'session' => array (
'cookieParams' => array(
'domain' => '.example.org',
),
),
</syntaxhighlight>


If you have mutiples installation on the same server, it can be more quick and easy to set different session name for each LimeSurvey instance. This can be need for IE11 in some condition (see [https://bugs.limesurvey.org/view.php?id=12083#c42892 issue 12083])
<syntaxhighlight lang="php" enclose="pre"> // Set the name of the session
'session' => array (
'sessionName' => "LimeSurveyN1",
),
</syntaxhighlight>

==Request settings== 
The request settings are important, but the default settings are already optimized for LimeSurvey usage. To read more about them, see the [http://www.yiiframework.com/doc/api/1.1/CHttpRequest Yii Documentation].


For example, the LimeSurvey request settings configuration may be modified in the following way (at your own risk) :
<syntaxhighlight lang="php" enclose="pre"> // Disable CSRF protection
'request' => array(
'enableCsrfValidation'=>false,
),
</syntaxhighlight>
<syntaxhighlight lang="php" enclose="pre"> // Enforce a certain URL base
'request' => array(
'hostInfo' => 'http://www.example.org/'
),
</syntaxhighlight>
<syntaxhighlight lang="php" enclose="pre"> // Set the cookie domain name and path for CSRF protection, path is used if you have different instance on same domain
'request' => array(
'csrfCookie' => array(
'domain' => '.example.com',
'path' => '/limesurvey/',
)
),
</syntaxhighlight>


If you need to update only the url for token emails, set your [[Optional_settings#Advanced_path_settings|publicurl]] in your config.php file.

==Allow usage of session and Csrf Validation in iFrame {{NewIn|v=3.24.3}}== 


After allow [[Global_settings#Security|Iframe embedding]] you need to update some configuration part.


{{Alert|Attention, even with all settings : allow form in iframe can broke on some browser or with user specific settings. This settings was tested with Firefox 81.0.2 to 115 and Chromium 85.0.4183.121 to 119, and119 Edge with default settings. '''No support on this feature, only community support'''.}}

===Allow session start in iframe=== 


The session needs to be secure (valid https) , httponly and samesite to None. All settings must be set to all lowercase.


<syntaxhighlight lang="php" enclose="pre"> 'session' => array (
'sessionName'=>'LS-VBXZZORFJZCAKGYI',
// Uncomment the following lines if you need table-based sessions.
// Note: Table-based sessions are currently not supported on MSSQL server.
// 'class' => 'application.core.web.DbHttpSession',
// 'connectionID' => 'db',
// 'sessionTableName' => '{{sessions}}',
'cookieParams' => array(
'secure' => true,
'httponly' => true,
'samesite' => 'None',
),
),
</syntaxhighlight>

===Allow csrf cookie in iframe=== 


Same as session: must be secure and sameSite set to None. The whole array must be added at the same level as session.


<syntaxhighlight lang="php" enclose="pre"> 'request' => array(
'enableCsrfValidation'=>true,
'csrfCookie' => array(
'sameSite' => 'None',
'secure' => true,
),
),
</syntaxhighlight>

==URL settings== 


{{Alert|If you need to update only the url for token and other emails, set your [[Optional_settings#Advanced_url_settings|publicurl]] in your config.php file.}}


To change the default URL settings, update the urlManager:
<syntaxhighlight lang="php" enclose="pre"> // Use short URL
'urlManager' => array(
'urlFormat' => 'path',
'showScriptName' => false,
),
</syntaxhighlight>


You can also add .html after the survey id in the following way:
<syntaxhighlight lang="php" enclose="pre"> // Use short URL
'urlManager' => array(
'urlFormat' => 'path',
'rules' => array (
'<sid:\d+>' => array('survey/index','urlSuffix'=>'.html','matchValue'=>true),
),
'showScriptName' => false,
),
</syntaxhighlight>
For more information, check the [http://www.yiiframework.com/doc/guide/1.1/en/topics.url Yii documentation].

==Logging settings== 


Yii provides different solutions to generate logs. To find out more about them, check the [http://www.yiiframework.com/doc/guide/1.1/en/topics.logging logging special topic]. LimeSurvey uses '1' or '2' by default, which allows every web user to see the logs. You can create your own settings using Yii directly.


For example, a quick solution to log errors and warnings in files is:
<syntaxhighlight lang="php" enclose="pre">
return array(
'components' => array(
/* Other component part here 'db' for example */
'log' => array(
'routes' => array(
'fileError' => array(
'class' => 'CFileLogRoute',
'levels' => 'warning, error',
'except' => 'exception.CHttpException.404',
),
),
),
/* Other component part here 'urlManager' for example */
),
/* Final part (with 'runtimePath' 'config' for example) */
);
</syntaxhighlight>


{{Hint|Text=The file is saved by default to <code><nowiki>limesurvey/tmp/runtime/application.log</nowiki></code>, which is located in the LimeSurvey root folder.}}
{{Alert|Yii uses runtime path. By default, the logs are web accessible. They may contain a lot of information from your server. It is better to use a directory that cannot be accessed via the web. You can set it in routes or by updating the [[Optional settings#Yii settings#Runtime path|Runtime path]].}}.

==Runtime path== 


[http://www.yiiframework.com/doc/guide/1.1/en/basics.convention#directory The runtime path] must be a readable and writable directory for the “web user”. However, the runtime path contains files with potential security information that are located in the public web access area. LimeSurvey collects these files in the temp directory of the LimeSurvey root directory. In order to eliminate the access to such important data, you can set the runtime path outside the public web access by editing the respective lines in the /application/config/config.php file:


<syntaxhighlight lang="php" enclose="pre">
return array(
'components' => array(
[…]
'runtimePath'=>'/var/limesurvey/runtime/',
'config'=>array(
[…]
)
)
)
</syntaxhighlight>

=General settings= 


*'''sitename''': Gives your survey site a name. This name will appear in the survey list overview and in the administration header. The default value is 'LimeSurvey' and it can be overridden in the [[Global settings|global settings]] dialog or edited in config.php.
*'''siteadminemail:''' This is the default email address of the site administrator and it is used for system messages and contact options. This setting is used only as default value and can be overridden in the [[Global settings|global settings]] dialog.
*'''showEmailInError:''' Use default site admin email (siteadminemail) for mailto link in error page. Disable to shown only the administrator name. Default to avoid more spam on administration email.
*'''siteadminbounce:''' This is the email address where bounced emails will be sent to. This setting is used only as default value and can be overridden by the [[Global settings|global settings]] dialog.
*'''siteadminname:''' The real name of the site administrator. This setting is used only as default value and can be overridden in the [[Global settings|global settings]] dialog).
*'''proxy_host_name:''' This is the host name of your proxy server (it has to be mentioned if you are behind a proxy and you want to update LimeSurvey using [[ComfortUpdate|ComfortUpdate]]).
*'''proxy_host_port:''' This is the port of your proxy server (it has to be mentioned if you are behind a proxy and you want to update LimeSurvey using [[ComfortUpdate|ComfortUpdate]]).

= Security= 


* '''maxLoginAttempt''': This is the number of attempts a user has to enter the correct password before he or she gets her or his IP address blocked/locked out. The default value is 3 and it can be modified from config.php.
* '''timeOutTime''': If the user enters the password incorrectly for <maxLoginAttempt>, she or he gets locked out for <timeOutTime> seconds. The default value is 10 minutes and it can be modified from config.php.
* '''maxLoginAttemptParticipants''': This is the number of attempts a participant has to enter a valid token before he or she gets her or his IP address blocked/locked out. The default value is 3 and it can be modified from config.php.
* '''timeOutParticipants''': If the participant enters the token incorrectly for <maxLoginAttemptParticipants>, she or he gets locked out for <timeOutParticipants> seconds. The default value is 10 minutes and it can be modified from config.php.
* '''surveyPreview_require_Auth''': Set to true by default. If you set this to 'false', any person can test your survey using the survey URL, without logging in to the administration panel and without having to activate the survey first. This setting is a default value and can be overridden in the [[Global settings|global settings]] dialog or edited in config.php.
* '''usercontrolSameGroupPolicy''': Set to true by default. By default, non-admin users defined in the LimeSurvey management interface will only be able to see users they create or users that belong to at least one same group. The default value can be overridden in the [[Global settings|global settings]] dialog or edited in config.php.
*'''filterxsshtml:''' This setting enables the filtering of suspicious html tags located within surveys, groups, and questions and answer texts in the administration interface. Leave this to 'false' only if you absolutely trust the users you created for the administration of LimeSurvey and if you want to allow these users to be able to use Javascript, Flash Movies, etc.. <span class="warning">The super admins never have their HTML filtered</span>. The default value can be overridden in the [[Global settings|global settings]] dialog or edited in config.php.
*'''demoMode:''' If this option is set to 'true' in config.php, then LimeSurvey will go into demo mode. The demo mode changes the following things:
** Disables admin user's details and password changing;
** Disables the upload of files on the template editor;
** Disables sending email invitations and reminders;
** Disables the creation of a database dump;
** Disables the ability to modify the following global settings: site name, default language, default HTML editor mode, XSS filter.
*'''forcedsuperadmin:''' Array of user id whith all rights on all LimeSurvey. This settings can only be updated in config.php file. This user's rights can not be edited in [[Manage_users#Set_global_permissions_for_a_user|global permissions for a user]] even by other forced super administrator. By default : user with this rights is user with id : 1. The first user created just after installation.
*'''force_ssl:''' forces LimeSurvey to run through HTTPS or to block HTTPS. See [https://manual.limesurvey.org/Global_settings#Security Force HTTPS] in global settings admin GUI.
*'''ssl_emergency_override:''' This setting forces SSL off. If You've turned HTTPS/SSL on in the global settings but your server doesn't have HTTPS enabled, the only way to turn it off is by changing a value in the database directly. This allows you to force HTTPS off while you change the global settings for Force Secure. This should always be false except in emergencies where you change it to true until you fix the problem. This setting can be only set via config.php file.
*'''ssl_disable_alert:''' Disable alert for super-admin about unforced SSL, if you really can not or don't want to force ssl. This setting can be only set via config.php file.

== Allowed file upload ==

*'''allowedthemeimageformats''' : Image file types allowed to be uploaded in the themes section., By default SVG file are disabled due to potential XSS attack.
*'''allowedthemeuploads''' : Other file types allowed to be uploaded in the themes section (zip file)
*'''allowedfileuploads''' : file type allowed for file uploads
*'''allowedresourcesuploads''' : File types allowed to be uploaded in the resources sections, and with the HTML Editor
*'''allowedpluginuploads''' : File type allowed when upload plugin zip file.

Just enter a string of comma separated extensions. For example: <pre>'allowedthemeimageformats' => 'jpg,jpeg,gif,png,webm,svg',</pre>

Warning: Always be careful when allowing file uploads. Malicious activities could be expected.

== Plugins ==

*'''usePluginWhitelist''' : If true plugins that are not in the allowlist (see 'pluginWhitelist') cannot be installed nor loaded. This may disable already installed plugins.
*'''pluginWhitelist''' : List of plugin names allowed to be installed and loaded when 'usePluginWhitelist' is true. Core plugins are implicitly allowlisted.
*'''corePluginBlacklist''' : List of core plugin names forbidden when 'usePluginWhitelist' is true.
*'''disablePluginUpload''' : When this setting is true, the "Plugin Upload" feature is disabled

= Resources= 
*'''sessionlifetime:''' Defines the time in seconds after which a survey session expires. It applies only if you are using database sessions. If you do use database sessions, change the parameter in config.php or override the default value from the [[Global settings|global settings]] dialog.
*'''memorylimit:''' This determines how much memory LimeSurvey can access. '128 MB' is the minimum (MB=Megabyte) recommended. If you receive time out errors or have problems generating statistics or exporting files, raise this limit to '256 MB' or higher. If your web server has set a higher limit in config.php, then this setting will be ignored.


<div class="warningbox">'''Please bear in mind that such local settings can always be overruled by the changes done in the global settings dialog'''.</div>


To increase the memory limit to 128M you could also try adding:
*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 128M in a .htaccess file in the LimeSurvey root


*'''max_execution_time:''' Set the number of seconds a script is allowed to run. If this is reached, the script returns a fatal error. To be allowed to export big survey data and statistics, LimeSurvey try to set it by default to 1200 seconds. You can set a bigger time or a lower time if needed. Only accessible via php config file.

=Appearance= 
*'''dropdownthreshold'''{{ObsoleteIn|2.50}}: When "R" is selected for <code>$dropdowns</code>, the administrator is allowed to set a maximum number of options that will be displayed as radio buttons, before converting back to a dropdown list. If there is a question that has a large number of options, displaying all of them at once as radio buttons can look unwieldy, and can become counter-intuitive to users. Setting this to a maximum of, say 25 (which is the default) means that large lists are easier to be used by the administrators for the survey participant.
*'''repeatheadings:''' With the Array question type, you'll often have a lot of subquestions, which - when displayed on screen - take up more than one page. This setting lets you decide how many subquestions should be displayed before repeating the header information for the question. A good setting for this is around 15. If you don't want the headings to repeat at all, set this to 0. This setting is overridden in the [[Global settings|global settings]] dialog {{NewIn|2.05}}.
*'''minrepeatheadings:''' The minimum number of remaining subquestions that are required before repeating the headings in Array questions. The default value is 3 and it can be edited in config.php.
*'''defaulttemplate:''' This setting specifies the default theme used for the 'public list' of surveys. This setting can be overridden in the [[Global settings|global settings]] dialog or edited in config.php.
*'''defaulthtmleditormode:''' Sets the default mode for the integrated HTML editor. This setting can be overridden in the [[Global settings|global settings]] dialog or edited in config.php. The valid settings are:
** 'inline' - Inline replacement of fields by an HTML editor. Slow but convenient and user friendly;
** 'popup' - Adds an icon that runs the HTML editor in a popup if needed. Faster, but HTML code is displayed in the form;
** 'none'- No HTML editor;
*'''column_style:''' Defines how columns are rendered for survey answers when using [[QS:Display_columns|display_columns]]. It can be edited in the config.php file. The valid settings are:
** 'css' - it uses one of the various CSS methods to create columns (see the template style sheet for details);
** 'ul' - the columns are rendered as multiple floated unordered lists (default);
** 'table' - it uses conventional-tables-based layout;
** NULL - it disables the use of columns.

=Language & time= 
*'''defaultlang:''' This should be set to the default language to be used in your administration scripts, and also the default setting for language in the public survey list. This setting can be overridden in the [[Global settings|global settings]] dialog or edited in config.php.
*'''timeadjust:''' If your web server is in a different time zone to the location where your surveys will be based, put the difference between your server and your home time zone here. For example, I live in Australia, but I use a US web server. The web server is 14 hours behind my local time zone. So my setting here is "14". In other words, it adds 14 hours to the web servers time. This setting is particularly important when surveys timestamp the responses. This setting can be overridden in the [[Global settings|global settings]] dialog or edited in config.php.

=Survey behavior= 
*'''deletenonvalues:''' Use this feature with caution. By default (a value of 1), irrelevant questions are NULLed in the database. This ensures that the data in your database is internally consistent. However, there are rare cases where you might want to hold onto irrelevant values, in which case you can set the value to 0. For example, you ask a male person his gender, and he accidentally says 'female' and then answers some female-specific questions (questions that are conditioned on being female, so are only relevant for women). Then, he realizes his mistake, backs up, sets the gender to 'male', and continues with the survey. Now, the female-specific questions are irrelevant. If <code>$deletenonvalues==1</code>, those irrelevant values will be cleared (NULLed) in the database. If <code>$deletenonvalues==0</code>, his erroneous answers will not be deleted, so they will still be present in the database when you analyze it.
*'''shownoanswer:''' When a radio button/select type question that contains editable answers (i.e.: List, Array questions) is not mandatory and 'shownoanswer' is set to 1, an additional 'No answer' entry is shown - so that participants may choose to not answer the question. Some people prefer this not to be available. This setting can be overridden from the [[Global settings|global settings]] dialog or edited in config.php. Valid values are:
**'0': No;
**'1': Yes;
**'2': The Survey admin can choose.
*'''printanswershonorsconditions:''' This setting determines if the printanswers feature will display entries from questions that were hidden by conditions-branching (Default: 1 = hide answers from questions hidden by conditions).
*'''hide_groupdescr_allinone:''' This setting is relevant for all-in-one surveys using conditions . When this is set to 'true', the group name and description is hidden if all questions in the group are hidden. The default value is 'true' - hides group name and description when all questions in the group are hidden by conditions. It can be edited in config.php.
*'''showpopups:''' Show popup messages if mandatory or conditional questions have not been answered correctly:
** '2' = defined by Theme option (default)
** '1'= show popup message;
** '0'= show message on page instead;
** '-1'= do not show the message at all (in this case, users will still see the question-specific tips indicating which questions must be answered).

== Numerical question type behavior == 


*'''bFixNumAuto:''' Numeric fields can be automatically filtered to remove all non numeric values. By default this is enable, you can disable it globally. This settings is related to ''Fix automatically numeric value'' in core theme options. It was enable for ''Yes'', disable for ''Only for expression'' and ''No''.
*'''bNumRealValue:''' Numeric fields used in expression manager can be fixed or not. It's fixed by default. If NUMERIC is a numerical question : disable or 0 : {NUMERIC} with bad caracters send <nowiki>''</nowiki>, enable or 1 : {NUMERIC} send all character entered. This settings is related to ''Fix automatically numeric value'' in core theme options. It was enable for ''Yes'' and ''Only for expression'' and disable for ''No''.

=Development and debugging= 
*'''debug:''' With this setting, you set the PHP error reporting to E_ALL. This means that every little notice, warning or error related to the script is shown. This setting should be only switched to '1' if you are trying to debug the application for any reason. If you are a developer, switch it to '2'. Don't switch it to '1' or '2' in production since it might cause path disclosure. The default value is '0' and it can be edited in config.php.
*'''debugsql:''' Activate this setting if you want to display all SQL queries executed for the script on the bottom of each page. Very useful for the optimization of the the number of queries. In order to activate it, change the default value to '1' from the config.php file.
*'''use_asset_manager:''' By default : debug mode disable asset manager, you can allow you to use asse manager with debug mode enable.


In the case in which you experience an error in the application, we strongly recommend to activate the debug setting in order to get a more detailed error that you can submit with the bug report:


<syntaxhighlight lang="php" enclose="pre">
'config'=>array(
'debug'=>2,
'debugsql'=>0,
)
</syntaxhighlight>


If you work on plugin and need a quick way to dump variables on screen : you can use traceVar function. If debug is set : this function use CWebLogRoute to be shown on HTML page. Usage <code>traceVar($MyVariable)</code>

= Email settings= 


All the settings from below can be overridden in the [[Global settings|global settings]] dialog.
*'''emailmethod:'' This determines how email messages are being sent. The following options are available:
**'mail:' it uses internal PHP mailer;
**'sendmail:' it uses sendmail mailer;
**'smtp:' it uses SMTP relaying. Use this setting when you are running LimeSurvey on a host that is not your mail server.
*'''emailsmtphost:'' If you use 'smtp' as <code>$emailmethod</code>, then you have to put your SMTP-server here. If you are using Google mail you might have to add the port number like $emailsmtphost = 'smtp.gmail.com:465'.
*''emailsmtpuser:'' If your SMTP-server needs authentication then set this to your user name, otherwise it must be blank.
*''emailsmtppassword:'' If your SMTP-server needs authentication then set this to your password, otherwise it must be blank.
*''emailsmtpssl:'' Set this to 'ssl' or 'tls' to use SSL/TLS for SMTP connection.
*''maxemails:'' When sending invitations or reminders to survey participants, this setting is used to determine how many emails can be sent in one bunch. Different web servers have different email capacities and if your script takes too long to send a bunch of emails, the script could time out and cause errors. Most web servers can send 100 emails at a time within the default 30 second time limit for a PHP script. If you get script timeout errors when sending large numbers of emails, reduce the number in this setting. Clicking the 'send email invitation' button from the token control toolbar (not the button situated on the right of each token) sends the <maxemails> number of invitations, then it displays a list of the addresses of the recipients and a warning that ''there are more emails pending than could be sent in one batch. Continue sending emails by clicking below. There are ### emails still to be sent.'' and provides a "continue button" to proceed with the next batch. I.e., the user determines when to send the next batch after each batch gets emailed. It is not necessary to wait with this screen active. The admin could log out and come back at a later time to send the next batch of invites.

= Statistics and response browsing= 
*'''filterout_incomplete_answers:''' Control the default behavior of filtering incomplete answers when browsing or analyzing responses. For a discussion on incomplete responses see our [[Responses & statistics#Responses summary|browsing survey results wiki]]. Since these records can corrupt the statistics, an option is given to switch this filter on or off in several GUI forms. The parameter can be edited in the config.php. The following options are available:
**'show': Allows you to visualize both complete and incomplete answers;
**'filter': It shows only complete answers;
**'incomplete': Show only incomplete answers.
*'''strip_query_from_referer_url''': This setting determines if the referrer URL saves the parameter or not. The default value is 'false' (in this case, the referrer URL saves all parameters). Alternatively, this value can be set to 'true' and the parameter part of the referrer URL will be removed.
*'''showaggregateddata:''' when activated, additional statistical values such as the arithmetic mean and standard deviation are shown. Furthermore, the data is aggregated to get a faster overview. For example, results of scale 1+2 and 4+5 are added to have a general ranking like "good" (1/2), "average" (3) and "bad" (4/5). This only affects question types "A" (5 point array) and "5" (5 point choice).
* '''PDF Export Settings:''' This feature activates PDF export for printable surveys and Print Answers. The PDF export function is totally experimental and the output is far from being perfect. Unfortunately, no support can be given at the moment - if you want to help to fix it, please get in touch with us.
**'usepdfexport': Set '0' to disable and '1' to enable;
**'pdfdefaultfont': It represents the default font that will be used by the pdf export function. The default value is 'auto'. To change it, you have to set it to one of the [https://tcpdf.org/docs/fonts/ PDF core fonts].
**'alternatepdffontfile': It's an array with language keys and their corresponding font. The default font for each language can be replaced in the config.php file;
**'pdffontsize': it shows the font size for normal texts; For the title of the survey, it is <pdffontsize>+4, while for the group title is <pdffontsize>+2. It can be edited in the config.php file or from the [Global settings|global settings]] dialog;
**'notsupportlanguages': it includes a list with the languages for which no PDF font was found. The list includes Amharic ('am'), Sinhala ('si'), and Thai ('th'), and it can be found in the config-defaults.php file;
**'pdforientation': Set 'L' for Landscape or 'P' for portrait format. It can be edited from the config.php file.
*'''Graph setting'''
**'chartfontfile': Sets the font file name that is used to create the statistical charts. The file has to be located in the fonts directory, located in the LimeSurvey root folder. It can be edited in the config.php file;
**'alternatechartfontfile': It's an array with language keys and their corresponding font. It can be edited in the config.php file.
*'''showsgqacode:''' This setting is used at the printable survey feature and defaults to 'false''. If you set showsgqacode = 'true';, the IDs of each question - and answer if applicable - will be shown. These IDs match the column heading at the Lime_survey_12345 table, which holds the answer data for a certain survey. These IDs can be used for a code book for manual database queries.

= [[LDAP settings]]= 


As this is an extensive topic we have moved [[LDAP settings]] to [[LDAP settings|another page.]]

= Authentication= 


Starting with LimeSurvey 2.05, authentication will be handled by plugins. As a result, the information below might be outdated. See [[Plugins|the plugins wiki]] for most up to date information.

== Authentication delegation to the webserver== 


System administrators may want to have their '''survey administrators''' authenticated against a central authentication system (Active Directory, openLdap, Radius, ...) rather than using the internal LimeSurvey database. An easy way to do this is to setup your web server software to use this external authentication system, and then ask LimeSurvey to trust the user identity reported by the web server. In order to enable this feature, you have to:
* set '''auth_webserver''' to 'true' in config.php;
* enable authentication from the web server side.


Please note that:
* LimeSurvey will then bypass its own authentication process (by using the login name reported by the web server without asking for a password);
* this can only replace the LimeSurvey GUI authentication system, '''not the survey invitation system''' (participant interface).

== Authentication delegation with no automatic user import== 


Please note that <u>Authentication Delegation doesn't bypass the LimeSurvey authorization system by default</u> - meaning that, even if you don't have to manage passwords in LimeSurvey, you still need to define the users in the LimeSurvey database and assign them the correct set of rights in order to let them access the administration panel.


A user is then granted access to LimeSurvey if and only if:
* he has been authenticated to the web server;
* his login name is defined as a user in the LimeSurvey user database (the user is then granted the privileges of the user defined in the LimeSurvey user database).

== Authentication delegation with automatic user import== 


When managing a huge user database, it is sometimes easier to auto-import users in the LimeSurvey database:
*'''auth_webserver_autocreate_user''': If set to 'true', LimeSurvey will try to auto-import users authenticated by the web server but not already in its users DB.
*'''auth_webserver_autocreate_profile''': An array describing the default profile that will be assigned to the user, including the full (fake) name, email, and privileges.


If you want to customize the user profile so that it matches the logged-in user, you'll have to develop a simple function called '''hook_get_autouserprofile''' - with this function you can retrieve from a central user account database (for instance, from a LDAP directory) the true full name, names, and email of a particular user. You can even customize his privileges on the system based on the groups he is allocated in the external database.


The '''hook_get_auth_webserver_profile''' function takes the user login name as the only argument and can return:
* False or an empty array - in this case the user is denied access to LimeSurvey;
* an array containing all common userprofile entries as described in the <code>$WebserverAuth_autouserprofile</code>

</translate><syntaxhighlight lang="php">function hook_get_auth_webserver_profile($user_name)
{
// Retrieve user's data from your database backend (for instance LDAP) here
... get $user_name_from_backend
... get $user_email_from_backend
... get $user_lang_from_backend
... from groups defined in your backend set $user_admin_status_frombackend_0_or_1
return Array(
'full_name' => "$user_name_from_backend",
'email' => "$user_email_from_backend",
'lang' => '$user_lang_from_backend',
'htmleditormode' => 'inline',
'templatelist' => 'default,basic,MyOrgTemplate',
'create_survey' => 1,
'create_user' => 0,
'delete_user' => 0,
'superadmin' => $user_admin_status_frombackend_0_or_1,
'configurator' =>0,
'manage_template' => 0,
'manage_label' => 0);
}

// If user should be denied access, return an empty array

// return Array();</syntaxhighlight><translate>


{{Alert|The optionnal 'hook_get_auth_webserver_profile' function is for advanced user usage only! For further details, please read the comments from the config-defaults.php file.}}

== User name mapping== 


In the case in which some users have an external user name that is different from their LimeSurvey user name, you may find useful to use a user name mapping. This is done in LimeSurvey by using the '''auth_webserver_user_map''' parameter. For instance, imagine you don't have an 'admin' user name defined in your external authentication database. Then, in order to login to LimeSurvey as admin, you'll have to map your external user name (let's call it 'myname') to the admin login name in LimeSurvey. The corresponding setup is:

</translate>
<syntaxhighlight lang="php">'config'=>array(
...
'auth_webserver_user_map' => array ('myname' => 'admin');
)</syntaxhighlight><translate>


After a successful authentication with the 'myname' login and web server password, you'll be directly authorized to use LimeSurvey as the 'admin' user.


This has serious security implications, so use it with care. Also, protect your config.php from write access by the web server.

== Use one-time passwords== 


A user can open the LimeSurvey login page at default.com/limesurvey/admin and type the username and the one-time password which was previously written into the users table (column one_time_pw) by an external application.


This setting has to be turned on config.php file to enable the usage of one-time passwords (default = false).
<syntaxhighlight lang="php" enclose="pre">
'config'=>array(
'debug'=>0,
'debugsql'=>0,
'use_one_time_passwords'=>true,
)
</syntaxhighlight>


More information can be found in the [[Manage users#Use one-time passwords|"Manage Users" section]].

= Encryption settings {{NewIn|4.0.0}} = 


{{Alert|title=Attention|text=Once set, encryption keys should never be changed, otherwise all encrypted data could be lost !}}


{{Note|When update or install, this parameters was generated by LimeSurvey and set in <code>application/config/security.php</code> file. You can move this settings in config.php if you want or leave in security.php.}}


See [[data encryption]] for detail on this feature.


*'''encryptionkeypair'''
*'''encryptionpublickey'''
*'''encryptionsecretkey'''

= Advanced url settings= 


*'''publicurl:''' This should be set to the URL location of your 'public scripts'. The public scripts are those located in the "limesurvey" folder (or whatever name you gave to the directory that all the other scripts and directories are kept in). '''This settings is available in config.php and it is used when LimeSurvey need an absolute url (for example when token emails are sent).'''
*'''homeurl:''' This should be set to the URL location of your administration scripts. These are located in the /limesurvey/admin folder. This should be set to the WEB URL location - for example, ''http://www.example.com/limesurvey/html/admin''. Don't add a trailing slash to this entry. The default setting in config.php attempts to detect the name of your server automatically using a php variable setting - <code>{$_SERVER<nowiki>[</nowiki>'SERVER_NAME']}</code>. '''In most cases, you can leave this and just modify the remainder of this string to match the directory name you have put the LimeSurvey scripts in.'''
*'''tempurl:''' This should be set to the URL location of your "/limesurvey/tmp" directory - or to a directory in which you would like LimeSurvey to use to serve temporary files.
*'''uploadurl:''' This should be set to the URL location of your "/limesurvey/upload" directory - or to a directory in which you would like LimeSurvey to use to serve uploaded files. This allow you to set uploaded files on another url domain.

= Advanced path settings= 


*'''homedir:''' This should be set to the physical disk location of your administration scripts - for example "/home/usr/htdocs/limesurvey/admin". Don't add a trailing slash to this entry. The default setting in config.php attempts to detect the default root path of all your documents using the php variable setting <code>{$_SERVER<nowiki>[</nowiki>'DOCUMENT_ROOT']}</code>. In most cases you can leave this and just modify the remainder of this string to match the directory name you have put the LimeSurvey scripts in.
*'''publicdir:''' This should be set to the physical disk location of your 'public scripts'.
*'''tempdir:''' This should be set to the physical disk location of your /limesurvey/tmp directory so that the script can read and write files.
*'''uploaddir:''' This should be set to the physical disk location of your /limesurvey/upload directory so that the script can read and write files.
*'''sCKEditorURL:''' url of the fckeditor script.
*'''fckeditexpandtoolbar:''' defines if the fckeditor toolbar should be opened by default.
*'''pdfexportdir:''' This is the directory with the tcpdf.php extensiontcpdf.php.
*'''pdffonts:''' This is the directory for the TCPDF fonts.

= Other advanced settings= 

== Upload files== 


*'''allowedthemeuploads:''' File types allowed to be uploaded in theme editor
*'''allowedresourcesuploads:''' File types allowed to be uploaded in the resources sections, and with the HTML Editor
*'''allowedfileuploads''' {{NewIn|4.0.0}} Global restriction on file type to be uploaded
*'''magic_database:''' {{NewIn|3.17.17}} Allow to use a different MIME database for [https://www.php.net/manual/en/function.finfo-open.php finfo_open]. Can be updated only in config.php file. Example : <code>/usr/share/misc/magic.mgc</code> for redhat based linux.
*'''magic_file:''' {{NewIn|3.17.17}} Allow to use a different file to get the array of extension by mime type than the [https://github.com/LimeSurvey/LimeSurvey/blob/master/application/core/utils/fileExtensions.php included one]. Must be a PHP file return an array. Can be updated only in config.php file.

== Update == 


*'''updatable:''' This setting is in version.php. Can be true or false. If you set to true : when an super admin user log in : LimeSurvey checks if an update is available and show you a warning. If set to false : no check is done and you can't use ComfortUpdate.

</translate>

Debugging

2024-12-19T23:46:57Z

Tassoman: moah fixing

=Debugging=

Working with a framework can sometimes be hard to debug. In Yii we have some tools at our disposal to help debug the application. The very first thing to do is modify '''application/config/config.php''' and to set [[Optional_settings#Development_and_debugging|debug = 2]] at the end. Now we get more errors presented and we can use a trace function to see what a variable's content is at any time during program execution.

If you want to see what queries are sent to the database, you can also enable debugsql by setting it to 1.

To do a dump of a variable you can use the following syntax:

<syntaxhighlight lang="php">$variable = $this->someMethod(); // What would this return?

Yii::trace(CVarDumper::dumpAsString($variable), 'vardump');</syntaxhighlight>

We make use of the <nowiki>Yii::trace()</nowiki> method, and pass it the result of the static call to <nowiki>CVarDumper::dumpAsString()</nowiki>. What it does is is similar to var_dump but it allows a little more control if you need if. The second parameter 'vardump' makes sure our messages gets logged. All this is a lot of typing and since programmers are lazy, we created a global function to save you some trouble. Instead of the lines above you can also use:

<syntaxhighlight lang="php">traceVar($variable);</syntaxhighlight>

As a bonus you will also get the file and line that called the traceVar function to assist in debugging.

Debugging

2024-12-19T23:46:19Z

Tassoman: fixing syntax

=Debugging=

Working with a framework can sometimes be hard to debug. In Yii we have some tools at our disposal to help debug the application. The very first thing to do is modify '''application/config/config.php''' and to set [[Optional_settings#Development_and_debugging|debug = 2]] at the end. Now we get more errors presented and we can use a trace function to see what a variable's content is at any time during program execution.

If you want to see what queries are sent to the database, you can also enable debugsql by setting it to 1.

To do a dump of a variable you can use the following syntax:

<syntaxhighlight lang="php">$variable = $this->someMethod(); // What would this return?

Yii::trace(CVarDumper:dumpAsString($variable), 'vardump');</syntaxhighlight>

We make use of the <nowiki>Yii::trace()</nowiki> method, and pass it the result of the static call to <nowiki>CVarDumper::dumpAsString()</nowiki>. What it does is is similar to var_dump but it allows a little more control if you need if. The second parameter 'vardump' makes sure our messages gets logged. All this is a lot of typing and since programmers are lazy, we created a global function to save you some trouble. Instead of the lines above you can also use:

<syntaxhighlight lang="php">traceVar($variable);</syntaxhighlight>

As a bonus you will also get the file and line that called the traceVar function to assist in debugging.

Yii

2022-05-11T13:26:19Z

Tassoman: /* Yii */

=Yii=

Table of contents:{toc}

This page is intended to help people get started on the Yii branch of the code and to provide some guidance in coding. At the moment I am just getting started with the branch myself and run into some stuff I think needs to be adressed. Please feel free to help improve this page and correct me if I'm wrong ;-)

First some useful links:

[https://www.yiiframework.com/doc/guide/1.1/ Userguide of the Yii framework v1.1]

[http://www.yiiframework.com/wiki/83/netbeans-ide-and-yii-projects/ Some hints on code completion in NetBeans IDE]

==Controllers==

Most important stuff to know is in [http://www.yiiframework.com/doc/guide/1.1/en/basics.controller] where the basics of controllers / actions are described.

For LimeSurvey we use our own controller class LSYii_Controller to extend instead of the CController class. This helps us by providing the necessary libraries and some convenience methods and it also helps to have a single point to inject future extensions.

==Actions==

In Yii controllers can encapsulate actions when we use a method with a special name that is prefixed with 'action'. So a method actionSubmit would be the submit action. Actions can also be separated from their controller for various reasons. In LimeSurvey we try to do this as much as possible, placing the action classes in a subdirectory below the controllers directory with the lowercased name of the controller they belong to.

==Inline documentation==

To help our fellow coders understand what a method is supposed to do, we try to document using [http://en.wikipedia.org/wiki/PHPDoc docblocks] as much as possible. Providing type hints on return values helps in most IDE for code completion. Sometimes working like this can feel like more typing for the coder who knows his way around the code but for other who are not familiar with the code it can be of great value. So please document as much as possible.

Plugins - advanced

2022-05-05T15:29:39Z

Tassoman:

<languages /><translate>

== Overview == 


Starting from LimeSurvey 2.05, LimeSurvey will officially support plugins. Some plugins will be supported by the LimeSurvey team and will go into core. Some will be supported by others outside the LimeSurvey team. To help find them, check out the [[Available third party plugins]] and add your own plugin to it!


Plugins allow users to customize the functionality of their installation while still being able to benefit from regular software updates.


This documentation is meant for developers that are extending LimeSurvey for their own use or for their clients; end users will not be helped by this documentation.


Plugins must implement the [https://github.com/LimeSurvey/LimeSurvey/blob/master/application/libraries/PluginManager/iPlugin.php iPlugin] interface. We recommend extending your plugin class from the [https://github.com/LimeSurvey/LimeSurvey/blob/master/application/libraries/PluginManager/PluginBase.php PluginBase] class.


Plugins are developed around an [http://manual.limesurvey.org/Plugin_events event] mechanism.

== Plugin settings == 


By extending you benefit from common functionality required by plugins that we already have implemented for you. One of these function is the implementation of the getPluginSettings function. This function must return an array describing the configuration options for the user.


The example plugin exposes just 1 configurable setting, the message it'll show.


<syntaxhighlight lang="php">
protected $settings = array(
'logo' => array(
'type' => 'logo',
'path' => 'assets/logo.png'
),


'message' => array(
'type' => 'string',
'label' => 'Message'
)
);
</syntaxhighlight>


The array contains a name for each setting as a key. The values are arrays containing the required meta data.


Supported types are:


* logo
* int (integer number)
* string (alphanumeric)
* html
* choice
* relevance
* info


Besides type a number of other keys are available:


* label, defines a label
* default, defines a value to show if no value is specified (only for global settings, not for survey settings)
* current, defines the current value.
* readOnly : shown the settings as readonly
* htmlOptions, the htmlOptions of the input part ( see Yii manual [[https://www.yiiframework.com/doc/api/1.1/CHtml]])
* pluginOptions, for some settings (html or select) : set the widget option
* labelOptions : htmlOptions of the label
* controlOptions : htmlOptions of the wrapper of label and input

You can find a plugin example using all actual settings at [https://framagit.org/Shnoulle/exampleSettings exampleSettings]
=== Read and write plugin settings === 


It's possible to read and write plugin settings directly from your plugin code.


Example:


<syntaxhighlight lang="php">
$mySetting = $this->get('mySetting');
$this->set('mySetting', $mySetting + 1);
</syntaxhighlight>


You can get a default value if the setting happens to be null:


<syntaxhighlight lang="php">
$mySetting = $this->get('mySetting', null, null, 10); // 10 is default
</syntaxhighlight>

== Events == 


Plugins subscribe to events and can interact with LimeSurvey when the event is fired. For a list of currently available events check [[Plugin events]].

== API == 


Plugins should only extend LimeSurvey via its "public" API. This means that directly using classes found in the source code is a bad practice. Though we can't force you not to, you risk having a broken plugin with every minor update we do.


As much as possible interact with LimeSurvey only via methods described [http://api.limesurvey.org/classes/LimeSurvey.PluginManager.LimesurveyApi.html here]. Same as for events.


The API object is available via <code>$this->api</code> when extending from PluginBase, otherwise you can get it from the PluginManager instance that is passed to your plugins' constructor.


New functions can be added to the API object upon request.

== Localization {{NewIn|v=3}} == 


It's possible for plugins to add their own locale files. File format used is .mo, same as core translations. The files must be stored in


<plugin root folder>/locale/<language>/<language>.mo


where "<language>" is a two letter word like "de" or "fr".


To use the specific locale file, use the plugin function gT:


<syntaxhighlight lang="php">
$this->gT("A plugin text that needs to be translated");
</syntaxhighlight>


If the given string can't be found in the plugin specific locale file, the function will look in the core locale files. So it's safe to use strings like "Cancel":


<syntaxhighlight lang="php">
$this->gT("Cancel"); // Will be translated even if "Cancel" is not in the plugin locale file
</syntaxhighlight>


If you are using views together with your plugin, you should use


<syntaxhighlight lang="php">
$plugin->gT("Translate me");
</syntaxhighlight>


to do plugin specific translation in your view.


You can use the [https://github.com/LimeSurvey/LimeSurvey/blob/master/locale/_template/limesurvey.pot limesurvey.pot] file as an example of how a pot file can look like. This is imported into your translation tool.

=== Tools === 


One open-source tool to edit po- and mo-files is [https://poedit.net/ Poedit].

== Logging {{NewIn|v=3}} == 


If you want to log something from your plugin, just write


<syntaxhighlight lang="php">
$this->log("Your message");
</syntaxhighlight>


The default logging level is trace, but you can give another log level as an optional second argument:


<syntaxhighlight lang="php">
$this->log("Something went wrong!", CLogger::LEVEL_ERROR);
</syntaxhighlight>


The log file can be found in folder


<limesurvey root folder>/tmp/runtime/plugin.log


Your plugin name is automatically used as category. A nice way to see only the errors from your plugin is using grep (on Linux):


$ tail -f tmp/runtime/plugin.log | grep <your plugin name>


More info about configuring logging in Yii 1: [[Optional_settings#Logging_settings]].

== Extension updates {{NewIn|v=4}} == 


Since LimeSurvey version 4.0.0, there's a system in place to deal with plugin and other extension updates. To use this system, your extension config.xml file needs to include updater configuration.


<syntaxhighlight lang="xml">
<updaters>
<updater>
<stable>1</stable>
<type>rest</type>
<source>https://comfortupdate.limesurvey.org/index.php?r=limestorerest</source>
<manualUpdateUrl>https://somedownloadlink.com/maybegithub</manualUpdateUrl>
</updater>
</updaters>
</syntaxhighlight>


(The source tag above points to the LimeStore REST API, which will be used for all extensions available in our LimeStore.)


{| class="wikitable"
|+ Updater tag descriptions
|-
! Tag
! Description
|-
| stable
| "1" if this source only gives you stable version numbers; "0" if the source will also provide unstable versions, like <code>0.3.3-beta</code>.
|-
| type
| For now, only type <code>rest</code> is supported. It's easy to add new updater types (version checkers), like git, wget, etc.
|-
| source
| The URL to fetch new versions from.
|-
| manualUpdateUrl
| URL which the user can go to to update the latest version of the extension.
|-
| automaticUpdateUrl
| TODO
|}


If you don't want to supply an updater, you should put the following text in your config XML file:


<syntaxhighlight lang="xml">
<updaters disabled="disabled">
</updaters>
</syntaxhighlight>


This way, you tell the system that you purposefully disabled the update system, and didn't just forget to add it.


The new plugin '''UpdateCheck''' - installed and activated by default - checks for new updates for ''all'' installed extensions when a super admin logs in, asynchronously, max one time every 24 hours. If any new versions are found, a notification is pushed.


[[File:availableupdates.png||Available updates]]


If a new security update is found, the notification will open automatically and be styled in "danger" class.


[[File:availablesecurityupdates.png||Available security updates]]


You can manually check for updates by going to the plugin manager view and click on "Check updates". Note that this button is only visible if the UpdateCheck plugin is activated.


[[File:manuallycheckforupdates.png||Manually check for updates]]

=== Under the hood === 


This section provides a brief overview over the extension updater implementation.


The extension updater is part of the ExtensionInstaller library. Below is a UML diagram for the classes related to the updater process.


[[File:extensionupdateruml.png||Extension updater UML diagram]]


Program flow when Yii starts:


<pre>
Yii init
VersionFetcherServiceLocator->init()
Add REST version fetcher
ExtensionUpdaterServiceLocator->init()
Add PluginUpdater
TODO: Add an updater for each extension type (theme, question template, ...)
</pre>


Program flow when running the UpdaterCheck plugin:


<pre>
Get all updaters from ExtensionUpdaterServiceLocator
Loop each updater
For each updater, loop through version fetchers configured by <updater> XML
For each version fetcher, contact remote source and get version information
Compose all versions into a notification
</pre>


The [https://github.com/LimeSurvey/LimeSurvey/blob/develop/application/core/plugins/UpdateCheck/UpdateCheck.php#L130 checkAll] method in the UpdateCheck plugin provides an example of how to query all extensions for new versions.

==== Adding new version fetchers ==== 


To add a new custom version fetcher, run this during Yii initialization:


<syntaxhighlight lang="php">
$service = \Yii::app()->versionFetcherServiceLocator
$service->addVersionFetcherType(
'myNewVersionFetcherType',
function (\SimpleXMLElement $updaterXml) {
return new MyNewVersionFetcher($updaterXml);
}
);
</syntaxhighlight>


Of course, the class <code>MyNewVersionFetcher</code> has to subclass <code>VersionFetcher</code>.


To use your new version fetcher, configure the <code>type</code> tag in the updater XML to use
<code>myNewVersionFetcherType</code> (instead of e.g. <code>rest</code>).

==== Adding new extension updaters ==== 


To add a new custom extension updater, run this during Yii initialization:


<syntaxhighlight lang="php">
$service = \Yii::app()->extensionUpdaterServiceLocator;
$service->addUpdaterType(
'myNewExtensionUpdater',
function () {
return MyNewExtensionUpdater::createUpdaters();
}
);
</syntaxhighlight>


Class <code>MyNewExtensionUpdater</code> has to subclass <code>ExtensionUpdater</code>.


The top <code>type</code> tag in config.xml ('plugin', 'theme', ...) will control which extension updater are used for this extension. The system is not fully customizable yet, since you also need to add a custom ExtensionInstaller, menu items, etc. But in theory, and maybe in the future, it should be possible to add a new type of extension this way.

== Extension installer == 


The extension installer library consists of two abstract classes:


* ExtensionInstaller
* FileFetcher


The ExtensionInstaller is subclassed for each extension type, like PluginInstaller, QuestionThemeInstaller, etc.


The FileFetcher is subclassed for each different way to fetch files. Currently, only uploaded zip files are supported, but in the future, there could be a Github or LimeStore fetcher too.


[[File: extensioninstalleruml.png]]

== Special plugins == 


* [[Authentication plugin development]]
* [[Export plugin development]]

== Available plugins == 
* [[Authentication plugins]]
* [[Audit log]]
* [[CintLink]]
* [[Available third party plugins]]

== Tutorial == 
[https://medium.com/@evently/creating-limesurvey-plugins-adcdf8d7e334 This] step-by-step tutorial shows how to create a plugin that sends a post request on every survey response submission. The tutorial shows you how to create and save global and per-survey settings, how to register events and more.


[[Category:Development]]
[[Category:Plugins]]
</translate>

Using regular expressions

2022-01-19T17:43:08Z

Tassoman: adding multiline email validation

<languages /> <translate>


__TOC__


Regular Expressions must start and finish with a forward slash ("/"). You can find a good library of regular expressions at http://www.regexlib.net/. These patterns will almost always work if they are surrounded by forward slashes.


To test your regex you can [https://regex101.com/ use this regex tester].


{{Note|To improve this wiki section, we kindly ask you to add your successfully tested regular expression(s) to provide a better understanding of this feature to the new LimeSurvey (potential) users.}}


{{Alert|title=Attention|text= Please note that all the below examples are written on one line!}}

=Important: Regular Expressions in conditions= 


Note that when using regular expressions in the condition editor, do NOT include the beginning and ending slash.

=Email validation= 


Update (12/2018): Since these days domain names cannot only hold special characters like “ü” but also use more than 3 characters as domain name like .''tech'' or .''company'', the below email regex only checks if “@” and “.” exists within the entered email address.
<source lang="html">
/^.+?@.+?\..+$/
</source>

If you want to validate one address per line, in a multiline long text field:
<source lang="html">
/^(((\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*(\r\n)?\n?)+)*)$/
</source>

At this outdated regex the domain name is limited to 3 characters which doesn't cover all available domains:
<source lang="html">
/^(\w[-._+\w]*\w@\w[-._\w]*\w\.\w{2,3})$/
</source>

=Postcodes= 

==Australian postcodes:== 


<source lang="html">/^[0-9]{4}/</source>

==Brazilian postcodes== 


<source lang="html">/^[0-9]{2}\.[0-9]{3}-[0-9]{3}$/</source>

==Canadian postcodes== 


<source lang="html">/^[a-zA-Z]\d{1}[a-zA-Z](\-| |)\d{1}[a-zA-Z]\d{1}$/</source>

==US postal codes== 


<source lang="html">/^[0-9]{5}([- /]?[0-9]{4})?$/</source>


For the postal code to start with zero, use:


<source lang="html">/^[0-9]{5}(?:-[0-9]{4})?$/</source>

==UK postcodes== 


<source lang="html">/^[A-Z][A-Z]?[0-9][A-Z0-9]? ?[0-9][ABDEFGHJLNPQRSTUWXYZ]{2}$/i</source>


Note that this is not very exact, and a more exact validation is much more complex. For example, see [https://stackoverflow.com/questions/164979/uk-postcode-regex-comprehensive StackOverflow answer] and [https://en.wikipedia.org/wiki/Talk:Postcodes_in_the_United_Kingdom#Regular_Expressions Wikipedia] for more information.

==French postcodes== 


<source lang="html">/(^[0-8]\d\d{3}$)|(^9[0-5]\d{3}$)|(^97[1-6]\d{2}$)|(^98[46-8]\d{2}$)/</source>


The above expression is very precise and it will check whether or not the French Department exists (first two digits), including overseas Departments and overseas Territories (DOM-TOM).

=Phone numbers= 

==US phone numbers== 


<source lang="html">/^(?:$[2-9]\d{2}$\ ?|[2-9]\d{2}(?:\-?|\ ?))[2-9]\d{2}[- ]?\d{4}$/</source>


or


<source lang="html">/^[\.\- ]{0,}[0-9]{3}[\.\- ]{0,}[0-9]{3}[\.\- ]{0,}[0-9]{4}[\.\- ]{0,}$/</source>


This second option will match all phone Canadian and US phone numbers that include non-digit symbols including:


<source lang="html"> . ( ) - (space)</source>


This will allow you to match phone numbers which resemble below:
*(555)555 5555
*555.555.5555
*555 555 5555
*(555)-555-5555
*555-555-5555
*555555555

==Australian phone numbers== 


The following patterns match all various Australian mobile and landline phone numbers including with "+61" country prefix:
*(02) 9123 6535
*03 1234-5345
*0412 345 678
*+61 2 3456 789


But not:
* 234 3450 234
*a234 534 3432
*134567
*123456789013


Brackets, white space and hypens are ignored.


The 'Very precise:' versions listed here match against the first four or five digits in a number to ensure that they are valid Australian numbers.


The 'Not very precise:' only match against the first and second digit so may allow invaid numbers.

===All Australian phone numbers (mobile and landline - area code required)=== 


Very precise:


<source lang="html">/^$?(?:\+?61|0)(?:(?:2$?[ -]?(?:3[ -]?[38]|[46-9][ -]?[0-9]|5[ -]?[0-35-9])|3\)?(?:4[ -]?[0-57-9]|[57-9][ -]?[0-9]|6[ -]?[1-67])|7\)?[ -]?(?:[2-4][ -]?[0-9]|5[ -]?[2-7]|7[ -]?6)|8\)?[ -]?(?:5[ -]?[1-4]|6[ -]?[0-8]|[7-9][ -]?[0-9]))(?:[ -]?[0-9]){6}|4\)?[ -]?(?:(?:[01][ -]?[0-9]|2[ -]?[0-57-9]|3[ -]?[1-9]|4[ -]?[7-9]|5[ -]?[018])[ -]?[0-9]|3[ -]?0[ -]?[0-5])(?:[ -]?[0-9]){5})$/
</source>


Not very precise:


<source lang="html">/^(?:\+?61|0)[2-478](?:[ -]?[0-9]){8}$/</source>

===All Australian phone numbers (landlines only - area code required)=== 


Very precise:


<source lang="html">/^$?(?:\+?61|0)(?:2$?[ -]?(?:3[ -]?[38]|[46-9][ -]?[0-9]|5[ -]?[0-35-9])|3\)?(?:4[ -]?[0-57-9]|[57-9][ -]?[0-9]|6[ -]?[1-67])|7\)?[ -]?(?:[2-4][ -]?[0-9]|5[ -]?[2-7]|7[ -]?6)|8\)?[ -]?(?:5[ -]?[1-4]|6[ -]?[0-8]|[7-9][ -]?[0-9]))(?:[ -]?[0-9]){6}$/</source>


Not very precise:


<source lang="html">/^(?:\+?61|$?0)[2378]$?(?:[ -]?[0-9]){8}$/</source>

===New South Wales landline phone numbers (area code optional)=== 


Very precise:


<source lang="html">/^(?:$?(?:\+?61|0)2$?[ -]?)?(?:3[ -]?[38]|[46-9][ -]?[0-9]|5[ -]?[0-35-9])(?:[ -]?[0-9]){6}$/</source>


Not very precise:


<source lang="html">/^(?:$?(?:\+?61|0)2$?(?:[ -]?[0-9]){7}[0-9]$/</source>

===Victorian and Tasmanian landline phone numbers (area code optional)=== 


Very precise:


<source lang="html">/^(?:$?(?:\+?61|0)3$?[ -]?)?(?:4[ -]?[0-57-9]|[57-9][ -]?[0-9]|6[ -]?[1-67])(?:[ -]?[0-9]){6}$/</source>


Not very precise:


<source lang="html">/^(?:$?(?:\+?61|0)3$?(?:[ -]?[0-9]){7}[0-9]$/</source>

===Queensland landline phone numbers (area code optional)=== 


Very precise:


<source lang="html">/^(?:$?(?:\+?61|0)7$?[ -]?)?(?:[2-4][ -]?[0-9]|5[ -]?[2-7]|7[ -]?6)(?:[ -]?[0-9]){6}$/</source>


Not very precise:


<source lang="html">/^(?:$?(?:\+?61|0)7$?(?:[ -]?[0-9]){7}[0-9]$/</source>

===South Australia, Northern Territory, Western Australia landline phone numbers (area code optional)=== 


Very precise:


<source lang="html">/^(?:$?(?:\+?61|0)8$?[ -]?)?(?:5[1-4]|6[0-8]|[7-9][0-9])$/</source>


Not very precise:


<source lang="html">/^(?:$?(?:\+?61|0)8$?(?:[ -]?[0-9]){7}[0-9]$/</source>

===Australian mobile phone numbers only=== 


Very precise:


<source lang="html">/^(?:\+?61|0)4 ?(?:(?:[01] ?[0-9]|2 ?[0-57-9]|3 ?[1-9]|4 ?[7-9]|5 ?[018]) ?[0-9]|3 ?0 ?[0-5])(?: ?[0-9]){5}$/</source>


Not very precise:


<source lang="html">/^(?:$?(?:\+?61|0)4$?(?:[ -]?[0-9]){7}[0-9]$/</source>

==Belgian phone number== 
<source lang="html">/^((\+|00)32\s?|0)(\d\s?\d{3}|\d{2}\s?\d{2})(\s?\d{2}){2}$/</source>
==Belgian mobile phone number==
<source lang="html">/^((\+|00)32\s?|0)4(60|[789]\d)(\s?\d{2}){3}$/</source>
==French phone number==
<source lang="html">/^((\+|00)33\s?|0)[1-59](\s?\d{2}){4}$/</source>
==French mobile phone number==
<source lang="html">/^((\+|00)33\s?|0)[67](\s?\d{2}){4}$/</source>
==Luxemburg phone number==
<source lang="html">/^((\+|00\s?)352)?(\s?\d{2}){3,4}$/</source>
==Luxemburg mobile phone number==
<source lang="html">/^((\+|00\s?)352)?\s?6[269]1(\s?\d{3}){2}$/</source>
=German marks (with optional plus or minus)=
<source lang="html">/^[1-6]{1}[\+|\-]?$/</source>

=Age validation= 


Example: Age 20-99
<source lang="html">/([2-9][0-9])/</source>


Example: Age 18-35
<source lang="html">/(1[8-9]|2[0-9]|3[0-5])/</source>


Example: Age 19-65
<source lang="html">/^(1[8-9]|[2-5][0-9]|6[0-5])$/</source>

=Number validation= 

==Numbers from 1 to 99999== 
<source lang="html">/^([1-9]|[1-9][0-9]|[1-9][0-9][0-9]|[1-9][0-9][0-9][0-9]|[1-9][0-9][0-9][0-9][0-9])$/</source>
<source lang="html">/^[1-9][0-9]{0,4}$/ does the same as above but should run a little faster</source>
==Numbers from 1 to 999, 1.000 to 999.999 to 999.999.999==
<source lang="html">/^[1-9][0-9]{0,2}(?:\.[0-9]{3}){0,2}$/</source>
Accepts numbers from 1 to 999, 1.000 to 999.999 to 999.999.999 but
rejects numbers like 999.1.1 , 94.22.22, 999.1.22, 999.11.1, 999.1.333

==Number validation with optional decimal (for price)== 
Accepts numbers from 0 to 199, with 2 decimal optional:
<source lang="html">/^([1][0-9][0-9]|[1-9][0-9]|[0-9])((\.)[0-9][0-9])?$/</source>

==Number validation with thousand separator== 
Space as separator, no minus
<source lang="html">/^(?!0)\d{1,3}(\ \d{3})*$/</source>
Dot as separator, minus allowed
<source lang="html">/^-?(?!0)\d{1,3}(\.\d{3})*$/</source>


It forces two decimal points and accepts numbers from 1.00 to 999,999,999.00 with an optional comma delimiting thousands/millions
including all of the following: 1.00, 1,000.00, 12,345.67, 12345,02, 123,456,468.00, 1234566.00, 123456789.00
but not 1,23.00, 12,3.4 or 1234,43.04
<source lang="html">/^[1-9][0-9]{0,2}(?:,?[0-9]{3}){0,3}\.[0-9]{2}$/</source>

Similar to the above: Forces two decimal points but accepts a "0" before decimal separator ",".
<source lang="html">/[0-9]{0,2}(?:,?[0-9]{3}){0,3}\.[0-9]{2}$/</source>


Same as above, but the two decimal points are optional:
<source lang="html">/^[1-9][0-9]{0,2}(?:,?[0-9]{3}){0,3}(?:\.[0-9]{2})?$/ </source>

==Month (1-12)== 


If you want to ask for the month a person was born you can validate the input as follows:


<source lang="html">/^[0]*[1-9]$|^[0]*1[0-2]$/</source>

=Minimum width (set to 3 in this example)= 


<source lang="html">/^.{3,}$/</source>

=Currency= 

==US currency (dollar sign and cents optional)== 


<source lang="html">/^\$?\d+(\.(\d{2}))?$/</source>


Check for comma usage:
<source lang="html">/^\$?\d{1,3}(\d+(?!,))?(,\d{3})*(\.\d{2})?$/</source>

==Swiss price== 


A number with two decimal numbers after the decimal point of which the last one is either a 5 or a 0:


<source lang="html">/^(\d+)(\.\d(05)?)?$/</source>

=Validate score= 

==1-10== 


<source lang="html">/^[1-9]{1}$|^10$/</source>

==1-100== 


<source lang="html">/^[1-9]?[0-9]{1}$|^100$/</source>

=Text validation= 


The [[Question type - Multiple short text|multiple short text question type]] doesn't support minimum or maximum answers at the moment. One way around this is to use a [[Question type - Long free text|long free text question type]] with a regular expression.


The below expression tests for at least one word per line for at least 3 lines and no more than 10 lines:


<source lang="html">/(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+)*)(?:[,.;:?!& \n\r]?(?:\n|\r|\n\r|\r\n)(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+)*)){2,10}/is</source>


If you want, say five words per line, you could change the first and last star/asterisk to {4,}:


<source lang="html">/(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+){4,})(?:[,.;:?!& \n\r]?(?:\n|\r|\n\r|\r\n)(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+){4,})){2,10}/is</source>


If you wanted one or more words per line (between line 1 and line 5), you can change the content located within the last curly braces to '''0,4''' (note you use 0 because you're already matching the first line).


<source lang="html">/(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+)*)(?:[,.;:?!& \n\r]?(?:\n|\r|\n\r|\r\n)(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+)*)){0,4}/is</source>

==Word count== 


The following restricts the number of words allowed to a minimum of 1 and a maximum of 200:


<source lang="html">/^[-\w]+(?:\W+[-\w]+){0,199}\W*$/</source>


To increase the minimum change the zero part of {0,199}.


To increase or decrease the maximum change the "199" part of {0,199}.

=Time validation= 


There are a number of ways to write time formats. Some of the possible options are 12 hour or 24 hour, with seconds or without. Although it is an option to use the [[Question type - Date|date question type]] (it can also capture time) you can use the [[Question type - Short free text|short free text question type]] with one of the below validation regular expressions.


The following three validation strings test for 24 hour time (in order of appearances) without seconds, with optional seconds lastly with seconds required:


<source lang="html">/^(?:[01][0-9]|2[0-3]):[0-5][0-9]$/</source>


<source lang="html">/^(?:[01][0-9]|2[0-3]):[0-5][0-9](?::[0-5][0-9])?$/</source>


<source lang="html">/^(?:[01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]$/</source>


The following three match 12 hour time, as above with seconds, optional seconds and with seconds required:


<source lang="html">/^(?">00:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9] (?:pm|PM))$/</source>


<source lang="html">/^(?:00:[0-5][0-9](?::[0-5][0-9])? (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9](?::[0-5][0-9])? (?:[ap]m|[AP]M)|12:[0-5][0-9](?::[0-5][0-9])? (?:pm|PM))$/</source>


<source lang="html">/^(?:00:[0-5][0-9]:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9]:[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9]:[0-5][0-9] (?:pm|PM))$/</source>


The following three match either 12 or 24 hour time as above with seconds, optional seconds and with seconds required:


<source lang="html">/^(?:(?:00:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9] (?:pm|PM))|(?:[01][0-9]|2[0-3]):[0-5][0-9])$/</source>


<source lang="html">/^(?:(?:00:[0-5][0-9](?[0-5][0-9])? (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9](?[0-5][0-9])? (?:[ap]m|[AP]M)|12:[0-5][0-9](?[0-5][0-9])? (?:pm|PM))|(?:[01][0-9]|2[0-3]):[0-5][0-9](?[0-5][0-9])?)$/</source>


<source lang="html">/^(?:(?:00:[0-5][0-9]:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9]:[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9]:[0-5][0-9] (?:pm|PM))|(?:[01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9])$/</source>

=US states= 


To validate for one state use the following (example is Texas):
*TX uppercase only: <source lang="html">/^(TX)$/</source>
*tx lowercase only: <source lang="html">/^(tx)$/</source>
*TX upper or lowercase: <source lang="html">/^([T|t][X|x])$/</source>

=Profanity Filter= 


To filter profanity words from an answer:


<source lang="html">/^(?i)((?!\bENTERPROFANITYHERE\b).)*$(?-i)/</source>


Replace "ENTERPROFANITYHERE" with your bad word.


The \b will allow passing of words such as "assassination" and "hello" if you enter "ass" or "hell" as your profanity word. This also works if you are trying to omit other words, names etc. from answers.

=Helpful links= 


In the beginning of this wiki section, we recommend you to use https://regex101.com/ to test/create regular expressions. You can also use https://www.regextester.com/ to create expressions in case you are unhappy about the first option.

</translate>

Manage users/it

2019-05-29T14:29:52Z

Tassoman:

<languages />
__TOC__

= Gestione Utente =

<div class="mw-translate-fuzzy">
La gestione degli utenti ti permette di aggiungere degli utenti amministratori addizionali a LimeSurvey. In questo capitolo li chiameremmo semplicemente 'utenti'. Non devono essere confusi con [[Survey participants|survey participants]].
</div>

==Creare utenti==

<div class="mw-translate-fuzzy">
Per creare un nuovo utente, aprire il gestore utenti
("Configurazioni" -> "Utenti" -> "Gestione degli amministratori delle indagini"):
</div>

<center>[[File:LimeSurveyBenuzerVerwaltung.jpg]]</center>

Then, click on '''Add user''' located in the upper right area of '''User control''' table. A window will show up asking you to:

<div class="mw-translate-fuzzy">
[[File:LimeSurveyAddUser.jpg]]
* inserire lo username desiderato nel campo '''Username'''.
* inserire l'indirizzo email nel campo di testo '''e-mail'''. Nota:
** Se non vuoi che l'utente riceva l'email di conferma con il link all'istanza LimeSurvey, lo username, la password, puoi spedire l'email di conferma al tuo indirizzo di posta elettronica e solo in un secondo momento sostituirlo con quello dell'utente.
** LimeSurvey invierà una mail di conferma all'indirizzo inserito in questo campo.
* inserisci il nome completo dell'utente nel campo '''Nome Completo'''. Nota:
** Il nome completo inserito sarà utilizzato come nominativo standard nelle indagini create da quest'utente.
* Clicca su '''Salva'''
</div>

<center>[[File:LimeSurveyAddUser.jpg]]</center>

<div class="mw-translate-fuzzy">
Quindi, hai appena creato un nuovo utente. Potrai saperne di più su come impostare i permessi degli utenti, se continuerai a leggere oltre.
</div>

<center>[[File:LimeSurveyBleistiftSymbol.jpg]]</center>

As you can see below, there are four options under the '''Action''' column that allow you to:

<center>[[File:Edit users.png]]</center>

*edit the general aspects of a user - by clicking the pen symbol.
*delete the user from the survey administrators database - by clicking the wastebin button.
*set global permissions for a user - by clicking the lock symbol.
*set theme permissions for a user - by clicking the pen-and-lock symbol.

<div class="mw-translate-fuzzy">
==Modifica Utenti==
</div>

<div class="mw-translate-fuzzy">
Puoi usare il simbolo della 'penna' per modificare un utente:
</div>

<div class="mw-translate-fuzzy">
Puoi impostare un nuovo indirizzo email, nome completo ed anche cambiare la password. Quando hai terminato, clicca su '''Salva'''.
</div>

==Delete user==

<div class="mw-translate-fuzzy">
Per eliminare un account utente semplicemente clicca sul bottone del cestino nella linea corrispondente all'account utente che dovrebbe essere eliminato e premi '''OK'''.
</div>

<div class="mw-translate-fuzzy">
==Impostare permessi generali per un utente==
</div>

{{Alert|Global permissions apply to the whole LimeSurvey application. If you want to set permissions only for a specific survey, you can use the [[Manage users#Setting permissions for a single survey|survey permissions settings]].}}

<div class="mw-translate-fuzzy">
Per settare i permessi globali per un utente basta cliccare sul simbolo del lucchetto.
</div>

<center>[[File:User_global_permission.png]]</center>

<div class="mw-translate-fuzzy">
Il sistema utilizza CRUD (create, read, update and delete) come impostazioni dei permessi di un'indagine. Selezionando il primo input, si selezionato tutti i permessi CRUD per quella riga. Nel settare i permessi, si raccomanda fortemente di estendere la schermata utilizzando il bottone con la freccia sopra la colonna con le checkbox.
</div>

<center>[[File:User_global_permission_complete.png]]</center>

<div class="mw-translate-fuzzy">
Ora puoi aggiungere o rimuovere le seguenti autorizzazioni.
</div>

<div class="mw-translate-fuzzy">
*'''Panel Partecipanti''': see [[Central participants database]]
</div>

<div class="mw-translate-fuzzy">
*'''Set di etichette''': permesso di creare, aggiornare, utilizzare (visualizzare/leggere) e cancellare set di etichette. Questi non hanno specifici permessi (a differenza dei modelli).
</div>

<div class="mw-translate-fuzzy">
*'''Impostazioni & plugin''': con questi permessi un utente può controllare l'integrità dei dati, salvare il database SQL in un file .sql, settare le impostazioni generali, visualizzare le informazioni PHP nelle impostazioni generali e gestire tutti i plugin.
</div>

<div class="mw-translate-fuzzy">
*'''Indagini''': permette l'accesso a tutte le indagini. Per permettere ad un utente solamente di creare e gestire le proprie indagini, bisogna concedergli solo i permessi 'Creare'. Il creatore di un sondaggio è il proprietario dell'indagine e sarà sempre in grado di gestirla. Ricorda che ogni questionario può avere delle autorizzazioni specifiche, quelle globali sono applicate prima delle autorizzazioni specifiche dell'indagine.
</div>

<div class="mw-translate-fuzzy">
*'''Modello''': permette all'utente di utilizzare tutti i modelli e di modificare tutti quelli non standard. Una persona con questi diritti dovrebbe avere sufficienti conoscenze in termini di HTML, JavaScript e CSS. Se un utente non ha familiarità con queste cose e si suppone di utilizzare un modello specifico, sarebbe meglio dargli solo il permesso di 'Leggere'. Ogni template può avere permessi specifici.
</div>

*'''Gruppi di utenti''': questi permessi permettono ad un utente di creare/visualizzare/aggiornare/cancellare gruppi di utenti.

<div class="mw-translate-fuzzy">
*'''Utenti''': con questi permessi un utente può creare, modificare e cancellare i proprio utenti amministratori. I nuovi utenti non possono avere dei permessi maggiori di quelli del 'genitore' che li ha creati - inoltre non saranno in grado di modificare gli utenti appartenenti ad altri amministratori. Se ciò deve esser fatto, deve esser prima concessa un'autorizzazione da SuperAdmin.
</div>

<div class="mw-translate-fuzzy">
*'''SuperAdministrator''': questo permesso può essere aggiunto o rimosso solo dall'utente chiamato '''admin''' e garantisce autorizzazioni complete sull'intera istanza LimeSurvey. '''Nota''': quest'autorizzazione è molto potente e dovresti stare molto attento nel concederla.
</div>

*'''Use internal database authentication''': This permission allows users to access LimeSurvey's panel via the authentication page (e.g. ''http://domain/admin/authentication/sa/login''). If it is unchecked and the respective user tries to connect to LimeSuvey's panel, he will get the following error: 'Internal database authentication method is not allowed for this user'.

{{Note|All the permissions mentioned above that belong to the [[Optional_settings#Security|forced super administrator]] cannot be removed via the GUI.}}

<div class="mw-translate-fuzzy">
==Impostare permessi su modelli per un utente==
</div>

<div class="mw-translate-fuzzy">
Con i permessi sui modelli puoi impostare quale design template un utente può selezionare quanto crea o modifica un'indagine. Potrebbe esser una buona idea quella di restringere i modelli che un utente può selezionare allo scopo di prevenire utilizzi indesiderati di un template che non è adatto ad un particolare tipo di indagine/utente.
</div>

<div class="mw-translate-fuzzy">
'''Nota''': se hai uno specifico modello di design per un gruppo di utenti o clienti, potresti voler restringere il loro accesso ai solo modelli creati ai loro scopi.
</div>

<div class="mw-translate-fuzzy">
Per settare/modificare i permessi sui modelli per un semplice utente, cliccare sul simbolo 'penna-e-lucchetto'.
</div>

<center>[[File:LimeSurveySetDesignTemplatesLS.jpg]]</center>

<div class="mw-translate-fuzzy">
Ora è possibile selezionare i modelli di design che quell'utente può selezionare. Dopo aver completato la selezione/deselezione, clicca semplicemente su '''Salva''' nell'angola in alto a destra;
</div>

<div class="mw-translate-fuzzy">
I più importanti casi d'uso per garantire i diritti degli utenti sono raccolti nelle parte '''casi d'uso''' di quest'articolo.
</div>

=Utilizzare one-time password=

<div class="mw-translate-fuzzy">
Dalla versione 1.81 un utente può richiamare il login di LimeSurvey da /limesurvey/admin e passare il nome utente e una one-time password che era stata precedentemente inserita nella tabella utenti (colonna one_time_pw) da un'applicazione esterna.
</div>

<div class="mw-translate-fuzzy">
Per abilitare questo metodo di accesso [[Optional settings#Use_one_time_passwords |bisogna attivare un'impostazione]] ($use_one_time_passwords = true;) in config.php.
</div>

L'URL deve contenere le seguenti variabili:
*'''Utente''': l'username normalmente utilizzato per accedere a LimeSurvey. Questo nome utente deve esistere nella tabella 'users' del database.
*'''onepass''': il testo in chiaro della password che sarà poi comparata con la password contenuta nella tabella 'users'.

<div class="mw-translate-fuzzy">
Un valido accesso utilizzando una one-time password potrebbe assomigliare a questo ...
</div>

<div class="simplebox">http://www.yourdomain.org/limesurvey/index.php/admin/authentication/login?user=myusername&onepass=secretpassword</div>

<div class='simplebox'> [[File:help.png]] The 'secretpassword' field is plain text, not MD5 code.</div>

<div class="mw-translate-fuzzy">
'''Cose a cui prestare attenzione''':
* le one-time password devono essere abilitate settando "$suse_one_time_password = true;" (per v1.92) rispettivamente "use_one_time_password => true" (per v2.0 + nella sezione 'Configurazione') in config.php.
* Lo username trasmetto deve realmente esistere nella tabella 'utenti' di LimeSurvey.
* La one-time password, che può essere impostata da un'applicazione esterna, deve essere memorizzata come [http://www.php.net/md5 MD5 hash] nella colonna "one_time_pw" della tabella 'utenti'.
* Il testo in chiaro della password trasmesso sarà convertito utilizzando la funzione md50 e poi sarà comparato con il valore memorizzato in 'one_time_ppw' della tabella 'utenti'. Le due password devono essere combaciare.
* Dopo il primo accesso con la one-time password, questa password sarà eliminata dal database. L'utente non sarà più in grado di accedere utilizzando la stessa password una seconda volta.
</div>

<div class="mw-translate-fuzzy">
=Impostare i permessi per una singola indagine=
</div>

<div class="mw-translate-fuzzy">
Queste autorizzazioni si applicano solamente ad una singola indagine. Se sei interessato a settare le autorizzazioni per l'intero sistema puoi utilizzare i permessi globali.
</div>

<div class="mw-translate-fuzzy">
'''Nota''': è richiesto un account utente esistente per impostare le autorizzazioni per una singola indagine. Se l'account non esiste devi prima crearlo, poi potrai cambiare i permessi sull'indagine. Non devi applicare nessun permesso globale all'utente, è necessario solamente che l'account utente in se esista.
</div>

{{Note| By default, an user (non-admin) cannot grant survey permissions to users that are not part of the same group as the survey administrator. This is a security option enabled by '''default''' in LimeSurvey. To change this, you need to deactivate option [[Global_settings#Security|Group member can only see own group]], located in the '''Global settings''', under the '''Security tab'''. However, if you feel unsure about disabling this option, you can create groups containing those users that can be seen and be granted survey permissions by a survey creator.}}

<div class="mw-translate-fuzzy">
Per cambiare le autorizzazioni su un'indagine devi selezionare '''Permessi Indagine''' dal menù '''Proprietà indagine'''.
</div>

<center>[[File:LimeSurveySurveyPermissions.jpg]]</center>

<center>[[File:LimeSurveySurveyPermissionsRights.png]]</center>

<div class="mw-translate-fuzzy">
==Impostare i permessi dell'utente sulla singola indagine==
</div>

<div class="mw-translate-fuzzy">
nel prossimo step seleziona l'utente a cui vuoi cambiare i diritti sull'indagine e poi clicca su '''Aggiungi utente'''.
</div>

<center>[[File:LimeSurveyAddSurveyPermission.jpg]]</center>

<div class="mw-translate-fuzzy">
Dopo aver cliccato su '''Imposta i permessi per l'indagine''' verrà visualizzata la matrice delle autorizzazioni per l'indagine.
</div>

<center>[[File:LimeSurveyUserPermissionMatrix.jpg]]</center>

<div class="mw-translate-fuzzy">
In questa matrice puoi impostare i diritti per le diverse funzionalità e parti dell'indagine. Semplicemente devi cliccare in un checkbox se vuoi aggiungere o rimuovere un permesso. Selezionando una delle checkbox nella prima colonna, tutti i diritti su quella riga saranno selezionati o rimossi.
</div>

<div class="mw-translate-fuzzy">
Nelle altre colonne puoi scegliere se un utente può eseguire una certa azione su quella parte/funzione.
</div>

<div class="mw-translate-fuzzy">
I più importanti casi d'uso per garantire i diritti degli utenti sono raccolti nelle parte '''casi d'uso''' di quest'articolo.
</div>

==Grant survey permissions to a user group==

Click on add a user group and select the user group to which you would like to add the permission rights.

<center>[[File:LimeSurveyPermissionRightsUserGroup.png]]</center>

In the next step, select the permissions that you will allocate to the members of that user group. Do not forget to click on the double right arrowhead to get an extended view of the permissions matrix.

<center>[[File:UserGroupSurveyPermissions.png]]</center>

<div class="mw-translate-fuzzy">
Dopo aver concluso le modifiche ai permessi dell'indagine, cliccare su '''Salva''' o '''Salva e chiudi''' nell'angolo in alto a destra.
</div>

Some examples are provided [[Manage_users#Examples|below]] in order to help you get a better understanding of the Limesurvey's survey permissions system.

{{Note|[[Manage user groups|The user group function]] is still experimental. Use our [https://bugs.limesurvey.org/ bugs tracker] to describe any kind of inconsistencies.}}

<div class="mw-translate-fuzzy">
=Casi d'uso=
</div>

<div class="mw-translate-fuzzy">
In questa parte dell' articolo ti forniremo alcune idee su casi d'uso che possono esistere e su come e quali diritti sarebbe una buona scelta.
</div>

<div class="mw-translate-fuzzy">
==Aggiunta di un nuovo responsabile per la gestione di LimeSurvey==
* Accedi come '''admin'''
* Crea un nuovo account utente
* Imposta i permessi globali per l'utente a '''SuperAdministrator'''
* facoltativo: imposta i permessi sui modelli a '''SuperAdministrator''' come diritti su tutti i modelli.
* facoltativo: imposta i permessi dell'indagine a '''SuperAdministrator''' come permessi per tutte le indagini.
</div>

<div class="mw-translate-fuzzy">
==Un nuovo utente vuole creare le proprie indagini==
* Accedi come '''admin''' od utente con dei permessi da '''SuperAdministrator'''.
* Crea un nuovo account utente.
* imposta i permessi globali dell'utente a '''Creare Indagini'''
* imposta i permessi sui template dell'utente ai soli modelli che saranno utilizzati dall'utente o dal gruppo.
* facoltativo: imposta i permessi sull'indagine (il creatore dell'indagine possiede tutte le autorizzazioni sui propri sondaggi).
</div>

<div class="mw-translate-fuzzy">
==Il creatore di un'indagine ha bisogno di un'altra persona per modificare il proprio sondaggio==
* accedi come '''admin''' o come utente con permessi da '''SuperAdministrator'''-
* crea un nuovo utente
* imposta '''nessun permesso globale''' per l'utente
* Imposta '''nessun permesso sui modelli''' per l'utente
* imposta i permessi dell'indagine come preferisci. Questo dipende da cosa deve fare il nuovo utente e di quanti permessi necessità. Se deve essere in possesso di tutti i permessi sull'indagine puoi selezionare la checkbox nella prima colonna (quella con il pulsante '''<<''' o '''>>''' come intestazione).
</div>

<div class="mw-translate-fuzzy">
==Un responsabile del sondaggio vuole vedere i risultati dell'indagine ed esportarli==
* accedi come '''admin''' o come utente con permessi da ''SuperAdministrator'''.
* crea un nuovo account utente
* imposta '''nessun permesso globale''' per l'utente
* imposta '''nessun permesso sui modelli''' per l'utente
* imposta i permessi dell'indagine a: '''Risposte''': '''Visualizzare/Leggere''' e '''Esportare'''; '''Statistiche''': '''Visualizzare/Leggere'''.
</div>

<center>[[File:LimeSurveyCusomerOwnStatistics.jpg]]</center>

==I need help from two interns that can help me with the translation of my survey==
* Log in as ''admin'' (or as a user that has the ''Superadministrator'' permission).
* Create ''n'' user accounts (where n is the number of translators).
* Create a user group called ''Translators'' and add the ''n'' accounts to this group.
* Go to the '''Survey permissions''' and click on '''Add a user group'''.
* If they only do translations, then offer them the '''Quick translation''' permission.

<div class="mw-translate-fuzzy">
Ci sono diverse classi di persone che hanno accesso all'installazione LimeSurvey. Solo un set di persone è definito '''utente''' all'interno del codice e della documentazione. Quindi, capiamo che cosa e quali sono queste classi di persone in modo da comprendere meglio la terminologia del programma.
</div>

Translations:Manage users/2/it

2019-05-29T14:29:52Z

Tassoman:

= Gestione Utente =