Optional settings/ru - Revision history

FuzzyBot: Updating to match new version of source page

2026-06-13T22:10:13Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2025-08-12T14:28:16Z

Updating to match new version of source page

← Older revision		Revision as of 16:28, 12 August 2025
Line 4:		Line 4:
	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.		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.

			<span id="Introduction"></span>
	<div class="mw-translate-fuzzy">		<div class="mw-translate-fuzzy">
	=Примечание=		=Примечание=
Line 231:		Line 232:
	</syntaxhighlight>		</syntaxhighlight>

			<span id="General_settings"></span>
	=Общие настройки=		=Общие настройки=

Line 240:		Line 242:
	</div>		</div>

			<span id="Security"></span>
	=Безопасность=		=Безопасность=

Line 253:		Line 256:
	** Отключает возможность сохранения следующих глобальных параметров: имя сайта, язык по-умолчанию, режим HTML-редактора по-умолчанию, XSS фильтр		** Отключает возможность сохранения следующих глобальных параметров: имя сайта, язык по-умолчанию, режим HTML-редактора по-умолчанию, XSS фильтр
	</div>		</div>

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

	<div class="mw-translate-fuzzy">		<div class="mw-translate-fuzzy">
Line 321:		Line 343:
	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>		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>

			<span id="Email_settings"></span>
	=Настройки электронной почты=		=Настройки электронной почты=

Line 359:		Line 382:
	</div>		</div>

			<span id="LDAP_settings"></span>
	= [[LDAP settings\|Настройки LDAP]]=		= [[LDAP settings\|Настройки LDAP]]=

	Т.к. данная тема весьма и весьма обширна, то мы переместили [[LDAP settings\|Настройки LDAP]] на [[LDAP settings\|другую страницу.]]		Т.к. данная тема весьма и весьма обширна, то мы переместили [[LDAP settings\|Настройки LDAP]] на [[LDAP settings\|другую страницу.]]

			<span id="Authentication"></span>
	=Аутентификация=		=Аутентификация=

Line 369:		Line 394:
	</div>		</div>

			<span id="Authentication_delegation_to_the_webserver"></span>
	==Передача проверки подлинности Web-серверу==		==Передача проверки подлинности Web-серверу==

Line 379:		Line 405:
	*это может заменить графический интерфейс аутентификации системы '''не приглашение в систему опроса''' (интерфейс участника)		*это может заменить графический интерфейс аутентификации системы '''не приглашение в систему опроса''' (интерфейс участника)

			<span id="Authentication_delegation_with_no_automatic_user_import"></span>
	==Передача аутентификации без автоматического импорта пользователей==		==Передача аутентификации без автоматического импорта пользователей==

Line 387:		Line 414:
	*если он имеет такой же логин в локальной базе данных LimeSurvey (с присущими ему привилегиями)		*если он имеет такой же логин в локальной базе данных LimeSurvey (с присущими ему привилегиями)

			<span id="Authentication_delegation_with_automatic_user_import"></span>
	==Передача аутентификации с автоматическим импортом пользователей==		==Передача аутентификации с автоматическим импортом пользователей==

Line 425:		Line 453:
	{{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.}}		{{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.}}

			<span id="User_name_mapping"></span>
	==Сопоставление имен пользователей==		==Сопоставление имен пользователей==

Line 437:		Line 466:
	Очевидно, что данная процедура имеет определенные последствия в плане безопасности, так что применяйте это с осторожностью, и, пожалуйста, защитите Ваш config.php от записи Web-сервером.		Очевидно, что данная процедура имеет определенные последствия в плане безопасности, так что применяйте это с осторожностью, и, пожалуйста, защитите Ваш config.php от записи Web-сервером.

			<span id="Use_one-time_passwords"></span>
	==Использование одноразовых паролей==		==Использование одноразовых паролей==

Line 469:		Line 499:
	*'''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.		*'''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.

			<span id="Advanced_path_settings"></span>
	=Расширенные настройки директорий=		=Расширенные настройки директорий=

