I just called the public site with debug set to lvl 2 and obtained these errors as well:

http://surveys.atmymarket.com/surveys/index.php

That is the same error over and over again and it is pretty non-saying.
Set debug mode to 1 instead , try again and see if you get some more decent error.
Please report back.

Debug set to 1 produces a blank page...

What you are looking for is at the bottom of both my inital bug report and this debug from 160215.

Just skip over the complaining at the beginning of the variable.

This is in the first and 3rd of what I sent you:

Cannot modify header information - headers already sent by (output started at /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160213/framework/i18n/gettext/CGettextMoFile.php:234)

Cannot modify header information - headers already sent by (output started at /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160215/framework/i18n/gettext/CGettextMoFile.php:234

Error dump #01: 160213 - Admin Login

Error dump #02: 160213 - Site Home Page

Error dump #03: 160215 - Admin Login.

You just did not look far enough down...

I can read an error log myself - thank you.
The error is still non-saying and I cannot reproduce it.

There are STRICT warnings causing the headers to be sent early - probably you did not properly upload all files in binary mode to your server or your server is misconfigured.

Well since I did a wget from your server, and then simply untared it, I know it is in your code.

Also if you clear out /tmp/assets and prevent the code from writing anything to this directory you get a login page and can login.

This is entirely a bug in 2.5....

I found it:

The problem is in:

/tmp/assets/f143c333/lime-admin.css

If the site loads this file you simply get a blank white page.

So you are right in that it is not in the application, however I did upload and install correctly...

I have done a little more checking...

The first 1812 lines of the lime-admin.css sheet seem to work.

Up until:

.form-group {
margin-bottom: 17px; }

Within 100 lines after that the outputted page goes all white...

Here it is:

File: lime-admin.css

Lines: 1873-1877

.welcome .panel {
position: relative;
top: 50px;
opacity: 0;
box-shadow: 0 2px 5px 0 rgba(0, 0, 0, 0.16), 0 2px 10px 0 rgba(0, 0, 0, 0.12); }

These lines cause a blank white login screen in both Firefox V:44.0.2 and Internet Explorer V:11.0.9600.18204.

Simply removing those 4 lines makes everything visible again.

Him,

thank you for investigating.
The lines are fine though and validate perfectly in https://jigsaw.w3.org/css-validator/#validate_by_input

I have no clue what might be the reason - it sounds to me like you might have some security module installed on your server blocking the script. Hard to tell.
Nobody else can reproduce it so...

With all due respect, I must admit I find it distasteful at how quick you are to lay Blaine on the user or my configuration. You are jumping to conclusions with little to no evidence. Your not asking questions, your simply trying to blame your users.

Now the script is NOT being blocked. It is getting to the browser just fine.

I can view page source, and then load and view the css file from the page source.

The code may pass cuss validation, but that does not mean that it does not contain an error. Just because the syntax is correct does not mean that the logic or color choices are not causing this.

Here is is plain and simple...

If I use the 3900 line file as it ships with 16021[3|5] you get a blank white page when you go to the admin screen.

When you delete those 5 lines, but use the rest of the 3900 line file you get a login screen and everything works as expected.

There is something wrong with the logic in that one block declaration.

Also I am not the only one seeing this. If you go to the forums there are sooooooooo many messages of users getting a blank white screen. This was loosly blamed on the rootpath variable before.

I think that line creates a white box that sits in front of everything and hides the page.

Again with respect. The logic with your answer makes no sense at all.

If you BLOCK the scrript from sending, the SITE WORKS...

If you DO NOT BLOCK the script and allow it to send, the SITE IS BROKEN.

So any security module blocking this css file would make the site work not break it.

However again, simply removing those 5 lines fixes the problem.

The only way these 5 lines can affect this is if you have Javascript disabled in your browser or you maybe have some Javascript blocked by your AV software.
Or probably the the scripts are blocked by your server.
Can you check?

Feedback please?

As I stated before nothing is being blocked. JavaScript is turned on and running just fine, your files are downloading just fine.

Nothing is blocking anything from running.

Trust me, I would like nothing more than it to be as simple as JavaScript, but as I mentioned to you this is happening on two different browsers...

Now I can add this... Not only is it doing this on FIrefox and IE on my Windows 7 box, but it is also doing it on Safari on my iPad.

So 3 browsers and 2 platforms.

What's the URL to the installation so I can see it for myself?

?

You know the one this this tracker is missing is time zones. :)

I am in Canada so your asking for these things in the middle of the night for me.

Do you want the site setup with the 5 lines in so you see the error? (What I would presume.).

The URL was sent in the very first support message to you.

But I need 15 minutes to get to my station to put the original file back on-line to cause the errors.

Additionally would you like me to take 15 minutes and move to 160217?

The two that I have tested was 160213 and 160215. I am currently running 160215.

Last night when I logged into the admin area, it did offer to comfort upgrade to 160216.

I now see that I can also download 160217.

Okay I have restored the original version of lime-admin.css and I am getting the blank white page again.

By the way, debug is set to 0. Since I was starting to look around the admin area to get a feel for the application.

