Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/33/d214989360/htdocs/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/33/d214989360/htdocs/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/33/d214989360/htdocs/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/33/d214989360/htdocs/wp-includes/http.php on line 61

Strict Standards: Non-static method K2::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/functions.php on line 31

Strict Standards: Non-static method K2::register_scripts() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 51

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Options::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2Header::get_header_width() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/header.php on line 8

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::filter_post_comments() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 166

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458
2009 September Archive at Campaign Diaries
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::output_header_css() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
Monthly Archive for September, 2009


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Polls find Deeds and Corzine once again exchanging momentum, Lincoln tanking in Arkansas

Every few days, I am changing my mind as to which of the two governorships that are currently being contested Democrats have a better chance of defending. For a while in early September, Creigh Deeds looked so far gone that Jon Corzine’s fortunes looked stronger; then, the former managed to get himself back in the running and recent developments were getting me ready to settle on Virginia. But the narrative has changed once more: Now, it looks that Jon Corzine is in far better shape than Creigh Deeds heading into the campaigns’ 5 final weeks.

This is due to 3 polls released over the past 24 hours. The first is SUSA’s survey finding Bob McDonnell up 14%. I wrote about it last night, raising obvious questions as to whether the poll will turn out to be an outlier. As I pointed out, that poll was the only one since the master’s thesis story broke to have McDonnell leading by more than 7%. Well, we did not have to wait for long to get confirmation that SUSA was on to something: Rasmussen’s latest poll has the Republican leading 51% to 42%.

While Rasmussen is often criticized for finding numbers that look too friendly to the GOP, pointing that out cannot account for the trendline: Two weeks ago, Rasmussen found Deeds within the MoE, trailing by only 2% - a survey launched the narrative of the Democrat’s comeback. What’s perhaps worst for Deeds is that Rasmussen’s poll leaves him no clear path to close the gap: 51% of respondents (an impressive share) say the story of McDonnell’s master thesis is important in terms of their November vote. And yet, despite his remarkable success at making this a huge campaign story, Deeds trails by 9%! What more can he hope to do?

In New Jersey, by contrast, a Quinnipiac poll finds encouraging news for Corzine has received in months: The governor trails 43% to 39% - the smallest deficit he has faced in a Quinnipiac poll since November 2008. His favorability rating remains truly dismal (34/56) but Christie is clearly dipping. Consider this: Excluding Neighborhood Research polls (which are finding a bizarrely high level of undecideds) and Democracy Corps poll (which have had far more friendly results for Corzine than other pollsters), the Republican had not dipped as low as 43% in any poll since April!

As I have repeatedly pointed out, the biggest reason I have trouble envisioning Democrats keeping New Jersey is that Corzine is stuck in the 30s range - and that is again the case in this poll. But here’s the second reason Quinnipiac’s survey is good news for the governor: Chris Daggett reaches 12%, a 3% boost over Quinnipiac’s previous poll. The higher Daggett reaches, the more conceivable it is for Corzine to claim victory with just 39-42% of the vote.

Arkansas: Lincoln trails 4 Republican rivals

Keeping in mind that not all pick-ups are equal in terms of altering the balance of power - if Blanche Lincoln were to lose next year, it wouldn’t prove a particularly consequential blow to her party’s agenda considering her actions this year - let’s turn to a new Rasmussen poll that confirms that we should put her on the list of highly vulnerable incumbents. She trails state Senator Gilbert Baker 47% to 39%, state Senator Kim Hendren 44% to 41%, businessman Tom Cox 43% to 40% and businessman Chris Coleman 43% to 41%.

Any senator who trails all challengers irrespective of their profile, name recognition or experience is clearly facing a massive re-election problem. An important note: Once again, I do not for the life of me understand where Rasmussen gets its name recognition numbers: I refuse to believe that more than 60% of Arkansas have an opinion on Cox, Coleman and Baker. Last month, PPP found that 23% of voters had an opinion of Coleman and 22% of Baker. That sounds much more realistic.

Yet, it apparently has little effect on the match-up numbers: PPP also had Coleman and Baker leading, thus confirming Rasmussen’s finding that Lincoln is so vulnerable as to trail little-known opponents. On the other hand, a mid-September Research 2000 poll found far sunnier numbers for the incumbent, though she was still vulnerable. More polls will be needed to figure out the extent of Lincoln’s vulnerability.

Arizona: Second poll in two weeks finds that Goddard is front-runner

A race we have talked relatively little about is shaping up to be one of the Democrats’ top pick-up opportunities thanks to Attorney General Goddard’s popularity: In a new Rasmussen poll, his 54/38 favorability rating is far superior to Governor Jan Brewer’s 42/54 and former Governor Fife Symington’s 36/54. He leads 42% to 35% against Brewer and 44% to 37% against Symington. Those margins are actually smaller than those found by PPP last week, but they are an undeniable sign of strength for a challenger.

Brewer and Symington are arguably weaker candidates than other potential Republican nominees; Brewer because she has failed to impose herself since being elevated governor in early 2009, Symington because of the corruption scandal that forced him out in the 1990s. But for either of them to be defeated would mean a lower-profile Republican nominee, so Goddard’s name recognition and personal popularity would keep him the front-runner even if the GOP was to get rid of Brewer and Symington.

Maine: Gay marriage finally enjoys lead

Two weeks ago, the first and only poll of Maine’s Question 1 found worrisome news for gay marriage proponents: The “Yes” had a narrow lead. But a new poll conducted by Democracy Corps has far more encouraging numbers: 50% of respondents say they will oppose repealing the gay marriage law while 41% say they’ll vote for it.

The survey’s primary purpose seems to have been to gauge Maine voters’ feelings about their two senators in the context of the health care debate. And it does not look like progressive groups have been successful at turning this blue state against Olympia Snowe and Susan Collins 54% say they’ll probably or definitely vote for Collins when she runs for re-election (versus 32%) while 60% say the same of Snowe. Matched-up with a generic Democrat, Snowe leads 56% to 28%. Since I think few people who follow electoral politics expect Snowe and Collins to ever face much of a challenge - if a sitting congressman could not endanger the weaker of the two in 2008, how could Democrats succeed? - these numbers won’t come as much of a surprise.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Public option might be dead in Finance, but it remains alive in Congress

In a debate with unusually clear ideological faultlines, the Senate Finance Committee spent hours yesterday debating whether to include a public option in its version of health care reform. As had been expected, proponents of a public plan failed to rally a majority of the committee in two high-profile votes. This guarantees that the Finance Committee’s bill will not contain a public option, in contrast to the legislation’s all four other versions that passed other congressional committees over the summer.

Yet, in no way does this mean that the public option’s overall prospects are dead. The Finance Committee’s mark-up was never supposed to be the stage at which the public option might win the day; more propitious opportunities await.

It will certainly not be easy for the public option to work its way in the final bill, especially given reports that Barack Obama and Harry Reid are likely to side with those looking not to include it during behind-the-scenes negotiations. But numerous factors (the growing number of Senate Democrats who are on the record supporting a bill with a public option, House progressives’ continued insistence they’ll oppose a public option-less bill) mean that the floor debate or the conference committee will be far more decisive battles than today’s two votes.

Conrad, Lincoln, Baucus: 3 Democrats kill public option in committee

Yesterday, the first vote came on an amendment proposed by Jay Rockefeller; it would have implemented a robust public option based on Medicare rates. 5 Democrats joined the committee’s 10 Republicans in opposing the amendment - Max Baucus, Kent Conrad, Blanche Lincoln, Tom Carper and Bill Nelson - while 8 voted in favor of it, including Ron Wyden and Jeff Bingaman. Next came Chuck Schumer’s amendment implementing a weak “level playing field” public option. This time, Nelson and Carper voted yes; but Conrad, Lincoln and Baucus’s opposition led to the public option’s 10-13 defeat.

