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

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
Category Archive for ‘CO-Gov’ 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

Archive for the 'CO-Gov' Category


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

Poll watch: Bayh crushes Coats, Pomeroy & Shea-Porter struggle, GOP solid in PA

Less than three weeks from Texas’s primaries

Earlier this week, PPP shook up our expectations as Kay Bailey Hutchison suddenly looked in danger of being knocked out of the runoff by libertarian Debra Medina. Since then, three new Texas surveys have been released, all with a differing take on what is likely to happen on March 2nd. Research 2000 finds a likely runoff between Rick Perry and Hutchison, who come in at 42% and 30% with Medina at a still-impressive 17%. The University of Texas has Rick Perry closer to a first round victory (he is at 45%, with 16% still undecided) and a stunningly close race for second, with Hutchison at 21% and Medina at 19%. Finally, a poll conducted by two partisan firms shows Hutchison in front of Medina (27% to 19%) but Perry so close to 50% that it might not matter.

But all of these surveys were conducted before Medina attracted fire not only from the mainstream press but also conservatives like Glenn Beck for expressing openness to the possibility that the government was involved in bringing down of the World Trace Center. “I think some very good questions have been raised in that regard,” she said. “There are some very good arguments, and I think the American people have not seen all of the evidence there, so I have not taken a position on that. I’m certainly not into mind control or thought policing people.” This has gained a lot of coverage and should negatively affect her numbers. The question is: Does it help Perry cross 50% on March 2nd?

Two of these surveys also tested the general election, both finding Houston Mayor Bill White well within striking distance. In R2000, he trails Perry only 46% to 42%; he’s down 47-41 against Hutchison and 44-43 against Medina. The margins are larger according to the University of Texas, but both Perry and Hutchison are well under 50% (they lead 44-35 and 43-34, respectively); Medina and White are tied at 36%.

Bayh might not be that vulnerable after all

The week’s other very interesting poll comes from Indiana, where Research 2000 is the first pollster to test former Senator Dan Coats since he announced he was planning a political comeback two weeks ago. And the result is far less favorable than what the GOP was hoping to see: Coats’s favorability rating is only 38-34, weaker than former Rep. John Hosettler’s, which stands at 40-33. Evan Bayh, whose favorability rating stands at a solid 61-33, demolishes Coats 55% to 35%; against Hostettler, he is up by a narrower yet solid 53% to 37%.

A major reason Bayh has been painted as vulnerable in recent week is a Rasmussen survey showing him struggling against Mike Pence and against Hostettler; R2000 paints a very different situation, so it will certainly be interesting to see where other polls pit the race. Yet, Coats sure doesn’t look like a game-changer - and perhaps we should not be surprised at that: remember that he has not had his name on a ballot since 1992. The past 10 days have marked the first time most Indiana residents have heard about him in over a decade, and the coverage has been remarkably negative, which explains the rough welcome Coats has gotten as he has started to hit the trail.

House

VA-05: Given the number of House surveys that have found Democratic incumbents sinking (SUSA in AR-02, IN-09 and OH-01, most notably), we could have expected Rep. Tom Perriello to be in far worse shape than PPP finds him in. One of the NRCC’s top targets, Perriello is tied against state Senator Robert Hurt, 44% to 44%; the Democrat manages leads ranging from 4% to 10% against other GOP candidates. (While they might have a lower-profile, don’t forget how often we have seen unknown Republicans grab leads against incumbent Democrats lately.) Making matters more complicated is the prospect that former Rep. Virgil Goode, whom Perriello defeated in 2008, run as an independent: Boosted by a 57-28 favorability rating, Goode ties Perriello at 41%, with Hurt at 12%.

ND-AL: Tom Pomeroy might be keeping his head above water, but Earl Pomeroy is more vulnerable than is commonly believed, at least according to Rasmussen’s new poll. Like many of his colleagues, the 17-year incumbent finds himself trailing against Republicans he probably would have crushed in most cycles: against state Rep. Rick Berg, he is down 46% to 40%. While he maintains a 45-44 edge over Kevin Cramer, he has defeated him twice before, making this result underwhelming. Pomeroy does have a 47-38 edge over low-profile Paul Schaffner, but even then he remains under the 50% threshold. Put ND-AL in the column of truly endangered districts few expected would be vulnerable as 2009 started.

NH-01 and NH-02: In addition to releasing a Senate race (see below), UNH conducted a poll of both of New Hampshire’s districts, finding a very tough landscape for Democrats. (An important caveat: the margin of error is a large 6.2%.) In NH-01, Rep. Carol Shea-Porter is in a truly terrible position, failing to garner more than 33% whoever she faces and leading 43% to 33% against former Manchester Mayor Frank Guinta. In NH-02, left open by Democrat Paul Hodes, former GOP Rep. Charlie Bass would be favored to regain his old seat if he runs: He leads Ann McLane Kuster 39% to 28% and Katrina Swett 37% to 30%. Sure, Bass’s name recognition is higher but New Hampshire does seem fertile ground for Republicans this year.

Senate

New Hampshire: Two different polls found remarkably similar results and confirmed what surveys have found over and over again since last fall, namely that Attorney General Kelly Ayotte has built a comfortable but stable lead over Rep. Paul Hodes. UNH has her ahead 41% to 33% while Rasmussen pits it at 46% to 39%. However, other Republicans are weaker: Hodes leads decisively against Ovide Lamontagne (38-29 in UNH, 44-38 in Rasmussen), while it is closer against William Binnie (he’s up 34-30 in UNH, trails 42-41 in Rasmussen). A recent Research 2000 poll showed that Ayotte is far from certain of winning the primary, but the fact that Hodes is trailing against a relatively unknown businessman is a bad sign for voters’ willingness to vote Democratic.

Missouri: Rasmussen might be the only pollster to find Robin Carnahan trailing outside of the margin of error, but today marked the second poll they have released with such a finding: Weighed down by Barack Obama’s 40-59 approval rating, Carnahan trails Rep. Roy Blunt 49% to 42%. Though Carnahan would likely have an edge in normal circumstances, Missouri is conservative enough that it should not surprise us to see Blunt carried by the GOP currents.

North Dakota: No miracle for Democrats in North Dakota, where Governor John Hoeven looks even more formidable than conventional wisdom dictates according to Rasmussen’s latest poll. Not only does he enjoy an eye-popping 85% approval rating, but he crushes state Senator Potter and former Attorney General Heidi Heitkamp 71-17 and 65-29, respectively. This has got to be all the more frustrating for Democrats that Heitkamp’s has a respectable favorability rating (54-36).

Louisiana: Here’s one race Democrats will not be contesting come November. It’s been obvious for weeks that Rep. Charlie Melancon’s hopes of pulling off an upset have been fading, but the Rasmussen survey with Senator David Vitter leading 57% to 33% is brutal for Democrats. With a 67% to 26% favorability rating, Vitter’s standing bears no trace of the D.C. Madam scandal.

Pennsylvania: With Senate Democrats in bad shape in Delaware, Arkansas or Nevada, they cannot afford to lose but Rasmussen finds Pat Toomey leading Arlen Specter and Joe Sestak by decisive margins: 47-38 and 43-35, respectively. I’ve said it before, and I’ve said it again. I am not sure how a five-term senator can survive trailing by 9% and struggling to break 40%, while Pennsylvanians should be more open to voting for the lesser-known Sestak; that also explains why Toomey is further from 50% in the latter match-up. Yet, Specter manages to keep a comfortable lead in the primary: 51% to 36%. That might have been an encouraging back in the fall, but three months from Election Day, the time has come for Sestak to gain traction.

Governor

Colorado: Rasmussen confirms that replacing Governor Bill Ritter with Denver Mayor John Hickenlooper has improved Democratic prospects. While Ritter was weighed by a negative approval rating, Hickenlooper is popular (his favorability rating is 56-36); while Ritter trailed Scott McInnis in most late 2009 surveys, Hickenlooper leads 49% to 45%. That might not be anything for Democrats to celebrate, but it does leave them in a better position not just to defend the Governor’s Mansion but perhaps also the Senate seat.

Ohio: The good news for Ted Strickland is that his numbers are no longer in free fall. The bad news is that he stopped the bleeding too late not to look highly endangered. Weighed down by a negative approval rating (46-53) and facing a challenger that appears popular (John Kasich’s favorability rating is 47-30), Strickland trails 47% to 41% according to Rasmussen; that’s slightly less than in January, but it leaves him in a rough spot. Might Ohio Democrats have something to learn something from Colorado?

