| … | |
… | |
| 145 | at the messages in WeBWorK's error log (see below). |
145 | at the messages in WeBWorK's error log (see below). |
| 146 | |
146 | |
| 147 | Further look in the error logs for your webserver and in WeBWorK's error log |
147 | Further look in the error logs for your webserver and in WeBWorK's error log |
| 148 | .../webwork/system/logs/error_log. |
148 | .../webwork/system/logs/error_log. |
| 149 | |
149 | |
| 150 | For debugging errors in output (postscript,latex2html, etc), you can set |
150 | For debugging errors in output (postscript,latex2html, etc), set $imageDebugMode |
| 151 | $debugON=1 in .../cgi/cgiscripts/welcomeAction.pl and $debug=1 in |
151 | to 1 in Global.pm and then look at the messages in WeBWorK's error log |
| 152 | ../courseScripts/displayMacros.pl. Doing so will save intermediate temporary |
152 | ( .../webwork/system.logs/error_log) and in the webserver's error log. |
| 153 | files (log files, TeX files, etc) that may help in finding the error. Don't |
153 | Also with $imageDebugMode set to 1 intermediate temporary files (log files, |
|
|
154 | TeX files, etc) will be saved and these may help in finding the error. |
|
|
155 | You will find these files in the course's tmp directory. Don't leave |
| 154 | leave these set to 1. If you do, you will find your file system filling up. |
156 | $imageDebugMode set to 1. If you do, you will find your file system filling up. |
| 155 | |
157 | |
| 156 | If you do still have trouble (especially if you see Internal Server Error), |
158 | If you do still have trouble (especially if you see Internal Server Error), |
| 157 | edit ../webwork/system/lib/webworkConfig.pm setting |
159 | edit ../webwork/system/lib/webworkConfig.pm setting |
| 158 | $cgiDebugMode = 1; |
160 | $cgiDebugMode = 1; |
| 159 | $cgiDebugMode, when enabled, will call the debug wrapper scripts instead of the |
161 | $cgiDebugMode, when enabled, will call the debug wrapper scripts instead of the |
| 160 | cgi scripts themselves, allowing for header output, etc. In addition to setting |
162 | cgi scripts themselves, allowing for header output, etc. In addition to setting |
| 161 | $cgiDebugMode =1, you will also need to enable debugging in the wrapper script |
163 | $cgiDebugMode =1, you will also need to enable debugging in the wrapper script |
| 162 | for the cgi script that you wish to debug, by setting $debug = 1. Wrapper |
164 | for the cgi script that you wish to debug, by setting $debug = 1. Wrapper |
| 163 | scripts are found in the directory referred to by $cgiWebworkURL, which is # |
165 | scripts are found in the directory referred to by $cgiWebworkURL, which is |
| 164 | usually webwork/system/cgi and have the same name as the underlying cgi script. |
166 | usually webwork/system/cgi and have the same name as the underlying cgi script. |
| 165 | $cgiDebugMode = 0; |
|
|
| 166 | |
167 | |
| 167 | 11. Some problems have a hard coded statement that you have to get all parts |
168 | 11. Some problems have a hard coded statement that you have to get all parts |
| 168 | correct in order to receive credit. This is not true if the partial credit |
169 | correct in order to receive credit. This is not true if the partial credit |
| 169 | problem grader is used. In general, it is better to let the software generate |
170 | problem grader is used. In general, it is better to let the software generate |
| 170 | such statements rather than put them in problems. But we have not edited them |
171 | such statements rather than put them in problems. But we have not edited them |
Parent Directory
| 
Revision Log
| 
Patch