Upgrading from a previous version/fr

2017-09-13T15:20:29Z

Tpweb17: Created page with "{{Alert|title=Attention|text=Si vous mettez à jour à partir d'une version antérieure à 1.92, il peut être nécessaire de mettre à jour d'abord à partir de la dernière..."

<languages /> <div class="simplebox">La traduction de cette page n'est pas terminée.</div>

=Avant de commencer...=

<span style='color:#FF0000'>... lisez ceci car c'est très important: '''Ne jamais oublier de faire une sauvegarde des fichiers et de la base de données de votre installation actuelle !'''</span>

Vous pouvez le faire en utilisant les outils d'administration de la base de données comme [https://www.phpmyadmin.net phpMyAdmin] et un gestionnaire de fichiers ! Si vous ne savez pas comment procéder pour faire les sauvegardes des fichiers et de la base, alors vous devez demander à quelqu'un de le faire pour vous ou de vous l'apprendre, ou alors utilisez la méthode [[ComfortUpdate]] qui est censée tout faire pour vous.

=Méthode rapide (pour les changements mineurs de version)=

Vous pouvez suivre les instructions ci-après si vous effectuez une actualisation mineure (comme par exemple le passage de la version 1.86 à 1.87).
* Avant de commencer, sauvegardez vos fichiers et votre base de données (on l'avait déjà dit, n'est-ce pas ?)
* Supprimez tous vos fichiers et dossiers SAUF
** /application/config/config.php
** le dossier /upload
<div class="simplebox">[[File:help.png]]'''Note:''' Si vous avez personnalisé les templates dans le dossier /upload/templates, prenez soin de "rafraîchir" vos modifications en tenant compte des changements pouvant advenir avec la nouvelle version de LimeSurvey. Le moyen le plus simple pour retrouver de tels changements : comparer les fichiers de votre ancien template avec la nouvelle version du template par défaut. Si vous voyez des différences autres que vos personnalisations, il faudra rafraîchir. </div>
* Copiez les nouveaux fichiers et dossiers présents dans le paquet LimeSurvey que vous venez de télécharger et de dé-compacter vers l'emplacement de LimeSurvey dans votre serveur. Faites attention à ne pas écraser votre fichier actuel config.php (si vous faites cette erreur-là, vous pouvez vous récupérer en utilisant la sauvegarde préalable que vous n'avez pas oublié de faire, n'est-ce pas ?). Vous pouvez copier en écrasant tous les autres fichiers et dossiers - mais normalement vous les avez supprimés (sauf le fichier config.php et le dossier "upload") .
* Si vous remarquez des problèmes après la mise à jour : supprimez le cache de votre navigateur et les cookies!

=La méthode complète (pour les grands sauts de version)=

Malheureusement il y a quelques petites choses à faire, par conséquent veuillez lire attentivement les instructions suivantes

==Mettre à jour depuis une version 1.50 ou plus vers n'importe quelle version supérieure à 2.xx ==
#[https://www.limesurvey.org/about-limesurvey/download Télécharger] la dernière version de LimeSurvey.
# Préparer et sauvegarder l'ancienne installation
## Sauvegardez les fichiez de votre répertoire d'installation et la base données SQL juste au cas où :
### En ligne de commande, créez un zip (ou archive similaire) de l'ensemble du dossier d'installation (fichiers et arbirescence) Par exemple sous Linux 'tar cvzf foo.tgz cps100' va compresser et zipper entièrement le dossier cps100 ;
### Vous pouvez utiliser [httsp://www.phpmyadmin.net phpMyAdmin] pour exporter toutes vos tables, ou vous pouvez utiliser la fonction de sauvegarde de bases de données de LimeSurvey, laquelle est disponible dans le menu Configuration (sous l'onglet avancé) pour sauvegarder la base de données entière ;
<div class="simplebox">[[File:help.png]] '''Note:''' Dans les anciennes versions de LimeSurvey, cherchez le bouton '''LimeSurvey Administration''' [[File:button-export-sql.png]] pour exporter la base de données. </div>
## Copiez votre fichier '''config.php''' file, le dossier '''template''' modifié, et le dossier /upload séparément pour y avoir accès rapidement ensuite.
# Remplacer tous les répertoires d'installation :
## Supprimez tous les anciens fichiers dans le répertoire d'installation existant ;
## Uploadez et décompressez la nouvelle version du code dans le même répertoire d'installation ;
## Si votre version précédente est plus ancienne que 1.90, copiez tous les templates personnalisés dans '/upload/templates' - vous pouvez aussi devoir renommer chaque dossier de template dont le nom correspond à un template existant dans /templates.
## Copiez votre votre dossier '/upload' directory back to the old location;
## Vérifiez doublement les permissions des dossiers (un accès en écriture est requis pour '''/tmp''', '''/upload''', et leurs sous-dossiers) comme décrit dans [[Installation#Définir les permissions des dossiers|wiki installation]];
## Ouvrez http://<yourdomain>/<yourlimesurveydir>/admin dans votre navigateur et suivez les instructions (vous pouvez utiliser l'ancien config.php comme modèle). La base de données existante sera automatiquement détectée, et, si nécessaire, mise à jour après confirmation.
# Vérifiez si des vérifications manuelles spéciales listées ci-dessous s'appliquent ;
# '''Maintenant, videz le cache de votre navigateur et supprimez les cookies !''' et ce sera prêt.

{{Alert|title=Attention|text=Si vous mettez à jour à partir d'une version antérieure à 1.92, il peut être nécessaire de mettre à jour d'abord à partir de la dernière version 1.92 , ensuite 2.00, ensuite 2.06, et finalement la dernière version version (par exemple. 2.55.x). Lisez ci-dessous [[Mettre à our à partir d'une version précédente#Mettre à jour à partir d'une version 1.50 or plus vers une version 1.xx |plus de details]].}}

{{Alert|title=Attention|text=Please note that the template structure has changed with the update from 2.0x to 2.50 or later. Your old templates will not be working anymore as the template system is now using responsive templates.}}

<div class="simplebox">'''Special checks after an upgrade''':
*'''from any earlier version to 2.xx''':
**Proper question codes are mandatory now. After upgrading the installation, check the survey logic of all surveys and correct the codes where necessary.
*'''from a version earlier than v1.53''': When upgrading from a version before v1.53 to the latest version, please check the '''global user rights''' of each user. There was a new '''superadmin''' right introduced in v1.53 that can give a user the same privilege as the master administration account created during the install. The upgrade script is guessing to whom should be given this permission in the older versions. As this is not perfect, it should be carefully checked;
*'''from any earlier version to v2.06''': From 2.05 to 2.06, some unused permissions when editing global permissions for 'surveys' were activated. For example, if a user had only the 'create' permission in 2.05, the other permissions located on the right of 'create' would also get activated with the update to 2.06 (View/read, Update, Delete, Import, Export). Please, check whether the admin users got any other global permissions besides the 'original' ones after the update. If yes, please edit them accordingly.
</div>

==Upgrading from version 1.50 or later to any later 1.xx version==
#[https://www.limesurvey.org/about-limesurvey/download Download] the desired version of LimeSurvey.
# Prepare and backup the old installation.
## Backup your installation directory files and SQL-based database just in case.
### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files. For example, in Linux 'tar cvzf foo.tgz cps100' will tar and zip the whole of the cps100 directory;
### Using [httsp://www.phpmyadmin.net phpMyAdmin] or similar to export all tables; or using the '''LimeSurvey Administration''' button [[File:button-export-sql.png]] to backup the entire database.
## Copy your '''config.php''' file, modified '''template''' directories, and the /upload directory separately for quick access later;
# Replace all the installation directory files:
## Delete all old files in the existing installation directory;
## Upload and unpack the new code version into the same installation directory;
## Edit or replace the '''config.php''' file:
### If your previous version was < 1.70: Edit the new '''config.php''' in order to reflect the changes from the backup '''config.php''' file. '''Do not just overwrite the new '''config.php''' with your old one!''';
### If your previous version was >= 1.70: Simply replace the new '''config.php''' with your backup '''config.php''' file (as the file format has not changed);
## If your previous version was older than 1.90: Copy any customized templates to '/upload/templates' - you will also need to rename each template directory whose name matches an existing template in /templates;
## Copy your '/upload' directory back to the old location;
## Double check the '''permissions''' set on the directories of LimeSurvey (write access to '''/tmp''', '''/upload''', and to their subdirectories is required) as described in the [[Installation#Set Directory permissions|installation wiki]];
# Finish the installation/upgrade process:
## Once you open the URL to your LimeSurvey administration, the database tables will be updated after confirmation;
## Remove or rename the '/admin/install' directory as/if instructed by the installation script;
## Check if any special manual checks apply (as listed below).

<div class="simplebox">'''Special checks after an upgrade''':
*'''from any earlier version to 1.92''': The '''templates''' have been changed. Please check your customized templates if they are still looking right. If not, you will have to edit your templates accordingly (check out the original templates to see what was changed)<br />
*'''from a version earlier than v1.53''': When upgrading from a version before v1.53 to the latest version, please check the '''global user rights''' of each user. There was a new '''superadmin''' right introduced in v1.53 that can give a user the same privilege as the master administration account created during the install. The upgrade script is guessing to whom should be given this permission in the older versions. As this is not perfect, it should be carefully checked.
</div>

==Upgrading from a version earlier than v1.50 (v1.0 through v1.44)==

Since the data structure and a lot of other things were changed, '''upgrading from any version previous to v1.50 is <u>NOT</u> possible'''. If you have old survey structure files with a *.sql extension, the only way to get these into a newer version is to install [http://www.limesurvey.org/en/archived-releases/289-limesurvey150zip version 1.50], import the .sql file(s) there, then upgrade that version to the most recent LimeSurvey version. Check the page related to [[Transferring an installation|how an installation can be transferred]] for more details.

=FAQ=

==What is the most recent LimeSurvey version that still supports PHP4?==

The last release offering PHP4 support was version 1.82+.

==Can I upgrade even if I have active surveys?==

Yes, you can. Exceptions may be mentioned in the thorough instructions above. We strongly advise to test your surveys after upgrade to check if your design templates still work alright.

==What is best way to port the *.sql survey structure files of LimeSurvey to the latest version?==

Install version 1.50, import the file, and export the survey structure to the newer .csv format. The latest version can still read the .csv survey structure format.

Translations:Upgrading from a previous version/23/fr

2017-09-13T15:20:29Z

{{Alert|title=Attention|text=Si vous mettez à jour à partir d'une version antérieure à 1.92, il peut être nécessaire de mettre à jour d'abord à partir de la dernière version 1.92 , ensuite 2.00, ensuite 2.06, et finalement la dernière version version (par exemple. 2.55.x). Lisez ci-dessous [[Mettre à our à partir d'une version précédente#Mettre à jour à partir d'une version 1.50 or plus vers une version 1.xx |plus de details]].}}

Upgrading from a previous version/fr

2017-09-13T15:15:24Z

Tpweb17:

<languages /> <div class="simplebox">La traduction de cette page n'est pas terminée.</div>

=Avant de commencer...=

<span style='color:#FF0000'>... lisez ceci car c'est très important: '''Ne jamais oublier de faire une sauvegarde des fichiers et de la base de données de votre installation actuelle !'''</span>

Vous pouvez le faire en utilisant les outils d'administration de la base de données comme [https://www.phpmyadmin.net phpMyAdmin] et un gestionnaire de fichiers ! Si vous ne savez pas comment procéder pour faire les sauvegardes des fichiers et de la base, alors vous devez demander à quelqu'un de le faire pour vous ou de vous l'apprendre, ou alors utilisez la méthode [[ComfortUpdate]] qui est censée tout faire pour vous.

=Méthode rapide (pour les changements mineurs de version)=

Vous pouvez suivre les instructions ci-après si vous effectuez une actualisation mineure (comme par exemple le passage de la version 1.86 à 1.87).
* Avant de commencer, sauvegardez vos fichiers et votre base de données (on l'avait déjà dit, n'est-ce pas ?)
* Supprimez tous vos fichiers et dossiers SAUF
** /application/config/config.php
** le dossier /upload
<div class="simplebox">[[File:help.png]]'''Note:''' Si vous avez personnalisé les templates dans le dossier /upload/templates, prenez soin de "rafraîchir" vos modifications en tenant compte des changements pouvant advenir avec la nouvelle version de LimeSurvey. Le moyen le plus simple pour retrouver de tels changements : comparer les fichiers de votre ancien template avec la nouvelle version du template par défaut. Si vous voyez des différences autres que vos personnalisations, il faudra rafraîchir. </div>
* Copiez les nouveaux fichiers et dossiers présents dans le paquet LimeSurvey que vous venez de télécharger et de dé-compacter vers l'emplacement de LimeSurvey dans votre serveur. Faites attention à ne pas écraser votre fichier actuel config.php (si vous faites cette erreur-là, vous pouvez vous récupérer en utilisant la sauvegarde préalable que vous n'avez pas oublié de faire, n'est-ce pas ?). Vous pouvez copier en écrasant tous les autres fichiers et dossiers - mais normalement vous les avez supprimés (sauf le fichier config.php et le dossier "upload") .
* Si vous remarquez des problèmes après la mise à jour : supprimez le cache de votre navigateur et les cookies!

=La méthode complète (pour les grands sauts de version)=

Malheureusement il y a quelques petites choses à faire, par conséquent veuillez lire attentivement les instructions suivantes

==Mettre à jour depuis une version 1.50 ou plus vers n'importe quelle version supérieure à 2.xx ==
#[https://www.limesurvey.org/about-limesurvey/download Télécharger] la dernière version de LimeSurvey.
# Préparer et sauvegarder l'ancienne installation
## Sauvegardez les fichiez de votre répertoire d'installation et la base données SQL juste au cas où :
### En ligne de commande, créez un zip (ou archive similaire) de l'ensemble du dossier d'installation (fichiers et arbirescence) Par exemple sous Linux 'tar cvzf foo.tgz cps100' va compresser et zipper entièrement le dossier cps100 ;
### Vous pouvez utiliser [httsp://www.phpmyadmin.net phpMyAdmin] pour exporter toutes vos tables, ou vous pouvez utiliser la fonction de sauvegarde de bases de données de LimeSurvey, laquelle est disponible dans le menu Configuration (sous l'onglet avancé) pour sauvegarder la base de données entière ;
<div class="simplebox">[[File:help.png]] '''Note:''' Dans les anciennes versions de LimeSurvey, cherchez le bouton '''LimeSurvey Administration''' [[File:button-export-sql.png]] pour exporter la base de données. </div>
## Copiez votre fichier '''config.php''' file, le dossier '''template''' modifié, et le dossier /upload séparément pour y avoir accès rapidement ensuite.
# Remplacer tous les répertoires d'installation :
## Supprimez tous les anciens fichiers dans le répertoire d'installation existant ;
## Uploadez et décompressez la nouvelle version du code dans le même répertoire d'installation ;
## Si votre version précédente est plus ancienne que 1.90, copiez tous les templates personnalisés dans '/upload/templates' - vous pouvez aussi devoir renommer chaque dossier de template dont le nom correspond à un template existant dans /templates.
## Copiez votre votre dossier '/upload' directory back to the old location;
## Vérifiez doublement les permissions des dossiers (un accès en écriture est requis pour '''/tmp''', '''/upload''', et leurs sous-dossiers) comme décrit dans [[Installation#Définir les permissions des dossiers|wiki installation]];
## Ouvrez http://<yourdomain>/<yourlimesurveydir>/admin dans votre navigateur et suivez les instructions (vous pouvez utiliser l'ancien config.php comme modèle). La base de données existante sera automatiquement détectée, et, si nécessaire, mise à jour après confirmation.
# Vérifiez si des vérifications manuelles spéciales listées ci-dessous s'appliquent ;
# '''Maintenant, videz le cache de votre navigateur et supprimez les cookies !''' et ce sera prêt.

{{Alert|title=Attention|text=If you upgrade from e.g. 1.92, it might be necessary to upgrade ''first'' to the latest 1.92 release, then to 2.00, then to 2.06, and then finally to the latest version (e.g. 2.55.x). Read below for [[Upgrading from a previous version#Upgrading from version 1.50 or later to any later 1.xx version|further details]].}}

{{Alert|title=Attention|text=Please note that the template structure has changed with the update from 2.0x to 2.50 or later. Your old templates will not be working anymore as the template system is now using responsive templates.}}

<div class="simplebox">'''Special checks after an upgrade''':
*'''from any earlier version to 2.xx''':
**Proper question codes are mandatory now. After upgrading the installation, check the survey logic of all surveys and correct the codes where necessary.
*'''from a version earlier than v1.53''': When upgrading from a version before v1.53 to the latest version, please check the '''global user rights''' of each user. There was a new '''superadmin''' right introduced in v1.53 that can give a user the same privilege as the master administration account created during the install. The upgrade script is guessing to whom should be given this permission in the older versions. As this is not perfect, it should be carefully checked;
*'''from any earlier version to v2.06''': From 2.05 to 2.06, some unused permissions when editing global permissions for 'surveys' were activated. For example, if a user had only the 'create' permission in 2.05, the other permissions located on the right of 'create' would also get activated with the update to 2.06 (View/read, Update, Delete, Import, Export). Please, check whether the admin users got any other global permissions besides the 'original' ones after the update. If yes, please edit them accordingly.
</div>

==Upgrading from version 1.50 or later to any later 1.xx version==
#[https://www.limesurvey.org/about-limesurvey/download Download] the desired version of LimeSurvey.
# Prepare and backup the old installation.
## Backup your installation directory files and SQL-based database just in case.
### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files. For example, in Linux 'tar cvzf foo.tgz cps100' will tar and zip the whole of the cps100 directory;
### Using [httsp://www.phpmyadmin.net phpMyAdmin] or similar to export all tables; or using the '''LimeSurvey Administration''' button [[File:button-export-sql.png]] to backup the entire database.
## Copy your '''config.php''' file, modified '''template''' directories, and the /upload directory separately for quick access later;
# Replace all the installation directory files:
## Delete all old files in the existing installation directory;
## Upload and unpack the new code version into the same installation directory;
## Edit or replace the '''config.php''' file:
### If your previous version was < 1.70: Edit the new '''config.php''' in order to reflect the changes from the backup '''config.php''' file. '''Do not just overwrite the new '''config.php''' with your old one!''';
### If your previous version was >= 1.70: Simply replace the new '''config.php''' with your backup '''config.php''' file (as the file format has not changed);
## If your previous version was older than 1.90: Copy any customized templates to '/upload/templates' - you will also need to rename each template directory whose name matches an existing template in /templates;
## Copy your '/upload' directory back to the old location;
## Double check the '''permissions''' set on the directories of LimeSurvey (write access to '''/tmp''', '''/upload''', and to their subdirectories is required) as described in the [[Installation#Set Directory permissions|installation wiki]];
# Finish the installation/upgrade process:
## Once you open the URL to your LimeSurvey administration, the database tables will be updated after confirmation;
## Remove or rename the '/admin/install' directory as/if instructed by the installation script;
## Check if any special manual checks apply (as listed below).

<div class="simplebox">'''Special checks after an upgrade''':
*'''from any earlier version to 1.92''': The '''templates''' have been changed. Please check your customized templates if they are still looking right. If not, you will have to edit your templates accordingly (check out the original templates to see what was changed)<br />
*'''from a version earlier than v1.53''': When upgrading from a version before v1.53 to the latest version, please check the '''global user rights''' of each user. There was a new '''superadmin''' right introduced in v1.53 that can give a user the same privilege as the master administration account created during the install. The upgrade script is guessing to whom should be given this permission in the older versions. As this is not perfect, it should be carefully checked.
</div>

==Upgrading from a version earlier than v1.50 (v1.0 through v1.44)==

Since the data structure and a lot of other things were changed, '''upgrading from any version previous to v1.50 is <u>NOT</u> possible'''. If you have old survey structure files with a *.sql extension, the only way to get these into a newer version is to install [http://www.limesurvey.org/en/archived-releases/289-limesurvey150zip version 1.50], import the .sql file(s) there, then upgrade that version to the most recent LimeSurvey version. Check the page related to [[Transferring an installation|how an installation can be transferred]] for more details.

=FAQ=

==What is the most recent LimeSurvey version that still supports PHP4?==

The last release offering PHP4 support was version 1.82+.

==Can I upgrade even if I have active surveys?==

Yes, you can. Exceptions may be mentioned in the thorough instructions above. We strongly advise to test your surveys after upgrade to check if your design templates still work alright.

==What is best way to port the *.sql survey structure files of LimeSurvey to the latest version?==

Install version 1.50, import the file, and export the survey structure to the newer .csv format. The latest version can still read the .csv survey structure format.

Translations:Upgrading from a previous version/9/fr

2017-09-13T15:15:24Z

Tpweb17:

==Mettre à jour depuis une version 1.50 ou plus vers n'importe quelle version supérieure à 2.xx ==
#[https://www.limesurvey.org/about-limesurvey/download Télécharger] la dernière version de LimeSurvey.
# Préparer et sauvegarder l'ancienne installation
## Sauvegardez les fichiez de votre répertoire d'installation et la base données SQL juste au cas où :
### En ligne de commande, créez un zip (ou archive similaire) de l'ensemble du dossier d'installation (fichiers et arbirescence) Par exemple sous Linux 'tar cvzf foo.tgz cps100' va compresser et zipper entièrement le dossier cps100 ;
### Vous pouvez utiliser [httsp://www.phpmyadmin.net phpMyAdmin] pour exporter toutes vos tables, ou vous pouvez utiliser la fonction de sauvegarde de bases de données de LimeSurvey, laquelle est disponible dans le menu Configuration (sous l'onglet avancé) pour sauvegarder la base de données entière ;
<div class="simplebox">[[File:help.png]] '''Note:''' Dans les anciennes versions de LimeSurvey, cherchez le bouton '''LimeSurvey Administration''' [[File:button-export-sql.png]] pour exporter la base de données. </div>
## Copiez votre fichier '''config.php''' file, le dossier '''template''' modifié, et le dossier /upload séparément pour y avoir accès rapidement ensuite.
# Remplacer tous les répertoires d'installation :
## Supprimez tous les anciens fichiers dans le répertoire d'installation existant ;
## Uploadez et décompressez la nouvelle version du code dans le même répertoire d'installation ;
## Si votre version précédente est plus ancienne que 1.90, copiez tous les templates personnalisés dans '/upload/templates' - vous pouvez aussi devoir renommer chaque dossier de template dont le nom correspond à un template existant dans /templates.
## Copiez votre votre dossier '/upload' directory back to the old location;
## Vérifiez doublement les permissions des dossiers (un accès en écriture est requis pour '''/tmp''', '''/upload''', et leurs sous-dossiers) comme décrit dans [[Installation#Définir les permissions des dossiers|wiki installation]];
## Ouvrez http://<yourdomain>/<yourlimesurveydir>/admin dans votre navigateur et suivez les instructions (vous pouvez utiliser l'ancien config.php comme modèle). La base de données existante sera automatiquement détectée, et, si nécessaire, mise à jour après confirmation.
# Vérifiez si des vérifications manuelles spéciales listées ci-dessous s'appliquent ;
# '''Maintenant, videz le cache de votre navigateur et supprimez les cookies !''' et ce sera prêt.

Upgrading from a previous version/fr

2017-09-13T15:14:58Z

Tpweb17:

<languages /> <div class="simplebox">La traduction de cette page n'est pas terminée.</div>

=Avant de commencer...=

<span style='color:#FF0000'>... lisez ceci car c'est très important: '''Ne jamais oublier de faire une sauvegarde des fichiers et de la base de données de votre installation actuelle !'''</span>

Vous pouvez le faire en utilisant les outils d'administration de la base de données comme [https://www.phpmyadmin.net phpMyAdmin] et un gestionnaire de fichiers ! Si vous ne savez pas comment procéder pour faire les sauvegardes des fichiers et de la base, alors vous devez demander à quelqu'un de le faire pour vous ou de vous l'apprendre, ou alors utilisez la méthode [[ComfortUpdate]] qui est censée tout faire pour vous.

=Méthode rapide (pour les changements mineurs de version)=

Vous pouvez suivre les instructions ci-après si vous effectuez une actualisation mineure (comme par exemple le passage de la version 1.86 à 1.87).
* Avant de commencer, sauvegardez vos fichiers et votre base de données (on l'avait déjà dit, n'est-ce pas ?)
* Supprimez tous vos fichiers et dossiers SAUF
** /application/config/config.php
** le dossier /upload
<div class="simplebox">[[File:help.png]]'''Note:''' Si vous avez personnalisé les templates dans le dossier /upload/templates, prenez soin de "rafraîchir" vos modifications en tenant compte des changements pouvant advenir avec la nouvelle version de LimeSurvey. Le moyen le plus simple pour retrouver de tels changements : comparer les fichiers de votre ancien template avec la nouvelle version du template par défaut. Si vous voyez des différences autres que vos personnalisations, il faudra rafraîchir. </div>
* Copiez les nouveaux fichiers et dossiers présents dans le paquet LimeSurvey que vous venez de télécharger et de dé-compacter vers l'emplacement de LimeSurvey dans votre serveur. Faites attention à ne pas écraser votre fichier actuel config.php (si vous faites cette erreur-là, vous pouvez vous récupérer en utilisant la sauvegarde préalable que vous n'avez pas oublié de faire, n'est-ce pas ?). Vous pouvez copier en écrasant tous les autres fichiers et dossiers - mais normalement vous les avez supprimés (sauf le fichier config.php et le dossier "upload") .
* Si vous remarquez des problèmes après la mise à jour : supprimez le cache de votre navigateur et les cookies!

=La méthode complète (pour les grands sauts de version)=

Malheureusement il y a quelques petites choses à faire, par conséquent veuillez lire attentivement les instructions suivantes

==Mettre à jour depuis une version 1.50 ou plus vers n'importe quelle version supérieure à 2.xx ==
#[https://www.limesurvey.org/about-limesurvey/download Télécharger] la dernière version de LimeSurvey.
# Préparer et sauvegarder l'ancienne installation
## Sauvegardez les fichiez de votre répertoire d'installation et la base données SQL juste au cas où :
### En ligne de commande, créez un zip (ou archive similaire) de l'ensemble du dossier d'installation (fichiers et arbirescence) Par exemple sous Linux 'tar cvzf foo.tgz cps100' va compresser et zipper entièrement le dossier cps100 ;
### Vous pouvez utiliser [httsp://www.phpmyadmin.net phpMyAdmin] pour exporter toutes vos tables, ou vous pouvez utiliser la fonction de sauvegarde de bases de données de LimeSurvey, laquelle est disponible dans le menu Configuration (sous l'onglet avancé) pour sauvegarder la base de données entière ;
<div class="simplebox">[[File:help.png]] '''Note:''' Dans les anciennes versions de LimeSurvey, cherchez le bouton '''LimeSurvey Administration''' [[File:button-export-sql.png]] pour exporter la base de données. </div>
## Copiez votre fichier '''config.php''' file, le dossier '''template''' modifié, et le dossier /upload séparément pour y avoir accès rapidement ensuite.
# Remplacer tous les répertoires d'installation :
## Supprimez tous les anciens fichiers dans le répertoire d'installation existant ;
## Uploadez et décompressez la nouvelle version du code dans le même répertoire d'installation ;
## Si votre version précédente est plus ancienne que 1.90, copiez tous les templates personnalisés dans '/upload/templates' - vous pouvez aussi devoir renommer chaque dossier de template dont le nom correspond à un template existant dans /templates.
## Copiez votre votre dossier '/upload' directory back to the old location;
## Vérifiez doublement les permissions des dossiers (un accès en écriture est requis pour '''/tmp''', '''/upload''', et leurs sous-dossiers) comme décrit dans [[Installation#Définir les permissions des dossiers|wiki installation]];
## Ouvrez http://<yourdomain>/<yourlimesurveydir>/admin dans votre navigateur et suivez les instructions (vous pouvez utiliser l'ancien config.php comme modèle). La base de données existante sera automatiquement détectée, et, si nécessaire, mise à jour après confirmation.
# Vérifiez si des vérifications manuelles spéciales listées ci-dessous s'appliquent ;
# '''Maintenant, videz le cache de votre navigateur et supprimez les cookies !''' et ce sera terminé.

{{Alert|title=Attention|text=If you upgrade from e.g. 1.92, it might be necessary to upgrade ''first'' to the latest 1.92 release, then to 2.00, then to 2.06, and then finally to the latest version (e.g. 2.55.x). Read below for [[Upgrading from a previous version#Upgrading from version 1.50 or later to any later 1.xx version|further details]].}}

{{Alert|title=Attention|text=Please note that the template structure has changed with the update from 2.0x to 2.50 or later. Your old templates will not be working anymore as the template system is now using responsive templates.}}

<div class="simplebox">'''Special checks after an upgrade''':
*'''from any earlier version to 2.xx''':
**Proper question codes are mandatory now. After upgrading the installation, check the survey logic of all surveys and correct the codes where necessary.
*'''from a version earlier than v1.53''': When upgrading from a version before v1.53 to the latest version, please check the '''global user rights''' of each user. There was a new '''superadmin''' right introduced in v1.53 that can give a user the same privilege as the master administration account created during the install. The upgrade script is guessing to whom should be given this permission in the older versions. As this is not perfect, it should be carefully checked;
*'''from any earlier version to v2.06''': From 2.05 to 2.06, some unused permissions when editing global permissions for 'surveys' were activated. For example, if a user had only the 'create' permission in 2.05, the other permissions located on the right of 'create' would also get activated with the update to 2.06 (View/read, Update, Delete, Import, Export). Please, check whether the admin users got any other global permissions besides the 'original' ones after the update. If yes, please edit them accordingly.
</div>

==Upgrading from version 1.50 or later to any later 1.xx version==
#[https://www.limesurvey.org/about-limesurvey/download Download] the desired version of LimeSurvey.
# Prepare and backup the old installation.
## Backup your installation directory files and SQL-based database just in case.
### At the command-line level, make a '''.zip''' or similar archive of the whole installation directory tree of files. For example, in Linux 'tar cvzf foo.tgz cps100' will tar and zip the whole of the cps100 directory;
### Using [httsp://www.phpmyadmin.net phpMyAdmin] or similar to export all tables; or using the '''LimeSurvey Administration''' button [[File:button-export-sql.png]] to backup the entire database.
## Copy your '''config.php''' file, modified '''template''' directories, and the /upload directory separately for quick access later;
# Replace all the installation directory files:
## Delete all old files in the existing installation directory;
## Upload and unpack the new code version into the same installation directory;
## Edit or replace the '''config.php''' file:
### If your previous version was < 1.70: Edit the new '''config.php''' in order to reflect the changes from the backup '''config.php''' file. '''Do not just overwrite the new '''config.php''' with your old one!''';
### If your previous version was >= 1.70: Simply replace the new '''config.php''' with your backup '''config.php''' file (as the file format has not changed);
## If your previous version was older than 1.90: Copy any customized templates to '/upload/templates' - you will also need to rename each template directory whose name matches an existing template in /templates;
## Copy your '/upload' directory back to the old location;
## Double check the '''permissions''' set on the directories of LimeSurvey (write access to '''/tmp''', '''/upload''', and to their subdirectories is required) as described in the [[Installation#Set Directory permissions|installation wiki]];
# Finish the installation/upgrade process:
## Once you open the URL to your LimeSurvey administration, the database tables will be updated after confirmation;
## Remove or rename the '/admin/install' directory as/if instructed by the installation script;
## Check if any special manual checks apply (as listed below).

<div class="simplebox">'''Special checks after an upgrade''':
*'''from any earlier version to 1.92''': The '''templates''' have been changed. Please check your customized templates if they are still looking right. If not, you will have to edit your templates accordingly (check out the original templates to see what was changed)<br />
*'''from a version earlier than v1.53''': When upgrading from a version before v1.53 to the latest version, please check the '''global user rights''' of each user. There was a new '''superadmin''' right introduced in v1.53 that can give a user the same privilege as the master administration account created during the install. The upgrade script is guessing to whom should be given this permission in the older versions. As this is not perfect, it should be carefully checked.
</div>

==Upgrading from a version earlier than v1.50 (v1.0 through v1.44)==

Since the data structure and a lot of other things were changed, '''upgrading from any version previous to v1.50 is <u>NOT</u> possible'''. If you have old survey structure files with a *.sql extension, the only way to get these into a newer version is to install [http://www.limesurvey.org/en/archived-releases/289-limesurvey150zip version 1.50], import the .sql file(s) there, then upgrade that version to the most recent LimeSurvey version. Check the page related to [[Transferring an installation|how an installation can be transferred]] for more details.

=FAQ=

==What is the most recent LimeSurvey version that still supports PHP4?==

The last release offering PHP4 support was version 1.82+.

==Can I upgrade even if I have active surveys?==

Yes, you can. Exceptions may be mentioned in the thorough instructions above. We strongly advise to test your surveys after upgrade to check if your design templates still work alright.

==What is best way to port the *.sql survey structure files of LimeSurvey to the latest version?==

Install version 1.50, import the file, and export the survey structure to the newer .csv format. The latest version can still read the .csv survey structure format.

2017-09-07T23:25:43Z

Tpweb17: Created page with "Si vous souhaitez fixer le domaine pour un cookie, utilisez ceci dans config.php: <syntaxhighlight lang="php" enclose="pre"> // Set the domain for cookie 'sessi..."

Si vous souhaitez fixer le domaine pour un cookie, utilisez ceci dans config.php:
<syntaxhighlight lang="php" enclose="pre"> // Set the domain for cookie
'session' => array (
'cookieParams' => array(
'domain' => '.example.org',
),
),
</syntaxhighlight>

Optional settings/fr

2017-09-07T23:24:55Z

Tpweb17: Created page with "Si vous utilisez SSL ('https') pour votre installation de LimeSurvey, ajouter les lignes suivantes dans votre config.php augmentera la sécurité de la session : <syntaxhighli..."

<languages />
__TOC__

=Comment modifier les réglages optionnels=

Ces réglages optionnels se trouvent dans le fichier /application/config/config-default.php d’une installation standard - certains ne sont utilisés que lors de l'installation, certains sont surchargés par les [[Global settings/fr|paramètres généraux]].

{{Alert|Si vous souhaitez modifier ces réglages, merci de ne pas le faire dans config-defaults.php mais copiez le réglage ou la ligne dans /application/config/config.php in <nowiki>'config'=>array()</nowiki> and modifiez-la à cet endroit.}}
Tous les réglages de config.php récrivent les valeurs par défaut de config-defaults.php et certains de ce réglages serontécras&és dans le dialogue des réglages globaux {{NewIn|1.87}}. Cette procédure rendra beaucoup plus facile la mise à jour ultérieure de votre installation !

Pour modifier/ajouter les options de LimeSurvey settings dans /application/config/config.php vous devez modifier le tableau de configuration :
<syntaxhighlight lang="php" enclose="pre">
'config'=>array(
'debug'=>0,
'debugsql'=>0,
'LimeSurveySetting'=>'New value',
)
</syntaxhighlight>

=Réglages de Yii=
LimeSurvey utilise le framework Yii et Yii possède ses propres paramètres de configuration dans le fichier application/config/config.php. Vous pouvez aussi accéder à certains réglages spécifiques de configuratrion de LimeSurvey en passant par la configuration de Yii.

Les paramètres spécifiques de Yii sont déclarés dans le tableau des composants :
<syntaxhighlight lang="php" enclose="pre">
'components' => array(
'db' => array(
....
),
'Specific settings'=>array(
....
),
),
</syntaxhighlight>

==Database settings==
The database settings are written by the installer to the config.php file when you install LimeSurvey for the first time. If needed you can update this part of the config. 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 database types mysql,pgsql,dblib,mssql, and sqlsrv.

==Paramètres de session==
Vous pouvez déclarer des paramètres de session dans config.php, le premier exemple étant la session de la base de données. You pouvez décommenter/ajouter la partie nécessaire dans config.php. Voir [[http://www.yiiframework.com/doc/api/1.1/CHttpSession Documentation de Yii]] pour les autres paramètres.

Si vous utilisez SSL ('https') pour votre installation de LimeSurvey, ajouter les lignes suivantes dans votre config.php augmentera la sécurité de la session :
<syntaxhighlight lang="php" enclose="pre"> // Définir le cookie avec SSL
'session' => array (
'cookieParams' => array(
'secure' => true, // utiliser SSL pour les cookies
'httponly' => true // Les cookies ne seront pas utilisés pour les autres protocoles - experimental
),
),
</syntaxhighlight>

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

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

Some example you can modify in your LimeSurvey configuration:<sup>At your own risk</sup> :
<syntaxhighlight lang="php" enclose="pre"> // Disable CSRF protection
'request' => array(
'enableCsrfValidation'=>false,
),
</syntaxhighlight>
<syntaxhighlight lang="php" enclose="pre"> // Enforce a certain base URL
'request' => array(
'hostInfo' => 'http://www.example.org/'
),
</syntaxhighlight>
<syntaxhighlight lang="php" enclose="pre"> // Set the cookie domain name for CSRF protection
'request' => array(
'csrfCookie' => array( 'domain' => '.example.com' )
),
</syntaxhighlight>

If you need updating only the url for token email : you can set your [[Optional_settings#Advanced_Path_Settings|publicurl]] in your config.php file.

==URL settings==
To have the same behaviour like the old 'Fancy URL' feature , you can update the urlManager
<syntaxhighlight lang="php" enclose="pre"> // Use short URL
'urlManager' => array(
'urlFormat' => 'path',
'showScriptName' => false,
),
</syntaxhighlight>
Adding .html after the survey id
<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>
Find more information in the [http://www.yiiframework.com/doc/guide/1.1/en/topics.url Yii documentation].

==Paramètres généraux==
*'''$sitename :''' Permet de donner un nom à votre site d'enquêtes en ligne. Ce nom apparaitra dans la vue de la liste des questionnaires et dans l'entête de l'administration. (depuis la version 1.87 ce paramètre est écrasé par les [[Global settings/fr|paramètres généraux]])
*'''$siteadminemail :''' Adresse par défaut de l’administrateur du site. Elle est utilisée pour les messages systèmes et les opérations de contact. (depuis la version 1.87 ce paramètre est écrasé par les [[Global settings/fr|paramètres généraux]])
*'''$siteadminbounce :''' Adresse vers laquelle seront acheminés les messages rejetés. (depuis la version 1.87 ce paramètre est écrasé par les [[Global settings/fr|paramètres généraux]])
*'''$siteadminname :''' Nom réel de l'administrateur du site. (depuis la version 1.87 ce paramètre est écrasé par les [[Global settings/fr|paramètres généraux]])

*'''sitename''': Give your survey site a name. This name will appear in the survey list overview and in the administration header. This setting is used only as default value and overridden in the [[Global settings]] dialog {{NewIn|1.87}}.
*'''siteadminemail:''' This is the default email address of the site administrator and used for system messages and contact options. This setting is used only as default value and overridden by the [[Global settings]] dialog {{NewIn|1.87}}.
*'''siteadminbounce:''' This is the email address where bounced emails will be sent to. This setting is used only as default value and overridden by the [[Global settings]] dialog {{NewIn|1.87}}.
*'''siteadminname:''' The real name of the site administrator. This setting is used only as default value and overridden in the [[Global settings]] dialog) {{NewIn|1.87}}.
*'''proxy_host_name:''' This is the host name of your proxy server (if you are behind a proxy and want to update LimeSurvey using ComfortUpdate) {{NewIn|2.05}}.
*'''proxy_host_port:''' This is the port of your proxy server (if you are behind a proxy and want to update LimeSurvey using ComfortUpdate) {{NewIn|2.05}}.

= Security=

* '''maxLoginAttempt''': If the user enters password incorrectly this is the number of attempts before the users is locked out by IP address.
* '''timeOutTime''': If the user enters password incorrectly for <maxLoginAttempt> set the lock out time (in seconds).
* '''surveyPreview_require_Auth''': 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 and without having to activate the survey first. This setting is a default value and can be overridden in the [[Global settings]] dialog {{NewIn|1.87}}.
* '''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 belongs to at least one same group. This setting is a default value and can be overridden in the [[Global settings]] dialog.
*'''filterxsshtml:''' This setting enables filtering of suspicious html tags in survey, group, questions and answer texts in the administration interface. Only leave this to 'false' 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">Super admin never have their HTML filtered</span>. This setting is a default value and can be overridden in the [[Global settings]] dialog {{NewIn|1.87}}.
*'''demoModeOnly:''' If this option is set to true, then LimeSurvey will go into demo mode. The demo mode changes the following things:
** Disables changing of the admin user's details and password
** Disables uploading files on the template editor
** Disables sending email invitations and reminders
** Disables doing a database dump
** Disables the ability to modify the following global settings: Site name, Default language, Default Htmleditor Mode, XSS filter