Illinois: The first poll taken since the Illinois primary found Governor Pat Quinn in a stronger position than he looked to be a few weeks ago, perhaps due to a bounce resulting from the coverage of his victory. Against state Senator Bill Brady, Quinn leads 42% to 31%, with 4% going to Green Party nominee Rich Whitney; against state Senator Kirk Dillard, who trails the GOP primary by 400 votes and has not conceded, Quinn is up 41% to 35%. An important caveat: The poll was conducted by Victory Research, a group I had never heard before.

Pennsylvania: Now that he has gotten rid of Jim Gerlach’s primary threat, Attorney General Tom Corbett looks unstoppable in Rasmussen’s latest poll: He crushes Jack Wagner 49-29, Joe Hoeffel 51-29 and Dan Onorato 52-26. While this is nothing we haven’t seen before, and even if we account for Rasmussen representing the GOP-friendly end of the polling spectrum, the margins by which Corbett is demolishing his opponents bode ill for other Pennsylvania Democrats.

Michigan: Rasmussen’s poll of this wide open race confirms the GOP can be optimistic since Republican candidates lead 11 of 12 trial heats. Only Speaker Andy Dillon  manages a 36-35 edge over Attorney General Mike Cox, though he trails 40-32 against Sheriff Mike Bouchard and 41-34 against Rep. Pete Hoekstra. The other important match-ups concern Lansing Mayor Van Bernero, who trails by 6%, 9% and 13%, respectively. This poll is somewhat surprising, since EPIC-MRA has repeatedly shown Cox to be the strongest Republican in the general election; it is also striking that Democrats looked to be in worse shape when Lieutenant Governor John Cherry was in the race. Cherry never looked to be within striking distance, whereas Bernero and Dillon do.


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

Poll watch: Dems holds edge in Hawaii, GOP leads Senate races in MO, PA and AR

I have avoided spending much talk about the 2012 presidential race, but two new polls released by Fox News and PPP are worth mentioning since they offer quite contrasting takes on the state of Barack Obama’s standing with the electorate - and thus say a lot about the fact that we still have a lot to learn about what the 2010 landscape will look like and also how it will affect 2012. First, Fox has Obama crushing the 3 Republicans that are matched-up against him: 47% against Mitt Romney, 55% to 31% against Sarah Palin and 53% to 29% against Newt Gingrich. PPP, however, has Obama leading David Petraeus 44% to 34%, Palin 49% to 41%, Romney 44% to 42% - but trailing Mike Huckabee 45% to 44%.

I believe PPP’s survey marks the first time Obama has trailed a match-up since early September 2008 - yet another sign of how much the landscape has shifted in recent months. Yet, Fox News’s numbers leave nothing to be desired for the president - and it is striking that both surveys find that it would be a very bad idea for the GOP to nominate Palin.

Meanwhile, a number of important down-ballot polls were released this week. Our first look at HI-01’s special election and at Hawaii’s gubernatorial election, find that Democrats are leading both, while the first Georgia poll since former Governor Roy Barnes announced he wanted his old job back shows that Democrats have a great shot at regaining a Southern governorship. Yet, the news is mostly news for Republicans, as Democratic incumbents trail in Arkansas, Pennsylvania and IN-09. Perhaps the best news for the GOP is that Robin Carnahan has fallen behind for the first time in Missouri’s Senate race.

House

HI-01: Mason Dixon polled the soon-to-be-called special election in HI-01, which Neil Abercrombie is resigning from. Despite the district’s blue bent, Republicans are optimistic about this opportunity for two reasons. First, They believe Charles Djou is a top-tier candidate; second, they’re hoping that the fact that the special election will have no primary can help them pick-up the seat since 2 Democratic candidates will be splitting their party’s vote. Mason Dixon finds neither reason is justified: Djou receives a low 17%, far behind both Democratic candidates - Ed Case is at 35% while Colleen Hanabusa is at 25%. Looks like HI-01 is blue enough that it can accommodate two Democrats without handing itself over to a Republican. But can it accommodate three? Democrats today received the troubling news that state Senator Will Espero was forming an exploratory committee to join the race. If he manages to gain some traction, it would mean that the Democratic vote would split in three, strengthening Djou’s chances of pulling an upset.

NY-01: Rep. Tom Bishop hasn’t faced a competitive race since he won a tough open seat in 2002, but the GOP’s confidence that it can unseat him in 2010 will be boosted by a new SUSA poll showing the incumbent barely holding on 47% to 45% against challenger Randy Altschuler, a businessman with deep pockets. But here’s the deal: Swing State Project noticed that SUSA’s samples include an absurdly low number of 18-34 year olds - just 1% in this survey! In 2008, 17% of the electorate was made up of 18-29 year olds; sure, turnout among young voters will drop a lot next year, but it certainly won’t fall as low as 1% - it stood at 12% in the 2006 midterms, and that’s the 18-29 rather than the 18-34 year-old group we’re talking about. This skew is bound to have major consequences on what the results look like.

IN-09: The fourth survey in the series of FiredogLake/SUSA polls tested Rep. Baron Hill, and I can’t say I expected the Democrat to trail 49% to 41% against Mike Sodrel, who he’s running against for the 5th straight time. If the survey is confirmed (I never have had reason to doubt SUSA, and the sample’s age breakdown is less problematic than it was in the NY-01 poll), it would guarantee that the cycle will be very tough for Democrats: Hill just crushed him by 20% in 2008, and I recently wrote I found it highly unlikely that Sodrel was the GOP’s best bet. Hill is the third Democratic incumbent SUSA found trailing outside of the MoE in the space of two weeks.

Senate

Missouri: In what is one of the clearest polling signs yet that the midterm landscape has dramatically shifted in the GOP’s favor, the Democratic decline is now even affecting Robin Carnahan. Throughout the fall, I had marveled that she was one of the party’s only candidates nationally who had managed to remain stable - but Rasmussen’s latest poll has Roy Blunt leading 49% to 43%. Not only is this the first Rasmussen survey in which Blunt is ahead (Carnahan led by 2% last month), but it is also one of the first polls taken of this race that has one of the candidates’ leading outside of the margin of error. Sure, on paper Missouri is much more certain to be a Republican hold than OH or NH if the environment favors the party, but Carnahan is undoubtedly one of the cycle’s strongest Democratic recruits; if even she has fallen behind 6%, how are Jack Conway or Paul Hodes supposed to remain competitive?

North Carolina: PPP’s first poll of the year shows the same result it found throughout 2009: Senator Richard Burr inspires little passion among his constituents (his approval rating is an unimpressive 36/33, with 31% saying they have no opinion), he is stuck well under 50% of the vote and Secretary of State Elaine Marshall comes closest. Burr leads 44% to 37% against her, 45% to 36% against Cal Cunningham and 46% to 34% against Kenneth Lewis. The good news for the Republican is that his numbers are slightly better than they were last month, as Marshall then only trailed by 5%. But the good news for Democrats is that this is the first time Marshall performs better than a generic Democrat (who is behind 9%). Burr is undoubtedly the cycle’s most (only?) vulnerable Republican incumbent.

Pennsylvania: Rasmussen’s latest poll finds Pat Toomey expanding the leads he had built in the fall and continue to dominate both Arlen Specter (49% to 40%) and Joe Sestak (43% to 35%). While the two Democrats’ margins are similar, it is far more worrisome for an entrenched senator to trail by 9% (a deficit from which few such incumbents can recover) than for a candidate with no statewide profile to do so. As such, Democrats’ best bet to defeat Toomey remains getting rid of Specter - but here lies the party’s problem: Sestak’s primary momentum appears to have completely stalled. Specter now has a 53% to 31% lead, the largest he has received yet in a Rasmussen poll; back in the summer, I would have said this margin is encouraging for the challenger but now that we are 5 months away from Election Day Sestak’s lack of progress is more consequential.

Arkansas: Yet another rough poll for Blanche Lincoln, this time from Mason-Dixon. Not only does the conservative Democrat trail state Senator Gilbert Baker 43% to 39% and her 2004 opponent Jim Holt 43% to 37%, but she can barely manage leads against a series of low-profile Republicans: she’s up 40-39 against Curtis Coleman, 41-38 against Conrad Reynolds, 43-38 against Kim Hendren and 41-38 against Tom Cox. Sure, Mason Dixon’s numbers aren’t quite as brutal for Lincoln as its Nevada polls have been for Reid, but the fact that a two-term incumbent fails to break out of the low 40s obviously a bad sign - one that is sure to fuel speculation that Democrats might try to push Lincoln out; but the poll also suggests that the best way to do that would be convincing her to retire, since she does have a 52% to 34% lead in a potential match-up against Lieutenant Governor Brian Halter. Sure, that’s no insurmountable margin when we’re talking about a primary race, but it’s not like Halter is an unknown figure.

