This is a re-reporting of issue 6394

CDbException

CDbCommand failed to execute the SQL statement: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'stg_value' cannot be null. The SQL statement executed was: UPDATE lime_settings_global SET stg_name=:yp0, stg_value=:yp1 WHERE lime_settings_global.stg_name='emailsmtpssl'

C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\limesurvey\framework\db\CDbCommand.php(354))

I can confirm this is an issue with the latest version of LimeSurvey (downloaded this afternoon using the links on the download page). It's a clean fresh install, MySQL 5.1, Apache 2.2, PHP 5.2.10 running on Windows XP.

This issue appears to be caused by a problem with the 'returnGlobal' function in application\helpers\common_helper.php.

returnGlobal uses the 'empty' function to decide whether it needs to retrieve the value from say $_POST and use it to populate $urlParam.

Unfortunately, the field that caused me headaches with this (emailsmtpdebug) uses the value '0' for Off. Clearly from the documents at php.net, the empty function considers '0' to be empty and thus returns TRUE meaning that (!empty($_POST[$stringname])) evaluates to false and the value is not returned. As a consequence, a NULL value is passed into setGlobalSetting which results in the SQL failing because stg_value gets a NULL (hence the constraint violation error).

I've only literally just downloaded LimeSurvey and I've not got enough time at the moment to investigate and put forward a fix, but a change from using empty is probably required. As I say, if I had more time I would investigate the knock on effects of making such a change and possibly submit a patch. It really needs a dev who knows plenty more about the project as a whole to make an assessment as I suspect 'returnGlobal' is used quite a lot.