Differences

This shows you the differences between two versions of the page.

--- en:create:debugging [22.09.2017 17:33] – johannes.lotz
+++ en:create:debugging [22.09.2017 17:39] – johannes.lotz
@@ Line 19: / Line 19: @@
 Open the questionnaire in debug mode by clicking on the yellow arrow next to **run questionnaire**{{:button.debug.gif?nolink|debugging of questionnaire}}. Use the yellow arrow with protruding line {{:button.debug.here.gif?nolink|debugging from current page}} to start debug mode from a specific page.
-  * In debug mode ({{:button.debug.gif?nolink|debug mode}}) and in preview mode ({{:button.run.gif?nolink|preview mode}}) you see warnings (orange) and hints (yellow) for possible problems that are not being displayed in the normal questionnaire (e.g. by applying ''value()'' to a variable that has not yet been retrieved).
+  * In debug mode ({{:button.debug.gif?nolink|debug mode}}) and in preview mode ({{:button.run.gif?nolink|preview mode}}) you see warnings (orange) and hints (yellow) for possible problems that are not being displayed in the normal questionnaire (e.g., by applying ''value()'' to a variable that has not yet been retrieved).
   * 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.
@@ Line 29: / Line 29: @@
 {{ :de:create:scr.debug.closed.png?nolink |Debug-Leiste ausgeblendet}}
-**Note:** If you start the questionnaire in debug-mode, you will find this later in your data. It will have "debug" ([[de:results:variables]]) displayed as its variable //MODE//. Use **data obtained** -> **show data** to inquire into your saved data.
+**Note:** If you start the questionnaire in debug-mode, you will find this later in your data. It will have "debug" ([[en:results:variables]]) displayed as its variable //MODE//. Use **data obtained** -> **show data** to inquire into your saved data.
 ==== Navigation ====
-You've got a question designed to filter on page 2, however, the actual [[:de:create:filters|Filter]]  is found on page 10? Use the navigation in the debug control panel to directly switch between the pages.
+You've got a question designed to filter on page 2, however, the actual [[:en:create:filters|Filter]]  is found on page 10? Use the navigation in the debug control panel to directly switch between the pages.
 {{:de:create:scr.debug.navigation.png?nolink|}}
@@ Line 48: / Line 48: @@
 ==== Survey Route ====
-If you work with ''[[:de:create:functions:gotopage]]'' or
+If you work with ''[[:en:create:functions:gotopage]]'' or
-''[[:de:create:functions:setpageorder]]'' , you might want to retrace which pages have been displayed over the course of the interview. Move your courser over the name of the survey to do so.
+''[[:en:create:functions:setpageorder]]'' , you might want to retrace which pages have been displayed over the course of the interview. Move your courser over the name of the survey to do so.
 {{:de:create:scr.debug.history.png?nolink|Informationen zum Fragebogen und Verlauf}}
-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 ''[[:de:create:functions:setpageorder]]'' or ''[[:de:create:functions:setnextpage]]'' you can decide which page shall be shown after clicking on "next"; this will be shown in the list as grey.
+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 ''[[:en:create:functions:setpageorder]]'' or ''[[:en:create:functions:setnextpage]]'' you can decide which page shall be shown after clicking on "next"; this will be shown in the list as grey.
 ==== Debug Information ====
-Whenever you work with Wann immer Sie mit PHP-Code arbeiten, the debug information will give you helpful input. Click "debug information" on the top right to have the window fade in or out.
+Whenever you work with PHP code, the debug information will give you helpful input. Click "debug information" on the top right to have the window (dis-)appear.
 {{ :de:create:scr.debug.information.png?nolink |Debug-Information einblenden}}
-The debug information shows the relevant steps that have happened in the background inbetween the start of the current page (e.g., by clicking on "next") and the display of the page on screen.
+The debug information shows the relevant steps that have happened in the background in between the start of the current page (e.g., by clicking on "next") and the display of the page on screen.
 Here you can see:
@@ Line 72: / Line 72: @@
 ==== Filter Questions ====
-The example used shows a survey page with a small [[:de:create:filters|Filter]].
+The example used shows a survey page with a small [[:en:create:filters|Filter]].
 {{:de:create:scr.debug.info01source.png?nolink|Beispiel für eine Fragebogen-Seite mit Filter}}
@@ Line 85: / Line 85: @@
 ==== Variables ====
-Using the command ''[[:de:create:functions:debug]]'' you can see the value of any variable in your data set or PHP-Code. As an example serves the following page of a questionnaire, which calculates a new value out of an open text entry of a participant in "AB11_01" while using a filter.
+Using the command ''[[:en:create:functions:debug]]'' you can see the value of any variable in your data set or PHP-Code. As an example serves the following page of a questionnaire, which calculates a new value out of an open text entry of a participant in "AB11_01" while using a filter.
 {{:de:create:scr.debug.info02source.png?nolink|Beispiel-Fragebogenseite}}
@@ Line 125: / Line 125: @@
 </code>
-Here only the output of the debugging mode will help ([[#debug-information|Debug-Information]]). This shows that the command ''[[:de:create:functions:text]]'' is not being executed, the ''goToPage()'' however is. Thus it is not the filter that produces the problem.
+Here only the output of the debugging mode will help ([[#debug-information|Debug-Information]]). This shows that the command ''[[:en:create:functions:text]]'' is not being executed, the ''goToPage()'' however is. Thus it is not the filter that produces the problem.
 Take a look a the initial of the command:''[[:de:create:functions:gotopage]]''. It tells us that it will make you jump to the specific page directly without executing anything else on the page of origin. In this example, not even ''text()''. If you are aware of the cause, the solution is simple: Move ''text()'' in front of ''goTopage()''.
@@ Line 139: / Line 139: @@
 ===== Finding Bugs in Java =====
-While the PHP code of SoSci Survey is being executed on the server, [[de:create:javascript|JavaScript]] will run in the browser of the participant. Accordingly the browser is responsible for finding errors and information.
+While the PHP code of SoSci Survey is being executed on the server, [[en:create:javascript|JavaScript]] will run in the browser of the participant. Accordingly the browser is responsible for finding errors and information.
 To do so, the error log is needed. One can find it -- depending on the browser -- at different places.