Governor

Georgia: Here’s one Republican-held seat Democrats have an excellent chance of picking-up! Rasmussen’s poll of the general election has former Governor Ray Barnes performing stronger than Georgia Democrats have grown to expect against a trio of Republicans. John Oxendine is narrowly up 44-42 while Rep. Nathan Deal and SoS Karen Handel are both down 43-42. On the other hand, these Republicans lead by margins ranging from 18% to 12% against Attorney General Baker. This is the very first survey of the state taken since Barnes jumped in the race in June 2009. While the dearth of polling has made us forget that the former Governor’s entry in the race is one of Democrats’ best recruitment coups of the cycle, this survey leaves little doubt that Barnes could help his party regain a footing in the South.

Hawaii: Mason Dixon released the very first poll we have seen of this state, and it suggest Republicans have a better shot than I expected to defend the governorship. While both Democratic candidates are clearly ahead, Lieutenant Governor Aiona does manage to stay in contact: he trail 43% to 34% against Rep. Neil Abercrombie, 41% to 35% against Honolulu Mayor Hannemann. The state holds very late primaries (on September 18th), so it will be quite a while before the Aiona has to worry about Democrats turning their fire on him.

California: General Jerry Brown remains favored to regain his old job back, but he cannot take the general election for granted. The latest Field Poll has Meg Whitman cutting her deficit by half to trail 46% to 36%. Given that her name recognition is about half of Brown’s she has room to grow, and it’s not like Democrats can hope for Whitman to be tripped up in her primary: she has opened a huge 45-17 lead Steve Poizner, who faces a 48% to 31% deficit against Brown. Rasmussen also tested this race and it found Brown leading Whitman by a much smaller margin (43% to 39%), though he is ahead of Poizner by 10%; strangely, the poll also has Senator Diane Feinstein, arguably the state’s most towering political figure, lead Whitman only 43-42. (The poll’s trendline is actually positive for Democrats, since Brown and Whitman were tied in November.) Even though Rasmussen’s numbers are out-of-line with other pollsters’ results, there is little doubt that Brown shouldn’t be considered a shoo-in.

Texas: For the first time, Rasmussen tested this race’s general election, which vindicated conventional wisdom. While Houston Mayor Bill White, has a shot at an upset, he does face an uphill climb - and his chances probably depend on the outcome of the Republican primary. While Perry leads White 50% to 40%, Hutchison is ahead by a larger 52% to 37%, which confirms that White’s potential would be greater if he were to face the incumbent. Interestingly, White has a slight lead when matched-up against libertarian Debra Medina 44% to 38%, suggesting Texas voters are willing not to automatically back the Republican.

Colorado: I covered the Senate half of Research 2000’s Colorado poll earlier this week, but they also released gubernatorial numbers that confirm not only that the race will be competitive but also that Denver Mayor John Hickenlooper is the strongest of the Democrats who were mentioned as replacements for the retiring Ritter: While Hickenlooper ties probable GOP nominee Scott McInnis at 43%, McInnis has a 2% lead against Ken Salazar (a striking result given Salazar’s statewide profile), a 5% lead over Andrew Romanoff and an 8% lead over Rep. Ed Perlmutter. Here’s further good news for Hickenlooper: Twice as many Democrats as Republicans were undecided in the poll, suggesting he has more room to grow, and he has a slight lead among independents, which is more than can be said of other Democrats across the country.

Maryland: We still have little information on whether former Governor Bob Ehrlich will challenge incumbent Marty O’Malley, but if he does he will start with a 48% to 39% deficit according to a new poll by GOP firm Gonzalez Research; Ehlrich is undoubtedly the only Republican who’d make this race worth watching. The poll also delivers useful confirmation that Barbara Mikulski is one senator Democrats do not have to worry about, since her approval rating stands at 64% to 23%


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

Hickenlooper in, Bysiewicz out

For years, Denver Mayor John Hickenlooper has been passing countless opportunities to run for open seats. He finally decided that this was his year; that’s a curious choice considering ambitious Democrats have generally been trying to avoid running in 2010, but his party isn’t going to argue since it gives them a prominent candidate to field in Colorado’s Governor’s race.

Governor Bill Ritter’s unexpected withdrawal left a void in the Democratic ticket. The opportunity to replace him wasn’t quite as promising as that of swapping Chris Dodd for Richard Blumenthal, but given Ritter’s low approval ratings the party had more to gain than to lose. With Hickenlooper, Democrats have almost certainly improved their chances to hold on to the nomination considering that the two-term mayor has a strong statewide standing: back in December 2008, a poll that tested him in potential Senate match-ups found him crushing former Governor Bill Owens by double-digits. I am not aware of any other recent poll testing him but Research 2000 is currently in the field in Colorado, so we won’t have to wait long.

(Note that Hickenlooper cannot be sure he’ll have the Democratic field for himself: former state Speaker Andrew Romanoff is still considering switching from the Senate race, where he is challenging Bennet in the primary, to the Governor’s race.)

Republicans tend to relish attacking statewide candidates who are either from Boulder or from Denver, two cities that are more liberal than the state-at-large. (You might remember that saying Mark Udall was a “Boulder Democrat” was in-and-of itself considered an attack during the 2008.) Yet, Denver has nearly 600,000 inhabitants while its metropolitan area makes up more than half of Colorado’s population. Mayors are often better-known (and often better-liked) than other political officials, and Hickenlooper has been leading Denver for the past six years. If he manages to perform as well or better among voters who’ve been following him closely for the past than recent Democratic candidates who aren’t from Denver (Salazar, Udall and of course Obama), he would be sure to be competitive.

As such, Hickenlooper’s entry guarantees Democrats remain relevant in this crucial race - and this should have repercussions far beyond the question of who controls the state’s Governor’s Mansion. Senator Michael Bennet has never faced an election, he is still largely unknown and as of now he hasn’t displayed a particular ability to energize any voters, let alone a depressed Democratic base; had his part had suffered recruitment setbacks in the Governor’s race and had they settled on a lower-tier candidate, it would have raised troublesome questions as to who could carry the Democratic flag and draw voters to the poll next fall. Whatever Hickenlooper’s ultimate fate (as of now, a general election match-up against Republican Scott McInnis can only be called a toss-up), the presence of a well-known Democrat on the ballot has to be a relief for all the party’s other nominees down-ballot.

Another consideration is that Hickenlooper has a more moderate profile than other state Democrats; when we were speculating as to who would be appointed to Ken Salazar’s seat, Hickenlooper was considered a more conservative option than Democrats like Ed Permutter - and certainly than liberals like Diana DeGette. How will that impact the Democratic ticket considering that Bennet also has a centrist profile? Furthermore, Hickenlooper has had a rough relationship with unions; we’ll have to see how that affects how interests unions are in helping out Democrats in Colorado. Considering the party is facing turnout problems, it certainly cannot afford losing out on labor’s help.

If Democrats gained a prominent candidate in Colorado today, they’re also losing a formidable gubernatorial contender in Connecticut: Secretary of the State Susan Bysiewicz had arguably become the front-runner ever since Jodi Rell announced her retirement, which made today’s reports that she was preparing to drop out to run in the newly-open Attorney General race instead all the more surprising!

Indeed, this is one withdrawal we can’t link to a fear about a tough environment: Just last week, a poll was released that showed Bysiewicz crushing her Republican rivals by 25% and 22%. She was also in a strong position in the Democratic primary; though she did face tough competition (the most recent Quinnipiac poll had her leading Ned Lamont 26% to 23%, with Dan Malloy in single-digits), she never expected to have the field for herself since Malloy was always sure of running. More puzzling still: it’s not like Bysiewicz will have an easy time in the Attorney General race. She’ll have to face former state Senate Majority Leader George Jepsen, who is close to current-Senate candidate Richard Blumenthal.

Bysiewicz’s exit leaves three Democrats to battle it out: 2006 Senate candidate Ned Lamont, former House Speaker James Amann and Stamford Mayor Dan Malloy. While all three would be strong general election contenders against Lieut. Gov. Michael Fedele and former Ambassador Tom Foley, last week’s PPP poll did suggest that none would be as formidable as Bysiewicz; Lamont and Malloy’s leads were half as large as Bysiewicz’s.

