Strict Standards: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php on line 355

Strict Standards: Declaration of PropertyCollection::create() should be compatible with ItemCollection::create() in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php on line 355

Strict Standards: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php on line 404

Strict Standards: Declaration of PropertyItem::setField() should be compatible with Item::setField($field, $value, $safe = true) in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php on line 404

Strict Standards: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/classes/contenido/class.client.php on line 258

Strict Standards: Declaration of cApiClient::deleteProperty() should be compatible with Item::deleteProperty($type, $name) in /homepages/6/d241095248/htdocs/cms/contenido/classes/contenido/class.client.php on line 258

Strict Standards: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 302

Strict Standards: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 302

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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 330

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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 330

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 382

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 382

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 383

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 383

Strict Standards: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 302

Strict Standards: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 302

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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 330

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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 330

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 382

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 382

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 383

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/includes/pseudo-cron.inc.php on line 383

Strict Standards: header(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 479

Warning: Cannot modify header information - headers already sent by (output started at /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php:355) in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 479

Strict Standards: header(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 484

Warning: Cannot modify header information - headers already sent by (output started at /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php:355) in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 484

Strict Standards: header(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 485

Warning: Cannot modify header information - headers already sent by (output started at /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php:355) in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 485

Strict Standards: header(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 486

Warning: Cannot modify header information - headers already sent by (output started at /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php:355) in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 486

Strict Standards: header(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 487

Warning: Cannot modify header information - headers already sent by (output started at /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php:355) in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 487

Strict Standards: header(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 488

Warning: Cannot modify header information - headers already sent by (output started at /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php:355) in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 488

Strict Standards: header(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 489

Warning: Cannot modify header information - headers already sent by (output started at /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php:355) in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 489

Strict Standards: setcookie(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 128

Warning: Cannot modify header information - headers already sent by (output started at /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php:355) in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 128

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 138

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 138

Strict Standards: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.frontend.permissions.php on line 142

Strict Standards: Declaration of FrontendPermissionCollection::create() should be compatible with ItemCollection::create() in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.frontend.permissions.php on line 142

Strict Standards: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.frontend.users.php on line 128

Strict Standards: Declaration of FrontendUserCollection::create() should be compatible with ItemCollection::create() in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.frontend.users.php on line 128

Strict Standards: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.frontend.groups.php on line 88

Strict Standards: Declaration of FrontendGroupCollection::create() should be compatible with ItemCollection::create() in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.frontend.groups.php on line 88

Strict Standards: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.frontend.groups.php on line 205

Strict Standards: Declaration of FrontendGroupMemberCollection::create() should be compatible with ItemCollection::create() in /homepages/6/d241095248/htdocs/cms/contenido/classes/class.frontend.groups.php on line 205

Strict Standards: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/classes/contenido/class.user.php on line 49

Strict Standards: Declaration of cApiUserCollection::create() should be compatible with ItemCollection::create() in /homepages/6/d241095248/htdocs/cms/contenido/classes/contenido/class.user.php on line 49

Strict Standards: require_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowallocation.php on line 131

Strict Standards: Declaration of WorkflowAllocations::create() should be compatible with ItemCollection::create() in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowallocation.php on line 131

Strict Standards: require_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowallocation.php on line 220

Strict Standards: Declaration of WorkflowAllocation::setField() should be compatible with Item::setField($field, $value, $safe = true) in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowallocation.php on line 220

Strict Standards: require_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowartallocation.php on line 74

Strict Standards: Declaration of WorkflowArtAllocations::create() should be compatible with ItemCollection::create() in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowartallocation.php on line 74

Strict Standards: require_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowitems.php on line 179

Strict Standards: Declaration of WorkflowItems::create() should be compatible with ItemCollection::create() in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowitems.php on line 179

Strict Standards: require_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowitems.php on line 302

Strict Standards: Declaration of WorkflowItem::setField() should be compatible with Item::setField($field, $value, $safe = true) in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowitems.php on line 302

Strict Standards: require_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowusersequence.php on line 152

Strict Standards: Declaration of WorkflowUserSequences::create() should be compatible with ItemCollection::create() in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowusersequence.php on line 152

Strict Standards: require_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowusersequence.php on line 257

Strict Standards: Declaration of WorkflowUserSequence::setField() should be compatible with Item::setField($field, $value, $safe = true) in /homepages/6/d241095248/htdocs/cms/contenido/plugins/workflow/classes/class.workflowusersequence.php on line 257

Strict Standards: header(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php on line 211

Warning: Cannot modify header information - headers already sent by (output started at /homepages/6/d241095248/htdocs/cms/contenido/classes/class.properties.php:355) in /homepages/6/d241095248/htdocs/web/front_content.php on line 211

Strict Standards: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/contenido/classes/contenido/class.clientslang.php on line 150

Strict Standards: Declaration of cApiClientLanguage::deleteProperty() should be compatible with Item::deleteProperty($type, $name) in /homepages/6/d241095248/htdocs/cms/contenido/classes/contenido/class.clientslang.php on line 150
MIKE ROCKENFELLER | Official website
Klick here to get FlashPlayer 8 \n

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 193

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 193

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 196

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 196

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 193

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 193

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 196

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 196


Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 822

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/web/front_content.php(917) : eval()'d code on line 823

Neuen Eintrag verfassen



Daniela schreibt:
20. Sep 2010

Homepage:     Email:
 

Hallo Mike!

Du hast jetzt auch Fans in Ostwestfalen! :-)
Tolles Rennen am Sonntag!
Mach bitte weiter so!

Liebe Grüße und alles Gute für die nächsten Rennen
Daniela

   

Marcel Bonté schreibt:
19. Sep 2010
Hey Mike,

Gratulation zum 5. Platz !! schade das es nicht ganz aufs Treppchen gereicht hat nach der super Qualifikation aber wie ich finde ein toller Erfolg nach den letzten eher unglücklich verlaufenen Rennen als 2. bester Audi-Pilot ins Ziel zu kommen:) genieß es & so soll es weiter gehen.

LG Marcel

   

Marcel Bonté schreibt:
09. Aug 2010
vielen Dank für einen unvergesslichen Tag:)

LG von mir & meiner Mum,
Marcel

PS: "Willkommen in der DTM" lol ganz schön frech die Susie!!!, schade das es diesmal nicht so geklappt hat wie erhofft aber Kopf hoch & viel Glück für die nächsten Rennen, das wird schon wieder.

   

stefan Zeidan schreibt:
04. Aug 2010

Homepage:     Email: stefan-zeidan87@gmx.de
 

Hey mike,

Ich bin es Stefan aus der werkstatt fand es toll das du heute bei uns warst, Du ein ganz netter typ nun erzähle ich dir was mir Hobbys Schwimmen, Fußball, Musik und noch viel mehr!! Meine leidenschaft ist fußball
jetzt habe ich endlich einen
spielerpass bei der SG 2000
Mülheim-Kärlich,Geburtstag 17.09.1987 bin noch Fan-Betreuer in Mülheim-Kärlich.
Geburtsort:Koblenz

Status Single
wer cool wenn ich dich in meinen Freundeskreis aufnehmen könntr denn ich kenne viele Prommis,Die haben alle nur was mit fußball zu tun du bist echt cool drauf würde dich gerne zu meinen freunden zählen!

Kontakt: Handy 0151-18450484
Adresse: Kurfürstensraße 37 in 56218 Mülheim-Kärlich
Mail: stefan-zeidan87@gmx.de
Büro 02630/3313

Ich habe noch eine Bitte an dich

ein klassenkammerat von mir markus ist großer DTM Fan hat schon fotos mit Bernd Schneider gemacht markus ist 22J. sitz auch im Rollstuhl und hat durch seine krankheit keine Hohe Lebenerwartung könnten du, Ich und uns Mal treffen? Das wer super er würde sich sehr freuen! Name markus heimann 22J. Wohnort Kruft er würde sich auch über ein Autogram von dir freuen.
Bitte um Antwort

Gruß Stefan

PS: Viel glück fürs nächste Rennen

   

Rüdiger "Rudgar" Kessler schreibt:
01. Jul 2010
Herzlichen Glückwunsch nochmal nachträglich zum Sieg in Le Mans! Viel Glück am Norisring! ... und das mit dem "ein bißchen krank, wenn der Druck von einem abfällt" kenn ich auch - ich nenn' das meist "Spannungsabfall-Syndrom" ;-) Gruß, Ich

   

Tiefenau schreibt:
15. Jun 2010

Homepage:     Email: w.tiefenau@rz-online.de
 

Hallo Mike,

Herzlichen Glückwünsche zum tollen Le Mans Sieg wünschen Dir die 4 Tiefenaus aus Melsbach!

Waltraud, Klaus, Tobias und Stefan.

   

Fam.Homscheid schreibt:
15. Jun 2010

Homepage:     Email: elke.homscheid@t-online.de
 

Hey,MIKE Gratulation Dir u. Dem Team diesen Klassiker zu Gewinnen,Super,wir haben uns mit Dir gefreut Jürgen,elke,u.Nils Homscheid.

   

claudia luhr schreibt:
15. Jun 2010

Homepage:     Email:
 

hallihallo lieber mike
auf diesem wege nochmal herzlichen glueckwunsch zu deinem (eurem) sieg in le mans wir sind alle so mega stolz auf dich !!
vielen dank das wir dein glueck mit dir feiern durften war super schoen
wir druecken dich ganz fest lg claudia

   

Mark Holzer schreibt:
15. Jun 2010

Homepage:     Email:
 

Hi Mike,
First congratulations on the LM24 overall win. Well deserved. Youve probably have a lot going through your mind right now.
Andre Lotterer has really cool blog that tells what he is up to,his racing results, and a little bit of personal life as well. Do you think you could add some info to the news about what you do when you are not racing on a weekend.

   

Timo Ehlscheid schreibt:
14. Jun 2010

Homepage:     Email:
 

Hey Mike
alles gute zum Gesamtsieg beim 24-Stunden Rennen in Le Mans wünschen dir die 4 Ehlis vom Berg.

Liebe Grüße
die Ehlis

   

Judy W.G. schreibt:
14. Jun 2010

Homepage:     Email: rock_of_ages000@yahoo.com
 

Huge Congratulations to you, Timo & Romain (& the fab Audi crew) on winning LeMans!!! Well deserved. :Dnull

   

Jürgen schreibt:
14. Jun 2010

Homepage:     Email:
 

Chapeau und herzliche Gratulation zu diesem Supersieg bei den 24h von Le Mans!

   

Jonathan Foote schreibt:
14. Jun 2010

Homepage:     Email: Footewerks@gmail.com
 

CONGRATULATIONS ROCKY!!!! Awesome job by you and Romain and Timo and the Audi team! I can't even begin to know what you're feeling right now by taking an overall victory in the 24 Hours of Daytona and the 24 Hours of Le Mans in the same year! You've worked really hard and come a long way to get to this point and I can't think of anyone else who deserves it as much as you do and I'm sure there will be lots more victories in your future! Congratulations again and take care!

-Jon Foote

   

Pascale schreibt:
13. Jun 2010

Homepage:     Email: depiessepascale@hotmail.com
 

Bravo pour cette belle victoire Mike, elle est méritée ! A bientôt en Dtm ...

   

die Kohlis schreibt:
13. Jun 2010

Homepage:     Email: mach.kohl@t-online.de
 

Hi Mike,

waaahnsinn, super gemacht, geiler Sieg: Wir gratulieren dir von Herzen. Genieß die Momente und lass die Korken knallen!

Viele Grüße aus Niederbieber
die Kohlis

   

Marcel Bonté schreibt:
13. Jun 2010
**GRATULATION** zum Le Mans Triumph !!! und zugleich jüngster Le Mans Sieger aller Zeiten das ist ja der absolute Wahnsinn:)) dieses historische Rennen zu gewinnen haben nur die ganz Großen geschafft und Du bist jetzt einer davon, das ganze Team hat einen super Job gemacht jetzt lasst es auf der Feier mal so richtig schön krachen & genießt den Erfolg.

LG Marcel

   

Frank Kaim schreibt:
13. Jun 2010

Homepage:     Email: Frank_Kaim@web.de
 

Meinen herzlichsten Glückwunsch zu Deinem ersten Le Mans Sieg. Super Leistung. Gratulation!Ich freue mich bei einem so historischen 3fachSieg live dabei gewesen zu sein und auch für Dich muss es was ganz Besonderes sein!
F.Kaim

   

Dmitry schreibt:
13. Jun 2010

Homepage:     Email:
 

Hello, Mike!
Congratulations with Le-Mans win! It's really great! Fantastic performance, consistent lap times and two reacords beaten - laps number and distance. I think almost everybody of your fans have no words now - just emotions. Because it's an achievement that you can't compare with anything else.

   

Ralph Ringel schreibt:
13. Jun 2010

Homepage:     Email: ringel@krw-online.de
 

Hallo Herr Rockenfeller,
meine herzlichsten Glückwünsche zum Le Mans Sieg! Und zu einer weiteren Rolex!!
Beste Grüße aus Rengsdorf
Ralph Ringel

   

Manfred Hildebrand schreibt:
13. Jun 2010

Homepage:     Email: imhildebrand@t-online.de
 

Hallo Mike,
herzlichen Glückwunsch zum Le Mans
Sieg
Manfred Hildebrand aus der Nachbarschaft, Niederbieber kommt
noch ganz groß raus.

   

Rogall schreibt:
13. Jun 2010

Homepage:     Email: Hartmut.Rogall@stb-rogall.deFnABh
 

Meinen herzlichen Glückwunsch zu Ihrem ersten Le Mans Sieg mit Ihrem Team. Super Leistung. Gratulation von ganzem Herzen.
Ihr Hartmut Rogall

   

Patrick schreibt:
13. Jun 2010

Homepage:     Email: Patrick.schneider@gmx.de
 

Hey Mike, der Timo ist grad auf der letzen Runde und es ist der Wahnsinn das ihr es geschafft hat.
Jetzt hast ud deine Rechnung mit Le Mans beglichen!!
Einfach nur Hammer!!
Lass es krachen und lasst euch feiern! Ihr habts verdient!!!

   

Marcel Bonté schreibt:
07. Jun 2010
Hey Mike,

Gratulation zum 4. Platz, erneut bester Audipilot, hast stark gegen Paffett gegengehalten, wünsch Dir viel Glück für Le Mans!!

LG Marcel

   

Jo datzert schreibt:
07. Jun 2010

Homepage:     Email: jodatzert@online.de
 

Hi Mike,

super Rennen, weiter so!

Grüße aus Segendorf

   

Glanzmann Philipp schreibt:
27. Mai 2010

Homepage:     Email:
 

Hallo Herr Rockenfeller

Besten Dank für das nette Gespäch von heute morgen. Wünsche Ihnen noch eine gute Saison und allenfalls sehen wir uns ja wieder einmal unter anderen Umständen...:-)

Freundliche Grüsse

Ph. Glanzmann

   

Hans schreibt:
30. Apr 2010

Homepage:     Email: cosamaha@bluewin.ch
 

Hallo Mike
Möchte mich noch herzlichst für das super Wochenende in Hockenheim bedanken. Der Boxenbesuch mit dem Fürst war super interessant, und ich werde nächstes Jahr wieder ganz sicher dabei sein. Und vorallem möchte ich Dir zu dem Super Rennen und die gute Plazierung beglückwünschen. Werden uns sicher wieder mal sehen und der Besuch^auf die Driving Ranche steht. Gruss Hans (TC)

   

Marcel Bonté schreibt:
26. Apr 2010
*GRATULATION* zum tollen 5. Platz, bester Audipilot so kann es weiter gehen, wünsch Dir für die anstehenden Rennen viel Erfolg.

LG Marcel

PS: vielen Dank für die Autogramme habe mich sehr gefreut!

   

Fuchs-Rodenbach schreibt:
26. Apr 2010

Homepage:     Email: fuchs-neuwied@t-online.de
 

Hallo Mike toller Rennauftakt gestern Deine Eltern können stolz sein einen solchen erfolgreichen Sohn zu haben. Gruß an die Familie
Mach weiter so
Jürgen

   

Jo Datzert schreibt:
26. Apr 2010

Homepage:     Email: jodatzert@online.de
 

Hi Mike,

super Saisonstart und tolles Rennen. Selbst die Segendorfer sind stolz auf Dich ;-)) Weiter so! Gruß Jo

   

Michael Schönemann schreibt:
25. Apr 2010

Homepage:     Email: michael.schoenemann@freenet.de
 

Wow, was für ein Rennen, was für ein Saisonstart!!! Herzlichen Glückwunsch zum bisher größten DTM-Erfolg! Das scheint ja ein super Auto von einem tollen Team zu sein... Möge es so weitergehen. Die Daumen drücken Michael & Oliver (größter Fan) Schönemann

   

Martina Tavaglione-Nestola schreibt:
23. Mär 2010

Homepage:     Email: Leonardosamuele@freenet.de
 

Hallo Mike,
das anschauen deiner Homepage war schon längst überfällig, grosses Kompliment dafür.
Ich wünsche dir für die anstehenden Rennen viel Glück. Erfolg und auch Spass, besonders bei den Einsätzen gemeinsam mit Roberto.

Liebe Grüsse
Martina Tavaglione-Nestola

   

Hartmut.Rogall schreibt:
08. Mär 2010

Homepage:     Email: Hartmut.Rogall@stb-rogall.de
 

Hallo Herr Rockenfeller,

soeben dachte ich, muss doch mal schauen, was "mein Mike" dieses Jahr macht. Wummst! Da hat der Kerl schon zugeschlagen und ich hab' alles verpasst. Gratuliere!! und weiter so. Da haben Sie aber allen mal wieder gezeigt, was in Ihnen steckt, wenn man sie nur richtig bestückt.
Ich wünsche Ihnen weiter viel Erfolg für 2010 und drücke die Daumen.
Viele Grüße
Hartmut Rogall

   

Bo schreibt:
03. Feb 2010

Homepage: http://Denmark    Email: oerbjerg@gmail.com
 

Hey Rocky,
I congratulate you with the Rolex win - you are a champ!
I look forward to receive the photos you signed wiht Eddie.
Hope to meet in 24 Heures Le Mans?
Mit freundliche Grüsse
Bo from Denmark

   

Erich Serger schreibt:
03. Feb 2010

Homepage:     Email: eserger@t-online.de
 

Hallo Herr Rockenfeller,
zunächst vorweg die allerherzlichsten Glückwünsche zum Gesamtsieg bei den 24h in Daytona. Habe gestern die Berichterstattung auf Focus-online (http://www.focus.de/sport/mehrsport/motorsport- 24-stunden-rennen-porsche-siegt-erneut-in- daytona_aid_476080.html) korrigieren müssen, da es für dich ja bereits der 2. Gesamtsieg bei einem 24h Rennen war. Bereits im Jahr 2006 konntest Du ebenfalls mit Porschepower auf dem perfekt vorbereiteten Manthey 996 RSR das prestigeträchtige 24h Rennen auf der Nordschleife des Nürburgringes (u.a. als Fahrer des Schlussturns) gewinnen. Weiterhin viel Erfolg,

lG

Erich Sergerr, Ochtendung

   

Marcel Bonté schreibt:
01. Feb 2010
Hallo Mike,

gratulation zum tollen Erfolg in Daytona! wow was für ein toller Start ins Jahr 2010 so kann es weitergehen für mich als US Racing Fan wäre es echt toll Dich in Zukunft mal in der Nascar o. IndyCar Serie zu sehen zumal Du Dir durch die Erfolge in der American LeMans Serie einen Namen gemacht drüben gemacht/viele Fans hast:)) wünsche Dir auf jedenfall viel Erfolg für die anstehende DTM Saison!

