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
Senator Bunning looks cornered by the NRSC’s self-fulfilling prophecy 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

Senator Bunning looks cornered by the NRSC’s self-fulfilling prophecy

On Thursday, I was so perplexed by the news that Kentucky Secretary of State Trey Grayson was forming an exploratory committee for the 2010 Senate race that I neglected to even mention it on this blog. But with time comes perspective, and the time has come to ask a simple question: Did the NRSC finally manage to out-maneuver Jim Bunning?

Until last week, Grayson had said that he would not run unless the incumbent retired but Bunning was insisting that retirement wasn’t even on his mind. Thus, the news that he was forming an exploratory committee led to an obvious question: Was Grayson breaking his word or had Bunning told him that he would not seek re-election?

Within hours, press outlets cited numerous Republican sources to report that Bunning had given Grayson his blessing and had thus settled on retiring. Of course, these sources were all anonymous. Here is, for instance, Politico’s account:

Kentucky GOP operatives say [Grayson's move is] a precursor to Bunning’s retirement… “He told Trey to do this,” one senior congressional official said of Bunning. “Why else would he tell his main rival to prepare for a run?”

One Kentucky Republican operative said that the seeds of Bunning’s decision were planted at a public event back in Kentucky that both Grayson and Bunning attended several weeks ago. Bunning sensed that Grayson was getting anxious waiting for him to decide whether to run for re-election, so he told Grayson that he should just form an exploratory committee.

Yet, that same article goes on to quote Bunning:

Asked to comment outside the Senate chamber Thursday, Bunning said: “I won’t talk to you.”

And Bunning spokesman Mike Reynard insisted Thursday that Bunning currently has no plans to retire. “Senator Bunning has every intention of running,” said Reynard.

On Friday, Grayson back Thursday’s reports. “Jim Bunning suggested I form an exploratory committee several weeks ago,” he said. Still no confirmation from Bunning or from his office.

Apparently, we are to believe that the unpredictable Senator suddenly became so readable that his exact intentions were known by countless GOP operatives - all of whom knew for sure that everything Bunning and his office have been saying publicly since December (including threatening to sue the NRSC if they do not back his re-election bid) has been a lie.

What makes these operatives credible is that their analysis seems obvious: Why else would Grayson form an exploratory committee than because Bunning told him to? And why else would Bunning tell him to do so ifhe was not planning on retiring?

All of that is plausible, of course. But it is as plausible that the GOP establishment is seeking to corner a stubborn Bunning into such an untenable situation that he will have no choice but to bow out of the race.

For months, Bunning has been repeating that he will run for re-election. At first, no one took him at his words, and that’s just how the NRSC liked it. These retirement chronicles had a destabilizing effect on Bunning, his morale and his fundraising numbers. Last month, I described the NRSC’s asphyxiation strategy as such: “By continually sending off such messages, the GOP establishment is trying to harass Bunning into retirement; they are looking to exhaust him with constant underhanded insults so that the Senator finally gives up the fight.”

Yet, somewhere around the time Bunning blasted John Cornyn and threatened to sue the NRSC, people started to take the Senator seriously - opening a window for him to rebound and attract support. That window is now closed.

Whether or not Bunning actually gave Grayson his blessing, the press is now reporting that the Senator is poised to retire, about to leave the race, on the verge of calling it quits. Everything Bunning worked to build over the past few months evaporated in an afternoon based on quotes by a few anonymous GOP operatives.

In short, spreading word that Bunning is ready to bow out is the surest way to push him towards retirement. The conventional wisdom once again holds that Bunning will retire - and that should have a devastating effect on the Senator’s ability to build a credible campaign infrastructure.

Credits for The Courier Journal’s James Carroll for summarizing the situation very well in his piece “Die may be cast for Grayson’s Senate run:”

If the casual observer of Kentucky and Washington politics is confused about what the heck Bunning is up to now, don’t be.

It almost doesn’t matter, because the die is now cast.

Grayson insists he will not run if Bunning continues to seek a third term, but that is simply good political manners. The indisputable fact is that Grayson is now going to be asking Kentucky Republicans for money.

Grayson either is going to be competing directly with Bunning for cash (if the senator really is staying in the race) or simply taking over the fundraising field (if Bunning is planning to step away).

Indeed. We might never know what happened in Kentucky over the past month, nor what came down between Bunning, McConnell, Grayson and the NRSC. But it does seem hard to imagine Bunning able to mount a credible enough campaign to carry it through. Not only has McConnell signaled to GOP donors that he would rather they not contribute to Bunning’s campaign, there now is a Republican candidate - one who is ostensibly Bunning’s friend - that said donors can donate to.

When it comes to his re-election race, it looks like Bunning becomes a visionary. Here is the lament he voiced last month:

When they recruit someone to run against you in a primary, it puts doubt in people’s minds that you are going to finish the race. Therefore, they’re waiting and waiting and waiting. It’s almost a self-fulfilling prophecy.

He saw it coming, but he is proving unable to stop it. Maybe he should switch over to the Democratic Party.


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::filter_comments_array() 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 469

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

3 Responses to “Senator Bunning looks cornered by the NRSC’s self-fulfilling prophecy”


  1. 1 MSW

    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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
    May 5, 2009 at 8:04 am

    I vaguely remember that there was some speculation in 2004 that Bunning may suffer from dementia. I don’t wish this on my worst enemy, but Bunning’s bizzare behavior over the last 6 months makes me wonder if there is some truth to that old rumor.

    I know that you are joking about Bunning becoming a Democrat. I would absolutely make it clear that he’s not welcome in our caucus, not because of his far right beliefs, but because he’s so angry at the world. The GOP needs to find a way to block his nomination in 2010.

  2. 2 Taniel

    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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
    May 5, 2009 at 9:13 am

    MSW,
    I was joking indeed, and it was obviously meant to deride Specter’s willingness to jump parties if it means saving his seat! Bunning is way to conservative to consider defecting to Democrats. And Bunning’s 2004 “senior moments” indeed helped Mongiardo come within a few points of unseating him.

  3. 3 MSW

    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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
    May 5, 2009 at 11:20 am

    LOL. Bunning will not be re-elected in 2010. I was at one time thinking he would resign before his term ended, giving the KY governor a chance to appoint Chandler or whomever as a senator. My point was that with Bunning, assume the absurd. I could see Bunning threatening to leave the GOP caucus and become an independent. He’s that crazy.

Leave a Reply



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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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 'EST/-5.0/no 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