Also, a good point from Politico: If Bysiewicz wins the Attorney General race, Democrats are likely to remember the strong poll numbers she enjoyed over the past few months when they look for someone to take on Joe Lieberman in 2012.

A third and last important story about Democratic gubernatorial candidates comes to us from Rep. Stupak (yes, that Stupak) is now actively mulling the possibility that he might run for Governor in Michigan. That would probably leave everyone in his party unhappy, since the DCCC would have another tough open seat to defend while state Democrats would have to deal with one of liberals’ biggest looking villain looking to represent them. I’ll wait for Stupak to make up his mind to delve more into this possibility.


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

In now unsettled Gov races, can Hickenlooper & Dillon impose themselves to Dems?

Besides Dodd, Dorgan and Ritter, Tuesday saw a fourth major Democratic drop-out: Lieutenant Governor John Cherry ended his gubernatorial campaign in Michigan.

The party’s presumptive nominee since the beginning of the cycle, Cherry had long looked like he would take Democrats off the cliff. On paper, it seemed obvious that Cherry would have trouble appealing to voters who are eager to turn the page of the unpopular Jennifer Granholm administration but the decisiveness of the deficits he faced against all Republicans in 2009 polls was nonetheless surprising. On Tuesday, Cherry took care of his party’s dilemma by taking it upon himself to drop out of the race. (Interestingly, there has been little buzz of Cherry facing pressure from the national party, the way Barbara Lawton did and the way David Paterson is.)

From an overall perspective on the cycle, Cherry’s decision (just like Dodd and Ritter’s withdrawals) is an indication of just how much Democratic fortunes have fallen over the past 12 months. But Democrats are certainly relieved at his decision, which allows them to hope for a candidate who could campaign as an outsider and have a better shot at holding this crucial governorship.

Michigan’s situation is closer to Colorado’s than to Connecticut’s: Democrats have no miracle solution, no formidable heir apparent waiting in the wings whose mere entry will take care of the party’s trouble. That’s obviously not surprising, since the latter is a blue state while Colorado is a swing state and Michigan, while leaning Democratic, has always been competitive; but it’s important to point out that no one is under the illusion that Cherry’s withdrawal means Democrats are suddenly favored to win this open race. In fact, the state’s particularly dismal economic situation combined with the strength of the GOP field keeps Republicans as slight favorites.

Unlike even Colorado, in fact, Democrats aren’t likely to coalesce around a single candidate. The politician who’s name pops up the most is state Speaker Andy Dillon, a moderate who has drawn the pronounced hostility labor groups. In a union-heavy state like Michigan, that should not only make it tricky for him to win the Democratic primary but it would also mean trouble in the general election. The party will have enough trouble turning out its base as it is; if unions put in a weaker-than-usual effort to drive up turnout because they do not trust the man at the top of the Democratic ticket, it would be a headache for Democrats up and down the ballot. (Dillon is also pro-life, though I’m not sure how that might play out.)

Dillon is doing his best to impose himself as Cherry’s obvious heir apparent. Not only was his name floating throughout 2009, but he is the first to make his move since the Lieutenant Governor’s departure: He announced today that he was forming an exploratory committee. Yet, Dillon will probably not be able to become the clear front-runner. For one, state Rep. Alma Wheeler Smith, former state Rep. John Freeman and Flint Mayor Don Williamson were already in the race before Cherry departed, and while they were clear underdogs Dillon is a less formidable figure. Candidates who could still get in include Lansing mayor Virg Bernero and MSU trustee George Perles. It will be interesting to see whether unions try to coordinate rallying around a single opponent to Cherry.

Over in the other gubernatorial race that was thrown in turmoil on Tuesday, Democrats look like they’re preparing to rally around the candidate that had always looked like their strongest bet - though not in the Blumenthal sense.

Interior Secretary Ken Salazar made up his mind quicker than I expected: He will not run for Governor, even though this seems to have been his career-long dream. Contrary to what we are reading in some quarters, I believe this is is good news as there is no evidence Salazar would have been their best option - let alone that he is popular. While he won his Senate seat in a tough environment in 2004, his opponent was not the most formidable of Republicans and heading into the 2010 cycle (where he would have been up for re-election) Salazar’s approval rating was not impressive. While it’s impossible to know how vulnerable he would have been had he not moved to Washington, he was in the GOP’s cross hairs. In short: he was no savior.

Salazar’s exit paves the way for Democrats to rally aorund Denver Mayor John Hickenlooper… if he agrees to get in. While Hickenlooper has been at the top of Democrats’ wish-list every two years for all the open seats that have popped up this decade, he’s passed on every opportunity. Will 2010 be different? Signs suggest that he is likely to run: Not only did he issue a statement yesterday announcing he would take a hard look at jumping in if Salazar does not, but the Interior Secretary himself urged the mayor to run in the statement he released today.

We can talk more about Hickenlooper’s strengths and weaknesses if he does run, but we can already cite a poll Rasmussen hurriedly conducted in the aftermath of Ritter’s announcement: It shows the Denver Mayor is the strongest nominee Democrats can turn to. But the bad news for his party is that Scott McInnis has a lead in all three potential match-ups: 45% to 42% against Hickenlooper (which is within the MoE), 47% to 41% against Salazar and 47% to 37% against Andrew Romanoff.

That shouldn’t obscure the fact that Hickenlooper’s favorability rating (57%) positions him to rally a broader electorate than Ritter, plagued by a negative approval rating (44-52). Even if Hickenlooper loses to McInnis, he should be able to keep the race close and thus be of help to his party’s Senate prospects.


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

In day’s third big bombshell, Governor Bill Ritter drops re-election bid

21! There will be 21 open Governor’s race in the 2010 cycle, 4 of which will be due to voluntary retirements rather than to term-limits. The latest chief executive to join the ranks of retirees is the most stunning yet: Colorado’s first-term Governor Bill Ritter is set to announce today that he will not seek re-election this fall.

Last night, some pointed out that I lost sight of the big picture when commenting on Chris Dodd’s retirement, and I think that might be right. I don’t mean that I should have addressed the possibility that so many high-profile Democrats calling it quits in a single day will create a damaging narrative for the party (at this point, it’s become conventional wisdom that Democrats are facing the prospect of tough losses), but that I should place these decisions in the context of the entire cycle: We have gotten so used to the fact that Dodd and Ritter suffered from dismal approval ratings that we forget that at the start of 2009, no one could have foreseen that Dodd, Ritter or Byron Dorgan would have trouble securing additional terms in 2010.

All three looked like very popular incumbents, two of them veteran lawmakers and the third having enjoyed a landslide victory in 2006. By this week, we knew that both Ritter and Dodd were a weight on Democrats so their retirements are good developments for their party because they allow the nomination of more electable candidates; but from the perspective of where we stood in early 2009, their decisions confirm just how much the electoral landscape has shifted over the past 12 months. Anyone who reads this blog is obviously aware of that, but it’s still important to keep in mind.

This said, the bottom line is that most incumbent governors have become liabilities for their party: states are bearing the grunt of the recession, and governors have to deal with their states’ fiscal crises. That makes them unexpectedly vulnerable heading into 2010, which is obvious not only in Democratic-controlled states (Iowa, Ohio and also Colorado) but also in Republican-controlled states (polls suggest that Charlie Crist’s collapse is not just due to criticism from the right, but also from the decline of his approval rating that mirrors that of other governors). As such, PPP found Ritter leading Scott McInnis by a 49% to 36% margin; in August and again in November, PPP had him trailing by 5%. In the meantime, McInnis didn’t mount a campaign and he didn’t increase his name recognition; that dramatic 18% shift is entirely due to a change in Ritter’s fortunes.

As such, it’s unclear whether Ritter would have been able to ever be truly competitive against McInnis: All polls taken over the past 6 months find him stuck around the 40% mark, which raises obvious questions as to an incumbent’s electability. (Jon Corzine, anyone? And that was in New Jersey.) His exit gives Democrats a chance to start anew.

To be sure, the situation in no way compares to that of Connecticut. For one, Colorado is a swing state in which independents who swung to the left in 2008 have no long history of voting Democratic, so a tough environment would have disastrous consequences for the party in this state. Second, Democrats have no Blumenthal-like savior. But while they have no savior, Democrats have a solid bench nonetheless: Denver Mayor John Hickenlooper probably tops Democrats’ wish list, but former Speaker Andrew Romanoff is also considering the race; other possibilities include members of the congressional delegation (Democrats control 5 out of 7 House seats). Many of these politicians could mount strong campaigns.

