Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
en:create:debugging [22.09.2017 17:39]
johannes.lotz
en:create:debugging [26.09.2017 17:25]
lchnr.web Correction of some typos up to Filter questions
Line 1: Line 1:
-====== Questionnaire ​Problem Solutions ​======+====== ​Solving ​Questionnaire ​Problems ​======
  
 Getting started using [[:​en:​create:​php|PHP-Code]] and [[en:​create:​javascript|JavaScript]] is not always trivial -- especially when you have a more complex task ahead of you, things do not always work out as expected. Getting started using [[:​en:​create:​php|PHP-Code]] and [[en:​create:​javascript|JavaScript]] is not always trivial -- especially when you have a more complex task ahead of you, things do not always work out as expected.
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-screenand
   * ... 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 ([[#​beispiel|example]]).+Content errors are harder to find. The code is working, but does not produce ​the desired outcome. In this case the background display can help to show what is actually happening ([[#​beispiel|example]]).
  
  
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. 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 used).
   * 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 43: Line 43:
   * Use the arrow pointing right (►), to get to the next page without checking on integrity (obligation to respond/​tackling the response).   * Use the arrow pointing right (►), to get to the next page without checking on integrity (obligation to respond/​tackling the response).
  
-**Hint:** If you directly jump to another page, all specifications made will be automatically savedyou do not need to click the "​next"​ button.+**Hint:** If you directly jump to another page, the data provided ​will be automatically saved so you do not need to click the "​next"​ button.
  
  
Line 61: Line 61:
 {{ :​de:​create:​scr.debug.information.png?​nolink |Debug-Information einblenden}} {{ :​de:​create:​scr.debug.information.png?​nolink |Debug-Information einblenden}}
  
-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. ​+The debug information shows the relevant steps that have taken place 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: 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 ("​Erstelle Fragebogen-Seite Nr. ...").   * ... what has been processed on the current page ("​Erstelle Fragebogen-Seite Nr. ...").
  
en/create/debugging.txt · Last modified: 27.09.2017 10:57 by lchnr.web
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
Driven by DokuWiki