This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
en:create:debugging [22.09.2017 17:33] – johannes.lotz | en:create:debugging [26.09.2017 17:25] – Correction of some typos up to Filter questions lchnr.web | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Questionnaire | + | ====== |
Getting started using [[: | Getting started using [[: | ||
Line 7: | Line 7: | ||
* ... where the problem is located, when nothing is working anymore (formal errors), | * ... where the problem is located, when nothing is working anymore (formal errors), | ||
- | * ... what is happening in the background before something appears on-screen and | + | * ... what is happening in the background before something appears on-screen, and |
* ... whether the expected content has been saved in variables (content errors). | * ... whether the expected content has been saved in variables (content errors). | ||
Formal errors are the easiest to find. When a semicolon is missing at the end of a command or a missing bracket (syntax error) the command code won't even be executed. SoSci Survey will then show an error message. Therefore the error console has to be opened. | Formal errors are the easiest to find. When a semicolon is missing at the end of a command or a missing bracket (syntax error) the command code won't even be executed. SoSci Survey will then show an error message. Therefore the error console has to be opened. | ||
- | Content errors are harder to find. The code is working, but does not lead to the desired outcome. In this case the background display can help to show what is actually happening ([[# | + | Content errors are harder to find. The code is working, but does not produce |
Line 19: | Line 19: | ||
Open the questionnaire in debug mode by clicking on the yellow arrow next to **run questionnaire**{{: | Open the questionnaire in debug mode by clicking on the yellow arrow next to **run questionnaire**{{: | ||
- | * In debug mode ({{: | + | * In debug mode ({{: |
* In debug mode the identifier and description is being displayed next to every question. Move your cursor over the description to make additional notes to the question. They will also be displayed in the question catalog when opening a question for editing. | * In debug mode the identifier and description is being displayed next to every question. Move your cursor over the description to make additional notes to the question. They will also be displayed in the question catalog when opening a question for editing. | ||
* In debug mode you have an additional control panel at the top (debug panel) to show you additional information to questions. | * In debug mode you have an additional control panel at the top (debug panel) to show you additional information to questions. | ||
Line 29: | Line 29: | ||
{{ : | {{ : | ||
- | **Note:** If you start the questionnaire in debug-mode, you will find this later in your data. It will have " | + | **Note:** If you start the questionnaire in debug-mode, you will find this later in your data. It will have " |
==== Navigation ==== | ==== Navigation ==== | ||
- | You've got a question designed to filter on page 2, however, the actual [[:de: | + | You've got a question designed to filter on page 2, however, the actual [[:en: |
{{: | {{: | ||
Line 43: | Line 43: | ||
* Use the arrow pointing right (►), to get to the next page without checking on integrity (obligation to respond/ | * Use the arrow pointing right (►), to get to the next page without checking on integrity (obligation to respond/ | ||
- | **Hint:** If you directly jump to another page, all specifications made will be automatically saved, you do not need to click the " | + | **Hint:** If you directly jump to another page, the data provided |
==== Survey Route ==== | ==== Survey Route ==== | ||
- | If you work with '' | + | If you work with '' |
- | '' | + | '' |
{{: | {{: | ||
- | You will see a list of pages that have been shown over the course of the interview. The most recent position will be shown in bold. By means of '' | + | You will see a list of pages that have been shown over the course of the interview. The most recent position will be shown in bold. By means of '' |
==== Debug Information ==== | ==== Debug Information ==== | ||
- | Whenever you work with Wann immer Sie mit PHP-Code arbeiten, the debug information will give you helpful input. Click "debug information" | + | Whenever you work with PHP code, the debug information will give you helpful input. Click "debug information" |
{{ : | {{ : | ||
- | The debug information shows the relevant steps that have happened | + | The debug information shows the relevant steps that have taken place in the background |
Here you can see: | Here you can see: | ||
- | * ... which answers have been read and been saved on your data ("Lese Antworten von Seite ...") and | + | * ... which answers have been read and saved on your data ("Lese Antworten von Seite ...") and |
* ... what has been processed on the current page (" | * ... what has been processed on the current page (" | ||
Line 72: | Line 72: | ||
==== Filter Questions ==== | ==== Filter Questions ==== | ||
- | The example used shows a survey page with a small [[:de: | + | The example used shows a survey page with a small [[:en: |
{{: | {{: | ||
Line 85: | Line 85: | ||
==== Variables ==== | ==== Variables ==== | ||
- | Using the command '' | + | Using the command '' |
{{: | {{: | ||
Line 125: | Line 125: | ||
</ | </ | ||
- | Here only the output of the debugging mode will help ([[# | + | Here only the output of the debugging mode will help ([[# |
Take a look a the initial of the command:'' | Take a look a the initial of the command:'' | ||
Line 139: | Line 139: | ||
===== Finding Bugs in Java ===== | ===== Finding Bugs in Java ===== | ||
- | While the PHP code of SoSci Survey is being executed on the server, [[de: | + | While the PHP code of SoSci Survey is being executed on the server, [[en: |
To do so, the error log is needed. One can find it -- depending on the browser -- at different places. | To do so, the error log is needed. One can find it -- depending on the browser -- at different places. |