View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
08621 | Bug reports | ComfortUpdate | public | 2014-01-29 02:03 | 2014-02-02 18:52 |
Reporter | holch | Assigned To | c_schmitz | ||
Priority | normal | Severity | minor | ||
Status | closed | Resolution | fixed | ||
Fixed in Version | 2.05+ | ||||
Summary | 08621: Blank screen after comfort update (Not problem with PHP lower than 5.3 | ||||
Description | I was running PHP 5.4.24 and got a blank screen during the comfort update as well. Downgraded to PHP 5.3.27 but it did not resolve the problem. I have a LS 2.05 install in parallel and all works fine, with 5.4 and with 5.3. | ||||
Tags | No tags attached. | ||||
Bug heat | 4 | ||||
Complete LimeSurvey version number (& build) | |||||
I will donate to the project if issue is resolved | |||||
Browser | |||||
Database type & version | |||||
Server OS (if known) | |||||
Webserver software & version (if known) | |||||
PHP Version | |||||
From what version did you update? Did you activate debug mode and see if you get an error? Why do I even have to ask this ? |
|
Update of LS 2.0 to the newest version of LS 2.0 offered by the comfort update (I did not note down which version I had before and which one was supposed to be upgraded to. Couldn't access the system anymore. However:
|
|
Do you remember which build you updated from? Could it be that the update wasn't allowed to write to all directories? 2.05 is not yet available to 2.00 users because we are still ironing out update |
|
I did not upgrade for a while, because I had a project running at the beginning of the year. I checked in the forum post where I had helped someone with a similar problem (but here it was solved with an upgrade to PHP 5.3): it was version v131206. My 2.05 installation is running just fine. I had installed this separately of course. |
|
And I don't think it was the permissions. All prior comfort updates ran just smooth (of course, it could have been that the missing file was never touched by previous updates, but...) |
|
I checked and this is resolved now. It should not happen again. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2014-01-29 02:03 | holch | New Issue | |
2014-01-29 02:03 | holch | Status | new => assigned |
2014-01-29 02:03 | holch | Assigned To | => c_schmitz |
2014-01-29 09:56 | c_schmitz | Project | Feature requests => Bug reports |
2014-01-29 09:57 | c_schmitz | Severity | feature => minor |
2014-01-29 09:58 | c_schmitz | Note Added: 28258 | |
2014-01-29 09:58 | c_schmitz | Status | assigned => feedback |
2014-01-29 12:11 | holch | Note Added: 28261 | |
2014-01-29 12:11 | holch | Status | feedback => assigned |
2014-01-29 16:09 | c_schmitz | Note Added: 28263 | |
2014-01-29 17:47 | holch | Note Added: 28264 | |
2014-01-29 17:49 | holch | Note Added: 28265 | |
2014-02-02 18:51 | c_schmitz | Note Added: 28399 | |
2014-02-02 18:52 | c_schmitz | Status | assigned => closed |
2014-02-02 18:52 | c_schmitz | Resolution | open => fixed |
2014-02-02 18:52 | c_schmitz | Fixed in Version | => 2.05+ |