= Resources=
*'''sessionlifetime:''' Defines the time in seconds after which a survey session expires. It applies only if you are using database sessions. This setting is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}.
*'''memorylimit:''' This sets how much memory LimeSurvey can access. '128M' is the minimum (M=Megabyte) recommended. If you receive time out errors or have problems generating statistics or exporting files raise this limit to '256M' or higher. If your webserver has set a higher limit then this setting will be ignored.

<div class="warningbox">Please mind that such local settings by an application can always be overruled by global server settings.</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

=Appearance=
*'''lwcdropdowns:'''{{ObsoleteIn|2.0}} This can be set to either "L" or "R". Setting it to "R" will result in 'List with Comment' questions being displayed as radio buttons, whereas "L" will result in 'List with Comment' questions being displayed in a 'dropdown' list box .
*'''dropdownthreshold:''''{{ObsoleteIn|2.50}} When you have selected "R" for $dropdowns, this allows you to set a maximum number of options that will display as radio buttons, before converting back to a dropdown list. If you have a question that has a large number of options, displaying them all as radio buttons can look unweildy, and be counter-intuitive to users. Setting this to a maximum of, say 25 (which is the default) means that large lists are easier for the survey participant to use.
*'''repeatheadings:''' With the Array type question, often you'll 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]] dialog) {{NewIn|2.05}}.
*'''minrepeatheadings:''' The minimum number of remaining subquestions that are required before repeating the headings in Array questions.
*'''defaulttemplate:''' This setting specifys the default theme used for the 'public list' of surveys. This setting is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}.
*'''defaulthtmleditormode:''' Sets the default mode for integrated HTML editor. This setting is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}. 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]]. Valid settings are:
** 'css' using one of the various CSS only methods for creating columns (see template style sheet for details).
** 'ul' using multiple floated unordered lists. (default)
** 'table' using conventional tables based layout.
** NULL disable 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 is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}.
*'''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 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 is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}.

=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. Say you ask the 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 $deletenonvalues==1, those irrelevant values will be cleared (NULLed) in the database. If $deletenonvalues==0, his erroneous answers will not be deleted, so they will still be present in the database when you analyze it.
*'''shownoanswer:''' When a question of a radio button/select type that contains editable answers (ie: 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 is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}. Valid values are:
**0 = no ,
**1 = yes ,
**2 = 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:'''{{NewIn|1.85}} 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. (Default: true - hide group name and description when all conditions in the group are hidden by conditions)
*'''showpopups:''' Show popup messages if mandatory or conditional questions have not been answered correctly. 1=Show popup message (default), 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).

