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/8/d35752861/htdocs/contenido/classes/class.properties.php on line 403

Strict Standards: Declaration of PropertyCollection::create() should be compatible with ItemCollection::create() in /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php on line 403

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/8/d35752861/htdocs/contenido/classes/class.properties.php on line 451

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

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/8/d35752861/htdocs/contenido/classes/contenido/class.client.php on line 303

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

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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

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

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

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

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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

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

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

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

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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

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

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

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

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 309

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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/8/d35752861/htdocs/contenido/includes/pseudo-cron.inc.php on line 337

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

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

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

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

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/8/d35752861/htdocs/conlib/session.inc on line 502

Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php:403) in /homepages/8/d35752861/htdocs/conlib/session.inc on line 502

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/8/d35752861/htdocs/conlib/session.inc on line 507

Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php:403) in /homepages/8/d35752861/htdocs/conlib/session.inc on line 507

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/8/d35752861/htdocs/conlib/session.inc on line 508

Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php:403) in /homepages/8/d35752861/htdocs/conlib/session.inc on line 508

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/8/d35752861/htdocs/conlib/session.inc on line 509

Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php:403) in /homepages/8/d35752861/htdocs/conlib/session.inc on line 509

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/8/d35752861/htdocs/conlib/session.inc on line 510

Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php:403) in /homepages/8/d35752861/htdocs/conlib/session.inc on line 510

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/8/d35752861/htdocs/conlib/session.inc on line 511

Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php:403) in /homepages/8/d35752861/htdocs/conlib/session.inc on line 511

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/8/d35752861/htdocs/conlib/session.inc on line 512

Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php:403) in /homepages/8/d35752861/htdocs/conlib/session.inc on line 512

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/8/d35752861/htdocs/conlib/session.inc on line 151

Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php:403) in /homepages/8/d35752861/htdocs/conlib/session.inc on line 151

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/8/d35752861/htdocs/conlib/session.inc on line 161

Deprecated: Function ereg_replace() is deprecated in /homepages/8/d35752861/htdocs/conlib/session.inc on line 161

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/8/d35752861/htdocs/contenido/classes/class.frontend.permissions.php on line 165

Strict Standards: Declaration of FrontendPermissionCollection::create() should be compatible with ItemCollection::create() in /homepages/8/d35752861/htdocs/contenido/classes/class.frontend.permissions.php on line 165

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/8/d35752861/htdocs/contenido/classes/class.frontend.users.php on line 150

Strict Standards: Declaration of FrontendUserCollection::create() should be compatible with ItemCollection::create() in /homepages/8/d35752861/htdocs/contenido/classes/class.frontend.users.php on line 150

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/8/d35752861/htdocs/contenido/classes/class.frontend.groups.php on line 111

Strict Standards: Declaration of FrontendGroupCollection::create() should be compatible with ItemCollection::create() in /homepages/8/d35752861/htdocs/contenido/classes/class.frontend.groups.php on line 111

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/8/d35752861/htdocs/contenido/classes/class.frontend.groups.php on line 228

Strict Standards: Declaration of FrontendGroupMemberCollection::create() should be compatible with ItemCollection::create() in /homepages/8/d35752861/htdocs/contenido/classes/class.frontend.groups.php on line 228

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/8/d35752861/htdocs/contenido/classes/contenido/class.user.php on line 72

Strict Standards: Declaration of cApiUserCollection::create() should be compatible with ItemCollection::create() in /homepages/8/d35752861/htdocs/contenido/classes/contenido/class.user.php on line 72

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/8/d35752861/htdocs/contenido/plugins/workflow/classes/class.workflowallocation.php on line 148

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

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/8/d35752861/htdocs/contenido/plugins/workflow/classes/class.workflowallocation.php on line 237

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

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/8/d35752861/htdocs/contenido/plugins/workflow/classes/class.workflowartallocation.php on line 93

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

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/8/d35752861/htdocs/contenido/plugins/workflow/classes/class.workflowitems.php on line 198

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

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/8/d35752861/htdocs/contenido/plugins/workflow/classes/class.workflowitems.php on line 321

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

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/8/d35752861/htdocs/contenido/plugins/workflow/classes/class.workflowusersequence.php on line 169

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

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/8/d35752861/htdocs/contenido/plugins/workflow/classes/class.workflowusersequence.php on line 274

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

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/8/d35752861/htdocs/contenido/classes/UrlBuilder/Contenido_UrlBuilder.class.php on line 55

Strict Standards: Static function Contenido_UrlBuilder::getInstance() should not be abstract in /homepages/8/d35752861/htdocs/contenido/classes/UrlBuilder/Contenido_UrlBuilder.class.php on line 55

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/8/d35752861/htdocs/cms/front_content.php on line 242

Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php:403) in /homepages/8/d35752861/htdocs/cms/front_content.php on line 242

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

Deprecated: Function split() is deprecated in /homepages/8/d35752861/htdocs/conlib/perm.inc on line 636

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

Deprecated: Function split() is deprecated in /homepages/8/d35752861/htdocs/conlib/perm.inc on line 651

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/8/d35752861/htdocs/contenido/classes/contenido/class.clientslang.php on line 185

Strict Standards: Declaration of cApiClientLanguage::deleteProperty() should be compatible with Item::deleteProperty($type, $name) in /homepages/8/d35752861/htdocs/contenido/classes/contenido/class.clientslang.php on line 185

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/8/d35752861/htdocs/conlib/session.inc on line 216

Deprecated: Function ereg_replace() is deprecated in /homepages/8/d35752861/htdocs/conlib/session.inc on line 216

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/8/d35752861/htdocs/conlib/session.inc on line 219

Deprecated: Function ereg_replace() is deprecated in /homepages/8/d35752861/htdocs/conlib/session.inc on line 219

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/8/d35752861/htdocs/cms/front_crcloginform.inc.php on line 70

Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d35752861/htdocs/contenido/classes/class.properties.php:403) in /homepages/8/d35752861/htdocs/cms/front_crcloginform.inc.php on line 70