Ok, I can see the white page - now can you please update to the latest 2.50 version, too? There have been numerous fixes by now. Anyway, please let me know which version I am looking at right now.

Your looking at 160215... Give me 15 and I will wipe it and do a clean 17...

Can you try wiping the database, too?
I can see that half of the CSS and JS files are missing from your page header.

I always do wipe the db. :)

Okay here is a new one...

160217 will not install. When you go to populate the db you get this error:

Please fix the following input errors:

There were errors when trying to populate the database:

CDbCommand failed to execute the SQL statement: SQLSTATE[42000]: Syntax error or access violation: 1115 Unknown character set: 'utf8mb4'

By the way, when I moved from 160213 to 160215 I also wiped the db and created a new one. Basically I simply deleted all the tables and ran the install again.

The collation that I normally use for my dbs is: utf8_general_ci

Would changing that to utf8_unicode_ci help?

Ah, that might be the reason. LimeSurvey requires MySQL 5.5.3
In the past this wasn't immediately noticable, with the latest build we changed to a collation that is only available in 5.5.3 or later.

We will put this requirement as a check into the installer to prevent further disappointment for users.

RedHat and therefor Cent currently ship a 5.2.X line with OS V:6.7.

So that would mean most likely we need OS V:7.X to run this.

Okay Fedora 22 ships with Maria DB.

The community branch of MySQL. However the version numbers do not match. For example current under Fedora 22 is 10.0.21.

Will your software work with this server?

With the utmost respect to your team, I think you will have a lot of problem with that newer collation. Many of us will not stray from a stock installed/supported RedHat product.

Your asking for something that is simply not mainstream enough yet. :)

Again respectfully.

MariaDB supports it from version 5.5, too
LimeSurvey should run just fine on MariaDB

MySQL 5.5.3 was released in early 2011 - it is not a problem for most people.
Also already LimeSurvey 2.06 had this requirement and nobody complained then ;).

Hey I wont deny RedHat is beyond the last to adapt. lol

Funny if 2.06 had it, then why did 160213 and 160215 even install?

I think it might be time to put a hard block at the system compatibility test page for the MySQL server. :)

The only warnings I got in the installer was a lack of php-ldap and php-zip. :)

Just in case there might be something here, not using ldap, and zip was only a warning.

Yes, unfortunately we can only check the database after we connected to it. Will put a check in right after connection.

Chicken and egg thing. lol

I am going to set this up on the Maria DB server, since this particular client owns a VPS with one on it.

This will take a few minutes, I lock down all connections by IP, so I have to do a wack of security updates.

I will let you know how this effects things...

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=17485

Looks like MariaDB is not quite a go!

Please fix the following input errors:

There were errors when trying to populate the database:

Executing: CREATE TABLE lime_participant_attribute_names_lang ( attribute_id int(11) NOT NULL, attribute_name varchar(30) NOT NULL, lang varchar(255) NOT NULL, PRIMARY KEY (attribute_id,lang) ) ENGINE=MYISAM CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; failed! Reason: exception 'CDbException' with message 'CDbCommand failed to execute the SQL statement: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes' in /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160217/framework/db/CDbCommand.php:358 Stack trace: #0 /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160217/application/controllers/InstallerController.php(990): CDbCommand->execute() #1 /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160217/application/controllers/InstallerController.php(960): InstallerController->executeSQLFile('/hsphere/local/...', 'lime') #2 /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160217/application/controllers/InstallerController.php(577): InstallerController->_setup_tables('/hsphere/local/...') #3 /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160217/application/controllers/InstallerController.php(79): InstallerController->stepPopulateDb() #4 /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160217/framework/web/CWebApplication.php(282): InstallerController->run('populatedb') #5 /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160217/framework/web/CWebApplication.php(141): CWebApplication->runController('installer/popul...') #6 /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160217/framework/base/CApplication.php(184): CWebApplication->processRequest() #7 /hsphere/local/home/wwwuser/surveys.atmymarket.com/limesurvey-250plus-160217/index.php(211): CApplication->run() #8 {main}

Here are the tables it did create...

