https://manual.limesurvey.org/api.php?action=feedcontributions&user=Anonymous&feedformat=atomLimeSurvey Manual - User contributions [en]2024-03-29T01:21:36ZUser contributionsMediaWiki 1.35.10https://manual.limesurvey.org/index.php?title=How_to_translate_LimeSurvey&diff=1508How to translate LimeSurvey2009-06-08T10:01:31Z<p>Anonymous: </p>
<hr />
<div><br />
{REDIRECT(page=LimeSurvey 1.x Translating LimeSurvey) /}</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Installation_security_hints&diff=1719Installation security hints2009-05-20T13:37:30Z<p>Anonymous: </p>
<hr />
<div><br />
__TOC__<br />
<br />
==General==<br />
<br />
LimeSurvey relies on its own security system which is activated by default. The authors of this software takes no responsibility and makes no claims in relation to the appropriateness or secureness of this software. However we take security issues very serious and react quickly - if you know of any security problems with LimeSurvey please let us know: info@limesurvey.org .<br />
<br />
==Linux file permissions==<br />
<br />
If you are using a Linux server, setting file permissions is required to secure your LimeSurey installation.<br />
<br />
===Basic facts about Linux/*nix file permissions===<br />
<br />
A Linux/*nix operating system is multi-user. This means that, apart from your personal account, other user accounts exist on the system and you should take care of what permissions you give to other users.<br />
<br />
<div class="simplebox">[[File:help.png]] '''Hint:''' Setting file permissions is especially important in order to secure configuration files holding critical data such as passwords.</div><br />
<br />
''Note however that the 'root' account will always be granted permission to access your files (no matter what file permissions you set) as it is the super-admin user.''<br />
<br />
The webserver (which runs LimeSurvey), is also running under a given identity (user). On Linux, this is usually the 'www','www-data' (on Debian/Ubuntu), 'apache' or 'nobody' user. However, some hosting companies use systems (such as suexec) which make it possible to run LimeSurvey scripts with your personal user. Of course the webserver user must have the right to read LimeSurvey files. However, only a small subset of LimeSurvey subdirectories must be writeable by the webserver user.<br />
<br />
<div class="simplebox">[[File:help.png]] '''Hint''': It is very valuable to revoke write permission for the webserver user to these LimeSurvey subdirectories that do not require it. Indeed, even if a LimeSurvey vulnerability is discovered, the main files will still be protected from an illicit modification thanks to the file system permissions.</div><br />
<br />
===Setting file permissions on a self-managed Linux system===<br />
<br />
If you're managing your webserver and operating system configuration (you are the owner of the physical server or are renting a virtual server on which you have root access), you can follow these recommendations.<br />
<br />
You can first set the owner and group of your LimeSurvey files so that it will ease the file permissions setup.<br />
<br />
A possible strategy is to set the owner of the LimeSurvey files to your personal username, and the group of the LimeSurvey files to the webserver group. Usually this webserver group only contains the webserver account (and possibly another webmaster account).<br />
<br />
For instance if your username is 'myaccount' and the webserver user is 'apache' in the 'apache' group, then, from a shell access, you can use the following commands:<br />
<br />
$ chown -R myaccount limesurvey/<br />
<br />
$ chgrp -R apache limesurvey/<br />
<br />
Then set the file and subdirectories permissions.<br />
<br />
For the script to work properly it needs write access to some directories:<br />
*The "/limesurvey/tmp" directory is used for import-uploads and should be set to ''Read & Write'' for your webserver.<br />
*You should also set ''Read & Write'' for your webserver for the "limesurvey/template" directory and its sub-directories and files if you want to be able to edit and copy templates.<br />
*The upload/ directory and all its subdirectories must also have ''Read & Write'' for your webserver in order to enable picture and media files upload.<br />
* The other directories and files should be set to ''Read Only''<br />
<br />
<div class="simplebox">[[File:help.png]] '''Hint:''' Supposing you've followed the above recommendations on owner/group, these settings can be applied by the following commands:<br />
<br />
$ chmod -R o-r-w-x limesurvey/<br />
<br />
$ chmod -R -w limesurvey/<br />
<br />
$ chmod -R 770 limesurvey/tmp<br />
<br />
$ chmod -R 770 limesurvey/templates<br />
<br />
$ chmod -R 770 limesurvey/upload </div><br />
<br />
===Setting file permissions on a hosted webserver===<br />
<br />
Giving a standard procedure to secure a web application on a hosted environment is rather difficult because hosted environments differ in so many ways.<br />
<br />
As in the managed server case, for the script to work properly it needs write access to some directories:<br />
*The "/limesurvey/tmp" directory is used for import-uploads and should be set to ''Read & Write'' for your webserver.<br />
*You should also set ''Read & Write'' for your webserver for the "limesurvey/template" directory and its sub-directories and files if you want to be able to edit and copy templates.<br />
*The upload/ directory and all its sub directories must also have ''Read & Write'' for your webserver in order to enable picture and media files upload.<br />
* The other directories and files should be set to ''Read Only''<br />
<br />
<div class="simplebox">[[File:help.png]] '''Hint:'''<br />
* Depending on your webserver configuration you will have to chmod the rights on the writable folders to 755 or 777 to make it writable for the webserver. Try 755 first - if it does not work 'upgrade' to 777.<br />
* You can also try to remove read access to config.php to others by setting this file's permissions to 750 - if it does not work 'upgrade' to 755.</div><br />
<br />
==Windows file permissions==<br />
<br />
If you are using a windows server your should ensure that the admin folder allows the owner of the webserver process to write files to this directory, however all other files can be set to read-only and execute.<br />
<br />
==.htaccess files==<br />
<br />
For additionally security protect sensitive directories, such as /admin/*, with .htaccess files. For example you could restrict access to a certain IP Address range.<br />
<br />
==Other security issues==<br />
<br />
The config.php file contains a user name and password for your database server. This poses certain security issues, particularly if you are using a login that has high level administrative access to your database. In the event of some error returning the content of this php file to a user's browser, your database password and other details could be compromised. One way to minimize risk (a little) is set up a specific login that only has specific rights to your limesurvey database.<br />
<br />
A better way to secure this information is to put the config.php file in a non-web directory, i.e. for Apache users this is the directory above the htdocs (aka public_html or www) folder. Begin by copying your working config.php file to the directory above the htdocs directory. Before doing any of these things, back up your files!<br />
<br />
'''NOTE:''' You will need to modify every php file in the survey script, changing the line (that will occur near the top of the file) that reads `include ("config.php");` to the full path of your config.php file (eg: `include("c:/program files/apache group/apache/phpsafe/config.php");`. '''This is NOT tested''' If you give it a try let us know how it goes - please post in the bugtracker or the forums about it! Future versions of LimeSurvey might consider a simpler way to refer to this file. The advantage of this method is that admin changes to your limesurvey installation should automatically change the config.php file.<br />
<br />
Another idea is to continue to use config.php, but have one line in it - a line that includes the file with ACTUAL configuration information (ex: <?php include("/home/hostfolder/safedata/configreal.php"); ?>). Remove all actual configuration information from config.php, and paste it into the other file (configreal.php) that is included by config.php. This other file should be located in a non-Web directory. Then config.php will not contain database passwords, etc. - just the name of the file that DOES contain the database info. This avoids having to change all the other files that include config.php, since they can still include it, and it will include the real config information. You'll also will need to fillout the $rootdir value in your realconfig.php file. For example: $rootdir = '/home/hostfolder/public_html/limesurvey';<br />
<br />
''I see in the paragraph above that feeback is requested. I did not try changing ALL php files, but I DID implement the method in this paragraph, of having the config.php file just include another file, which contains the config information. This did work.''<br />
<br />
Don't use "admin" as the default user. Go to your MySQL database (or other one if you installed LimeSurvey on different database) and change default user name "admin" to whatever you prefer (e.g. "admin_xyz"). It will be now much harder to guess administrator's new user name. Remember, this is one of the two variables intruders can use to gain access. The admin password is the other variable. So choose it with extreme care.</div>Anonymoushttps://manual.limesurvey.org/index.php?title=SGQA_identifier&diff=2995SGQA identifier2009-05-19T14:51:55Z<p>Anonymous: </p>
<hr />
<div><br />
__TOC__<br />
<br />
<div class="simplebox">'''Hint:''' This page describes how you can find out an SQGA identifier. For information how to use it please refer to the page [[Adding a question]]. </div><br />
<br />
=General Description=<br />
<br />
The SGQA (Survey/Group/Question/Answer) identifier is a shortcut to the answer of a question. Every survey, group and question you are creating gets a unique number assigned in your database. You can see this number in the admin interface in the title of the survey, group and question bar.<br />
<br />
<center>[[File:SGQA.png]]</center><br />
<br />
To determine the SGQA identifier, you have to put these numbers together with the letter 'X' in between.<br />
<br />
<div class="simplebox">'''Note:''' Always use capital letters ("X" instead of "x")!</div><br />
<br />
=Identifier for Single Choice Questions=<br />
<br />
For example: Survey has ID 1, Group has ID 6, Question has ID 12. Your identifier for a single choice question would look like this:<br />
<br />
1X6X12<br />
<br />
=Identifier for Single Choice Questions using Label Sets=<br />
<br />
Since it is a single choice question using a label set the particular answer from the label set must be identified too. Just add the code of that label without an X. For example: Survey has ID 1, Group has ID 6, Question has ID 12. The particular label has code 'lab1'<br />
<br />
Your identifier for a Single Choice question answer would look like this:<br />
<br />
1X6X12lab1<br />
<br />
=Identifier for Multiple Choice Questions=<br />
<br />
Since it is a multiple choice question the particular answer must be identified too. Just add the code of that answer without an X. For example: Survey has ID 1, Group has ID 6, Question has ID 12. The particular answer has code 'ber1'.<br />
<br />
Your identifier for this multiple choice question answer would look like this:<br />
<br />
1X6X12ber1<br />
<br />
=Identifier for "Array (Multi Flexible)" text or number Questions=<br />
<br />
Since it is a combined array question the particular answer within the cell must be identified too. Add the answer code of the row without an X, then append the underscore char and finally add the label code that indentify the column. For example: Survey has ID 1, Group has ID 6, Question has ID 12. The particular answer has code 'ber1', and the column is identified by the label with code 'lab1'<br />
<br />
Your identifier for this Array (Multi Flexible) question answer would look like this:<br />
<br />
1X6X12ber1_lab1<br />
<br />
=Uses of the SGQA identifier=<br />
<br />
The SGQA identifier can be used to load the answers to previously saved questions into the question text of later questions. (See [[Adding a question]] - Information from previous answers)<br />
<br />
It can also be used in the query URL of a survey to "prefill" answers to a survey. eg: for SGQA 1X6X121ab1, your query URL could include "&1X6X121ab1=Y" to prefill that answer with a "Y". (See workarounds -> [http://docs.limesurvey.org/tiki-index.php?page=Workarounds#Prefilling_survey_answers_using_the_survey_URL Prefilling survey answers using the survey URL])<br />
<br />
The SGQA identifier is also the field name where the data for each question is stored in the database survey responses table.</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Surveys_-_introduction&diff=4143Surveys - introduction2009-05-17T20:43:14Z<p>Anonymous: </p>
<hr />
<div><br />
__TOC__<br />
<br />
=Video tutorial=<br />
<br />
<div class="simplebox">This video tutorial was made available to us by Andreas Pursche ([http://www.paul-consultants.de/ PAUL Consultants e.V.] of University of Technology Dresden). Therefore all interface components use German language. The english translation was done by user [http://docs.limesurvey.org/tiki-index.php?page=UserPage%20Mazi "Mazi"].<br />
<br />
<center><br/>'''[[LimeSurvey Video-Tutorial]]''' <br/></center></div><br />
<br />
=Basic survey elements=<br />
<br />
A '''survey''' has three integral elements, each of which must exist:<br />
*A survey name<br />
*At least one group<br />
*At least one [[Question types|question]]<br />
<br />
Optional elements to a new '''survey''' include:<br />
*Applicable answers to each question<br />
*Modifiable labels (known as label sets)<br />
*Conditions that determine whether a question should be asked<br />
<br />
==Survey name==<br />
<br />
The '''survey name''' provides the unique title to a '''survey''' and becomes the handle to access various option settings that apply to the survey as a whole. Settings such as the welcome message on the opening screen, the description of the survey, contact information for the survey administrator, and what format the questions are to be asked.<br />
<br />
==Question Groups==<br />
<br />
A '''survey''' requires each question to be a member of a '''group''' (and only that '''group'''). Depending on the number of questions in the survey, '''Groups''' can be used to define logical sections, common subject themes, or possibly pages on the screen. A group can have questions about a similar subject or simply be setup as a manageable number of questions.<br />
<br />
<div class="simplebox">'''Note''':<br/>This whole chapter deals with '''question groups'''. Do not confuse a '''question group''' with a '''user group'''. Each is very different and used in different ways, based on the object being grouped.</div><br />
<br />
A question '''group''' has a title and an optional description. You must have at least one '''group''' in each survey, even if you do not wish to divide the survey into multiple groups.<br />
<br />
==Questions==<br />
<br />
'''Questions''' are the core of your survey. There is no real limit to the number of '''questions''' you can have in your '''survey''' or in a '''group'''. '''Questions''' include the actual question text as well as settings that determine what form of answer you will accept. You can also specify a short 'help' explanation for each question and determine whether the question is mandatory (that is, must be answered) or optional. For more details check the [[Question types|question types]] section.<br />
<br />
=Basics of navigating the survey administrative interface=<br />
<br />
The '''LimeSurvey''' tool presents horizontal tool bars to the survey creator in their web browser. These toolbars are the header of a window allowing interaction.<br />
<br />
==Administrative Tool Bar==<br />
<br />
The top toolbar is usually the '''Administrative Tool Bar''' providing top level, global actions. One of the key items there is the drop down list of surveys along with a '''Create New (Survey)''' button; if available and enabled for your login account. Both are on the right side of the toolbar.<br />
<br />
[[File:SystemAdmin.png]]<br />
<br />
<div class="simplebox">'''Hint''':<br/>Want to know more about a particular icon button in a tool bar? Hover over the icon to see its name or click on the Help button [[File:help-button.png]] in the '''Administrative Tool Bar''' to see a description of icons in the currently active toolbar.</div><br />
<br />
If the '''Administrative Tool Bar''' does not appear to be on top, click the home button [[File:button-home.png]] to get back to it. The Labelset [[File:button-labelset.png]] and Template [[File:button-template-editor.png]] editors, available in this tool bar, are the only ones that can replace the '''Administrative Tool Bar'''.<br />
<br />
By clicking the '''Create New (Survey)''' button [[File:CreateSurvey-button.png]] or selecting an existing survey, you minimize the Administrative window and open a new tool bar below to manage the '''Survey'''.<br />
<br />
[[File:GroupToolbarSmall.png]]<br />
<br />
==Survey Tool Bar==<br />
<br />
Similar to before, one can click on the drop down list of question '''Groups''' or on the '''Create New (Group)''' button [[File:CreateSurvey-button.png]] on the '''Survey''' toolbar. Either selection will bring up the question '''Group''' toolbar below the '''Survey''' toolbar.<br />
<br />
[[File:SurveyToolbarSelectGroupSmall.png]]<br />
<br />
==Group Tool Bar==<br />
<br />
In the Question Group, you can click on the drop down list of '''Questions''' or click the '''Create New (Question)''' button [[File:CreateSurvey-button.png]] to add a fourth toolbar to now edit a '''Question'''.<br />
<br />
[[File:GroupToolbarSelectQuestion.png]]<br />
<br />
==Common Buttons==<br />
<br />
In these nested toolbars are some common, navigational buttons. There is an '''Edit''' button [[File:edit-button.png]] to edit the object you selected. By default, you will be put in the editor if you create the object. There is a '''Delete''' button [[File:delete-button.png]] to delete the object. For '''Groups''' and '''Questions''', there is a '''Reorder''' button [[File:change-order-button.png]] to change the order the object appears in during the survey execution. Finally, there is an '''Export''' button [[File:export-button.png]] to export a survey, question group or question that you can import back into another survey. Note that the '''Create''' button [[File:CreateSurvey-button.png]] also allows you to import a previously exported object.<br />
<br />
[[File:QuestionToolbar.png]]<br />
<br />
Finally, there are two to three small buttons to the far right [[File:CommonButtons.png]] to minimize, maximize, and close the window of a toolbar. The maximize button will take you back to the summary window of the currently selected object.<br />
<br />
As seems natural, the window of the current toolbar is automatically minimized when you select a lower level object to edit. Only the current toolbar and its window can be closed. You can open a previous toolbar and window by clicking on its maximize button. And you can jump around by selecting or creating a new object in another toolbar without having to close the currently open window first.<br />
<br />
We will discuss navigating through a survey itself later on in the section on testing the survey.<br />
<br />
Now that we have some basics down, lets move onto [[Creating a new survey]]</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Other_Online_Surveys_and_Interface_Examples&diff=2389Other Online Surveys and Interface Examples2009-05-09T12:01:30Z<p>Anonymous: </p>
<hr />
<div><br />
A few examples of surveys input and reports:<br />
<br />
LS2 needs to be first an uber-simple survey service like:<br />
<br />
http://polldaddy.com/<br />
<br />
... that people then grow into when they have more complicated surveys to conduct.<br />
<br />
WuFoo: a la BaseCamp, online form generation<br />
<br />
http://wufoo.com/examples/<br />
<br />
An example of SurveyMonkey statistics:<br />
<br />
http://wac.osu.edu/workshops/survey_of_surveys/img/survey_gizmo_stats.jpg<br />
<br />
A great approach for data visualisation:<br />
<br />
http://www.gapminder.org/video/talks/ted-2007---the-seemingly-impossible-is-possible.html<br />
<br />
More Gapminder Examples:<br />
<br />
- Google Spreadsheet: http://spreadsheets.google.com/pub?key=pCQbetd-CptE1ZQeQk8LoNw<br />
<br />
- Motion Chart: http://www.gapminder.org/blog/gapminder-foundation-blog/google-announces-motion-chart.html<br />
<br />
- More Charts: http://www.ted.com/index.php/talks/view/id/92<br />
<br />
Obsurvey: some interesting tidbits:<br />
<br />
http://www.obsurvey.com/<br />
<br />
'''Polldaddy and Wufoo is our competition.'''<br />
<br />
Uber Swanky Form input page w/Ajaxy roll-up goodness<br />
<br />
http://www.wishlistr.se/skapakonto/<br />
<br />
Comparing Mac Minis (the home page is worth a look too)<br />
<br />
http://www.primatelabs.ca/blog/2007/08/mac-mini-performance-august-2007/<br />
<br />
SAT-style (not the best designed) feedback form<br />
<br />
http://adcweb.apple.com/survey/<br />
<br />
Basic feedback forms for Apple products<br />
<br />
http://www.apple.com/feedback/macpro.html<br />
<br />
http://www.apple.com/feedback/ipod.html<br />
<br />
Pownce&rsquo;s signup w/inline help<br />
<br />
http://www.pownce.com/signup/<br />
<br />
Fantastic Search Interface<br />
<br />
http://www.luckyoliver.com/<br />
<br />
Form Design Primer<br />
<br />
http://www.adobe.com/devnet/livecycle/articles/graph_effective_form_design.html<br />
<br />
http://www.adobe.com/devnet/livecycle/articles/graph_effective_form_design_pt2.html<br />
<br />
http://www.adobe.com/devnet/livecycle/articles/graph_effective_form_design_pt3.html<br />
<br />
Dynamic help in forms article (a few good points)<br />
<br />
http://www.uxmatters.com/MT/archives/000191.php<br />
<br />
List Apart on Form Usability<br />
<br />
http://www.alistapart.com/articles/sensibleforms<br />
<br />
.......Extraneous UI examples.......<br />
<br />
I&rsquo;m not a huge fan of the UI, but some elements are slick. See the QT movie.<br />
<br />
http://joyent.com/connector/collaboration-suite<br />
<br />
Nice RT &lsquo;customization&rsquo;<br />
<br />
http://www.swfir.com/<br />
<br />
Adobe 'Form Follows Function' walkthru<br />
<br />
http://www.adobe.com/cfusion/xd/inspire/index.cfm<br />
<br />
Let&rsquo;s continue to grow this example list.</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Survey_security_settings&diff=3311Survey security settings2009-05-06T05:43:31Z<p>Anonymous: </p>
<hr />
<div><br />
From this screen you can add other users/groups who may have access to your survey. After adding a group/user you can assign the following special rights:<br />
<br />
=Edit survey properties=<br />
*Edit Current Survey<br />
*Set Assessment rules<br />
*Initialize and Manage Tokens<br />
<br />
=Define questions=<br />
*Add/Edit/Remove Groups<br />
*Add/Edit/Remove Questions<br />
*Add/Edit/Remove Answers<br />
*Add/Remove Conditions<br />
*Copy Question<br />
*Preview Question<br />
<br />
=Browse responses=<br />
*Browse Responses / Responses Management ( No Delete )<br />
*View saved but not submitted responses<br />
*View Tokens<br />
*Data Entry<br />
<br />
=Export=<br />
*Export Survey Structure<br />
*Export Groups<br />
*Export Questions<br />
*Export Tokens<br />
*Export Survey Results<br />
<br />
=Delete survey=<br />
*Delete Survey<br />
*Delete Responses<br />
*Activate Survey<br />
*Activate Survey<br />
*Initialize and Manage Tokens</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Label_sets&diff=1847Label sets2009-05-02T12:29:55Z<p>Anonymous: </p>
<hr />
<div><br />
=General=<br />
<br />
Label sets are basically lists; each list has a set of codes and a set of labels and can be used in multiple choice answers in a variety of ways. Your question must be of type "flexible labels" to assign a label set to it. More details are provided in the [[Question types]] page.<br />
<br />
<div class="simplebox">'''Hint:''' A label set must be at least contain the same base language as the survey, else you will not be able to use it for any question of your survey.</div><br />
<br />
An example of label set is as follows. If one wants to define a custom 7-points Likert scales, a label set provides this function. In this example, a very simple custom label set with the code/label pairs is shown. Note that the label is what appears in the actual questions.<br />
<br />
{|<br />
|'''code'''||'''label'''<br />
|-<br />
|1||not useful at all<br />
|-<br />
|2||2<br />
|-<br />
|3||3<br />
|-<br />
|4||somewhat useful<br />
|-<br />
|5||5<br />
|-<br />
|6||6<br />
|-<br />
|7||very useful<br />
|}<br />
<br />
Another graphical example:<br />
<br />
Graphic (3 different smileys) instead of label text:<br />
<br />
[[File:3xSmiley-Question.gif]]<br />
<br />
===How to.===<br />
<br />
Click on the [[File:labels.png]] "Edit/Add Label Sets"-Icon in the Administration-Menu to edit, create, delete, import or export label sets used in the 'flexible' labels questions.<br />
<br />
==='''Add New Label Set:'''===<br />
*'''Set Name:''' Each new label set has to be given a name.<br />
*'''Languages:''' Every label set must be specified for the language it's used for. You can choose as many languages from the menu as you want.<br />
<br />
='''Import label set:'''=<br />
*Choose a previous exported label set in a .csv-Format and click on the "Import Label Set"-Button to import. Alternative: import a whole survey - in this case the Label-Sets are imported with the questions.<br />
*To edit a label set outside of LimeSurvey (for instance, using a text editor or Excel), see this tutorial: [[Editing label sets using Microsoft Excel]].<br />
<br />
='''Edit, delete, export label set:'''=<br />
<br />
Choose an already existing label Set in the drop-down-Box in the label set administration bar to edit, delete or export a label set.<br />
*'''Edit label set:''' Here it&acute;s possible to rename the Label Set and add/remove languages for this Label Set.<br />
**To edit a label set outside of LimeSurvey (for instance, using a text editor or Excel), see this tutorial: [[Editing label sets using Microsoft Excel]].<br />
*'''Delete label set:''' After a pop-up, you can delete the selected Label Set.<br />
*'''Export label set:''' Export current Label Set to a .csv-File.<br />
*'''Labels bar:'''<br />
<br />
+To add a new label you have to fill in a label code, assessment value and label-text and press on the "Add new label"-Button. After this the label should be listed above. It's possible to use a graphic instead of or additionally to a label text. Just use HTML-code to include the graphic you want, e.g.:<br />
<br />
<syntaxhighlight lang="php" enclose="div"><br />
<br />
<img border="0" src="http://www.yourdomain.at/pics/pic.gif"><br />
<br />
</syntaxhighlight><br />
<br />
If your label set has more than one language, you can choose which language you want to edit. Every label needs a code, an assessment value and a title. The code can only be changed in the base language of the Label Set. The assessment value can be ignored (set it to 0) if you do not use [[Assessments|assessments]]. The title is the text, which is displayed in the question.<br />
*'''Del-button''': You can delete labels with the "Del"-button.<br />
*'''Up/down-buttons''': It's possible to change the row of labels by the "Up" and "Dn"-buttons.<br />
*'''Fix sort''': You can check the consistency and do a sort of the labels by pressing the "Fix Sort"-Button.<br />
<br />
Labels which are in use by questions are hyperlinked to the question.<br />
<br />
<div class="simplebox">(:idea:) '''Hint:''' The order of the labels can be modified by editing the label-set, however it is not possible to add new labels once the label-set is in use with question of an active survey.</div><br />
<br />
<div class="simplebox">(:idea:) '''Hint:''' Some useful label sets are available on the [http://www.limesurvey.org/component/option,com_remository/Itemid,109/func,select/id,8/lang,fr/ limesurvey site]</div><br />
<br />
=Uploaded resources management=<br />
<br />
This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor.<br />
<br />
You can:<br />
* Browse available files<br />
* Export files as a ZIP archive<br />
* Import a ZIP archive of files<br />
<br />
Caution:<br />
* Authorized file extensions are defined in config-defaults.php by your system administrator.<br />
* Files for the survey are in the upload/labels/<lid> sub directory.<br />
** Uploaded files will only be seen while browsing resources on this survey objects (labels) not in other labels or objects (groups, questions, answers).<br />
** However do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who knows the URL to the file.<br />
* Creation of sub directories of the ZIP archive won't work.<br />
* You can't import a ZIP file containing sub directories.</div>Anonymoushttps://manual.limesurvey.org/index.php?title=LimeSurvey-kompatible_Internet-Provider&diff=2137LimeSurvey-kompatible Internet-Provider2009-04-26T13:38:13Z<p>Anonymous: </p>
<hr />
<div><br />
<div class="simplebox">Translation in progress.</div><br />
<br />
These providers have been tested successfully with LimeSurvey. Please add your provider if everything works fine - just don't add a link.<br />
<br />
==&Ouml;sterreich==<br />
* World4you<br />
* CISC, LLC.<br />
<br />
==Deutschland==<br />
* 1&1<br />
* 1blue<br />
* All-incl.com<br />
* alphahosting<br />
* Domainfactory<br />
* EUserv Internet<br />
* gn2-netwerk<br />
* HostEurope<br />
* kesslernet<br />
* NX24 GmbH<br />
* PCB - Tobias Berndt Hosting<br />
* Sysprovide<br />
* Webhostone<br />
* zedat FU Berlin<br />
<br />
==Schweiz==<br />
* Metanet<br />
<br />
==Vereinigtes K&ouml;nigreich/England==<br />
* 1&1<br />
* 2020Media.com<br />
* Centicero (using package Website)<br />
<br />
==USA==<br />
* 1&1<br />
* Dreamhost<br />
* GoDaddy (Using PHP 5.x and MySQL 5.x)<br />
* Host Color<br />
* Web Hosting Buzz</div>Anonymoushttps://manual.limesurvey.org/index.php?title=LS2_Authentication_%26_Permission_Development&diff=2159LS2 Authentication & Permission Development2009-04-22T14:53:56Z<p>Anonymous: </p>
<hr />
<div><br />
=General=<br />
<br />
=Internal Authentication=<br />
<br />
==Login==<br />
<br />
On login a user is authenticated against different authentication mechanism - these authententication mechanisms can be set in his profile - the default authenticaction mechanism for a user is the LS internal one (username/password has stored in the users table) but it can also be set for example to only auth against LDAP. If a user manages to authenticate against one of the allowed mechanisms he/she may log in.<br />
<br />
If a user athenticates the first time against a non-DB authentication mechanism his user is created automatically in the internal DB.<br />
*A non-DB authentication mechanism should be handled like a plugin and should be stored in the /plugins dir. Authentication mechanism plugin names have to start with the letters 'am' (for example: question types have qt)<br />
*There should be a table where a new authentication mechanism is registered and so made usable to the application<br />
*There should be a table which indicates wich user may use which authentication mechanism on login<br />
*The authentication plugin should have a GUI which is able to be shown in the general settings - as a separate tab for each authentication mechanism - the settings dialogue has to be adjusted to load and show the tabs from the authentication plugins automatically.<br />
<br />
=Permission - What areas does a user have access to?=<br />
<br />
LS2 is using CakePHP ACL to determine who gets access to what part of the application.<br />
<br />
Please read up on [http://book.cakephp.org/view/171/Access-Control-Lists CAKE ACL]<br />
<br />
ARO:<br />
*Rights can be assigned to groups and users<br />
*Alias naming convention for ARO groups: <groupname> model:group<br />
*Alias naming convention for ARO users: user::<User ID> model:user<br />
<br />
ACO:<br />
*Naming convention for ACO application function groups (define areas of the application): a<application area><br />
*Naming convention for ACO application single function (define a certain function of the application): s<function name><br />
<br />
=User Security Groups=<br />
<br />
Restrictions are posed by ACL (see above)<br />
*Security Groups (can) have a single parent<br />
<br />
Basic groups defined when installing the application:<br />
*Admins:<br />
<br />
+Complete system access using a super-admin right<br />
*Users:<br />
<br />
+Can login (if the 'canlogin' field in the users table is set to true), can take assigned surveys.<br />
*Custom groups:<br />
<br />
+ACL allows to create new groups with custom rights.<br />
<br />
=Permission GUI=<br />
<br />
There has to be a GUI created to explicetly change permissions of a security group or create/delete these.<br />
<br />
=Permission areas=<br />
<br />
The application has to be logically separated into permission areas, optionally with fine-grained read/write/... permissions.<br />
<br />
=Permission & Authentication=<br />
<br />
Some authenticaction mechanism also provide permission data. In a first step this should not be considered</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Localization&diff=2150Localization2009-04-16T15:32:47Z<p>Anonymous: </p>
<hr />
<div><br />
{maketoc title="On this page:"}<br />
<br />
There are two places where language specific localization are defined and stored.<br />
<br />
One is in the Installation directory where built-in messages to the PHP code are stored in language specific files. These must be translated and installed by the system administrator before that language is available for the administrative interface and for some basic buttons and built-in messages seen by survey participants. Normally, a survey developer would not have access to edit but only select these translations.<br />
<br />
The other source of language specific localization is in the survey's themselves. These translations for each survey consist of the survey title, overview, and each group, question, answer and labelset text. All these translations are stored in the SQL database tables themselves. Normally, a survey developer must define all the desired translations beyond the base language.<br />
<br />
=== Languages for administration interface and built-in messages for survey participants===<br />
<br />
The public survey screens and the admin interface can be localized so that built-in messages and text will appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the Deutsch/German version. Limesurvey has about 50 different languages of built-in messages already translated. To see the translation status for these languages please follow the link:<br />
<br />
[http://www.limesurvey.org/component/option,com_wrapper/Itemid,79/lang,en/ Translations Status]<br />
<br />
You can create/update your own translation locally by using these instructions:<br />
<br />
[[How to translate LimeSurvey]]<br />
<br />
If you do modify or create a new translation, please consider contributing it for future releases. Also, if you do modify or create a new translation, remember to take care of this when upgrade to a newer version later.<br />
<br />
<div class="simplebox">'''Note:''' The template files are not currently localized and thus are language independent. Try to avoid putting text directly into the template files. Instead, define the necessary language in other files that are localized.</div><br />
<br />
So far we only discussed translating the built-in text of the administration interface that the survey participants and developers see; that part that is independent of any survey. Each survey can have one or more languages associated with it as well independent of this interface. So care must be taken to offer the appropriate translations there as well.<br />
<br />
=== Languages for surveys themselves===<br />
<br />
If more than one language is defined for a survey, then when editing that survey or each question, answer or labelset within it -- you then need to make sure to add all the language translations desired. Otherwise, the default language of the survey will appear if no translation is available. This is available when editing a Survey, Group, Question, Answer set or labelset.<br />
<br />
<div class="simplebox">'''Note:''' If you do not have permission to edit labelsets, you will not be able to provide the translation of that labelset either. Talk to your survey administrator about either giving you the permission to edit the labelset or providing the translation in your desired language.</div></div>Anonymoushttps://manual.limesurvey.org/index.php?title=Instalacja&diff=1572Instalacja2009-03-23T18:00:06Z<p>Anonymous: </p>
<hr />
<div><br />
Spis treści:__TOC__<br />
<br />
===1. Upewnij się, że posiadasz odpowiednie środowisko pracy dla LimeSurvey===<br />
<br />
Sprawdź ustawienia swojego serwera pod kątem następujących wymagań::<br />
<br />
Wymagania:<br />
* Około 40 megabajt&oacute;w miejsca na dysku dla skrypt&oacute;w<br />
* język PHP w wersji 4.3.2 lub nowszej '''albo''' PHP w wersji 5.x lub nowszej z zainstalowanymi rozszerzeniami:<br />
** mbstring (dla lokalizacji), zobacz także [[Installation FAQ]];<br />
** mysql4 lub mysql5 lub odbc_mssql lub pgsql - zależnie od bazy danych, kt&oacute;rej używasz (do komunikacji z bazą danych);<br />
** session (sesje), zobacz [http://de2.php.net/manual/en/session.installation.php PHP Session Documentation];<br />
** pcre (wyrażenia regularne), zobacz [http://de2.php.net/manual/en/book.pcre.php PHP PCRE Documentation].<br />
<br />
Opcjonalnie zainstalowane rozszerzenia PHP:<br />
* gd (dla zabezpieczeń CAPCHA w formularzach) zobacz [http://de3.php.net/manual/en/ref.image.php PHP GD Documentation]<br />
* ldap(wykorzystywana do importu token&oacute;w przy użyciu LDAP) zobacz [http://de.php.net/manual/en/ref.ldap.php PHP LDAP Documentation]<br />
* iconv (tylko dla PHP 4 - niezbędne przy eksporcie do Excel-a)<br />
<br />
W ogromnej większości przypadk&oacute;w Tw&oacute;j dostawca hostingu jest w stanie zapewnić Ci takie ustawienia.<br />
<br />
===2. Pobierz pakiet LimeSurvey===<br />
<br />
[http://sourceforge.net/projects/limesurvey/ Pobierz] najnowszą wersję LimeSurvey w preferowanym formacie (zip, 7-zip, tar.gz lub tzr.bz2) i zapisz go na swoim dysku. Paczka zajmuje ok 15 MB.<br />
<br />
===3. Rozpakuj pakiet LimeSurvey===<br />
<br />
Rozpakuj uprzednio zapisane archiwum. Upewnij się, że rozpakowane archiwum zachowało oryginalną struktura katalog&oacute;w i plik&oacute;w (ustawienie domyślne większości archiwizator&oacute;w).<br />
<br />
===4. Zbierz informacje o swoim serwerze===<br />
<br />
Potrzebujesz poniższych informacji aby poprawnie zainstalować skrypt LimeSurvey na swoim serwerze.<br />
*Adres URL swojej strony, na kt&oacute;rej ma działać LimeSurvey (np.: 'http://www.twoja.strona.pl/limesurvey');<br />
*Adres dostępu do serwera obsługującego bazę danych (np: 'localhost' lub 'mysql.tw&oacute;j-provider.pl');<br />
**Jeśli baza danych wymaga dostępu na niestandardowym porcie, dowiedz sę jaki to port;<br />
*Nazwę użytkownika oraz jego hasło dostępu do serwera bazy danych'<br />
<br />
===5. Skonfiguruj skrypt LimeSurvey===<br />
<br />
Wyedytuj plik config.php znajdujący się w katalogu do kt&oacute;rego zostało rozpakowane LimeSurvey wykorzystując dowolny edytor tekstowy (np.: Notatnik). Wprowadź do niego następujące dane:<br />
<br />
====5.1 Ustawienia podstawowe (wymagane)====<br />
*'''$databasetype:''' Typ wykorzystywanej bazy danych. Obecnie przetestowane to: "mysql" dla MySQL, "odbc_mssql" dla Microsoft SQL, "postgres" dla Postgres SQL.<br />
*'''$databaselocation:''' Adres dostępu do serwera obsługującego bazę. Typowo jest to "localhost".<br />
*'''$databasename:''' Nazwa bazy danych, kt&oacute;ra będzie obsługiwać skrypt LimeSurvey. Jeśli posiadasz prawa do tworzenia baz danych za pomocą skrypt&oacute;w może wpisać dowolną nazwę. W przeciwnym przypadku należy wprowadzić nazwę istniejącej bazy danych. Jeśli wykorzystujesz już istniejącą bazę danych, sprawdź czy nie zawiera ona tabel wykorzystywanych przez wcześniejszą instalację skryptu LimeSurvey.<br />
*'''$databaseuser:''' Nazwa użytkownika serwera bazy danych.<br />
*'''$databasepass:''' Hasło dostępu do serwera bazy danych.<br />
*'''$dbprefix:''' Możesz pozostawić to pole pustym (np.: $dbprefix="";) jeśli baza danych wykorzystywana będzie tylko do obsługi LimeSurvey. Jeśli chcesz wsp&oacute;łdzielić bazę danych z innymi skryptami, dodaj prefiks np.: "lime_".<br />
*'''$databaseport:''' Jeśli Tw&oacute;j hostingodawca świadczy dostęp do bazy danych na niestandardowym porcie (innym niż "3306" dla MySQL lub "5432" dla Postgre SQL), podaj jego numer w tej opcji.<br />
*'''$rooturl:''' Adres URL Twojej strony internetowej ze skryptem LimeSurvey. Domyślne ustawienie automatycznie wykryje nazwę domeny, dlatego typowo nie trzeba będzie tu nic zmieniać. Jeśli ustawienie domyślne nie działa, sprawdź katalog gł&oacute;wny skryptu i wpisz go po znaku "/" np.: "http://{$_SERVER<nowiki>[</nowiki>'SERVER_NAME']}/limesurvey". Jeśli w dalszym ciągu ustawienie nie działa możesz spr&oacute;bować wprowadzić ręcznie pełną nazwę serwera/domeny np.: "http://www.twoja.strona.pl/limesurvey".<br />
*'''$rootdir:''' Fizyczny adres dostępu do skryptu na serwerze. ustawienie domyślne "dirname(!!!FILE!!!);" spr&oacute;buje automatycznie wykryć ścieżkę dostępu. W przypadku gdyby nie zadziałało, wprowadź ścieżkę ręcznie np.: "/home/użytkownik/public_html/limesurvey".)<br />
*'''$sitename:''' Nazwa serwisu LmeSurvey, jaka będzie się wyświetlać w pasku tytułu przeglądarki WWW.<br />
*'''$siteadminemail:''' Adres administratora serwisu. Adres ten będzie pojawiał się np. w stopkach list&oacute;w wysyłanych przez LimeSurvey.<br />
*'''$siteadminbounce:''' Adres, na kt&oacute;ry odsyłane będą odrzucone wiadomości.<br />
*'''$siteadminname:''' Nazwa administratora serwisu LimeSurvey. Podaj tutaj np. swoje imię i nazwisko lub nazwę firmy.<br />
*'''$defaultlang:''' Domyślny język interfejsu LimeSurvey. Jeśli czytasz to wiki, to prawdopodobnie będzie to 'pl' (:biggrin:)<br />
*'''$defaultuser:''' Login administratora, kt&oacute;rego konto utworzone zostanie przez skrypt instalacyjny.<br />
*'''$defaultpass:''' Hasło administratora, kt&oacute;rego konto utworzone zostanie przez skrypt instalacyjny.<br />
<br />
====5.2 Ustawienia dodatkowe (opcjonalne)====<br />
<br />
Poza wymienionymi w poprzednim punkcie, LimeSurvey udostępnia bardzo dużo innych opcji konfiguracyjnych, kt&oacute;rych zdefiniowanie nie jest jednak konieczne do zainstalowania i uruchomienia LimeSurvey.<br />
<br />
Możesz się z nimi zapoznać [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings tutaj] (strona w języku angielskim).<br />
<br />
===6. Umieść pliki na serwerze.===<br />
<br />
Połącz się ze swoim serwerem www, np. poprzez ftp i utw&oacute;rz na nim odpowiedni katalog (np. 'limesurvey' - w przykładach w dalszej części założymy właśnie taką nazwę). Skopiuj do tego katalogu pliki oraz katalogi LimeSurvey nie zmieniając ich struktury.<br />
<br />
===7. Ustaw prawa dostępu.===<br />
<br />
Dla zapewnienia poprawnego działania LimeSurvey upewnij się, że użytkownik, na kt&oacute;rego prawach wykonywane są skrypty ma prawa odczytu zapisu do katalog&oacute;w: "tmp", "upload" oraz "templates" w katalogu, w kt&oacute;rym umieściłeś LimeSurvey.<br />
* jeśli skrypty wykonywane są na prawach właściciela skryptu, właściwymi prawami dostępu do powyższych katalog&oacute;w będzie, w zapisie Unix-owym, 755 (wszystkie prawa dla właściciela, grupa i pozostali tylko odczyt i wykonanie);<br />
* jeśli skrypty wykonywane są na prawach serwera WWW, właściwymi prawami dostępu do powyższych katalog&oacute;w będzie, w zapisie Unix-owym, 777 (wszyscy mają prawo do odczytu, zapisu i wykonania);<br />
* jeśli nie wiesz, na jakich prawach wykonywane są skrypty na Twoim serwerze, spr&oacute;buj najpierw pierwszego z powyższych ustawień, a dopiero, jeśli ono nie zadziała, drugiego.<br />
<br />
Pozostałym plikom wystarczą prawa do odczytu (Unix-owe 644), a katalogom do odczytu i wykonywania (Unix-owe 755).<br />
<br />
===8. Uruchom skrypt instalacyjny===<br />
<br />
Przejdź na stronę "http://twoja.domena.com/limesurvey/admin/install/index.php". Jeśli wszystko zostało skonfigurowane poprawnie skrypt instalacyjny zapyta Cię o pozwolenie na utworzenie bazy danych i/lub odpowiednich tabel. W niekt&oacute;rych przypadkach, gdy serwery bazodanowe nie pozwalają tworzyć nowych baz poprzez skrypty, będziesz musiał samemu lub za pośrednictwem administratora stworzyć bazę danych, a następnie ponownie wykonać skrypt instalacyjny. Gdy ujrzysz komunikat informujący o poprawnie przeprowadzonej instalacji zmień nazwę lub skasuj katalog instalacyjny ("install").<br />
<br />
Jeśli zamiast prośby o pozwolenie na utworzenie bazy danych wyświetli sie pusta strona lub zostaniesz zalany komunikatami o błędach, dopisz w pliku "config.php" opcję "$translationmode = 1;".<br />
<br />
===9. Zaloguj się jako administrator===<br />
<br />
Wejdź pod adres "http://twoja.domena.com/limesurvey/admin/admin.php" i zaloguj się używając loginu i hasła, jakie zdefiniowałeś uprzednio w pliku "config.php" (domyślnie login "admin" i hasło "password").<br />
<br />
'''Jeśli nie zmieniłeś domyślnych danych w trakcie instalacji zr&oacute;b to teraz, aby nikt niepowołany nie m&oacute;gł zalogować się do panelu administracyjnego.'''<br />
<br />
===9. Co jeśli wystąpią problemy...===<br />
<br />
Autorzy skrypt&oacute;w dołożyli wszelkich starań aby skrypty LimeSurvey działały poprawnie i zgodnie z instrukcjami. Nie można jednak w 100% wykluczyć błęd&oacute;w. Jeśli przytrafi Ci się taka sytuacja i jesteś pewien, że wszystkie ustawienia są poprawne w pierwszej kolejności sprawdź dział często zadawanych pytań nt. instalacji - Instalacja FAQ.<br />
<br />
Jeśli nie znajdziesz tam rozwiązania swojego problemu dokładnie opisz go włączając w to komunikaty błęd&oacute;w i prześlij te informacje autorom skryptu za pomocą [http://www.limesurvey.org/component/option,com_fireboard/Itemid,86/lang,en/ forum LimeSurvey] na limesurvey.org lub sieci IRC (przyłącz się do [irc://irc.freenode.net/limesurvey|kanału IRC LimeSurvey]):<br />
<br />
irc://irc.freenode.net/limesurvey</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Question_groups_-_introduction&diff=4133Question groups - introduction2009-03-14T11:12:52Z<p>Anonymous: </p>
<hr />
<div><br />
Before you can [[Adding a question|add questions]] to your survey you must create a group. Create a new group by clicking on the Add icon [[File:add.png]] in the Survey Button Bar. Alternatively you can import a previously exported group. The import feature does NOT import groups from LimeSurvey (PHPSurveyor) versions older than 1.45.<br />
<br />
If you have only one group in your survey then the name of this group is irrelevant (except of course for display). If, however, you are going to have multiple groups, you should note that the survey questions will be displayed by group (depending on the setting in the survey settings). Use the group re-ordering feature to display the groups in a particular order.<br />
<br />
You can create as many groups as you like.<br />
<br />
Groups can also include a "description". This field allows you to publish an explanatory note for any set of questions. If you add a description, then when the public are using the public survey system, they will be presented with that explanation before commencing any of the questions in that group. If you do not include any text here, then public participants will simply move on to the first question in the group with no stop. Use the HTML editor to include images, formatted text, etc. to your liking.</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Survey_status_screen&diff=3314Survey status screen2009-02-28T21:59:21Z<p>Anonymous: </p>
<hr />
<div><br />
In the administration bar you can choose a survey and then some status information for this survey gets displayed.<br />
<br />
Most of the displayed items are rather self-explanatory and are the settings and information set when "Creating a new Survey" or "Edit Current Survey".<br />
<br />
The following information is displayed:<br />
#'''Title:''' The title of the survey, followed by the unique Survey-ID.<br />
#'''Survey URL:''' This is the URL to access the survey in/from the internet, looks like: http://www.yourdomain.com/limesurvey/index.php?sid=xxx&lang;=yy <br/>xxx is your Survey-ID.<br/>yy is the language code for the survey.<br/>When you use tokens, then you have to add "&token;=zzz" at the end of your URL. zzz is the token.<br />
#'''Description:''' A description to the survey.<br />
#'''Welcome:''' The text, which is displayed on the welcome page.<br />
#'''Administrator:''' The name of the administrator, followed by the email-address of the administrator.<br />
#'''Fax To:''' The fax number for this survey.<br />
#'''Start Date:''' The date the survey starts if "Timed Start" is set to Yes.<br />
#'''Expiry Date:''' If an expire-date is set, it will be shown here.<br />
#'''Template:''' The template, which is used for this survey.<br />
#'''Base Language:''' The main language for this survey.<br />
#'''Additional Languages:''' Translated languages which are in use for this survey.<br />
#'''Exit Link:''' This is the link of the End-ur<x>l, which is displayed or directly loaded when a survey is successfully submitted.<br />
#'''Number of questions/groups:''' Shows the number of questions and groups in your survey.<br />
#'''Survey currently active:''' Shows the status of your survey - active or not active.<br />
#'''Survey table name:''' If the survey is active, the table name of the survey in the database is shown.<br />
#'''Hints:'''<br />
*Answers are anonymous or not.<br />
*Format of the survey: Question by Question, Group by Group or All in one.<br />
*Responses are datestamped or not.<br />
*IP Address will be logged or not.<br />
*Referrer-URL will be saved or not.<br />
*Allow saves turned on or off.<br />
*Email notification turned on or off.<br />
*Regenerate Question Codes:<br />
**Straight: Every Question gets a new question code. First question gets 001, second question 002, third question 003,... (Group classification is ignored).<br />
**By Group: Every Question gets a new question code. First question in each group gets 001, second question in each group 002, third question in each group 003,...</div>Anonymoushttps://manual.limesurvey.org/index.php?title=R%C3%A9glages_de_s%C3%A9curit%C3%A9_d%27un_questionnaire&diff=2895Réglages de sécurité d'un questionnaire2008-12-17T10:52:27Z<p>Anonymous: </p>
<hr />
<div><br />
Depuis cet &eacute;cran vous pouvez ajouter des utilisateurs ou des groupes qui peuvent acc&eacute;der &agrave; votre questionnaire.<br />
<br />
Un questionnaire appartient uniquement &agrave; l'utilisateur qui l'a cr&eacute;&eacute;. Cependant, cet utilisateur peut d&eacute;l&eacute;guer un certains nombre de droits &agrave; d'autres utilisateurs/groupes.<br />
<br />
Seul un utilisateur disposant d'un profil "Super Administrateur" peut avoir une vue d'ensemble de tous les questionnaires cr&eacute;&eacute;s par les autres utilisateurs. Il est donc impossible pour un administrateur de voir les questionnaires cr&eacute;&eacute;s par les autres administrateurs.<br />
<br />
Pour autoriser un utilisateur &agrave; modifier les &eacute;l&eacute;ments d'un questionnaire, la d&eacute;marche est la suivante :<br />
<br />
S&eacute;lection du questionnaire -> Param&egrave;tre de s&eacute;curit&eacute; du questionnaire -> S&eacute;lection d'un Utilisateur ou d'un groupe -> ajout -> d&eacute;finition des droits de l'utilisateur -> fin<br />
<br />
Apr&egrave;s avoir ajout&eacute; un groupe ou un utilisateur vous pouvez leur assigner des droits particuliers:<br />
*&Eacute;diter les propri&eacute;t&eacute;s du questionnaire<br />
**Editer le questionnaire courant<br />
**D&eacute;finir des r&egrave;gles d'&eacute;valuation<br />
**Initialiser et g&eacute;rer les invitations<br />
*D&eacute;finir des questions<br />
**Ajouter/Editer/Supprimer des Groupes de questions<br />
**Ajouter/Editer/Supprimer des Questions<br />
**Ajouter/Editer/Supprimer des R&eacute;ponses<br />
**Ajouter/Supprimer des Conditions<br />
**Copier des Questions<br />
**Afficher un aper&ccedil;u des Questions<br />
*Parcourir les R&eacute;ponses<br />
**Parcourir les R&eacute;ponses / Gestion des R&eacute;ponses (Pas de suppression)<br />
**Visualiser les r&eacute;ponses sauv&eacute;es mais non soumises<br />
**Visualiser les Invitations<br />
**Saisie manuelle de r&eacute;ponses au questionnaire<br />
*Exporter<br />
**Exporter les questionnaires<br />
**Exporter les Groupes<br />
**Exporter les Questions<br />
**Exporter les Invitations<br />
**Exporter les R&eacute;ponses du questionnaire<br />
*Supprimer un questionnaire<br />
**Supprimer un questionnaire<br />
**Supprimer les r&eacute;ponses<br />
*Activer un questionnaire<br />
**Activer un questionnaire<br />
**Initialiser et g&eacute;rer les Invitations<br />
<br />
Pour supprimer des autorisations, la d&eacute;marche est sensiblement identique &agrave; celle d'ajout de droit :<br />
<br />
S&eacute;lection du questionnaire -> Param&egrave;tre de s&eacute;curit&eacute; du questionnaire -> S&eacute;lection d'un Utilisateur ou d'un groupe &agrave; modifier/supprimer -> fin<br />
<br />
Bien entendu, la gestion des droits utilisateur ne s'applique qu'aux versions de LimeSurvey sup&eacute;rieure &agrave; la 1.0.</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Manage_user_groups&diff=2161Manage user groups2008-12-15T19:47:17Z<p>Anonymous: </p>
<hr />
<div><br />
If you click on the '''Create / Edit Groups''' Icon [[File:usergroup.png]] (aka Group Security) in the main administration menu bar at the top, you are taken to the '''User Group''' management sub-screen.<br />
<br />
<div class="simplebox">'''Note:'''<br/>'''User Groups''' are limited in functionality at the moment. There are no real rights bound to a group. Groups serve more as a macro or textual convenience to work with groups of Users.</div><br />
<br />
There are two main functions associated with '''User Groups''' currently.<br />
<br />
A '''User Group''' can be used as the target to send an email. So it is convenient to add all administrative users associated with a survey to a group. Access to send an email is on the '''Create / Edit Groups''' menu once you select the group of interest there.<br />
<br />
A '''User Group''' can be the target of '''Survey Security Settings''' when in a Survey. When in a Survey, click on the '''Survey Security''' icon. Once there, you can add either individual '''Users''' or user '''Groups'''. You add a '''User''' so you can then give them specific privileges in that given survey. Privileges like editing the questions, activating the survey, and maybe viewing the responses; among others. Adding a '''User Group''' behaves like a macro function that simply adds all the current members of the '''User Group''' with the same privileges at that same time to the '''Survey'''.<br />
<br />
<div class="simplebox">'''Note:'''<br/> Changes to a '''User Group''' after adding them in the '''Survey''' will not cause changes to the '''Survey Security Settings'''. The '''User Group''' members are only looked at when you add the '''User Group''' to the '''Survey Security Settings'''.</div></div>Anonymoushttps://manual.limesurvey.org/index.php?title=Running_a_survey_safely&diff=2960Running a survey safely2008-11-12T16:08:24Z<p>Anonymous: </p>
<hr />
<div><br />
<br/>Once you have activated a survey and are receiving responses it is worthwhile considering the following:<br />
*Export the survey structure ([[File:exportcsv.png]]) immediately and save the .csv file on a safe place.<br />
*Regularly visit the "browse" screen ([[File:browse.png]])and export the received responses and keep a copy of the file.<br />
*Try not to make changes to the survey. There are some parts of the survey that can still be changed after it has been activated, and while these shouldn't cause problems, it's better safe than sorry. Fully test your survey before you activate it and then try to leave it exactly as it is.<br />
*If you have access to phpMyAdmin or a similar facility, try making regular backups of the entire LimeSurvey database (structure and data). If the worst happens and the whole database disappears, you could re-create the database and import the backed-up tables, and LimeSurvey will likely be able to pick up where it left off.</div>Anonymoushttps://manual.limesurvey.org/index.php?title=LimeSurvey_1.x_navigating_the_source_code&diff=1870LimeSurvey 1.x navigating the source code2008-09-24T13:13:20Z<p>Anonymous: </p>
<hr />
<div><br />
After downloading the source code via SVN [[(See: Accessing the Source Code]]) you see the following directories:<br />
<br />
====Source====<br />
<br />
====/limesurvey====<br />
<br />
This is the current stable branch of LimeSurvey v1.70+ and contains the latest hotfixes and translation updates.<br />
<br />
====/original art====<br />
<br />
This is the directory with the original arts used in LimeSurvey.<br />
<br />
====/server-scripts====<br />
<br />
In this directory are server scripts which are in use in http://www.limesurvey.org .<br />
<br />
===releases===<br />
<br />
In this directory are the files, as they are delivered in the download package of the according version.<br />
<br />
===Code===<br />
<br />
'''''''''''''''_<br />
<br />
===Translations===<br />
<br />
To translate some text displayed on screen you have to either create a new instance of ''''limesurvey_lang'''' (limesurvey\classes\core\language.php) or in some cirumstances there is already an instance created called ''''$clang''''.<br />
<br />
To translate you call the function '''gT''' ($clang->gT(string))<br />
<br />
In general '''$clang''' is set in (limesurvey\common.php) and uses a number of variables to determine language.<br />
<br />
''s_lang''<br />
<br />
''$baselang''<br />
<br />
''$_SESSION['adminlang']''</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Question_pools&diff=2544Question pools2008-09-15T22:30:49Z<p>Anonymous: </p>
<hr />
<div><br />
Here is a simple solution to create question pools for Limesurvey.<br />
<br />
It will require access to the backend database. I'm not going to explain how to do this, as if you don;t understand it, then you shouldn't really do it. Hopefully an option will appear in a new version.<br />
<br />
Basically 3 tables exist that we care about<br />
<br />
lime_surveys - id field = sid<br />
<br />
lime_groups - id field = gid<br />
<br />
lime_questions id field = qid<br />
<br />
In order to show the questions correctly the id field from the lime_groups table exists in the lime_questions table. This then is used to create the parent/child relationship.<br />
<br />
However, if you want to create a pool of questions all you need to do is to amend the gid field in the LIME_QUESTIONS table to a value that doesn't exist in the lime_groups table. I would use 0 or a something silly like 10000. Try this with one question and you will notice it doesnt appear in the question list.<br />
<br />
It's a crude workaround, but allows you to create as many questions as you want, without having them visible.<br />
<br />
This could also be applied for groups as well just by using the sid field in the lime_groups table.</div>Anonymoushttps://manual.limesurvey.org/index.php?title=Greek_Manual&diff=1402Greek Manual2008-04-17T12:43:45Z<p>Anonymous: </p>
<hr />
<div><br />
&Epsilon;&kappa;&tau;ό&sigmaf; &alpha;&pi;ό &alpha;&upsilon;&tau;ή&nu; &tau;&eta;&nu; online &tau;&epsilon;&kappa;&mu;&eta;&rho;ί&omega;&sigma;&eta; &upsilon;&pi;ά&rho;&chi;&epsilon;&iota; έ&nu;&alpha; &beta;&alpha;&sigma;&iota;&kappa;ό &epsilon;&gamma;&chi;&epsilon;&iota;&rho;ί&delta;&iota;&omicron; &chi;&rho;ή&sigma;&eta;&sigmaf; &sigma;&epsilon; PDF ό&pi;&omicron;&upsilon; &mu;&pi;&omicron;&rho;&epsilon;ί&tau;&epsilon; &nu;&alpha; &tau;&omicron; &kappa;&alpha;&tau;&epsilon;&beta;ά&sigma;&epsilon;&tau;&epsilon; &alpha;&pi;ό &tau;&omicron;&nu; &sigma;ύ&nu;&delta;&epsilon;&sigma;&mu;&omicron; &sigma;&tau;&omicron; &kappa;ά&tau;&omega; &mu;έ&rho;&omicron;&sigmaf; &alpha;&upsilon;&tau;ή&sigmaf; &tau;&eta;&sigmaf; &sigma;&epsilon;&lambda;ί&delta;&alpha;&sigmaf;.<br />
<br />
----<br />
*[[&Epsilon;&gamma;&kappa;&alpha;&tau;ά&sigma;&tau;&alpha;&sigma;&eta;]]<br />
**[[&Alpha;&nu;&alpha;&beta;ά&theta;&mu;&eta;&sigma;&eta; &alpha;&pi;ό &Pi;&rho;&omicron;&eta;&gamma;&omicron;ύ&mu;&epsilon;&nu;&eta; Έ&kappa;&delta;o&sigma;&eta;]]<br />
**[[&Epsilon;&rho;&omega;&tau;ή&sigma;&epsilon;&iota;&sigmaf;/&Alpha;&pi;&alpha;&nu;&tau;ή&sigma;&epsilon;&iota;&sigmaf; &Epsilon;&gamma;&kappa;&alpha;&tau;ά&sigma;&tau;&alpha;&sigma;&eta;&sigmaf;]]<br />
**[[&Omicron;&delta;&eta;&gamma;ό&sigmaf; &Epsilon;&gamma;&kappa;&alpha;&tau;ά&sigma;&tau;&alpha;&sigma;&eta;&sigmaf; &gamma;&iota;&alpha; OS/2 Warp]]<br />
*[[&Theta;έ&mu;&alpha;&tau;&alpha; &Alpha;&sigma;&phi;ά&lambda;&epsilon;&iota;&alpha;&sigmaf;]]<br />
*[[&Delta;&iota;&alpha;&chi;&epsilon;ί&rho;&iota;&sigma;&eta; &Chi;&rho;&eta;&sigma;&tau;ώ&nu;]] / [[&Delta;&iota;&alpha;&chi;&epsilon;ί&rho;&iota;&sigma;&eta; &Omicron;&mu;ά&delta;&omega;&nu;]]<br />
*[[&Delta;&omicron;&mu;ή &kappa;&alpha;&iota; &Sigma;&chi;&epsilon;&delta;&iota;&alpha;&sigma;&mu;ό&sigmaf; Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
*&Delta;&eta;&mu;&iota;&omicron;&upsilon;&rho;&gamma;ί&alpha; &Epsilon;&rho;&epsilon;&upsilon;&nu;ώ&nu;<br />
**[[&Delta;&eta;&mu;&iota;&omicron;&upsilon;&rho;&gamma;ί&alpha; &Nu;έ&alpha;&sigmaf; Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
**[[&Epsilon;&iota;&sigma;&alpha;&gamma;&omega;&gamma;ή Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
**[[&Rho;&upsilon;&theta;&mu;ί&sigma;&epsilon;&iota;&sigmaf; &Alpha;&sigma;&phi;&alpha;&lambda;&epsilon;ί&alpha;&sigmaf; Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
**[[&Delta;&eta;&mu;&iota;&omicron;&upsilon;&rho;&gamma;ί&alpha; &Nu;έ&alpha;&sigmaf; &Omicron;&mu;ά&delta;&alpha;&sigmaf;]]<br />
***[[&Alpha;&lambda;&lambda;&alpha;&gamma;ή &Tau;&alpha;&xi;&iota;&nu;ό&mu;&eta;&sigma;&eta;&sigmaf; &Omicron;&mu;ά&delta;&omega;&nu;]]<br />
**[[&Pi;&rho;&omicron;&sigma;&theta;ή&kappa;&eta; &Epsilon;&rho;ώ&tau;&eta;&sigma;&eta;&sigmaf;]]<br />
***[[&Tau;ύ&pi;&omicron;&iota; &Epsilon;&rho;&omega;&tau;ή&sigma;&epsilon;&omega;&nu;]]<br />
***[[&Iota;&delta;&iota;ό&tau;&eta;&tau;&epsilon;&sigmaf; &Epsilon;&rho;&omega;&tau;ή&sigma;&epsilon;&omega;&nu;]]<br />
***[[&Kappa;&alpha;&theta;&omicron;&rho;&iota;&sigma;&mu;ό&sigmaf; Ό&rho;&omega;&nu;]]<br />
***[[&Tau;&alpha;&xi;&iota;&nu;ό&mu;&eta;&sigma;&eta; &Epsilon;&rho;&omega;&tau;ή&sigma;&epsilon;&omega;&nu;]]<br />
***[[&Pi;&rho;&omicron;&epsilon;&pi;&iota;&sigma;&kappa;ό&pi;&eta;&sigma;&eta; &Epsilon;&rho;ώ&tau;&eta;&sigma;&eta;&sigmaf;]]<br />
***[[&Alpha;&nu;&alpha;&gamma;&nu;&omega;&rho;&iota;&sigma;&tau;&iota;&kappa;ό SGQA]]<br />
**[[&Pi;&rho;&omicron;&sigma;&theta;ή&kappa;&eta; &Alpha;&pi;&alpha;&nu;&tau;ή&sigma;&epsilon;&omega;&nu;]]<br />
*[[&Omicron;&theta;ό&nu;&eta; &Kappa;&alpha;&tau;ά&sigma;&tau;&alpha;&sigma;&eta;&sigmaf; Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
*[[&Delta;&omicron;&kappa;&iota;&mu;ή Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
*[[&Epsilon;&xi;&alpha;&gamma;&omega;&gamma;ή Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
*[[&Kappa;&alpha;&nu;ό&nu;&epsilon;&sigmaf; &Alpha;&xi;&iota;&omicron;&lambda;ό&gamma;&eta;&sigma;&eta;&sigmaf;]]<br />
*[[&Sigma;&chi;&epsilon;&delta;&iota;ό&tau;&upsilon;&pi;&alpha; / &Epsilon;&pi;&epsilon;&xi;&epsilon;&rho;&gamma;&alpha;&sigma;&tau;ή&sigmaf; &Sigma;&chi;&epsilon;&delta;&iota;&omicron;&tau;ύ&pi;&omega;&nu;]]<br />
*[[&Sigma;ύ&nu;&omicron;&lambda;&alpha; &Epsilon;&tau;&iota;&kappa;&epsilon;&tau;ώ&nu;]]<br />
*[[&Pi;&rho;&omicron;&sigma;&alpha;&rho;&mu;&omicron;&gamma;ή]]<br />
*[[&Epsilon;&nu;&epsilon;&rho;&gamma;&omicron;&pi;&omicron;ί&eta;&sigma;&eta; Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
*[[&Alpha;&sigma;&phi;&alpha;&lambda;ή&sigmaf; &Epsilon;&kappa;&tau;έ&lambda;&epsilon;&sigma;&eta; Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
*[[&Epsilon;&xi;&epsilon;&rho;&epsilon;ύ&nu;&eta;&sigma;&eta; &Alpha;&pi;&omicron;&tau;&epsilon;&lambda;&epsilon;&sigma;&mu;ά&tau;&omega;&nu; Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
*[[&Kappa;&lambda;&epsilon;ί&sigma;&iota;&mu;&omicron; Έ&rho;&epsilon;&upsilon;&nu;&alpha;&sigmaf;]]<br />
*[[&Kappa;&omicron;&upsilon;&pi;ό&nu;&iota;&alpha;]]<br />
*[[&Epsilon;&iota;&sigma;&alpha;&gamma;&omega;&gamma;ή &Delta;&epsilon;&delta;&omicron;&mu;έ&nu;&omega;&nu;]]<br />
*[[&Epsilon;&xi;&alpha;&gamma;&omega;&gamma;ή &Alpha;&pi;&omicron;&tau;&epsilon;&lambda;&epsilon;&sigma;&mu;ά&tau;&omega;&nu;]]<br />
*[[&Sigma;&tau;&alpha;&tau;&iota;&sigma;&tau;&iota;&kappa;ά]]<br />
*[[&Sigma;&upsilon;&chi;&nu;έ&sigmaf; &Epsilon;&rho;&omega;&tau;ή&sigma;&epsilon;&iota;&sigmaf;]]<br />
*[[&Pi;&rho;&omicron;&beta;&lambda;ή&mu;&alpha;&tau;&alpha; &kappa;&alpha;&iota; &Lambda;ύ&sigma;&epsilon;&iota;&sigmaf;]]<br />
*[[Ά&delta;&epsilon;&iota;&alpha; &Chi;&rho;ή&sigma;&eta;&sigmaf;]]<br />
*[[&Alpha;&rho;&chi;&epsilon;ί&omicron; &Alpha;&lambda;&lambda;&alpha;&gamma;ώ&nu;]]</div>Anonymous