=Development and debugging=
*'''debug:''' With this setting you set the PHP error reporting to E_ALL. That means every little notice, warning or error with 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. (Default: 0)
*'''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 optimizing the number of queries

If you experience an error in the application, we strongly recommend to acivate the debug setting so you usually get some more detailed error that you can submit with the bug report:

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

= Email Settings=

Note: All these settings in this section are overridden in the [[Global settings]] dialog{{NewIn|1.87}}.
*'''emailmethod:''' This determines how E-mail messages are being sent. The following options are available:
**'''mail:''' use internal PHP mailer
**'''sendmail:''' use sendmail mailer
**'''smtp:'''use 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 $emailmethod 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 on the token control toolbar, (not the button on the right of each token), sends the maxemails number of invitations, then displays a list of the addresses sent to 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 off and come back at a later time to send the next batch of invites.

= Statistics and Response Browsing=
*'''usejpgraph:''' {{ObsoleteIn|1.8}} The [http://www.aditus.nu/jpgraph/ JPGraph-library] lets you display the results of your survey in the statistics part of LimeSurvey in bar- and pie charts. If you have a correctly configured jpgraph class set up on your server, you can turn this feature on or off (1=on, 0=off). Please have a look, every version of PHP needs another version of JPGraph! This feature is currently in development, so expect a few weird outcomes.
*'''jpgraphdir:''' {{ObsoleteIn|1.8}} The physical disk location of the jpgraph class scripts. This setting is only required if $usejpgraph is equal to 1.
*'''jpgraphfont:''' {{ObsoleteIn|1.8}} The font to use with graphs. A failsafe setting would be "FF_FONT1"
*'''embedded:'''{{ObsoleteIn|2.0}} If you want to integrate LimeSurvey into another page then you can turn off sending HTML headers by using this setting and point instead to the header method of a custom function. This is a dirty hack but should work for a quick integration.
*'''filterout_incomplete_answers:''' Control the default behaviour of filtering incomplete answers when browsing or analyzing responses. For a discussion on incomplete Responses see [[Browsing survey results]]. Since these records can corrupt the statistics, an option is given to switch this filter on or off in several GUI forms. This parameter config.php is just the default state for the incomplete answer filter. The following options are available:
**''show'': Show both complete and incomplete answers
**''filter'': Show only complete answers
**''incomplete'': Show only incomplete answers
*'''strip_query_from_referer_url''': This setting determine if the referrer URL saves parameter or not. Default value is "false" (in this case referrer URL saves all parameter). Alternatively this value can be set to "true" and the parameter part of the referrer URL will be removed.
*'''showaggregateddata:''' {{NewIn|1.8}} When activated there are additional values like arithmetic mean and standard deviation at statistics. Furthermore data is aggregated to get a faster overview e.g. 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:''' {{NewIn|1.85}} This feature activates PDF export for printable survey and Print Answers. The PDF export is totally experimental. The output is mostly ugly. At this point no support can be given - if you want to help to fix it please get in touch with us.
**usepdfexport: Set 0 to disable; 1 to enable
**pdfdefaultfont: Default font for the pdf Export
**alternatepdffontfile: an array with key for language and specific font for this language can be replaced or just updated .
**pdffontsize: Fontsize for normal text; Surveytitle is +4; grouptitle is +2
**notsupportlanguages = array('zh-Hant-TW','zh-Hant-HK','zh-Hans','ja','th');
**pdforientation: Set L for Landscape or P for portrait format
*'"Graph setting"'
** chartfontfile : Font file to be used : must be in the server font directory or in ./fot directory
** alternatechartfontfile : an array with key for language and specific font for this language can be replaced or just updated .
*'''showsgqacode:''' {{NewIn|1.91}} This setting is used at the printable survey feature and defaults to ''false''. If you set ''showsgqacode = true;'' the IDs for 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. Because of this the information below might be outdated. See [[Plugins]] for most up to date information.