This open race starts as a toss-up, and unless a really strong red wave submerges the country it will probably remain a toss-up.

(You hopefully recognized Romanoff’s name: He is currently challenging appointed Senator Michael Bennet in the Senate race’s Democratic primary. His exit would thus guarantee Bennett can move to the general election, which I am not sure is good news for Democrats since there are big questions for now as to whether he will be able to defend the seat. On the other hand, Democrats’ prospects of holding the Senate seat could be improved by the possibility that they’ll have stronger candidate heading the ballot: A Ritter-Bennet ticket would have been very unlikely to inspire many Democrats.)

On the Republican side, McInnis is a solid candidate for Republicans: He is certainly not the youngest and most fresh of candidates, but he is well-connected and experienced enough to take full advantage of any GOP advantage in the environment. That said, it will be interesting to see whether others join McInnis in the primary. You might remember that the GOP took great care of showing off its unity in late 2009 as Tom Tancredo and Josh Penry dropped their bids to rally by the former representative, so it’s tough to see them reconsidering; but might Attorney General John Suthers be interesting in running for the open seat? Another possibility is former Rep. Bob Beauprez, who was once vocal about his interest in running for something but has been very discreet for the past few months.

There’s a lot more to be said about Colorado. And about Michigan. And about New York. And about Connecticut and North Dakota. (How did everything happen within 12 hours?) But I am now heading out for a day-long trip… so it will all have to wait. If I get Internet while waiting for my connecting flight, I’ll try to get to the latest in CT and ND (or to any other bombshells that might have occur in the next few hours).


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

Poll watch: Rubio ties Crist, Marshall within 5% of Burr, GOP leads 3 key Governor’s races

With 9 months to go, Rubio has already tied Crist

As soon as Marco Rubio made it clear he would stick to the Senate race, it was clear that Florida’s Republican primary had the potential to be explosive. But who expected him to gain enough traction to make his race with Charlie Crist a toss-up before we even entered 2010? There is still 9 months to the primary, but the former state Speaker has for the first time tied in the Governor in a public poll: Rasmussen finds the two at 43%.

Until now Rasmussen’s poll numbers have not been excessively positive for Rubio. In August, Crist led by 29% in Quinnipiac and 23% in Rasmussen; in October, Crist led by 15% in Quinnipiac and by 14% in Rasmussen. We have yet to receive a Quinnipiac survey this month, but it shall be very interesting to see whether that pollster will continue finding the same trend as Rasmussen. For now, we can certainly say that there is a lot of evidence that the Governor’s fortunes have collapsed.

Somewhat surprisingly, Crist’s favorability rating among Republicans remains overwhelmingly positive (61% to 38%) but that also means he is far from having hit rock bottom: As conservative groups start pouring in millions to portray him as unprincipled, liberal and/or too friendly to Obama, Crist should see his numbers continue to drop and he’ll have to ensure his campaign isn’t as hapless over the next 9 months as it’s been since the summer. Crist has spent little time engaging Rubio, which has allowed the conservative to build strong popularity among Republicans (64% to 15%); the Governor has plenty of money and institutional support to ensure Rubio’s numbers take a dive.

Two polls find Burr under 50%, vulnerable against Marshall

Richard Burr’s poll numbers have been low ever since the cycle began and two new polls confirm he has a lot of work to do to ensure his re-election. PPP finds his approval rating is plagued by two worrisome signs: For one, it is in negative territory (35/37); second, an unusually large share of voters don’t know him well enough to have an opinion. That also translates to Burr polling at weak levels in match-ups. Against a generic Democrat, he leads 41% to 40% while he is up 42% to 37% against Elaine Marshall. In the Civitas poll, Burr is ahead by a larger margin but he is even further away from the 50% threshold, since he leads 40% to 32%.

While Burr’s numbers are stronger than those many Democratic incumbents are facing, they still point to his being vulnerable - as is any incumbent who is stuck in the low 40s. In fact, given the name recognition differential between Burr and Marshall (69% of respondents don’t have an opinion of her), she has room to grow and her 5% deficit could be smaller still: While only 13% of Republicans undecided, 24% of Democrats and 25% of African-Americans say the same.

Despite the lack of evidence Marshall faces any electability problem, the DSCC is committed to defeating her so let’s look at her rivals’ numbers: PPP finds that Kenneth Lewis trails Burr 43% to 37% while Cunningham is behind 45% to 36%. That’s right, the candidate the DSCC is reportedly mulling spending millions on is polling at a weaker level than two other contenders - and it’s not like this can be explained by a difference in name recognition: 81% of respondents have no opinion of Cunningham, 80% of Lewis and 69% of Marshall.

Sure, the difference between the candidates’ performances is too small to draw overarching conclusions, but let me repeat that the DSCC is considering mulling spending millions helping Cunningham in the Democratic primary. I remain on the lookout for a coherent argument as to why he would be the most formidable general election candidate when he has neither name recognition, nor an obvious fundraising network, nor statewide experience - not to mention that Marshall is in a good position herself and that Cunningham’s policy positions are less of a fit with the Democratic base’s preferences.

GOP leads 3 key gubernatorial races

A week after releasing an avalanche of surveys finding Democrats in trouble in Senate races, Rasmussen finds Republicans ahead in 3 key Governor’s contests; here again, Rasmussen’s numbers might be friendlier to the GOP than the polling average but they do not substantially differ from other numbers we have seen from pollsters like Quinnipiac and PPP:

  • In Colorado, former Rep. Scott McInnis ensured his hold on the GOP nomination by pushing out John Penry and Tom Tancredo, and he starts with a solid 48% to 40% edge over Governor Bill Ritter. Rasmussen also tested Penry, who trails Ritter 41% to 40%.
  • In Pennsylvania, Attorney General Tom Corbett is by far the best-known candidate, but his name recognition advantage cannot by itself account for his huge leads over the entirety of the crowded Democratic field: He crushes Auditor Jack Wagner 43% to 30%, former Rep. Joe Hoeffel 48% to 26%, Dan Ornato 44% to 28% and Scranton Mayor Chris Doherty 46% to 23%.
  • In Florida, Attorney General Bill McCollum leads CFO Alex Sink 44% to 39%. That’s actually an improvement for the Democrat, who trailed by 11% in Rasmussen’s October survey. That poll now seems like an outlier, since Research 2000 and Quinnipiac recently found McCollum leading by 2% and 4%, respectively. As always, the Republican enjoys higher name recognition which suggests that the race should be a complete toss-up once Sink introduces herself to Democratic voters.

For all of the Democrats’ woes in the first two states, where they are also struggling in the Senate races, the party also received some good news: They have gained an edge in party registration in Colorado for the first time in years, so the gains they posted in the 2006-2008 period not only haven’t reversed themselves but they’ve somewhat surprisingly continued. The challenge for Democrats is now to ensure these voters turn out.


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

Greg Walden and Tom Tancredo rule out gubernatorial runs

Late last week, Rep. Greg Walden announced that he would run for re-election, a blow to Republican chances of contesting Oregon’s gubernatorial race. In his absence, the GOP primary will be headlined by entrepreneur Allen Alley and by former state Senator John Lim; former NBA player Chris Dudley has formed an exploratory committee, so he could still jump in.

Walden had long since entertained the possibility that he could run for statewide, which would have given the GOP a high-profile recruit against the Democratic primary’s all-star cast: former Secretary of State Bill Bradbury and former Governor John Kitzhaber are going head-to-head, while Rep. Peter DeFazio has yet to rule out jumping in the race. (Conventional wisdom is still one of skepticism that DeFazio might abandon his relatively safe and increasingly influential position in the House for such a difficult tough primary; but every time state observers are preparing to cross him out, the progressive Democrat is reiterating his interest in the race and insisting he could still jump in.)

Whoever Democrats nominate will now be clearly favored in the general election. That’s not to say that Republicans won’t have a shot at victory, but it will be an uphill climb. Lim is now 73 (rarely an age at which a candidate can be so gripping as to get voters to go against their traditional allegiances), while Dudley will have to demonstrate he has the political skills necessary to be taken seriously by voters (there are plenty of examples of sports player successfully entering politics, but such a transition can never be taken for granted). That leaves us with Alley, who actually performed well in his 2008 campaign for state Treasurer: He lost 51% to 45%, which means he significantly outperformed John McCain.