Had two of these three senators voted for it yesterday, the issue would have been resolved for good: All committees would have passed legislation with a public option and that would have all but guaranteed that the final bill debated on the floor would include it as well. As I review below, there is no clear evidence that a bill with a public option lacks the votes for passage; so if health care reform ends up lacking a public plan, no Senators - not even Lieberman or Ben Nelson - will be as responsible as Lincoln, Conrad and Baucus.

Two twists: (1) Lincoln did not bother showing up or explaining her vote, which means that Conrad was the loudest Democratic opponent of a public option in today’s proceedings, mounting a full assault on Rockefeller’s proposal to tie the public option to Medicare rates. (2) Max Baucus used bizarre logic to explain his opposition. He explained that he was in full support of a public option but that he opposed it because it lacked the votes to pass. “My first job is to get this job across the finish line,” Baucus said. “I fear if this provision is in this bill as it goes out of this committee, it will jeopardize real meaningful health reform.”

We now know that the public option would get a majority in the Senate

Public option proponents did get one piece of excellent news during today’s proceedings: In voting “yes” to Chuck Schumer’s amendment, Carper and Bill Nelson went on the record for the very first time as supporting some version of a public option. Until now, both had been noncommittal. This does not mean that they would not prefer some other reform to be implemented (Carper is now trying to push potential compromises like co-ops or state-based public plans) but it certainly suggests neither would vote against whatever reform Democrats end up bringing to the Senate floor.

This certainly helps clarify the situation as to where the public option, and with it the odds of a relatively progressive bill, stand in the full Senate. Based on the Washington Independent’s excellent overview of every senator’s stance on the issue, we can now say that the public option-inclusive bill would clear a majority in the U.S. Senate. (The count lists 47 supporters, but Carper, Bill Nelson and Claire McCaskill are all on record supporting a public option in their respective committee, which brings the total to 50; with Joe Biden’s tie-breaking vote, that means 51.)

What this means: Health care reform that includes a public option would be sure of getting the votes it needs to pass if Democrats chose to push it through reconciliation. Now, there are certainly other reasons not to take that route, but this is important to keep in mind as I am still reading that the public option would not even be sure of getting 51 votes.

What about 60 votes? Only 6 Dems could conceivably oppose cloture

50 senators are on record supporting a bill with a public option, which means 10 either oppose it or are on the fence - and none of them has promised to at least vote for cloture. They are: Ben Nelson, Joe Lieberman, Landrieu, Conrad, Lincoln, Evan Bayh, Mark Begich, Jon Tester and Mark Pryor.

Based on recent comments by Tester and Pryor (see the Washington Independent’s overview) they have left themselves little cover to oppose a constrained public option like that proposed by the Schumer amendment. It’s also difficult to see Baucus voting to filibuster health care reform due to his role in drafting the legislation and to his insistence that he only voted against the public option today because he does not think it could eventually get 60 votes. I also find it improbable that Begich would take the risk of becoming a pariah within his own party just 10 months after being sworn in for his first Senate term.

That leaves us with only 5 Democrats who could plausibly choose to join a GOP filibuster of a bill containing even a weak public option: Conrad, Lincoln, Landrieu, Ben Nelson, Lieberman and Bayh.

When you hear that the Senate does not have the votes to pass the public option, we are not talking about the prospect of the bill failing to be adopted: While all 6 of these senators could very well vote against final passage, we already know that their votes will not be decisive. So what we are talking about is one or more of these 6 senators going as far as to vote against cloture and for a GOP filibuster.

We can debate how much credence to give to that possibility - to my knowledge, only Nelson has explicitly raised the possibility of opposing cloture - and I personally still find it hard to imagine these typically cautious senators taking the gigantic political risk of joining such a small, exposed group to prevent their own party’s health care reform from moving on to an up-and-down vote.

Deciding floor bill, floor debate, conference: What is next for PO

That a bill containing public option still has a path to 60 cloture votes does not mean that the Democratic leadership will choose to go down that route. Yet, whether or not congressmen vote on legislation that includes a public option will soon entirely depend on Barack Obama and Harry Reid. Once the Finance Committee passes its bill, its chairman Max Baucus will meet with HELP Chairman Tom Harkin and Harry Reid to shape the bill that will be introduced on the floor of the Senate; the White House will have a seat at the table.

Most reports suggest that Reid and Obama will side with Baucus over Harkin, which would mean that the bill that would advance to the Senate floor would not have a public option. (It will then be interesting to see whether Harkin gets any concessions from centrists in return.)

The next step will be the floor fight over a public option. I am somewhat unclear as to how many votes would be needed here. If the bill already contains a weak public option, it does not look that Republicans would have the votes to strip it since 50 Democrats (plus Biden) are on record supporting it. If it does not, however, I believe it would take 60 votes for an amendment introducing it to pass (it’s next to impossible for a public option standing on its own to get that much) but I have also read that 50 would suffice.

If the bill finally adopted by the Senate does not contain a public option, a final opportunity to include it will occur at conference since the House legislation is likely to have a public option. A same scenario would occur here, with Senate negotiators and House negotiators clashing with the White House in a position to arbitrate. This time, however, the left would have a stronger hand because about 60 House Democrats are still threatening to vote against a public option-less bill.

For the leadership, this certainly raises the stakes of once again dumping the public option, and much will depend on the Congressional Progressive Caucus’s credibility. Will the White House take them seriously enough to think that removing the public option would cause a bigger headache that including it?


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

SUSA brings brutal numbers to Virginia Democrats

Is SUSA’s latest poll of Virginia’s Governor’s race an outlier? Or is it an accurate reflection of the dynamics that might have seized the state over the past few days, perhaps due to reactions to the first debate opposing Bob McDonnell and Creigh Deeds? Whatever the answer turns out to be, it is sure to cause some sleepless nights at Democratic headquarters since it all but destroys the poll-fueled narrative of a Deeds comeback: SUSA finds the Republican nominee leading by 14% - 55% to 41%.

Adding insult to injury for Deeds, SUSA finds that Republicans are leading by slightly smaller margins in the two other statewide races - Bill Bolling is up by 13% in the Lieutenant Governor race, Ken Cuccinelli is up by 11% in the Attorney General race. Conventional wisdom is that Deeds has more of a chance of winning than Jody Wagner and Steve Shannon, so this differential makes it harder for Deeds to dismiss this poll as overall skewed towards the right.

This is the third consecutive SUSA poll with McDonnell up double-digits: He led by 15% in July and by 12% four weeks ago. While that might suggest SUSA’s numbers are too GOP-friendly, its summer numbers were in line with those of other pollsters: McDonnell was up by double-digits in other summer surveys (PPP, WaPo poll).

But September surveys had found a narrow race so this new survey contradicts polls like Insider Advantage this week-end (4% margin) and PPP this morning (5% margin). Consider that: SUSA is the only pollster since mid-August to find McDonnell up by double-digits and the only pollster since the master’s thesis story gained steam to have him leading by more than 7%. And here we’re talking the double of that?

That said, what makes it hard to simply dismiss the poll as an outlier is that the poll’s internal numbers are certainly not aberrant based on what we know of this race and there is no mystery as to where McDonnell’s lead comes from:

  1. He has a gigantic lead among independents (59% to 35%); that is an improvement for him over his 11% early September lead. (That poll was also conducted after the Washington Post broke the master’s thesis story.)
  2. The pool of likely voters is far more GOP than the electorate at large. 51% of respondents said they voted for McCain in 2008 with 44% saying Obama; Republicans outnumber Democrats 37% to 32%; and to a low a share of respondents say they come from Northern Virginia.