== Delegate Authentication 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 Webserver software to use this external authentication system, and then ask LimeSurvey to trust the user identity reported by the webserver. In order to enable this feature you have to:
* set '''auth_webserver''' to true in config.php
* enable authentication at the webserver side

Please note that:
* LimeSurvey will then bypass its own authentication process (by using the login name reported by the webserver 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 however than <u>by default Authentication Delegation doesn't bypass the LimeSurvey authorization system</u>: this means 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 survey resources.

A user is then granted access to LimeSurvey if and only if:
* he has been authenticated to the webserver
* 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 huge user database, it is sometimes easier to auto-import user in the LimeSurvey database.
*'''auth_webserver_autocreate_user''': if set to true LimeSurvey will try to autoimport users authenticated by the webserver 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 fake First and Last name, email, 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 an LDAP directory), the true First&Last; names and email of a particular user. You can even customize his privileges on the system based on his groups on the external DB.

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 '''$WebserverAuth_autouserprofile'''
<syntaxhighlight lang="php" enclose="div">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>
== User name mapping==

In case 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' username defined in your external authentication database. Then in order to login to LimeSurvey as admin, you'll have to map your external username let's call it 'myname' to the admin login name ine LimeSurvey. The corresponding setup is :

<syntaxhighlight lang="php" enclose="div">$config['auth_webserver_user_map'] = Array ('myname' => 'admin');</syntaxhighlight>
After a successful authentication with the 'myname' login and password to the webserver, you'll be directly authorized to use LimeSurvey as the 'admin' user.

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