Walden’s decision has little consequence in the battle for the House: OR-02 is a heavily Republican district (it voted for Bush by 23% in 2004 and it went for McCain by 11% last year). Had Walden retired in a 2006-like environment and Democrats might have had a shot at winning it, but for him to leave the seat open next year wouldn’t have been a big headache for the NRCC.

Meanwhile, another Republican bowed out of a Governor’s race but this time, Democrats are the one who are disappointed.

Two weeks ago, the news that former Rep. Tom Tancredo was preparing to jump in Colorado’s gubernatorial race had threatened to completely alter the way race’s outlook. At worst for the GOP, Tancredo would have won the primary, transforming the general election on a referendum on his controversial persona and extremist rhetoric rather than on Governor Bill Ritter’s record; at best, the establishment would have powered former Rep. Scott McInnis through, but he would have emerged wounded, bruised up and unsure of benefiting from a united base.

But those worries dissipated as quickly as they appeared: McInnis’s nemeses rallied by his side this week-end. First, state Senator John Penry (who just dropped out of the Governor’s race two weeks ago) endorsed him; then, we learned that Tancredo was not only pulling the plug on a statewide run, but that he was preparing to back McInnis as well!

We can now be all but certain that the general election will pit Ritter to McInnis, a highly competitive match-up since the challenger has been narrowly ahead in recent polls.

These unexpected developments occurred after Penry and Tancredo convinced McInnis to adhere to a conservative platform (entitled “Platform for Prosperity”) that the three politicians devised with the help of other Republicans. In an unlikely show of party unity given how divided Colorado Republicans looked recently (and to some level have looked for years), the platform’s unveiling was also attended by former Governor Bill Owens.

As such, Colorado’s intraparty fight will have had the most ideal resolution the Republican establishment can dream of: It got its choice pick, it did so peacefully and the party’s conservative wing emerged satisfied since it got some concession. Perhaps McInnis will get a call from Jane Norton in the days ahead; she surely would like such a resolution to the tough Senate primary that’s shaping up between her, Ken Buck and Tom Wiens.

Since we’re on the subject of Governor’s races: I shall have new gubernatorial rankings out shortly, probably early next week.


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

Tancredo signals he’ll run for Governor, sets up yet another brutal GOP primary

Charlie Crist’s inevitability aura collapsed so suddenly that I am still taken aback by every new development that confirms Marco Rubio’s momentum. If there was still any doubt that the conservative establishment was still hesitating to embrace the former Speaker, this ought to dissipate it: Rubio will keynote the 2010 Conservative Political Action Conference, a very important annual gathering at which prominent Republicans pay homage to movement conservatives.

If the Club for Growth’s endorsement signaled that the Doug Hoffman coalition was moving to Florida, CPAC organizers’ decision suggests we might be getting to a point at which Crist becomes so radioactive that establishment politicians - at the very least those who have presidential ambitions - are forced to stay away from him.

This gets us to one of the most fascinating aspects of the GOP’s civil war: The Republican establishment is being forced to abandon some of its own. After all, it’s not like any politician can feel that safe at the moment: They are plenty of Republicans who are not moderates but are in danger of being Scozzafava’d. Their apostasy isn’t be related to policy, but to process-related issues - whether an unsatisfactory tone, their proximity to the national leadership, their weak ties to local activists.

Rep. Roy Blunt was in such a position: He might be a conservative congressman, but the fact that he was the GOP’s obvious candidate in the open Senate race was bound to attract movement conservatives’ animosity and he is lucky that Sarah Steelman, who had spent a few months blasting Blunt as a “white man in a suit,” chose not to pursue a primary challenge.

One Republican who isn’t so lucky is former Rep. Scott McInnis. He was not known as a centrist during his six terms in Congress; now that he is running for Governor, however, his status as a mainstream Republican with extensive ties to Washington makes him look untrustworthy to movement conservatives. A few days ago, McInnis caught what looked like a major break when state Senate Minority Leader Josh Penry dropped out of the race, but it now looks like Penry’s exit only set the stage for a higher-profile intraparty fight.

Former Rep. Tom Tancredo, a darling of the national far-right due to his views on immigration and foreign policy, is preparing to enter the race. And given the GOP electorate’s mood, Tancredo would have an excellent shot of beating McInnis.

In remarks he made this week, Tancredo left little doubt that he would position himself as the Tea Party candidate. “I’m not part of the Republican establishment,” he said. “My allegiance is more to a philosophy that it is to a party.” There is little doubt that Tancredo’s candidacy would capture the imagination of Colorado’s conservative activists and of national organizations. His presidential campaign in 2008 was just a last hurrah for a man whose reputation was long already established.

(Note that Tancredo was supporting Penry, so his entry is directly related to the state Senator’s exit. In fact, conservative mistrust towards McInnis is bound to increase due to the circumstance of Penry’s withdrawal: The Denver Post reports that a wealthy McInnis supporter approached Penry to inform him that a political committee was being created with the goal of launching independent expenditure attacks against anyone challenging McInnis - the type of heavy-handed tactic conservatives say is characteristic of the Republican establishment.)

Tancredo’s entry in the race is already delighting Democrats. At worst, McInnis will win the primary - but will do so bruised and having attracted the eternal animosity of Tancredo’s passionate supporters. At best, Tancredo will make it to the general election; not only would he face a harder time winning statewide than McInnis, but he is so controversial that the election would cease to be a referendum on Ritter’s record to become a referendum on Tancredo - a shift any incumbent governor would love to enjoy in 2010.

A February poll conducted by PPP found Governor Bill Ritter ahead of Bob Beauprez 46% to 40% but leading Tancredo 52% to 38%. Ritter’s numbers have considerably worsened since then (PPP has shown McInnis moving into a lead in recent months), but that doesn’t reduce the significance of the 8% differential between Beauprez and Tancredo’s performances. What I find most interesting is that there are far less undecided voters in the match-up involving Tancredo, and that this allows the governor to cross 50%: Tancredo is a polarizing figure who would have trouble forming a winning coalition.

With him as their nominee, Republicans would pay a steep price among Hispanics: That February PPP poll found Beauprez winning that group by 14%, while Tancredo lost it by 18% - a huge turnaround. Sure, the party’s other Republican candidates might not be as anti-immigration as he is, but their gubernatorial nominee would define the party’s brand and push Hispanics in the Democratic camps in races up-and-down the ballot. This could have an important impact in the Senate race.

Yet, for the same reasons I think Democrats shouldn’t wish Sarah Palin won the Republican nomination in 2012 (she’d likely take the GOP towards an electoral nightmare, but she still could win and then what would the left do?), I think Democrats should be very careful what they wish for in Colorado: Tancredo would face a tougher time winning the general election, but he could very well succeed. (In fact, he’s far more likely to do so.)

A Research 2000 poll conducted last December found his favorability rating at 41-46; that’s bad, but not so bad as to make him unelectable. Polls suggest Colorado is particularly tricky for Democrats, the national environment could be very sour for the party, incumbent governors could tank everywhere, the economy might not turn around, Ritter’s approval rating might dip even lower - all factors that make a Tancredo governorship a distinct possibility.


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

Richard Blumenthal, Josh Penry exit Governor’s races

Blumenthal and Simmons deny interest in succeeding Rell

Jodi Rell’s abrupt announcement that she will not seek re-election has altered Connecticut’s political landscape, but the biggest question mark has already been take care of: Attorney General Richard Blumenthal made it clear he would not jump in the now open race.

At the same time, Blumenthal delighted liberals nationwide by making it clear he is looking at running for Joe Lieberman’s Senate seat in 2012. “It would be a challenge that I would welcome, if it were the right time to do it, and I thought I could make a difference,” he said. “Stay tuned.” (Note that Lieberman has yet to make it clear whether he’ll seek the Democratic nomination, run as an independent from the start or even enter the Republican primary.)

Blumenthal would have entered the Democratic primary with an edge given his prominent stature, so his exit leaves the race wide open: A Quinnipiac poll released this morning finds Secretary of State Susan Bysiewicz leading Ned Lamont 26% to 23%, with Stamford Mayor Dan Malloy at 9%. This is anyone’s race to win.

