Strict Standards: Redefining already defined constructor for class wpdb in /homepages/19/d146200522/htdocs/ul/wp-includes/wp-db.php on line 57

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/19/d146200522/htdocs/ul/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/19/d146200522/htdocs/ul/wp-includes/cache.php on line 384

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/19/d146200522/htdocs/ul/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/19/d146200522/htdocs/ul/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/19/d146200522/htdocs/ul/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/19/d146200522/htdocs/ul/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/19/d146200522/htdocs/ul/wp-includes/classes.php on line 560

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/19/d146200522/htdocs/ul/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/19/d146200522/htdocs/ul/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/19/d146200522/htdocs/ul/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/19/d146200522/htdocs/ul/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/19/d146200522/htdocs/ul/wp-includes/classes.php on line 684

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/19/d146200522/htdocs/ul/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/19/d146200522/htdocs/ul/wp-includes/theme.php on line 540

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

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

Strict Standards: Non-static method K2::include_all() should not be called statically in /homepages/19/d146200522/htdocs/ul/wp-content/themes/k2/app/classes/k2.php on line 34

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/19/d146200522/htdocs/ul/wp-includes/plugin.php on line 164

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/19/d146200522/htdocs/ul/wp-includes/plugin.php on line 164

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

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGenerator::Enable() should not be called statically in /homepages/19/d146200522/htdocs/ul/wp-includes/plugin.php on line 164
Isn’t it ironic? Don’t you think? at untitledlife
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

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/19/d146200522/htdocs/ul/wp-includes/plugin.php on line 164

Strict Standards: Non-static method K2Header::random_picture() should not be called statically in /homepages/19/d146200522/htdocs/ul/wp-content/themes/k2/app/classes/header.php on line 85

Strict Standards: Non-static method K2Header::get_header_images() should not be called statically in /homepages/19/d146200522/htdocs/ul/wp-content/themes/k2/app/classes/header.php on line 72

Strict Standards: Non-static method K2::files_scan() should not be called statically in /homepages/19/d146200522/htdocs/ul/wp-content/themes/k2/app/classes/header.php on line 68

Strict Standards: Non-static method K2::_files_scan() should not be called statically in /homepages/19/d146200522/htdocs/ul/wp-content/themes/k2/app/classes/k2.php on line 299

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/kses.php on line 692


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

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

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

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

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

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

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

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

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

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


Isn’t it ironic? Don’t you think?


Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/formatting.php on line 82

Seen at work parking ramp – a white Hummer (one of the really big ones) with the following bumper sticker: Got freedom? Thank a solider!

Son, I think your bumper sticker would carry a bit more clout if you were driving something that got more than five miles to the gallon. It’s amazing to me how many people out there don’t connect our excessive gas usage with the sacrifice our soliders are making.

I, too, currently drive an earth-fucking Jeep (and we plan to replace it with a hybrid or something smaller as soon as the funds avail themselves). I would be embarrassed to place a yellow ribbon or American flag on my vehicle right now, knowing damn well that if the Middle East didn’t have oil, we wouldn’t be over there.

I also think that it’s no coinkydink that we are paying $3.25 for a gallon of gas, and our president’s family business IS the oil business. I imagine a little switch under his Oval Office desk. Memorial Day weekend, with no choice but to drive long distances? ON. Approval rating just hit an all-time low? OFF.

Now that he’s not running for re-election, it is a free-for-all at the pump. Bill never would’ve let this happen. Bill would’ve had Ann Coulter personally siphon every last vehicle in Dubai with her mouth before letting gas prices get this high (and she would’ve liked it).

On a related note, have you ever seen anyone other that short balding middle-aged white men driving Hummers? Dude, it would be much more cost-effective to forego the Hummer and simply wear a shirt that says, “My mind is not the only thing that is small.”

7 Responses to “Isn’t it ironic? Don’t you think?”


  1. 1 Suebob

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

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

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

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

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

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

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

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

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

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

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/formatting.php on line 82

    Oh, we have rich blond women driving them too. Always the skinny, always the blonde, always the ponytail. It is all required, I guess.

    I saw a youngish guy driving one and gave him the Loser sign - the big L. He followed me screaming at me for half and hour, finally pulled off an offramp, gesturing me to follow, so he could beat me up, I guess. As I said, what a loser.

  2. 2 marci lambert

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

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

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

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

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

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

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

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

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

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

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/formatting.php on line 82

    i see the rich blond women where i live driving hummers. with stickers for rangemasters (shooting range) on the back. i have to force myself not to throw up whenever i see a hummer. even the “little” h3.

  3. 3 St

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

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

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

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

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

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

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

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

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

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

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/formatting.php on line 82

    I’m pretty sure those women are married to the otherwise “less than average” guys mentioned in the post. ;)

  4. 4 Woman with Kids

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

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

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

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

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

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

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

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

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

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

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/formatting.php on line 82

    I love the shirt idea… perhaps we could get those for the other bald middle-aged men that drive the flashy sports cars and rev the engines all the time?

  5. 5 Sandi

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

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

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

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

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

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

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

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

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

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

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/formatting.php on line 82

    Isn’t it amazing how no one NO ONE (by no one I mean Repubs) get the connection between high gas prices = guy who runs our country is an oil tycoon?

    I am always just so thoroughly offended by the whole thing. Granted I drive an old full sized v-8 van, but damn our old 92 van gets better gas mileage than most the SUV’s out there. Yet, I still choose to not drive it around as much as I could or should when our boys and girls are dying over the oil.

    For those that think this isn’t about oil.. they’re wrong.

    Believe it or not, I am a military wife, and my husband who is Navy believes the same thing.

  6. 6 LurkerBabe

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

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

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

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

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

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

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

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

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

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

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/formatting.php on line 82

    a little too ironic, and yeah I really do think

    It’s like rain on your wedding day,
    It’s a free ride when you’ve already paid
    It’s the good advice that you just didn’t take
    Who would’ve thought….it figures

    :)

  7. 7 witchy

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

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

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

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

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

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

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

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

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

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

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d146200522/htdocs/ul/wp-includes/formatting.php on line 82

    Or maybe a bumper sticker that sez: “This is my real dick”

Comments are currently closed.