== Use one time passwords==

{{NewIn|1.81}} A user can open the LimeSurvey login at /limesurvey/admin and pass username and a 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 ('''use_one_time_passwords''' => true) to enable the usage of one time passwords (default = false). More information can be found at [[Manage users#Use one-time passwords|"Manage Users"]].

== Paramètres de répertoires avancés==

*'''homeurl:''' This should be set to the URL location of your administration scripts. These are the scripts 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 - {$_SERVER<nowiki>[</nowiki>'SERVER_NAME']}. 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.
*'''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 is used when sending token email.'''
*'''tempurl:''' This should be set to the URL location of your "/limesurvey/tmp" directory - or a directory which you would like LimeSurvey to use to store temporary files, including uploads. This directory must be set to read & write for your webserver (e.g. chmod 755).
*'''imagefiles:''' By default you should leave this pointing to the URL location of /limesurvey/admin/images - where the images are installed initially. You may, however, prefer to move these images to another location and if so point this to the URL directory where they are stored.
*'''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 - {$_SERVER<nowiki>[</nowiki>'DOCUMENT_ROOT']}. 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.
*'''sCKEditorURL:''' url of the fckeditor script
*'''fckeditexpandtoolbar:''' defines if the FCKeditor toolbar should be opened by default
*'''pdfexportdir:''' Directory with the tcpdf.php extensiontcpdf.php
*'''pdffonts:''' Directory for the TCPDF fonts

Translations:Optional settings/75/fr

2017-09-07T23:24:55Z

Si vous utilisez SSL ('https') pour votre installation de LimeSurvey, ajouter les lignes suivantes dans votre config.php augmentera la sécurité de la session :
<syntaxhighlight lang="php" enclose="pre"> // Définir le cookie avec SSL
'session' => array (
'cookieParams' => array(
'secure' => true, // utiliser SSL pour les cookies
'httponly' => true // Les cookies ne seront pas utilisés pour les autres protocoles - experimental
),
),
</syntaxhighlight>

Optional settings/fr

2017-09-07T23:20:45Z

Tpweb17: Created page with "==Paramètres de session== Vous pouvez déclarer des paramètres de session dans config.php, le premier exemple étant la session de la base de données. You pouvez décomment..."

<languages />
__TOC__

=Comment modifier les réglages optionnels=

Ces réglages optionnels se trouvent dans le fichier /application/config/config-default.php d’une installation standard - certains ne sont utilisés que lors de l'installation, certains sont surchargés par les [[Global settings/fr|paramètres généraux]].

{{Alert|Si vous souhaitez modifier ces réglages, merci de ne pas le faire dans config-defaults.php mais copiez le réglage ou la ligne dans /application/config/config.php in <nowiki>'config'=>array()</nowiki> and modifiez-la à cet endroit.}}
Tous les réglages de config.php récrivent les valeurs par défaut de config-defaults.php et certains de ce réglages serontécras&és dans le dialogue des réglages globaux {{NewIn|1.87}}. Cette procédure rendra beaucoup plus facile la mise à jour ultérieure de votre installation !

Pour modifier/ajouter les options de LimeSurvey settings dans /application/config/config.php vous devez modifier le tableau de configuration :
<syntaxhighlight lang="php" enclose="pre">
'config'=>array(
'debug'=>0,
'debugsql'=>0,
'LimeSurveySetting'=>'New value',
)
</syntaxhighlight>

=Réglages de Yii=
LimeSurvey utilise le framework Yii et Yii possède ses propres paramètres de configuration dans le fichier application/config/config.php. Vous pouvez aussi accéder à certains réglages spécifiques de configuratrion de LimeSurvey en passant par la configuration de Yii.

Les paramètres spécifiques de Yii sont déclarés dans le tableau des composants :
<syntaxhighlight lang="php" enclose="pre">
'components' => array(
'db' => array(
....
),
'Specific settings'=>array(
....
),
),
</syntaxhighlight>

==Database settings==
The database settings are written by the installer to the config.php file when you install LimeSurvey for the first time. If needed you can update this part of the config. 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 database types mysql,pgsql,dblib,mssql, and sqlsrv.

==Paramètres de session==
Vous pouvez déclarer des paramètres de session dans config.php, le premier exemple étant la session de la base de données. You pouvez décommenter/ajouter la partie nécessaire dans config.php. Voir [[http://www.yiiframework.com/doc/api/1.1/CHttpSession Documentation de Yii]] pour les autres paramètres.

If you use SSL ('https') for your LimeSurvey installation adding the following lines to your config.php will increase session security:
<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 this in config.php:
<syntaxhighlight lang="php" enclose="pre"> // Set the domain for cookie
'session' => array (
'cookieParams' => array(
'domain' => '.example.org',
),
),
</syntaxhighlight>

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

Some example you can modify in your LimeSurvey configuration:<sup>At your own risk</sup> :
<syntaxhighlight lang="php" enclose="pre"> // Disable CSRF protection
'request' => array(
'enableCsrfValidation'=>false,
),
</syntaxhighlight>
<syntaxhighlight lang="php" enclose="pre"> // Enforce a certain base URL
'request' => array(
'hostInfo' => 'http://www.example.org/'
),
</syntaxhighlight>
<syntaxhighlight lang="php" enclose="pre"> // Set the cookie domain name for CSRF protection
'request' => array(
'csrfCookie' => array( 'domain' => '.example.com' )
),
</syntaxhighlight>

If you need updating only the url for token email : you can set your [[Optional_settings#Advanced_Path_Settings|publicurl]] in your config.php file.

==URL settings==
To have the same behaviour like the old 'Fancy URL' feature , you can update the urlManager
<syntaxhighlight lang="php" enclose="pre"> // Use short URL
'urlManager' => array(
'urlFormat' => 'path',
'showScriptName' => false,
),
</syntaxhighlight>
Adding .html after the survey id
<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>
Find more information in the [http://www.yiiframework.com/doc/guide/1.1/en/topics.url Yii documentation].

==Paramètres généraux==
*'''$sitename :''' Permet de donner un nom à votre site d'enquêtes en ligne. Ce nom apparaitra dans la vue de la liste des questionnaires et dans l'entête de l'administration. (depuis la version 1.87 ce paramètre est écrasé par les [[Global settings/fr|paramètres généraux]])
*'''$siteadminemail :''' Adresse par défaut de l’administrateur du site. Elle est utilisée pour les messages systèmes et les opérations de contact. (depuis la version 1.87 ce paramètre est écrasé par les [[Global settings/fr|paramètres généraux]])
*'''$siteadminbounce :''' Adresse vers laquelle seront acheminés les messages rejetés. (depuis la version 1.87 ce paramètre est écrasé par les [[Global settings/fr|paramètres généraux]])
*'''$siteadminname :''' Nom réel de l'administrateur du site. (depuis la version 1.87 ce paramètre est écrasé par les [[Global settings/fr|paramètres généraux]])

*'''sitename''': Give your survey site a name. This name will appear in the survey list overview and in the administration header. This setting is used only as default value and overridden in the [[Global settings]] dialog {{NewIn|1.87}}.
*'''siteadminemail:''' This is the default email address of the site administrator and used for system messages and contact options. This setting is used only as default value and overridden by the [[Global settings]] dialog {{NewIn|1.87}}.
*'''siteadminbounce:''' This is the email address where bounced emails will be sent to. This setting is used only as default value and overridden by the [[Global settings]] dialog {{NewIn|1.87}}.
*'''siteadminname:''' The real name of the site administrator. This setting is used only as default value and overridden in the [[Global settings]] dialog) {{NewIn|1.87}}.
*'''proxy_host_name:''' This is the host name of your proxy server (if you are behind a proxy and want to update LimeSurvey using ComfortUpdate) {{NewIn|2.05}}.
*'''proxy_host_port:''' This is the port of your proxy server (if you are behind a proxy and want to update LimeSurvey using ComfortUpdate) {{NewIn|2.05}}.

= Security=

* '''maxLoginAttempt''': If the user enters password incorrectly this is the number of attempts before the users is locked out by IP address.
* '''timeOutTime''': If the user enters password incorrectly for <maxLoginAttempt> set the lock out time (in seconds).
* '''surveyPreview_require_Auth''': 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 and without having to activate the survey first. This setting is a default value and can be overridden in the [[Global settings]] dialog {{NewIn|1.87}}.
* '''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 belongs to at least one same group. This setting is a default value and can be overridden in the [[Global settings]] dialog.
*'''filterxsshtml:''' This setting enables filtering of suspicious html tags in survey, group, questions and answer texts in the administration interface. Only leave this to 'false' 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">Super admin never have their HTML filtered</span>. This setting is a default value and can be overridden in the [[Global settings]] dialog {{NewIn|1.87}}.
*'''demoModeOnly:''' If this option is set to true, then LimeSurvey will go into demo mode. The demo mode changes the following things:
** Disables changing of the admin user's details and password
** Disables uploading files on the template editor
** Disables sending email invitations and reminders
** Disables doing a database dump
** Disables the ability to modify the following global settings: Site name, Default language, Default Htmleditor Mode, XSS filter

= Resources=
*'''sessionlifetime:''' Defines the time in seconds after which a survey session expires. It applies only if you are using database sessions. This setting is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}.
*'''memorylimit:''' This sets how much memory LimeSurvey can access. '128M' is the minimum (M=Megabyte) recommended. If you receive time out errors or have problems generating statistics or exporting files raise this limit to '256M' or higher. If your webserver has set a higher limit then this setting will be ignored.

<div class="warningbox">Please mind that such local settings by an application can always be overruled by global server settings.</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

=Appearance=
*'''lwcdropdowns:'''{{ObsoleteIn|2.0}} This can be set to either "L" or "R". Setting it to "R" will result in 'List with Comment' questions being displayed as radio buttons, whereas "L" will result in 'List with Comment' questions being displayed in a 'dropdown' list box .
*'''dropdownthreshold:''''{{ObsoleteIn|2.50}} When you have selected "R" for $dropdowns, this allows you to set a maximum number of options that will display as radio buttons, before converting back to a dropdown list. If you have a question that has a large number of options, displaying them all as radio buttons can look unweildy, and be counter-intuitive to users. Setting this to a maximum of, say 25 (which is the default) means that large lists are easier for the survey participant to use.
*'''repeatheadings:''' With the Array type question, often you'll 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]] dialog) {{NewIn|2.05}}.
*'''minrepeatheadings:''' The minimum number of remaining subquestions that are required before repeating the headings in Array questions.
*'''defaulttemplate:''' This setting specifys the default theme used for the 'public list' of surveys. This setting is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}.
*'''defaulthtmleditormode:''' Sets the default mode for integrated HTML editor. This setting is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}. 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]]. Valid settings are:
** 'css' using one of the various CSS only methods for creating columns (see template style sheet for details).
** 'ul' using multiple floated unordered lists. (default)
** 'table' using conventional tables based layout.
** NULL disable 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 is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}.
*'''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 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 is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}.

=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. Say you ask the 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 $deletenonvalues==1, those irrelevant values will be cleared (NULLed) in the database. If $deletenonvalues==0, his erroneous answers will not be deleted, so they will still be present in the database when you analyze it.
*'''shownoanswer:''' When a question of a radio button/select type that contains editable answers (ie: 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 is overridden in the [[Global settings]] dialog) {{NewIn|1.87}}. Valid values are:
**0 = no ,
**1 = yes ,
**2 = 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:'''{{NewIn|1.85}} 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. (Default: true - hide group name and description when all conditions in the group are hidden by conditions)
*'''showpopups:''' Show popup messages if mandatory or conditional questions have not been answered correctly. 1=Show popup message (default), 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).