In the general election, Quinnipiac tested Rell since the survey was completed before the governor announced her retirement. There is speculation that the pollster leaked the results to the Governor’s office and that Rell took her decision after seeing that she was leading Bysiewicz by a worrisome margin: 46% to 40%. (In February, she was ahead by 21%.) But Rell posts much wider leads against Lamont (53% to 33%) and Malloy (52% to 33%).

Thus, Lamont might have his share of dedicated supporters that carry him into a primary tie with Bysiewicz but he performs 14% worse than her in the general election - a result that cannot be explained by a difference of name recognition, since the two enjoy an equivalent level of notoriety. Rather, Lamont seems plagued by the resentment of Lieberman voters. His favorability rating is mediocre overall (31% to 24%, compared to 43-11 for Bysiewicz); it is weaker both among Democrats (45-11 compared to 55-3) and independents (27-27 compared to 41-12).

Of course, we know since Rell’s retirement that the Democratic nominee won’t have to face a Republican who is as uncommonly popular among independents as the incumbent, which dramatically improves the party’s prospects of picking-up the governorship.

On the other hand, we don’t yet know how voters view Lieutenant Governor Michael Fedele, who has over the past 48 hours solidified his hold on the Republican nomination thanks to other potential candidates ruling out gubernatorial runs. In particular, all 5 of the GOP’s Senate candidates (all of whom have a credible shot at the nomination) denied any interest in switching races. That means that state Senator Sam Caligiuri, former Ambassador Tom Foley, businesswoman Linda McMahon, economic commentator Peter Schiff and former Rep. Rob Simmons will still battle it out for the right to face Chris Dodd.

That says a lot about the Democratic senator’s vulnerability. Sure, if one of these Republicans were to switch races, he’d have to get through Fedele but that isn’t any more difficult than winning a 5-way Senate primary. But the GOP’s prospects of defeating Dodd are higher than those of defending the governorship: In a blue state like Connecticut, a Republican has a better shot at statewide victory if he’s facing an unpopular incumbent than if he’s running for an open seat, which is why some Democrats were eager to push Corzine off of the ballot this summer.

Penry leaves Colorado’s Republican field to McInnis

Another state in which a Republican candidate might benefit from an unexpectedly easy gubernatorial primary is Colorado. We were expecting a high-stakes battle between former Rep. Scott McInnis and state Senate Minority Leader Josh Penry, an ambitious 33-year old who was held up by many Republicans as a rising star of the party.

Yet, Penry was failing to gain much traction. Polls showed him widely trailing McInnis and he could not get the former representative to  treat him like a serious rival. Add to that the fact that Penry was up for re-election in 2010 (so he would not have been able to fall back to his seat in the state Senate had he lost the Governor’s race) and that he is young enough that he can wait for another opportunity, and it is no shocker that he decided to drop out.

His move leaves the Republican field to McInnis and sets up what should be one of 2010’s most competitive Governor’s races: Ritter vs. McInnis.

Polls have repeatedly shown the Republican narrowly ahead, which at least suggests that he doesn’t face a major electability problem and Democrats shouldn’t look forward to facing him. Sure, they will be able to use his years in Washington against him - the electorate has decisively soured on anyone’s whose part of Congress lately - but Penry faced his own problem: it can be difficult for candidates as young as Penry to be elected to an office like governorship.

Another reason that Republicans should be relieved is that Penry had little choice but to run an anti-establishment campaign. “I think there’s been a recognition that if we continue to run the same old campaign with the same old type of message, that’s there’s going to be the same old results, which are resounding election night defeats,” he said over the summer. That kind of rhetoric is typical for any candidate who is facing a more established contender, but in the current context it could have led this primary to be covered through the lens of the GOP’s civil war. Given that Colorado holds a late primary (August), the rifts that might have then been created could have boosted Ritter’s re-election prospects.


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

Dodd once again in precarious position, Ritter once again trailing, Burr once again stuck in low 40s

I’m on record arguing that reports of coming Democratic doom are exaggerated, but it would be delusional to minimize the fact that a variety of pollsters (Mason Dixon, PPP, Rasmussen, R2000, Quinnipiac) are now showing the Majority Leader trailing a real estate developer and other incumbent Democratic Senators losing to city councilors and low-profile businessmen. Those who think that pointing this out is exhibiting a Republican bias are in denial - and yet another poll released today confirms that the DSCC will have plenty to defend in 2010.

Testing Connecticut for the first time this year, Rasmussen found the same result as Quinnipiac earlier this summer: Senator Chris Dodd trails former Rep. Rob Simmons by a substantial margin. While Quinnipiac had Simmons up 48-39, Rasmussen finds him ahead 49% to 39%, a showing made all the more worse for the Democrat by his dismal favorability rating (4o% to 59%) and by the fact that he struggles against other Republicans: He trails former Ambassador Tom Foley 43% to 40% while he leads state Senator Sam Caliguri 43% to 40% and the libertarian Peter Schiff 42% to 40%.

The poll’s most interesting finding is the confirmation that Dodd’s troubles have everything to do with his personal image. Barack Obama’s approval rating stands at a strong 59% to 39% and his 3 latter Republican opponents are competitive despite posting mediocre-to-bad favorability ratings of their own. As such, Dodd’s fall is not due to a deterioration in the Democratic brand but rather to months of controversy that have sapped voters’ confidence in Dodd’s ethics.

This is not comforting to the Senator, as it could be harder for him to climb back in contention if what he has to improve is his reputation rather than the national environment. But it could prove comforting to national Democrats, as it suggests Dodd’s misfortune should not be generalized as a sign that other veteran Senators could be vulnerable.

Democrats looking up in CA, in precarious position in CO

Indeed, another Democratic Senator has some reason to celebrate tonight: A new PPIC poll of California adds to the surveys (Field Poll, Research 2000) that found Barbara Boxer has little to worry about next year. While PPIC did not test any head-to-head match-up with Carly Fiorina, it found Boxer posting a strong approval rating - 53% to 32%. That’s roughly equal to the approval rating of her colleague Diane Feinstein (54-32), who no one would think of calling vulnerable. Given that Republicans often make a lot of empty noise about the Golden State, this Senate race is for now not one the DSCC should lose much sleep over.

Furthermore, the poll suggests that the Democratic brand as a whole remains popular in the country’s biggest state: Barack Obama enjoys a high rating (63% to 32%) and Nancy Pelosi’s numbers are positive as well (49-40). On the other hand, Governor Arnold Schwarzenegger is flirting with Bush-territory, with a 30% to 61% rating. With California set to host a large number of competitive House races (Democrats are at least targeting CA-03, CA-45, CA-48), these ratings could have a decisive impact on the 2010 landscape.

Yet, just as Democrats look to be in a strong overall position in California, it looks like both of their major Colorado incumbents are facing troublesome. To this afternoon’s poll finding Michael Bennet in trouble in the Senate race, Rasmussen added a gubernatorial poll as well. It has Governor Bill Ritter trailing former Rep. Scott McInnis 44% to 39%; he manages a 41% to 40% lead against the far lesser-known Josh Penry, the state Senate’s Minority Leader. It is somewhat surprising that Ritter does not enjoy better head-to-head numbers given that his approval rating is not particularly worrisome (49-49), nor is his favorability rating even negative (47-42).

Combined with the fact that McInnis is no unknown but a popular former congressman, those numbers suggest Ritter is not in as worrisome a situation as other governors (say Corzine) or even as Bennet. But there is no question that for any incumbent to be hovering around the 40% mark - let alone trailing any opponent by 5% - is a sign of great vulnerability. That’s all the more so the case given that Rasmussen’s numbers are confirmed by the Democratic firm PPP, which found Ritter tying Penry and trailing McInnis by 8% back in August.

As always, Burr fails to break out of low 40s

The day’s final statewide poll is a PPP survey of North Carolina. The poll finds North Carolina Richard Burr’s approval rating at 38-32. His closest competitor is not SoS Elaine Marshall, who just announced a race, but Rep. Bob Etheridge, who trails 41% to 34%. Burr leads Marshall and former LG Dennis Wicker 42% to 31%. He is up 42% to 30% against former state Sen. Cal Cunningham, 43% to 29% against Chaper Hill Mayor Kevin Foy and 43% to 27% against attorney Kenneth Lewis. The relatively small difference between the performances of Marshall/Wicker and that of the lesser-known Cunningham/Lewis suggest these numbers are more a reflection on voters’ perception of Burr than of the Democrats’ individual strength.