Independents heavily leaning towards McDonnell, a demoralized Democratic base - these are findings all pollsters found throughout the summer, notably PPP and The WaPo poll. Since then, these institutes had found Deeds energizing Democrats; but for SUSA, it’s as if the entire month of September had not happened! If SUSA’s turnout model resembles what is truly brewing on the ground, Deeds has no chance to win in 5 weeks - and the very fact that the possibility exists that the motivation differential is still this big is great news for the GOP.

(While this morning I wrote that PPP trendlines suggested the master’s thesis story helped Deeds, that was PPP’s first survey of the race post-WaPo article. On the other hand, this is SUSA’s second survey since that story: Their early September poll did find the turnout differential shrinking, and this new poll has the electorate’s composition remaining stable.)

Yet, Democrats can take comfort in the fact that all other recent polls have found a tightening race. Whatever they think of SUSA’s  poll, what is important for them to recognize is that they don’t need to trust it to follow the only possible conclusion that can be drawn from such numbers - that ensuring high Democratic turnout has to remain Deeds’s primary concern over the next few weeks. I said just as much this morning based on PPP, which painted a far more positive situation for Deeds.

At this point of the campaign, what other choice does he have but to keep hammering the master’s thesis story - at least in Northern Virginia? Other polls have found that this is making a difference, so it is perfectly advisable for Deeds to do so. In fact, he just released a new ad devoted to the issue:


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Deeds gains ground in two polls, features Warner in ad

A lot of people were wondering when Creigh Deeds would finally seek to milk his biggest asset, namely the popularity of Virginia’s past two Democratic governors: Incumbent Tim Kaine and his predecessor, now-Senator Mark Warner. Virginia voters traditionally vote for whichever party is not controlling the White House, but Democrats are hoping that their brand is strong enough at the local level that they can defy that history and convince voters to prolong Warner-Kaine’s legacy by another four years.

Yesterday, Deeds unveiled what I believe is the first ad to feature a direct plea from either of these two men, as Mark Warner urges voters to prolong his legacy of centrist governance:

“Do we move Virginia forward by continuing the pro-business economic policies I helped put in place or do we go backwards with the failed economic approach that ruined our economy?” asks Warner in the ad. And he goes on to frame the contest’s ideological opposition in a way any national Republican would be happy to embrace: “Creigh Deeds keeping taxes low and controlling spending is the best way to get Virginia is the right way to get Virginia the best place to do business.”

With five weeks still to go in this campaign, there is more than enough time for Deeds to make ample use of Warner and I expect at least some undecided voters to be moved towards the Democratic camp on the basis of Warner’s appeal. After all, as testified by his huge victory in last year’s Senate race, Warner is strikingly popular enough among Virginia’s electorate - particularly in the rural areas in which Deeds is hoping to make inroads.

Furthermore, Warner is popular enough among Virginia Democrats at large that his involvement could help excite the liberal base. That said, there is no question that other state politicians might have been a better fit for that, which is why Deeds’s failure to secure the endorsement of former Governor Doug Wilder last week was an important disappointment. Wilder cited Deeds’s opposition to gun control as a reason not to back him, and Deeds better hope this is not a preview of disinterest for this contest. While polls suggest that the turnout differential is shrinking, Deeds needs the Democratic base still more excited to overtake McDonnell’s lead.

At least, two new polls confirm that Deeds is moving in the right direction. The first, an Insider Advantage poll released over the week-end, has McDonnell leading 48% to 44%, an edge that’s just outside of the 3.8% MoE. This is Insider Advantage’s first poll of the race, so there is no trendline, but there is no question that a 4% margin is on the smaller end of the leads McDonnell has posted over the past few months.

The second is a PPP survey that comes with a bit more detail with which to analyze the results. The topline numbers, first: McDonnell leads 48 to 43, which is an improvement for Deeds over his 14% deficit in July and his 7% deficit in August.

This poll seems to confirm what other polls have suggested: The story of McDonnell’s master thesis is not about flipping his supporters against him but about convincing apathetic Democrats that this contest is really important. Deeds has gained ground primarily because the sample now contains a larger share of Obama voters - something other pollsters have also found, confirming that this is probably not just statistical noise.

McDonnell now enjoys the support of 96% of Republicans, a rare level of intraparty support. That’s obviously good news for him, but it is also somewhat worrisome: McDonnell has no little room to grow. His prospects of holding on to his lead now depend on whether he can control his image among independent voters, and in that regard one key internal has to be worrisome to his camp: His unfavorability rating has gone from 31% to 42%.

Even if many of the voters who now view him unfavorably were unlikely to back him anyway, this will complicate McDonnell’s efforts to secure the support of the remaining undecided voters. As importantly, that many Democrats now actively dislike McDonnell means they will now make sure to vote, and perhaps convince like-minded but even more apathetic voters to do so as well.

A little digression on Tim Kaine

It is no coincidence that Deeds’s ad features Warner, as he has been far more eager to link himself to the former governor than to the current one. In a time of economic crisis, that’s understandable but it’s worth noting that Kaine has not experienced the sort of collapse suffered by many of his colleagues. It will be interesting to see whether Kaine appears in a later ad of Deeds’s.

More generally, Kaine is in a somewhat difficult political position. Once he leaves office, he will still be DNC chairman for 3 years but, in contrast to his predecessors, he has few choices as to how he could stay in elected politics. When George Allen left office, one of the state’s senators was a Democrat so Allen ran against him (and won); when Mark Warner left office, the presidential race was open and one of the state’s senators was old and soon after chose to retire, giving him plenty of choices.

With the president and both of Virginia’s senators all first-term Democrats, Kaine cannot run for the White House before 2016 or for Senate before 2018. That leaves his only option to attempt a return to the Governor’s Mansion in 2013. (Whoever wins in November will be term-limited.) With Democrats  underdogs in this year’s LG and AG races, Kaine might not have that hard time positioning himself as the obvious nominee.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Polls show GOP boost in Ohio and Michigan, Jerry Brown’s strength in California

OH: Rasmussen gives Portman first lead in 9 months, Kasich first lead ever

Ever since George Voinovich retired, all but the very first of Ohio’s Senate polls found both Democratic candidates with a solid lead over Republican Rob Portman - one that had extended to as much as 15%. But as is often the case, Rasmussen brings comfort to Republicans by finding a far more competitive race: Portman gets 41% against Lieutenant Governor Lee Fisher’s 40%, and he is ahead of Secretary of State Jennifer Brunner 40% to 38%. Both margins are well within the MoE, but they represent substantially stronger Republican performances than in other polls.

This is Rasmussen’s first poll of the race, so there is no trendline. In fact, Ohio is rarely polled - especially when compared to a state like New York, which is frustrating considering the high stakes of the Buckeye State’s contests. It’s important to note that Rasmussen contradicts a central finding of other Ohio polls. There is here little name recognition differential between the Democratic candidates and Portman; yet, other polls found Brunner and Fisher far better known. (This is not the first time Rasmussen has found some puzzling name recognition results.)

Rasmussen also tested the Governor’s race, and here again the results are very encouraging for Republicans: Plagued by a mediocre-to-bad approval rating (47% to 50%), Governor Ted Strickland is behind former Rep. John Kasich 46% to 45%. This is the first poll ever released to find Kasich posting any sort of lead, and though the margin is well within the MoE there is no question that this is not favorable territory for any incumbent. Over the summer, PPP and Quinnipiac both found Strickland leading by low single-digits, so this poll does not come out of the blue.

CA: Brown runs far stronger than Newsom