=Development and debugging=
*'''debug:''' With this setting you set the PHP error reporting to E_ALL. That means every little notice, warning or error with 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. (Default: 0)
*'''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 optimizing the number of queries

If you experience an error in the application, we strongly recommend to acivate the debug setting so you usually get some more detailed error that you can submit with the bug report:

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

= Email Settings=

Note: All these settings in this section are overridden in the [[Global settings]] dialog{{NewIn|1.87}}.
*'''emailmethod:''' This determines how E-mail messages are being sent. The following options are available:
**'''mail:''' use internal PHP mailer
**'''sendmail:''' use sendmail mailer
**'''smtp:'''use 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 $emailmethod 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 on the token control toolbar, (not the button on the right of each token), sends the maxemails number of invitations, then displays a list of the addresses sent to 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 off and come back at a later time to send the next batch of invites.

= Statistics and Response Browsing=
*'''usejpgraph:''' {{ObsoleteIn|1.8}} The [http://www.aditus.nu/jpgraph/ JPGraph-library] lets you display the results of your survey in the statistics part of LimeSurvey in bar- and pie charts. If you have a correctly configured jpgraph class set up on your server, you can turn this feature on or off (1=on, 0=off). Please have a look, every version of PHP needs another version of JPGraph! This feature is currently in development, so expect a few weird outcomes.
*'''jpgraphdir:''' {{ObsoleteIn|1.8}} The physical disk location of the jpgraph class scripts. This setting is only required if $usejpgraph is equal to 1.
*'''jpgraphfont:''' {{ObsoleteIn|1.8}} The font to use with graphs. A failsafe setting would be "FF_FONT1"
*'''embedded:'''{{ObsoleteIn|2.0}} If you want to integrate LimeSurvey into another page then you can turn off sending HTML headers by using this setting and point instead to the header method of a custom function. This is a dirty hack but should work for a quick integration.
*'''filterout_incomplete_answers:''' Control the default behaviour of filtering incomplete answers when browsing or analyzing responses. For a discussion on incomplete Responses see [[Browsing survey results]]. Since these records can corrupt the statistics, an option is given to switch this filter on or off in several GUI forms. This parameter config.php is just the default state for the incomplete answer filter. The following options are available:
**''show'': Show both complete and incomplete answers
**''filter'': Show only complete answers
**''incomplete'': Show only incomplete answers
*'''strip_query_from_referer_url''': This setting determine if the referrer URL saves parameter or not. Default value is "false" (in this case referrer URL saves all parameter). Alternatively this value can be set to "true" and the parameter part of the referrer URL will be removed.
*'''showaggregateddata:''' {{NewIn|1.8}} When activated there are additional values like arithmetic mean and standard deviation at statistics. Furthermore data is aggregated to get a faster overview e.g. 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:''' {{NewIn|1.85}} This feature activates PDF export for printable survey and Print Answers. The PDF export is totally experimental. The output is mostly ugly. At this point no support can be given - if you want to help to fix it please get in touch with us.
**usepdfexport: Set 0 to disable; 1 to enable
**pdfdefaultfont: Default font for the pdf Export
**alternatepdffontfile: an array with key for language and specific font for this language can be replaced or just updated .
**pdffontsize: Fontsize for normal text; Surveytitle is +4; grouptitle is +2
**notsupportlanguages = array('zh-Hant-TW','zh-Hant-HK','zh-Hans','ja','th');
**pdforientation: Set L for Landscape or P for portrait format
*'"Graph setting"'
** chartfontfile : Font file to be used : must be in the server font directory or in ./fot directory
** alternatechartfontfile : an array with key for language and specific font for this language can be replaced or just updated .
*'''showsgqacode:''' {{NewIn|1.91}} This setting is used at the printable survey feature and defaults to ''false''. If you set ''showsgqacode = true;'' the IDs for 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. Because of this the information below might be outdated. See [[Plugins]] for most up to date information.