Line 492:		Line 523:
	== Update ==		== 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.		*'''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.

			== Tokens ==

			*'''allowedcharacters_pattern_token''' : These settings allow to set the regexp pattern when filtering token.

FuzzyBot: Updating to match new version of source page

2024-04-02T14:59:37Z

Updating to match new version of source page

← Older revision		Revision as of 16:59, 2 April 2024
Line 127:		Line 127:
	==Allow usage of session and Csrf Validation in iFrame {{NewIn\|v=3.24.3}}==		==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. Attention, even with all settings : allow form in iframe can broke on some browser. This settings was tested with Firefox 81.0.2 and Chromium 85.0.4183.121.		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===		===Allow session start in iframe===
Line 150:		Line 152:
	===Allow csrf cookie in iframe===		===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.		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(		<syntaxhighlight lang="php" enclose="pre"> 'request' => array(

FuzzyBot: Updating to match new version of source page

2023-11-28T09:01:33Z

Updating to match new version of source page

@@ Line 125: / Line 125: @@
-==Allow usage of surveys in an iframe==
+==Allow usage of session and Csrf Validation in iFrame {{NewIn|v=3.24.3}}==
-After allowing [[Global_settings#Security|Iframe embedding]] a 100% reliable solution can only be guaranteed if the framing site uses the same root domain. If you use LimeSurvey Cloud this can be achieved by using [https://www.limesurvey.org/support/faq/37-limesurvey-cloud/499-what-is-domain-aliasing-and-why-do-i-need-it domain aliasing]
+After allow [[Global_settings#Security|Iframe embedding]] you need to update some configuration part. Attention, even with all settings : allow form in iframe can broke on some browser. This settings was tested with Firefox 81.0.2 and Chromium 85.0.4183.121.
 ==URL settings==

FuzzyBot: Updating to match new version of source page

2023-10-10T10:45:55Z

Updating to match new version of source page

@@ Line 125: / Line 125: @@
-==Allow usage of session and Csrf Validation in iFrame==
+==Allow usage of surveys in an iframe==
-After allowing [[Global_settings#Security|Iframe embedding]] you need to update some configuration parts.
+After allowing [[Global_settings#Security|Iframe embedding]] a 100% reliable solution can only be guaranteed if the framing site uses the same root domain. If you use LimeSurvey Cloud this can be achieved by using [https://www.limesurvey.org/support/faq/37-limesurvey-cloud/499-what-is-domain-aliasing-and-why-do-i-need-it domain aliasing]
 ==URL settings==

FuzzyBot: Updating to match new version of source page

2023-04-18T12:35:57Z

Updating to match new version of source page

← Older revision		Revision as of 14:35, 18 April 2023
Line 128:		Line 128:

	After allowing [[Global_settings#Security\|Iframe embedding]] you need to update some configuration parts.		After allowing [[Global_settings#Security\|Iframe embedding]] you need to update some configuration parts.

	'''Attention: This solution will not work reliable in all browsers, even with all the settings set.'''		'''Attention: This solution will not work reliable in all browsers, even with all the settings set.'''

	A better and 100% reliable solution can only be guaranteed if the framing site uses the same root domain.		A better and 100% reliable solution can only be guaranteed if the framing site uses the same root domain.

FuzzyBot: Updating to match new version of source page

2023-04-18T12:34:03Z

Updating to match new version of source page

← Older revision		Revision as of 14:34, 18 April 2023
Line 125:		Line 125:


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

	After ~~allow~~ [[Global_settings#Security\|Iframe embedding]] you need to update some configuration ~~part~~. Attention, even with all settings ~~: allow form in iframe~~ can ~~broke on some browser~~. ~~This~~ settings ~~was~~ tested with Firefox 81.0.2 and Chromium 85.0.4183.121.		After allowing [[Global_settings#Security\|Iframe embedding]] you need to update some configuration parts.
			'''Attention: This solution will not work reliable in all browsers, even with all the settings set.'''
			A better and 100% reliable solution can only be guaranteed if the framing site uses the same root domain.

			These settings were tested with Firefox 81.0.2 and Chromium 85.0.4183.121.

	===Allow session start in iframe===		===Allow session start in iframe===

	The session ~~need~~ to be secure (valid https) , httponly and samesite to None. All settings must be ~~sent~~ all lowercase.		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 (		<syntaxhighlight lang="php" enclose="pre"> 'session' => array (
Line 150:		Line 154:
	===Allow csrf cookie in iframe===		===Allow csrf cookie in iframe===

	Same ~~than~~ session: must be secure and samesite to None. ~~Whole~~ array must be added at same level ~~than~~ session		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(		<syntaxhighlight lang="php" enclose="pre"> 'request' => array(

FuzzyBot: Updating to match new version of source page

2022-10-08T15:35:19Z

Updating to match new version of source page

← Older revision		Revision as of 17:35, 8 October 2022
Line 486:		Line 486:
	*'''allowedfileuploads''' {{NewIn\|4.0.0}} Global restriction on file type to be uploaded		*'''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_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/~~framework~~/utils/~~mimeTypes~~.php included one]. Must be a PHP file return an array. Can be updated only in config.php file.		*'''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 ==		== 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.		*'''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.

