queXS 1.10.1 Released

Submitted by adamzammit on Fri, 2014-02-14 15:06

queXS 1.10.1 has been released today on Sourceforge

This is a single bug fix release. The queXS 1.10.0 database installation script would fail on a fresh installation. Please use queXS 1.10.1 for new installations. It is not essential for users of 1.10.0 to upgrade, although translations have been updated

Read on for more details including how to upgrade from queXS 1.9.x (Database update required)

Upgrading from queXS 1.9.x

  1. Browse to the queXS administration page
  2. Click on "Start and monitor system wide case sorting"
  3. Confirm that the sorting process is stopped
  4. Click on "Start and monitor VoIP"
  5. Confirm that the VoIP process is stopped
  6. IMPORTANT: Backup your database and files
  7. Run the following SQL on the queXS database:

    ALTER TABLE `questionnaire` ADD `referral` TINYINT( 1 ) NOT NULL DEFAULT '0' AFTER `self_complete`;

    CREATE TABLE IF NOT EXISTS `extension` (
    `extension_id` int(11) NOT NULL AUTO_INCREMENT,
    `extension` char(10) COLLATE utf8_unicode_ci NOT NULL,
    `password` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
    `status` tinyint(1) NOT NULL DEFAULT '0',
    `current_operator_id` bigint(20) DEFAULT NULL,
    PRIMARY KEY (`extension_id`),
    UNIQUE KEY `extension` (`extension`),
    UNIQUE KEY `current_operator_id` (`current_operator_id`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ;

    INSERT INTO `extension` (extension,password,current_operator_id,status)
    SELECT extension,extension_password,operator_id,voip_status FROM operator;

    ALTER TABLE `operator` DROP `extension`, DROP `extension_password`, DROP `voip_status`;

  8. Rename the queXS 1.9.x directory
  9. Extract quexs-1.10.1 to a new directory on your web server
  10. Rename the new directory to the same as the existing installation was originally
  11. Copy the config.inc.local.php file from the queXS 1.9.x installation to this directory
  12. Consider the new ALLOW_OPERATOR_EXTENSION_SELECT feature if you wish to allow for operators to "hot desk" by selecting their extensions at the start of their shift
  13. If you used .htaccess files, copy these to their respective directories also, for example: .htaccess admin/.htaccess client/.htaccess include/limesurvey/admin/.htaccess