== Delegate Authentication 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 Webserver software to use this external authentication system, and then ask LimeSurvey to trust the user identity reported by the webserver. In order to enable this feature you have to:
* set '''auth_webserver''' to true in config.php
* enable authentication at the webserver side

Please note that:
* LimeSurvey will then bypass its own authentication process (by using the login name reported by the webserver 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 however than <u>by default Authentication Delegation doesn't bypass the LimeSurvey authorization system</u>: this means 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 survey resources.

A user is then granted access to LimeSurvey if and only if:
* he has been authenticated to the webserver
* 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 huge user database, it is sometimes easier to auto-import user in the LimeSurvey database.
*'''auth_webserver_autocreate_user''': if set to true LimeSurvey will try to autoimport users authenticated by the webserver 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 fake First and Last name, email, 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 an LDAP directory), the true First&Last; names and email of a particular user. You can even customize his privileges on the system based on his groups on the external DB.

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 '''$WebserverAuth_autouserprofile'''
<syntaxhighlight lang="php" enclose="div">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>
== User name mapping==

In case 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' username defined in your external authentication database. Then in order to login to LimeSurvey as admin, you'll have to map your external username let's call it 'myname' to the admin login name ine LimeSurvey. The corresponding setup is :

<syntaxhighlight lang="php" enclose="div">$config['auth_webserver_user_map'] = Array ('myname' => 'admin');</syntaxhighlight>
After a successful authentication with the 'myname' login and password to the webserver, you'll be directly authorized to use LimeSurvey as the 'admin' user.

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