In the heels of its poll finding Barbara Boxer building a lead in the Senate race, Rasmussen released that survey’s gubernatorial numbers. The results should please everyone in the race but San Fransisco Mayor Gavin Newsom. While former Governor Jerry Brown has comfortable leads against the 3 Republican candidates (44% to 35% against Meg Whitman, 44% to 34% against Tom Campbell, 45% to 32% against Steve Poizner) Newsom trails against all three: 42% to 36% against Campbell, 41% to 36% against Whitman and 40% to 36% against Poizner.

I don’t know whether the poll’s most surprising result is the huge differential between Newsom and Brown (Research 2000 recently found Brown running stronger, but nothing resembling Rasmussen’s findings) or the fact that Campbell enjoys a bigger lead than his two Republican rivals. Campbell is not as high-profile as Whitman and Poizner, and he has gotten less media attention - at least when it comes to a national audience. But with Whitman truly to respond to the jaw-dropping revelation that she did not vote for 30 years, Poizner and Campbell definitely have an opening to hammer her; the former is already trying with this hard-hitting new ad.

NJ: Democracy Corps shows Corzine gaining

For months, Democracy Corps has found the most favorable results for Jon Corzine but never had the New Jersey Governor been so close to his competitor: Chris Christie is up 40% to 39%, with Chris Daggett at 11%. Do with the margin what you will (as long as no other pollster finds Corzine within the MoE, whether PPP, Monmouth, Quinnipiac or Franklin, I’ll have trouble believing that Corzine has tied things up), but the trendline is certainly interesting since it suggests Corzine is slowly gaining ground even within Democracy Corps’s turnout model. The evolution is small, however: Christie led by 3% three weeks ago.

MI: Democrats face uphill climb

No one doubts that Democratic Lieutenant Governor John Cherry will have a tough fight on his hands in 2010, but two new surveys suggest Michigan’s governorship is one of the GOP’s top pick-up opportunities next year:

  • An Inside Michigan Politics survey has Cherry trailing Oakland County Sheriff Mike Bouchard 41% to 38%; he does lead businessman Rick Snyder 42% to 34%. IMP only tested Cox in an unexpected 3-way race involving Cherry and Democratic state Speaker Andy Dillon; Cox leads Cherry manages 35% to 33%.

The polls test different match-ups, so it is difficult to conclude anything electability-wise. Yet, Cox can point not only to his 13% lead but also to the fact that he comes on top of both polls’ primary trial heats. He is in a virtual tie with Rep. Hoekstra in one; he has a somewhat larger lead over Hoekstra in the latter. Also: Both institutes find Rick Snyder with only 2% of the GOP primary, but he should not be underestimated: He just surprisingly won the high-profile straw poll at Mackinac Island’s Republican Leadership Conference. This could help him get more attention, raise more money.

CO: A first look at Senate primaries

In what is the first poll testing Senator Michael Bennet’s vulnerability in the Democratic primary, Republican institute Tarrance Group found the incumbent in a dangerous position against former Speaker Andrew Romanoff: Bennet leads 41% to 27%, a certain proof of vulnerability. Obviously, Bennet cannot be held at the same standard as other senators, for whom a 14% lead in a primary would be verging on the catastrophic: Since his name recognition is still relatively low, Bennet has more room to grow than someone like Arlen Specter, despite the fact that the Pennsylvania senator is posting similar numbers.

On the Republican side, former LG Jennifer Norton crushes DA Ken Buck 45% to 15%. It’s still unclear how this race will shape-up: Buck is clearly to frame it as a conservative-versus-establishment battle, so we’ll have to see how Norton seeks to position herself. In the gubernatorial primary, former Rep. Scott McInnis starts far ahead of state Senator Josh Penry; however, McInnis might not be the establishment favorite since Penry has earned a lot of good press in conservative circles as a GOP rising star. He will have to battle McInnis’s superior name recognition, however.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Scozzafava under pressure: Ads leave her stuck in crosshairs, conservatives rally around Hoffman