The poll leaves us with the same bottom line we have been repeating for months: Burr’s surprisingly low name recognition and his repeated failure to break out of the low 40s tag him as a clearly vulnerable incumbent - especially now that Democrats have gotten a highly credible candidate to commit to the race (as I wrote two days ago, Marshall’s entrance is great news for Democrats not because she is already in a strong position poll-wise but because she occupies a prominent enough position that her candidacy cannot but attract the DSCC and liberal groups’ attention.) However, he manages to post substantial leads; that’s more than we can say of Democratic senators who on paper are in a similar position.


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

Poll watch: Republicans Grayson, McCollum and McInnis grab leads

Grayson holds slight edge in first post-Bunning poll

My surprise over Rand Paul’s strong showing led me to ignore the rest of that survey, though all of it was newsworthy: Kentucky remains a dramatically underpolled state and SUSA’s poll is one of the first released this entire year. This dearth of information is quite a shame since Kentucky’s race is more important than North Carolina or Florida’s often-polled contests since and Democrats have a stronger takeover chance here - or so we thought before Jim Bunning announced his retirement.

What is the situation now that the Senate race is open? The poll confirms what we had guessed: Bunning’s retirement improved the GOP’s prospects. Had he ran for re-election, Democrats would have enjoyed a slight edge because of his unpopularity; but as things stand now, the race is essentially a contest between credible statewide officials from both parties - and in such a generic partisan battle, Republicans are bound to have a slight advantage in what is a red-leaning state.

The poll finds Secretary of State Grayson leading Lieutenant Governor Dan Mongiardo 46% to 40%; against Attorney General Jack Conway, the margin is 44% to 37%.

Unfortunately, SUSA did not test favorability ratings so we cannot know whether any of Grayson’s lead comes from an advantage in name recognition. Comparatively low-profile Rand Paul’s competitiveness does suggest that the state’s electorate is in a GOP-friendly mood, however: If he were to win the GOP nomination, he would start trailing but not by much: Conway is ahead 43% to 38% and Mongiardo 43% to 41%.

There isn’t a meaningful electability difference between the two Democrats; to the extent that there are more Democrats who are undecided in match-ups involving Conway, the AG might have a bit more room to grow but that is negligeable. We’ll see whether a gap will open up once voters see both men in action over the next few months. And there isn’t much space between the two in the Democratic primary either: SUSA shows Mongiardo ahead 39% to 31% thanks to his lead in rural areas; Conway leads big in the Louisville region.

McCollum takes narrow edge in Quinnipiac survey

Ever since Florida’s gubernatorial race became competitive in May, Quinnipiac had been the only pollster to find any sort of lead for Democratic candidate Alex Sink - a 4% lead in an early June poll. Yet, Quinnipiac’s latest survey has them joining other pollsters in finding that Republican Bill McCollum enjoys a slight advantage: 38% to 34%, with a high 25% of voters undecided. The difference between the two polls comes from a 20% rightward shift among independent - we shall maybe know in the future whether that’s statistical noise or whether it’s due to a change in the national environment.

The good news for Sink is that she has a lot of room to grow since she has only a fraction of McCollum’s name recognition: While 55% of respondents have an opinion of McCollum, only 32% have one of Sink. That kind of differential is bound to impact general election trial heats, and it’s a testament to Florida’s competitiveness that Sink is already within 4% before introducing herself to voters.

On the other hand, McCollum is looking far more popular than is typical for a two-time failed Senate candidate: His favorability rating is a very solid 42-13 while 53% of respondents approve his job as Attorney General. So it’s not like voters are just waiting to be introduced to a strong alternative to suddenly desert McCollum, who looks popular among respondents who are now calling themselves independent.

Ritter trails McInnis in Colorado

It’s been a few months that Bill Ritter has gone from seemingly safe to highly endangered incumbents, and the curse that is plaguing governors nationwide is showing no sign that it will leave its approval ratings intact. But is that awareness enough to prepare us for ugly numbers like those of PPP’s latest poll?

PPP, which can hardly be accused of trying to boost Republicans, had already found Ritter in trouble in an April poll but its latest release finds the governor with his lowest approval rating of the cycle: This 40% to 45% is a stark drop from the 49% to 36% Ritter posted in PPP’s December survey.

The head-to-head match-ups are no prettier: Ritter trails former Rep. Scott McInnis 46% to 38%. He also fails to lead state Senator John Penry; Republicans might say isa rising star, but he still has a low enough profile that his tying Ritter at 40% is a very worrisome sign. For an incumbent to be under 50% is a clear sign of vulnerability, but to struggle to break the 40% mark against a little-known opponent is enough to put you on the list of most endangered governors.

Interestingly, these numbers are similar to the Senate results PPP released a few days ago: Ritter and Senator Michael Bennet both havor in the high 30s-low 40s range with their Republican opponents osclliating between a slight deficit and a lead depending on their notoriety. That suggests that these incumbents’ weak numbers have as much to do with the national environment as with anything particular pertaining to their tenures. What’s unfortunate for Democrats is that neither of their incumbents will be able to pull the other upward.


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

GOP resolves Illinois feud, gets crowded Colorado primary

Kirk re-enters Illinois Senate race

Andy McKenna was unable to sustain a week-end of heavy pressure from national Republicans. After he signaled late last week that he would not step aside for Rep. Mark Kirk, the chairman of the Illinois Republican Party released a statement today touting the need for party unity. “Mark Kirk and I met last evening as part of an ongoing discussion about the U. S. Senate race,” he said. “I reassured Mark that if he chooses to be a candidate, I will not oppose him.”

“I will run if Andy does not,” Kirk told The Hotline on Friday, so it now seems safe to say that the GOP will get their top candidate to run after all - a big relief for NRSC officials who were shell-shocked by Friday’s turn of events.

Thus, Illinois’s Senate seat will be a crucial battleground. Democrats start with an edge, but Kirk is well-positioned to win over independent voters and any complication in the national environment could push him across the finish-line. Also, the confirmation that Kirk will run for Senate will allow the jockeying to start for the House seat he’s leaving behind - and that is good news for Democrats.

There is also some news on the Democratic side, as The Fix alludes to speculation that Chris Kennedy might not jump in the race after all; perhaps the race now looks too competitive or perhaps he is disappointed that he can’t just expect to waltz into the Senate because of his last name. In any case, his exit would be a boost to Treasurer Alexi Giannoulias who would then be expected to pile establishment support rather than splitting it with Kennedy (Reps. Foster and Hare endorsed Giannoulias this morning) and it would complicate the election for Cheryle Jackson, who would have a better shot in a three-way race than a two-way contest.

In Colorado, Penry challenges McInnis

In Colorado, State Senate Minority Leader Josh Penry announced he would run for Governor - a quick turnaround for a 33-year old Republican who was first elected to the chamber in 2006. What’s particularly surprising in Penry’s decision is that it is not simply a way to increase his profile for future races: Penry is up for re-election in 2010, so he will have no position to fall back to if he loses the gubernatorial race.

Republicans have long been touting Penry as a rising star but the campaign won’t be easy: He’ll first have to face former Rep. Scott McInnis, who served six terms in the House before retiring in 2004; if he wins the GOP nomination, he’ll be up against Governor Bill Ritter, whose support has been declining in polls but who proved to be an unexpectedy strong candidate in 2006.

Yet, Penry has enough political experience to make for a credible candidate. A PPP poll released in April found Ritter trailing McInnis 48% to 41% and leading Penry 42% to 40%. Given his lower name recognition, Penry holding the Governor within the margin of error is nothing for him to be ashamed of. But one potential problem for Republicans is that their primary will be held relatively late - August - and that could make it difficult for their nominee to mend wounds if the primary is nasty.

There certainly are ingredients that could make Penry-McInnis a divisive battle. First, the generational divide will allow Penry to blast McInnis as the same-old, same-old: “I think there’s been a recognition that if we continue to run the same old campaign with the same old type of message, that’s there’s going to be the same old results, which are resounding election night defeats,” he already said over the week-end. Furthermore, McInnis is Penry’s former boss - making for an awkward dynamic - and he supported his brother-in-law in the 2006 state Senate race Penry eventually won, which increases the bad blood between the two.

A side note about Colorado’s Senate race: former Rep. Bob Beauprez, the highest-profile Republican who is considering challenging Senator Michael Bennet, is also thinking about running against Ritter. That the Governor’s race now looks like it will involve a slugfest between top Colorado Republicans should be enough to push Beauprez towards the Senate contest. Whether that would be good news for Republicans is an entirely different question, however: Beauprez might not be the GOP’s best shot at winning the race.



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