== Use one time passwords==

{{NewIn|1.81}} A user can open the LimeSurvey login at /limesurvey/admin and pass username and a 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 ('''use_one_time_passwords''' => true) to enable the usage of one time passwords (default = false). More information can be found at [[Manage users#Use one-time passwords|"Manage Users"]].

== Paramètres de répertoires avancés==

*'''homeurl:''' This should be set to the URL location of your administration scripts. These are the scripts 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 - {$_SERVER<nowiki>[</nowiki>'SERVER_NAME']}. 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.
*'''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 is used when sending token email.'''
*'''tempurl:''' This should be set to the URL location of your "/limesurvey/tmp" directory - or a directory which you would like LimeSurvey to use to store temporary files, including uploads. This directory must be set to read & write for your webserver (e.g. chmod 755).
*'''imagefiles:''' By default you should leave this pointing to the URL location of /limesurvey/admin/images - where the images are installed initially. You may, however, prefer to move these images to another location and if so point this to the URL directory where they are stored.
*'''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 - {$_SERVER<nowiki>[</nowiki>'DOCUMENT_ROOT']}. 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.
*'''sCKEditorURL:''' url of the fckeditor script
*'''fckeditexpandtoolbar:''' defines if the FCKeditor toolbar should be opened by default
*'''pdfexportdir:''' Directory with the tcpdf.php extensiontcpdf.php
*'''pdffonts:''' Directory for the TCPDF fonts