[root@devel-02 ~]# ls /var/lib/mysql/amm_surveys/ -l
total 308
-rw-rw---- 1 mysql mysql 67 Feb 17 17:07 db.opt
-rw-rw---- 1 mysql mysql 1694 Feb 17 17:07 lime_answers.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_answers.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_answers.MYI
-rw-rw---- 1 mysql mysql 2619 Feb 17 17:07 lime_assessments.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_assessments.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_assessments.MYI
-rw-rw---- 1 mysql mysql 2320 Feb 17 17:07 lime_boxes.frm
-rw-rw---- 1 mysql mysql 572 Feb 17 17:07 lime_boxes.MYD
-rw-rw---- 1 mysql mysql 2048 Feb 17 17:07 lime_boxes.MYI
-rw-rw---- 1 mysql mysql 3300 Feb 17 17:07 lime_conditions.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_conditions.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_conditions.MYI
-rw-rw---- 1 mysql mysql 1236 Feb 17 17:07 lime_defaultvalues.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_defaultvalues.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_defaultvalues.MYI
-rw-rw---- 1 mysql mysql 1571 Feb 17 17:07 lime_expression_errors.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_expression_errors.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_expression_errors.MYI
-rw-rw---- 1 mysql mysql 1250 Feb 17 17:07 lime_failed_login_attempts.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_failed_login_attempts.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_failed_login_attempts.MYI
-rw-rw---- 1 mysql mysql 2202 Feb 17 17:07 lime_groups.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_groups.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_groups.MYI
-rw-rw---- 1 mysql mysql 2182 Feb 17 17:07 lime_labelsets.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_labelsets.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_labelsets.MYI
-rw-rw---- 1 mysql mysql 1664 Feb 17 17:07 lime_labels.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_labels.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_labels.MYI
-rw-rw---- 1 mysql mysql 1197 Feb 17 17:07 lime_participant_attribute.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_participant_attribute.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_participant_attribute.MYI
-rw-rw---- 1 mysql mysql 1256 Feb 17 17:07 lime_participant_attribute_names.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_participant_attribute_names.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_participant_attribute_names.MYI
-rw-rw---- 1 mysql mysql 994 Feb 17 17:07 lime_participant_attribute_values.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_participant_attribute_values.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_participant_attribute_values.MYI
-rw-rw---- 1 mysql mysql 2772 Feb 17 17:07 lime_participants.frm
-rw-rw---- 1 mysql mysql 1244 Feb 17 17:07 lime_participant_shares.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_participant_shares.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_participant_shares.MYI
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_participants.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_participants.MYI
-rw-rw---- 1 mysql mysql 2299 Feb 17 17:07 lime_permissions.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_permissions.MYD
-rw-rw---- 1 mysql mysql 4096 Feb 17 17:07 lime_permissions.MYI
-rw-rw---- 1 mysql mysql 1462 Feb 17 17:07 lime_plugin_settings.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_plugin_settings.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_plugin_settings.MYI
-rw-rw---- 1 mysql mysql 1172 Feb 17 17:07 lime_plugins.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_plugins.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_plugins.MYI
-rw-rw---- 1 mysql mysql 2295 Feb 17 17:07 lime_question_attributes.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_question_attributes.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_question_attributes.MYI
-rw-rw---- 1 mysql mysql 4636 Feb 17 17:07 lime_questions.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_questions.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_questions.MYI
-rw-rw---- 1 mysql mysql 2598 Feb 17 17:07 lime_quota.frm
-rw-rw---- 1 mysql mysql 4387 Feb 17 17:07 lime_quota_languagesettings.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_quota_languagesettings.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_quota_languagesettings.MYI
-rw-rw---- 1 mysql mysql 1558 Feb 17 17:07 lime_quota_members.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_quota_members.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_quota_members.MYI
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_quota.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_quota.MYI
-rw-rw---- 1 mysql mysql 2753 Feb 17 17:07 lime_saved_control.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_saved_control.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_saved_control.MYI
-rw-rw---- 1 mysql mysql 1109 Feb 17 17:07 lime_sessions.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_sessions.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_sessions.MYI
-rw-rw---- 1 mysql mysql 2173 Feb 17 17:07 lime_settings_global.frm
-rw-rw---- 1 mysql mysql 20 Feb 17 17:07 lime_settings_global.MYD
-rw-rw---- 1 mysql mysql 2048 Feb 17 17:07 lime_settings_global.MYI
-rw-rw---- 1 mysql mysql 1308 Feb 17 17:07 lime_survey_links.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_survey_links.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_survey_links.MYI
-rw-rw---- 1 mysql mysql 8978 Feb 17 17:07 lime_surveys.frm
-rw-rw---- 1 mysql mysql 10112 Feb 17 17:07 lime_surveys_languagesettings.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_surveys_languagesettings.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_surveys_languagesettings.MYI
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_surveys.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_surveys.MYI
-rw-rw---- 1 mysql mysql 1238 Feb 17 17:07 lime_survey_url_parameters.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_survey_url_parameters.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_survey_url_parameters.MYI
-rw-rw---- 1 mysql mysql 1151 Feb 17 17:07 lime_templates.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_templates.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_templates.MYI
-rw-rw---- 1 mysql mysql 1584 Feb 17 17:07 lime_user_groups.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_user_groups.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_user_groups.MYI
-rw-rw---- 1 mysql mysql 949 Feb 17 17:07 lime_user_in_groups.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_user_in_groups.MYD
-rw-rw---- 1 mysql mysql 1024 Feb 17 17:07 lime_user_in_groups.MYI
-rw-rw---- 1 mysql mysql 3468 Feb 17 17:07 lime_users.frm
-rw-rw---- 1 mysql mysql 0 Feb 17 17:07 lime_users.MYD
-rw-rw---- 1 mysql mysql 2048 Feb 17 17:07 lime_users.MYI
[root@devel-02 ~]#

What I just added was also submitted as Bug 10519.

2.50+ Build 160218 released