[Updated with Fred Thompson and Club for Growth's endorsements] Given that John McHugh was so recently confirmed to the Cabinet and that the candidates for the upcoming special election just recently started airing advertisement, it’s hard to believe that the race is already in its final stretch: There is only 5 weeks left until voters put an end to NY-23’s frustratingly confusing contest.

Late last week, we got our second poll of the race. Once again, it is a survey commissioned by a group that has an interest in seeing Conservative Party nominee Doug Hoffman in a competitive position. Last time, it was Hoffman’s own campaign that leaked its internal numbers; this time, it’s the Club for Growth. If the first poll showed that this was a 3-way race, this second one has all three candidates within the margin of error: Dede Scozzafava gets 20%, Bill Owens and Doug Hoffman receive 17%.

We are in the bizarre situation of never having seen a public poll or an internal poll for Democrats or Republicans. Yet, the bottom line is that neither Scozzafava nor Owens, neither the DCCC nor the NRCC have chosen to release the results of their own surveys. That’s especially telling when it comes to Scozzafava: She would benefit greatly if she could convince the media that Hoffman was not a credible contender and should not be treated as such, so if one of her polls had Hoffman with a low percentage she presumably would have leaked it by now.

Conservatives rally against Scozzafava

Both Hoffman’s internal poll and the Club for Growth survey had a large share of undecideds, which is not surprising considering that few voters have probably been introduced to more than one of these candidates - if they have even know of Scozzafava. But that might soon change (and with it, poll numbers) as all camps are finally starting to accelerate their advertisement campaigns. I highlighted Owens’s first ad, but everyone has by now joined the fun, including national parties.

And as is to be expected in a 3-way race in which the conservative candidate’s path to victory depends on convincing right-wing voters that the Republican party’s actual nominee is a closeted Democrat, Scozzafava is in the cross hairs. Ads are being released left and right, all attacking the GOP nominee.

What’s most interesting is that Democrats are voicing the sort of arguments that should help Hoffman, for instance blasting Scozzafava for having supporting tax hikes. There’s no question that this sort of attack is more likely to appeal to voters who lean conservatives - those Hoffman is trying to convince Scozzafava is too liberal to get their vote. (It obviously makes sense for Democrats to boost Hoffman’s message: If the conservative grows too strong, it could obviously become a problem, but the bottom line is that his votes will come from Scozzafava, who is for now Owens’s main obstacle.)

Here’s the DCCC’s first ad of the race. The spot starts with ethical charges, accusing Scozzafava of failing to pay back taxes on a company she has ties to, before veering to an attack on the Republican’s record on tax increases:

Meanwhile, Hoffman’s campaign is out with a spot that compares Scozzafava with an Elvis impersonator! The ad says: “An Albany politician, liberal Republican Dede Scozzafava, twice voted for gay marriage. She supported that $180 million mortgage bank bailout. And she backed job-killing higher income taxes. That’s liberal. That’s Dede Scozzafava.”

In the absence of extensive polling of this race, it is hard to know how much Hoffman’s message is resonating among the district’s Republican voters; after all, Scozzafava represents a share of the district in the state Assembly, so some voters already know her. But it is very plausible that, if Hoffman brings it up enough, her vote in favor of gay marriage could convince a substantial number of Republicans not to vote for her. There is ample evidence that gay marriage is no longer an effective issue against Democrats who favor it (see the recent legislative special election in Iowa), but what is true among the electorate at large is not necessarily true among GOP voters.

One big question, of course, is whether Hoffman can hammer his simple “Scozzafava is a liberal” message loud enough to be heard. As such, the involvement of outside groups could be determinant: All eyes are on the Club for Growth to see whether they will get involved. “We’re looking very closely at the race and these poll results clearly show that New Yorkers may deliver a stunning rebuke to the big spenders in both the Republican and Democratic establishments,” said the Club’s executive director last week.

[Two major updates: If there was any question as to whether national conservatives will get involved, they have just been answered. The Club for Growth has just announced it will endorsed Hoffman - a major development that will put Scozzafava in even more difficulty. It will at the very least mean a substantial financial boost for Hoffman, and the Club has proven in past Republican primaries that it means business. Also, the Watertown Daily Journal reports that former presidential candidate Fred Thompson has endorsed Hoffman as well. Will still more big-name Republicans get involved?]

Owens continues to run as independent, NRCC attacks him as gift for Pelosi

If voters are trying to think through who is the ‘true’ Republican in this race - whatever that means to them - they might also need to figure out how Bill Owens fits with the other two contenders. If Owens’s first ad bore no mention of any party affiliation, his second one goes even further in positioning him as a non-partisan candidate (reminder: Owens was a registered independent until he was selected as the Democratic nominee). The spot features endorsements by two local officeholders, the first a Republican, the second a Democrat.

Just as I argued last week, I continue to think that it is a big tactical mistake for Owens to completely obscure his party affiliation and exclusively appeal to independent voters. I refer you back to that post for a long list of reasons, but the bottom line is that he cannot be sure that partisan Democrats will turn out in a special election, that Scozzafava is far better placed to win moderate voters - especially once Hoffman gets done with her - and that in a 3-way race he could win on the basis of liberal-leaning voters alone.

Since he is doing no effort to convince Democrats they should care about electing him, the DCCC should be relieved to see the NRCC is doing that job for him. National Republicans released a somewhat bizarre attack ad last week: The spot features a cartoon character of a gift-wrapped present, presented alternatively as “a present from Washington” and as a “gift from Pelosi - with love.”

The GOP might be guilty of overconfidence here. We know that Republicans are convinced that Democrats are heading right off the cliff - or at least towards a repeat of the 1994 nightmare. But in the absence of compelling evidence that voters are ready to turn against the Democratic agenda, is it really a good idea for them base their attacks on Owens’s party affiliation considering Obama won this district by 5%? That might not make it New York City-like Democratic, it’s certainly a reason not to think that a dancing gift-wrapped present will be enough to convince voters not to choose Owens.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Weekly 2010 update: Ron Kind’s decision and Jon Porter’s rumors dominate midterm news

This past week was relatively quiet on the midterm front, and there certainly were no game-changing announcements. The highest-profile 2010 news was arguably Rep. Ron Kind’s decision to run for re-election. That led me to reflect on House Democrats’ ability to hold the number of open seats they need to defend to a minimum, but Kind’s move also has obvious consequences in Wisconsin’s gubernatorial race by solidifying Lieutenant Governor Barbara Lawton’s hold on the Democratic nomination; Milwaukee Mayor Tom Barrett is the only politician who could make that race competitive, and he has yet to signal what he is thinking.

The contest that came closest to a radical makeover this week was Nevada’s Senate race as rumors suddenly erupted early this week that former Rep. Jon Porter was reconsidering his decision not to challenge Harry Reid. The GOP has been left with a B-list roster whose competitiveness entirely depends on Reid’s unpopularity. The senator’s numbers are dismal enough that it might very well not matter who Republican nominate, but there’s no question that recruiting Porter would have been a major get for the NRSC: It would ensure a strong nominee and potentially clear the primary field. Yet, the week ended as it had began: Porter reiterated that he would not run.

In other states, new GOP candidates jumped in already crowded races. In Arkansas, a bizarrely large list of low-profile Republicans are seeking to take advantage of Blanche Lincoln’s vulnerability and of the absence of a formidable GOP challenger: financial adviser Buddy Roggers became the sixth Republican to announce a run. In New Hampshire, it could become tough for conservatives to rally opposition to Kelly Ayotte if the field keeps getting more crowded; businessman William Bennie is the latest name to circulate as a potential candidate.

In Arizona, Governor Jan Brewer landed her first official primary opponent - an unsurprising development given that Brewer did was elevated to her position and is burdened by a low approval rating: Paradise Valley mayor Vernon Parker officially announced his candidacy. He should be a credible contender, though it seems fairly certain that other Republicans will still jump in. More surprisingly, there is now buzz that Maryland Governor Martin O’Malley could face a primary challenge from Prince George’s County Executive Wayne Curry; with few people betting on former Governor Bob Ehrlich attempting a comeback, Curry could be a more threatening challenger than anyone O’Malley might face in the general election.

As always, I list all the changes I have logged in during the week to the “retirement watch” and recruitment pages. Written in red are those politicians who announced their definite plans rather than simply expressed interest or stroke speculation. First, updates to Retirement Watch:

Will retire No one
Will not retire Rep. Ron Kind (D, WI-03)

Second, updates to the Senate recruitment page:

AR-Sen, GOP financial adviser Buddy Rogers announced run
MA-Sen, Dem City Year head Alan Khazei announced run
MA-Sen, GOP/Indie Curt Schelling will not run
NH-Sen, GOP businessman William Binnie added to list
NV-Sen, GOP former Rep. Jon Porter reconsiders run, rules it out again

Third, updates to gubernatorial recruitment:

AZ-Gov, GOP Paradise Valley mayor Vernon Parker announced run
MD-Gov, Dem Prince George’s Co. Exec. Wayne Curry added to list
PA-Gov, Dem ex-Rep. Joe Hoeffel plans to run
OR-Gov, Dem County Chairwoman Lynn Peterson ruled out run
WI-Gov, Dem Rep. Ron Kind ruled out run

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Three recent developments strengthen Boxer’s hand in race against Fiorina

Though I have been skeptical that the GOP can make Barbara Boxer break much of a sweat, Carly Fiorina’s decision to challenge Boxer combined with a July Rasmussen poll that showed the incumbent leading by only 4% gave Republicans hope they could score a pick-up in this race. Yet, new developments have strengthened the hands of those who think there isn’t much to see here.

1. A new Rasmussen poll

No other pollster has found results like Rasmussen’s July numbers. Earlier, the Field Poll and PPIC had found Boxer enjoying a solid approval rating and crushing both Fiorina and Arnold Schwarzenegger; later, Research 2000 contradicted Rasmussen, showing Boxer ahead of Fiorina by 19%. Unlike in other contests, where Rasmussen’s numbers might look more favorable to the GOP than those of other pollsters but only marginally so, Rasmussen was here the only one to show Boxer in any way endangered.

They just released a new poll. Boxer has a good favorability rating - 51% to 42% - especially when compared to the mediocre numbers of Fiorina (32-35) and Chuck DeVore (31-37). Against Fiorina, she leads 49% to 39%; against DeVore, 46% to 37%. Sure, these numbers still suggest Boxer is vulnerable but the bottom line is that the one pollster that has ever found her not enjoying a dominating lead - the one pollster who sparked the narrative of an endangered Boxer - now finds her comfortably ahead.

2. Fiorina reportedly will not self-fund

One major reason Fiorina’s candidacy was so appealing to the NRSC was her ability to self-fund her candidacy. California is too expensive a state for national Republicans to invest any money - at least not under they get convincing proof that their effort will be worthwhile. With Boxer the clear favorite to win, Republican candidates won’t find easy fundraising; so how can they introduce themselves to voters if they don’t have a personal bank account to rely on? Also, Boxer looks solid enough that her numbers won’t sink unless she faces a barrage of ads; so can the GOP hope to beat her unless it recruits a wealthy candidate?

The GOP’s two highest-profile gubernatorial candidates - Meg Whitman and Steve Poizner - look certain to spend millions of their own money in order to win next year, and Fiorina was considered likely to follow their path. Not so, according to new reports that seem confirmed by NRSC officials; she’ll make use of some personal money, but nowhere near the extent Whitman and Poizner will.

As a veteran of the McCain campaign and as the former CEO of Hewlett-Packard, Fiorina should have the national and business networks to be finally competitive; but I still have trouble seeing her building the financial strength she’d need just to endanger Boxer - let compete with her. And now that it looks like the NRSC will have plenty of better opportunities across the county (CO, CT, NV, AR, IL and perhaps DE), it looks all the more likely California will once again fall by the wayside. Financial constraints makes it hardly viable to envision a 7th offensive.

3. Primary troubles

As long as the NRSC seemed committed to making California competitive and as long as we thought Fiorina would just write herself as many checks as she needed, Assemblyman Chuck DeVore looked unlikely to cause much drama in the GOP primary: The financial disparity alone made him the underdog against Fiorina.

But times are changing: The NRSC is paying attention to other states, finances could be more balanced, Fiorina is losing use of the electability argument (Rasmussen has her falling behind, not to mention that DeVore actually polls better than her in that survey). Worst still for her prospects: California looks like it could become a new front in the war some conservatives are waging against the NRSC. Last week, Red State hit Fiorina just as it has been criticizing Ayotte and Crist, other Republicans for whom the NRSC has clearly signaled its preference.

California might be staunchly blue, but conservatives dominate the GOP primary and that has led the party to repeatedly nominate candidates that have been too far to the right - for instance in the 2002 gubernatorial race, when Bill Simon beat former LA Mayor Richard Riordan. The phenomenon could be accentuated if state Republicans decide to make their nomination process a closed primary, as is being discussed.

In short: The ingredients are there for Fiorina to experience serious primary troubles against DeVore. If it’s hard to see Boxer that vulnerable against Fiorina, she’ll be all the more favored against DeVore, whose conservative politics should be as odd a fit for California as those of most Republicans who’ve been nominated statewide in the past decade. (It’s no coincidence that their one victor, Schwarzenegger, did not have to go through a Republican primary.)

More trouble for state GOP: Whitman didn’t register to vote for nearly 30 years

I am not sure how much candidates are ever hurt by revelations about their shaky voting history, but Meg Whitman’s commitment to the electoral process is weak to a truly stunning degree. The Sacramento Bee launched an extensive investigation across the many states Whitman has lived in. Their finding: Whitman, who turned 18 in 1974, did not register to vote until 2002!

Even after her registration, she skipped many elections - including the 2003 recall vote and the 2005 special election called by Schwarzenegger. She did not start voting regularly until 2008, when she co-chaired Mitt Romney’s presidential bid and started to prepare her own gubernatorial campaign.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Why predictions of ‘10 gloom are off: By recent standards, Dems have few open seat headaches

For all the talk about House Democrats heading towards big losses in 2010, there is a major reason a red wave is unlikely: The party won’t have that much to worry about in terms of congressional retirements.

It might still be early in the cycle, but we can already say that their open seat headaches will look nothing like those that plagued the losing party of 1994, 2006 and 2008 - all cycles in which retirements were a huge factor. Needless to say, this will make it much harder for the GOP to score big gains. In a wave-like election, open seats provide easy pick-ups at little cost whereas incumbents are hard to beat even in the most favorable of environments.

Let’s review recent history:

  • 1994: Democrats lost 22 open seats - nearly 40% of their total loss.
  • 2006: At least 15 GOP-held open seats were considered competitive; the party lost 8 of them and spend a lot of money defending the rest (which included IL-06 and MN-06).
  • 2008: 18 GOP-held open seats were considered competitive; Democrats won 11 of them - nearly half of their net gain.

In 2010, it would be a big surprise if the DCCC has to defend more than 6-7 competitive open seats - and even that many would take a few unexpected retirements.

For now, 7 House Democrats have announced they won’t run for re-election. 3 represent heavily African-American districts in which the GOP has no chance: AL-02 (Artur Davis), FL-17 (Kendrick Meek) and IL-07 (Danny Davis). A fourth open seat is that of Neil Abercombie in Hawaii. Republicans are excited about Charles Djou’s candidacy, but the bottom line is that the district voted for Obama 70% to 28%. Not exactly an appealing opportunity, whatever Obama’s approval rating next fall.

That leaves us with three vulnerable open seats: LA-03 (Charlie Melancon), PA-07 (Joe Sestak), and NH-02 (Paul Hodes). Note that PA-07 and NH-02 voted for Al Gore and John Kerry and they gave Barack Obama a double-digit victory. Strong Republican recruitment should make both top-tier GOP opportunities, but they won’t be easy pick-ups.

And here’s where the news gets good for Democrats: There simply aren’t many more potentially tough seats that could open up. Just this week-end, Wisconsin Rep. Ron Kind announced he would not run for Governor - a relief for the DCCC.

At only 46, Kind is a 12-year incumbent, a Whip and a Ways and Means member; in short, he could rise to positions of power if only he stays in the House. Yet, he looked genuinely interested in a statewide race. Had he retired, the GOP would have had a good shot: While WI-03 gave Obama a 17% victory, it only went for Kerry and Gore by 3%. With Kirk now running for re-election, however, it heads off the map of competitive races. Kind has always cruised to re-election, albeit not always by dominating margins (he received 56% in 2004), and the district’s leftward turn last year should dissuade the GOP from paying much attention to the district.

So we are left with 3 vulnerable open seats - 4 if we grant that HI-01 could potentially be competitive. And I only see two House Democrats left whose retirement could create a headache for the DCCC:

  1. Rep. Bob Etheridge, who is considering running for Senate in North Carolina; NC-02 voted for Obama by 5%, for Bush by 8%.
  2. Rep. Peter DeFazio of OR-04, who is still deciding whether he wants to run for Governor in Oregon. Even if he does retire, once highly-touted GOP candidate Sid Leiken is not looking so hot anymore, to say the least.

Neither DeFazio nor Etheridge are likely to be vulnerable if they run for re-election, and at the moment I would not bet that either will retire. Even supposing that both do leaves the number of potentially competitive races at 5-6. (And let me repeat that this is already including seats in which the GOP would need to run a flawless campaign or rely on an excellent environment to be competitive; HI-01, OR-04 and PA-07 all lean blue.)

Other Democratic congressmen who have yet to rule out a retirement either are highly unlikely to quit or they don’t represent competitive districts. Gabrielle Giffords (AZ-08) or Jim Marshall (GA-08) running for Senate would be golden GOP opportunities, but neither has made any noise since the beginning of the year; polls showing McCain and Isakson in relatively good shape are unlikely to push them towards running. At 75, Leonard Boswell (IA-03) could retire from his swing district but he looks likely to stay put at least until redistricting. And the GOP has nothing to look forward to if Charles Rangel (NY-15) or John Dingell (MI-15) decide to retire. I believe that only leaves us with PA-11, where I once heard some buzz Paul Kanjorski might retire; but not only is that unlikely, it could also be good news for Democrats.

Let’s say a few such surprises occur, shooting the number of vulnerable Democratic open seats to 8-9. (As I said, this looks rather unlikely, especially with Kind announcing he’ll stay put.) Even that number bears no resemblance to the nightmare Democrats went through in 1994 or the retirement headaches the GOP endured in 2006 and 2008.

This did not happen for a lack of Democrats mulling retirement: At least 11 representatives who were actively considering seeking higher office or leaving politics decided to stick around to the House. Those include: Allen Boyd (FL-02), Ron Klein (FL-22), Dennis Moore (KY-03), Ben Chandler (KY-06), Mike McIntyre (NC-07), Heath Shuler (NC-11), Carol Shea-Porter (NH-02), Zach Space (OH-18), Patrick Murphy (PA-08), Stephanie Herseth Slandin (SD-AL) and Lincoln Davis (TN-04). That all chose to seek re-election speaks to their enjoying Democrats’ new status as the majority party.

By contrast, the NRCC has just as many open seat troubles to worry about as Democrats do. Jim Gerlach (PA-06) and Mark Kirk (IL-10)’s retirements create huge Democratic opportunities in blue territory, and DE-AL could soon become the most vulnerable district in the country if Mike Castle doesn’t run for re-election, as is expected (he has hinted he will retire if he does not run for Senate). Democrats have recruited competitive candidates in FL-12 and TN-03, both red-leaning but already-open districts. Bill Young (FL-10), Fred Upton (MI-06) and I believe Frank Wolf (VA-10) are still considering retirements, and any of them would host competitive open races.

In short: Before worrying about a coming red wave, Democrats should remember that they are leaving the GOP few obvious openings - a stark contrast to recent wave elections in which the losing party greatly contributed to its Election Day losses by having many of its incumbents retire.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Senate polls: MO is a tie, Gillibrand trails Giuliani, incumbents safe in AZ, IA and MD

Missouri: Rasmussen finds a tie

With Sarah Steelman dropping out of Missouri’s Senate race, it looks highly unlikely anything can derail a general election showdown between two of the biggest dynasties of state politics - Roy Blunt and Robin Carnahan. Since both enjoy high name recognition, early polls in this contest are more meaningful than in other Senate races but we have been getting fairly few polls from the state. Rasmussen finally released a survey earlier this week, finding Blunt and Carnahan tied at 46%. Both enjoy positive ratings, though the Republican’s is a bit stronger (57-33 instead of 52-42).

Democrats and Republicans alike are likely to be relieved by this survey. On the one hand, the DSCC has gotten plenty of bad polling news recently, and that’s especially the case in Rasmussen surveys. For instance, Rasmussen found Ayotte handily leading in New Hampshire - and that’s a blue-leaning state we’re talking about: That the GOP has been gaining strength is bound to impact red-leaning states like Missouri more than others, and Democrats were entitled to feel worried about what a Rasmussen poll of this race would show. That Carnahan is forcing a tie is a testament to her strength as a candidate.

On the other hand, Missouri is sometimes considered the Democrats’ top takeover opportunity because of the draw of Carnahan’s last name combined with the stain of Blunt’s years as a leader of the unpopular House GOP and the unpopularity of his son’s gubernatorial tenure. As such, for the Republican to force a tie will be considered good news at Republican headquarters.

All in all, this confirms what we have long suspected: This is one contest that is likely to be decided by nothing else than the national environment. One party typically sweeps most of a cycle’s competitive races, and I can’t imagine this contest bucking whatever general trend emerges. I also doubt we’ll ever see massive swings in public opinion in this contest: With both Blunt and Carnahan well-known and apparently relatively well-liked, they should both hold on to their mid-40s position at least until the general election heats up over the summer.

Marist, Siena have Giuliani handily beating Gillibrand

Since Gillibrand cleared the Democratic field, we have not been hearing that much about her re-election prospects but she won’t be out of the woods until George Pataki and… Rudy Giuliani make it clear they will not challenge her. Giuliani, you ask? A recent report suggested he might consider running for Senate instead of Governor, and while his camp has denied the rumor both Siena and Marist were intrigued enough to try out the match-out. The results are worrisome for Democrats.

The Marist poll has Giuliani crushing Gillibrand 51% to 40%, a margin that looks particularly bad because it’s not that far from the types of lead the former mayor posts against the highly unpopular David Paterson; Gillibrand also trails against Pataki, 45% to 41%. The Siena poll is somewhat less brutal for Gillibrand, who trails 46% to 38% against Giuliani. The Senator’s vulnerability is both a factor of her still-low name recognition, her mediocre favorability rating (29% to 24%) and Giuliani’s surprising popularity (56% to 38%).

The best news for Gillibrand comes from… Rasmussen (what is it this week with Rasmussen showing some better results for Democrats than other pollsters?): A new poll has her beating Pataki 44% to 41%. That’s not a particularly impressive margin, but it’s better than what other recent surveys have found - including the Marist poll. (Rasmussen did not test a match-up between Gillibrand and Giuliani.) Rasmussen does bring some bad news to Gillibrand though, as her favorability rating is a low 39-42. Again, her camp’s claim that her numbers will improve as she introduces herself are not proving true.

Rasmussen also released gubernatorial numbers. (Can pollsters please please stop polling New York, where numbers have not changed for months, and start exploring states like NH, MO or even PA?) Paterson is in relatively better shape, as his approval rating (39-60) is better than usual and he only trails Giuliani 50% to 39%; he ties Lazio at 38%. Cuomo beats Lazio 65% to 26% and Giuliani 58% to 37%.

McCain, Grassley and Murkowski Mikulski look safe

Democrats were once salivating at the prospect of ousting him in 2010 but John McCain is unlikely to face much of a race according to a new PPP poll. Despite last year’s many signs of a weak political standing and despite a mediocre approval rating (48% to 42%), he would handily beat all potential Democratic candidates - 53% to 40% against Napolitano, 57% to 30% against Rep. Gabrielle Giffords and 55% to 25% against Rodney Glassman. If McCain can top 50% against Napolitano, who would clearly have been the strongest Democrats had to offer, it’s hard to see anyone else topping him in the general election.

In Iowa, Republican Chuck Grassley is only facing low-profile opponent but a new Rasmussen poll doesn’t give us any reason to think he would be vulnerable even if he faced a top-tier challenger: Not only does he enjoy a formidable 68-30 favorability rating, but he easily tops the 50% mark against Bob Krause: 56% to 30%. The poll has me somewhat surprised, as I am unsure of how 63% of respondents can have an opinion on this low-profile a contender.

A Gonzalez Research poll of Maryland does not test any general election match-up involving Democratic Senator Barbara Mikulski, but her re-elect numbers make it clear she has nothing to fear in what is her fourth re-election race: Her favorability rating stands at 64/23 and her approval rating is even more formidable (67/22). 55% of respondents say they would definitely vote to re-elect her, with only 19% saying they definitely want to replace her; 26% say they’ll consider another candidate but with no Republican lining up to take Mikulski on this is one contest the DSCC doesn’t have to worry about.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Gubernatorial polls: Brewer, Culver, Patrick in trouble while O’Malley’s in control

Arizona: Democrat Terry Goddard looks strong

PPP gives us a rare glance at Arizona’s gubernatorial contest, finding that Democrats are in a very good position to score a pick-up - something we have not said about many new races over the past few months. Governor Jan Brewer, who rose to this position when Barack Obama appointed Janet Napolitano to his Cabinet, is very unpopular: Her dismal 26% to 43% rating is enough to make her one of the most endangered incumbents in the country.

The good news for Democrats is that their probable nominee Attorney General Terry Goddard looks like a formidable contender independently of Brewer’s weakness. Not only does he beat Brewer by a convincing 10% (46% to 36%), he also posts a solid favorability rating (44% to 22%) and has a 45% to 37% lead over Treasurer Dean Martin, who has said he might challenge Brewer in the Republican primary.

PPP’s survey also gives us an answer to a question I asked two weeks ago: Can former Governor Fife Symington have any hope to regain voters’ trust 13 years after being forced to resign due a bank fraud scandal? He might have rebuild his reputation in a court of law - his initial conviction was later overturned by an appeals court - but public option is dead set against him: His favorability rating is catastrophic (17% to 54%) and he is crushed by Goddard 52% to 29%. That tells us all we need to know about his general election viability, and we can only wish the poll had tested whether he had any chance of winning the GOP primary.

All the more admirable in Goddard’s strength is that it’s not like the poll reveals that Democrats are generally in great shape in the state - quite the contrary . In hypothetical match-ups in the 2012 presidential race, PPP finds Obama unable to muster a lead against Sarah Palin (the two are tied at 47%) while he trails Mitt Romney 50% to 43% and Mike Huckabee 49% to 45%. Given that it looked like Obama would have won the state in Arizona had his opponent not come from there, I am somewhat surprised at these results. Democrats also struggle to be competitive in the Senate race, but more on that tomorrow.

Iowa: When an incumbent trails by 20%

Democrats might be heading towards a pick-up in Arizona, but they are not in hot shape in Iowa, where Governor Chet Culver trails two potential Republican opponents in a Rasmussen poll - one of them by a gigantic margin. There is no doubt that former Governor Terry Branstad would be as formidable a challenger as the GOP can hope for; but it is still shocking to see Branstad leaving Culver 54% to 34%. Culver trails Bob Vander Plaats 43% to 39%, a more acceptable level but one that is still troubling given that Vander Plaats has never looked like the most electable Republican and that Culver still fails to break the 40% mark.

Note that Culver’s rating in this poll - 43% to 50% - is much lower than it was in a recent Selzer & Co poll, which had him at 50% to 38%. I am unable to find polls taken earlier in 2009, though I believe they exist. In any case, we do not have to believe the situation is as bad as Rasmussen suggests to still conclude that Culver is highly vulnerable, especially with Branstad considered likely to run.

Massachusetts: Patrick’s saving grace could be 3-way race

When Treasurer Tim Cahill announced he would run for Governor as an independent, I wrote that one possible scenario was that this could help Deval Patrick. He might be very unpopular, but Massachusetts is blue enough that Patrick can’t be expected to drop under 30%. That puts him closer to a 3-way plurality victory than a 2-way majority victory. A new Suffolk poll, which I believe is the first released since Cahill entered the race, confirms that analysis.

While Patrick’s approval rating is not that terrible (42% to 49%), only 29% of respondents say he deserves to win re-election; 56% say they would prefer someone else. You wouldn’t expect an incumbent with such a dismal re-elect to lead two match-ups by double-digits but that is exactly what Patrick is able to do thanks to the field’s crowded nature. If the Republican nominee is Charlie Baker, Patrick leads 36% to 23% for Cahill and 14% for Baker; if the GOP nominee is Charles Mihos, he leads 36% to 24% for Cahill and 17% for Mihos.

A genuine three-way race is bound to be unstable, as one candidate’s ups and downs can affect the margin between the two other. For instance, Patrick would be in trouble if the GOP nominee ends up collapsing in the low single-digits, letting his supporters move to Cahill’s camp; that’s what happened in Connecticut’s 2006 Senate race (Lieberman-Lamont). Also troubling for Patrick is that Cahill enjoys a strong favorability rating: 35-12 is a good foundation on which to build a statewide race.

NY: Voters are critical of Obama’s intervention, but it doesn’t make them like Paterson

Two new surveys of New York’s gubernatorial race find no surprises. First, Siena has his approval rating at a stunningly low 18%, his re-elect at 14%; he trails Cuomo 66% to 20%, Giuliani 52% to 35% and manages a 39% to 35% lead against Lazio. (Cuomo leads Giuliani by 13%.) Second, Marist released a second poll of the race in as many week, this one conducted in the immediate aftermath of news that Obama had asked Paterson not to run. 62% to 27%, respondents say Obama’s move was wrong; but they also say (25% to 63%) that Paterson should retire. With an approval rating at 17%, Paterson’s path to victory seems as damaged as ever.

Maryland: At least one Governor looks in good position

Here’s one incumbent that does not look to be in a world of hurt. According to a Gonzalez Research poll, Maryland’s Governor Martin O’Malley would beat his predecessor Bob Ehrlich 49% to 38% and RNC Chairman Michael Steele 52% to 37%. Sure, neither margin is that overwhelming but Ehrlich is the only credible candidate the state GOP has to offer (and it’s not looking very likely he’ll run), so if even he trails by single-digits it’s unlikely Republicans will be able to do much against O’Malley. After all, the 50% rule is less relevant in match-ups in which the challenger is a well-known figure whose name recognition is almost equal to that of the incumbent.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Senate Democrats are back at 60

At first, I confess I found it unlikely Massachusetts Democrats would accept granting Deval Patrick the right to appoint Teddy Kennedy’s successor; but intense pressure from national Democrats and state politicians convinced reluctant legislative leaders to push such a bill through. Given the overwhelming majorities the party enjoy in both chambers in the legislature, getting the Speaker and the Senate’s President to back the reform was all its proponents needed.

The process went about as fast as the legislature could have moved, and Deval Patrick wasted no time in announcing that he was appointment former DNC Chairman Paul G. Kirk. Once he is sworn in, Kirk will get Senate Democrats back at 60 seats.

And this time, it’s a filibuster-proof majority they can actually count on: All 60 Democrats are healthy enough not to miss important votes, and that includes Robert Byrd. The West Virginia Senator has missed a lot of votes this year, and he just spent a few days in the hospital this week (he was released today); but he has been able to attend enough roll calls that it doesn’t look like Democrats have to worry about his absence on high-profile occasion the coming showdown on health care reform.

Since Kirk will not seek a full term, his appointment will have no impact on January’s special election or in the 2010 midterms. But I do not need to tell you how important his vote will be in the coming months: Democrats no longer need a single Republican vote to pass health care reform (or anything else, for that matter). That does not mean liberals should claim victory since Olympia Snowe is not necessarily any more conservative than Ben Nelson and Blanche Lincoln.

Yet, centrist Democrats and centrist Republicans are subjected to very different types of pressure - especially when we’re talking about the cloture vote. As long as Snowe is the 60th vote Democrats need, we can imagine her bowing to her leadership’s injunctions and letting the bill die; but now that Nelson is in that decisive position, would he dare be the only Democrat to join a Republican filibuster and thus be entirely responsible for the bill’s failure?

Kirk’s appointment also prevents centrists like Nelson and Conrad from hiding behind the “lack of votes” to justify pushing legislation to the right without saying how they themselves would vote. Now, for them to say that the bill lacks 60 votes can only mean that they themselves are leaning towards a “no” vote - something they have been reluctant to say until now for obvious political reasons.

All of this said, as long as Obama signals he still desperately wants Olympia Snowe’s support, it will give Max Baucus the cover he needs not to move the bill further to the left. (Don’t forget that Baucus’s insistence that Enzi and Grassley should be included in the Gang of Six had nothing to do with passing the bill and everything to do with the Finance Chairman’s ideological leanings) and it will leave Snowe at the center of the game by allowing Nelson and Lincoln to still tie their votes to hers.

And a sign that the Democratic leadership has little intention to use its new-found filibuster-proof majority to push for a more liberal bill is buried in The Boston Globe report on Kirk’s appointment. I have already written that an important question in the coming weeks is which side of the Democratic divide - the Congressional Progressive Caucus or centrist Senators - the White House will put more pressure on, with Obama’s mid-September speech leaving little doubt it would be the former. Here’s more evidence that congressional liberals will need to face powerful intraparty opponents to get what they want:

Some Kennedy insiders who support Kirk’s appointment, though, have argued that Dukakis is too outspoken on health care issues, espousing liberal positions that could complicate Democrats’ attempts in Washington to moderate their approach on the legislation.

Also: I have been traveling in recent days, which has as you can see slowed down posting. But I should be back at the usual rhythm starting tomorrow.



If you like the website...

... Support Campaign Diaries


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::filter_post_comments() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 166

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Recent Posts


    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • All good things must come to an end

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • What remains on the table

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Confusion in Connecticut (Updated)

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Results thread, part 2: Dems suffer staggering losses in House and legislatives races, limit damage in statewide races

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Election Night results thread: Rep. Boucher’s fall first surprise of the night

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Election night cheat sheet

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Final ratings: Democrats brace for historic losses

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • What to watch for down-ballot

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Archives