Hello,
I too am having the blank page issue. I have been trying to install this app for about two days now. I originally started on an inmotion hosting account with the latest version 2. After nothing but blank page and being redirected to a url of
mydomain.com/index.php?r=installer/welcome
After reading through the forums here I found the page with supported hosts so being I have a personal hostgater account I then tried installing version 2 on that account. I had the same exact thing a blank page. I then deleted all files and found that on hostgater within the cpanel i was able to do a quick install of limesurvey. I was then able to get to the 1.8 version and then within the page I did perform the comfort upgrade to 1.92. I really would like the latest an greatest so I attempted to delete all files and upload the version 2 and I have followed the directions here
docs.limesurvey.org/Upgrading+from+a+pre...y_later_2.xx_version
I have just completed uploading all of the files. cleared my temp internet files and history and closed and reopened the browser both IE9 and Firefox and I am back to getting the
mydomain.com/index.php?r=installer/welcome and it is a blank page.
I have tried viewing this or accessing the /admin page on a number of computers with various versions of both IE and firefox and all with the same result.. What is it that will not allow the page to load.
Completely frustrated...
Thanks
Paul
UPDATE..
I have edited the config-sample-mysql.php to reflect my previous installed version db info and have set /config /tmp /tmp/runtime to 777 and set debug to 2 and I still get a blank page and the view source of the page I am being redirected to (
mydomain.com/index.php?r=installer/welcome) when trying to access
mydomain.com/admin is:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
<BODY></BODY></HTML>
I have also viewed the error log an access logs and there is not even any reference to the limesurvey in the error log and the entries in the access log all appear to be normal.