View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
05211 | Bug reports | ComfortUpdate | public | 2011-05-31 14:51 | 2011-05-31 19:39 |
Reporter | mot | Assigned To | c_schmitz | ||
Priority | normal | Severity | block | ||
Status | closed | Resolution | duplicate | ||
Product Version | 1.91 | ||||
Summary | 05211: Comfort Update Step 3 is empty page | ||||
Description | I've been running comfort update for the first time. Intro screen as well as step 1 and step 2 look good, but step three just gives me a white page. I assume that the script dies. | ||||
Steps To Reproduce | Stepping through comfort update. Always reproduceable on my end. | ||||
Additional Information | Will need to check the error log to provide more information. Reported for documentation purposes as of now. | ||||
Tags | No tags attached. | ||||
Bug heat | 2 | ||||
Complete LimeSurvey version number (& build) | 10062 | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | |||||
Database type & version | MySQL 5 Family | ||||
Server OS (if known) | Linux (Suse) | ||||
Webserver software & version (if known) | Apache 2.2 | ||||
PHP Version | 5.2.x | ||||
As an additional note in the margin: The "Change Log" given is not as comprehensive as the one in the bug-tracker, I get: == START == #Updated translation: Norwegian Nynorsk - kindly provided by Guttorm Flatab |
|
I have problems to solve this issue. I can not reproduce this on my testbed (which works on svn), because probably I'm to near to HEAD (my testbed is not on HEAD, it's "only" ~2-3 weeks behind it). On the life system I set $debug=1 to get warning, but I don't get any warnings nor is there some information in the PHP error log which I configured and keep monitored. So to summarize: Can reproduce but I'm unable to get more information easily. Will try to hack the life script for line by line debugging. |
|
Improvement note while debugging: Instead of storing the output into a variable and then returning it per each step function, those function can just output it. The calling main part of the script can buffer the output and output it then as it does now. The benefit of it is, that if the script crashes or dies, the buffer will be output (instead of a blank). output buffering is available since 4.2, see http://www.php.net/manual/en/ref.outcontrol.php . |
|
I found the culprit: require_once("dumpdb.php"); there is no such file. Script quits there, I thought I would see a fatal error but I don't. $debug = 1 in config.php. Error log is configured in config.php as well. |
|
found dumpdb.php one dir up (../dumpdb.php), that script get's included and then the exit; command is executed which ends the request. Does not make much sense, I assume it is included for the functions. Will compare against HEAD. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2011-05-31 14:51 | mot | New Issue | |
2011-05-31 14:51 | mot | Status | new => assigned |
2011-05-31 14:51 | mot | Assigned To | => c_schmitz |
2011-05-31 15:21 | mot | Note Added: 15183 | |
2011-05-31 15:32 | mot | Note Added: 15185 | |
2011-05-31 16:05 | mot | Note Added: 15186 | |
2011-05-31 16:13 | mot | Note Added: 15187 | |
2011-05-31 17:55 | mot | Note Added: 15188 | |
2011-05-31 19:39 | c_schmitz | Relationship added | duplicate of 05199 |
2011-05-31 19:39 | c_schmitz | Status | assigned => closed |
2011-05-31 19:39 | c_schmitz | Resolution | open => duplicate |