C schmitz: Text replacement - " enclose="div"" to ""

2022-02-16T13:05:17Z

Text replacement - " enclose="div"" to ""

← Older revision		Revision as of 15:05, 16 February 2022
Line 396:		Line 396:
	*False или пустой массив: в случае если пользователю запрещен доступ в LimeSurvey		*False или пустой массив: в случае если пользователю запрещен доступ в LimeSurvey
	*массив содержащий все общие атрибуты пользовательского профиля как описано в '''$WebserverAuth_autouserprofile'''		*массив содержащий все общие атрибуты пользовательского профиля как описано в '''$WebserverAuth_autouserprofile'''
	<syntaxhighlight lang="php~~" enclose="div~~">function hook_get_auth_webserver_profile($user_name)		<syntaxhighlight lang="php">function hook_get_auth_webserver_profile($user_name)
	{		{
	// Retrieve user's data from your database backend (for instance LDAP) here		// Retrieve user's data from your database backend (for instance LDAP) here
Line 427:		Line 427:
	В случае, если имя пользователя во внешней базе отличается от имени в локальной базе LimeSurvey, Вы можете найти полезной использование функции сопоставления имен пользователей. В LimeSurvey это осуществляется за счет использования параметра '''auth_webserver_user_map'''. Представим себе, что у Вас во внешней базе отсутствует пользователь с именем 'admin'. Чтобы в дальнейшем иметь возможность войти в LimeSurvey как admin, Вам необходимо сопоставить имя пользователя во внешней базе (пусть это будет 'myname') с логином 'admin' в LimeSurvey. Соответствующие этому настройки:		В случае, если имя пользователя во внешней базе отличается от имени в локальной базе LimeSurvey, Вы можете найти полезной использование функции сопоставления имен пользователей. В LimeSurvey это осуществляется за счет использования параметра '''auth_webserver_user_map'''. Представим себе, что у Вас во внешней базе отсутствует пользователь с именем 'admin'. Чтобы в дальнейшем иметь возможность войти в LimeSurvey как admin, Вам необходимо сопоставить имя пользователя во внешней базе (пусть это будет 'myname') с логином 'admin' в LimeSurvey. Соответствующие этому настройки:

	<syntaxhighlight lang="php~~" enclose="div~~">'config'=>array(		<syntaxhighlight lang="php">'config'=>array(
	...		...
	'auth_webserver_user_map' => array ('myname' => 'admin');		'auth_webserver_user_map' => array ('myname' => 'admin');

FuzzyBot: Updating to match new version of source page

2021-11-17T19:47:03Z

Updating to match new version of source page

← Older revision		Revision as of 21:47, 17 November 2021
Line 155:		Line 155:
	'enableCsrfValidation'=>true,		'enableCsrfValidation'=>true,
	'csrfCookie' => array(		'csrfCookie' => array(
	'~~samesite~~' => 'None',		'sameSite' => 'None',
	'secure' => true,		'secure' => true,
	),		),
Line 297:		Line 297:
	*'''$showpopups''': Показывать всплывающие окна сообщений если обязательный или вопрос с условием не был отвечен корректно. 1=показывать всплывающие окна сообщений (по-умолчанию), 0=показывать сообщения внутри текущего окна, -1=не показывать сообщения совсем (в таком случае пользователи будут видеть специфичные для вопроса подсказки, сообщающие о том, на какой вопрос необходимо ответить).		*'''$showpopups''': Показывать всплывающие окна сообщений если обязательный или вопрос с условием не был отвечен корректно. 1=показывать всплывающие окна сообщений (по-умолчанию), 0=показывать сообщения внутри текущего окна, -1=не показывать сообщения совсем (в таком случае пользователи будут видеть специфичные для вопроса подсказки, сообщающие о том, на какой вопрос необходимо ответить).
	</div>		</div>

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

	<div class="mw-translate-fuzzy">		<div class="mw-translate-fuzzy">
Line 485:		Line 490:
	== Update ==		== 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.		*'''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.

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