$vbulletin->config['MasterServer']['servername'], $vbulletin->config['MasterServer']['port'], $vbulletin->config['MasterServer']['username'], $vbulletin->config['MasterServer']['password'], $vbulletin->config['MasterServer']['usepconnect'], $vbulletin->config['SlaveServer']['servername'], $vbulletin->config['SlaveServer']['port'], $vbulletin->config['SlaveServer']['username'], $vbulletin->config['SlaveServer']['password'], $vbulletin->config['SlaveServer']['usepconnect'], $vbulletin->config['Mysqli']['ini_file'], (isset($vbulletin->config['Mysqli']['charset']) ? $vbulletin->config['Mysqli']['charset'] : '') ); //if (!empty($vbulletin->config['Database']['force_sql_mode'])) //{ $db->force_sql_mode(''); //} //30443 Right now the product doesn't work in strict mode at all. Its silly to make people have to edit their //config to handle what appears to be a very common case (though the mysql docs say that no mode is the default) //we no longer use the force_sql_mode parameter, though if the app is fixed to handle strict mode then we //may wish to change the default again, in which case we should honor the force_sql_mode option. //added the force parameter //if (!empty($vbulletin->config['Database']['force_sql_mode'])) //if (empty($vbulletin->config['Database']['no_force_sql_mode'])) //{ // $db->force_sql_mode(''); //} if (defined('DEMO_MODE') AND DEMO_MODE AND function_exists('vbulletin_demo_init_db')) {