LG vom ehemaligen Grundschulkameraden,
Marcel

   

Jonathan Foote schreibt:
01. Feb 2010

Homepage:     Email: Footewerks@gmail.com
 

Hello again Mike,

Just wanted to let you know that several people have posted their congratulations on your Daytona win to the Mike Rockenfeller Fan Page on Facebook. If you would like to stop by and check out the posts, feel free :) Again, take care!

Mike Rockenfeller Fan Page

   

Claus Zorn schreibt:
01. Feb 2010

Homepage:     Email: claus-zorn@t-online.de
 

Hallo Mike,

herzliche Gratulation zu deinem Sieg bei den 24h von Daytona vom Le Mans-Stammtisch Niederbieber

Frank, Michael, Berti, Walter, Klausi, Marcus, Jörg und Claus

   

Ralph Ringel schreibt:
31. Jan 2010
Hallo Herr Rockenfeller,
Herzlichen Glückwunsch zum Sieg in Daytona, und zur lange ersehnten Rolex !!
Habe den ganzen Sonntag vorm PC das Live Timing verfolgt, und eben im TV den Zieleinlauf.
Tolle Leistung!
Beste Grüße aus Rengsdorf
Ralph Ringel

   

Jonathan Foote schreibt:
31. Jan 2010

Homepage:     Email: Footewerks@gmail.com
 

CONGRATULATIONS ON THE ROLEX ROCKY!!! You certainly deserved it and I'm extremely happy for you and the Action Express Racing crew! Congratulations again Rocky!! Well Done!

   

Christopher Weiss schreibt:
01. Jan 2010

Homepage:     Email: christopher.weiss@t-online.de
 

Hallo Herr Rockenfeller,

Familie Weiss wünscht Ihnen einen erfolgreichen Saisonstart in Daytona!!!!!!!

Viele Grüße
Jannick, Marina und Christopher

   

 

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 286

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: ereg_replace(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Deprecated: Function ereg_replace() is deprecated in /homepages/6/d241095248/htdocs/cms/conlib/session.inc on line 305

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/ct_sql.inc on line 77

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead in /homepages/6/d241095248/htdocs/cms/conlib/ct_sql.inc on line 77