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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php on line 404

Strict Standards: Declaration of PropertyCollection::create() should be compatible with ItemCollection::create() in /homepages/2/d76355920/htdocs/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php on line 452

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

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/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/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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

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

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

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

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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

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

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

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

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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

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

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

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

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 306

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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

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

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

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

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/conlib/session.inc on line 508

Warning: Cannot modify header information - headers already sent by (output started at /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php:404) in /homepages/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/conlib/session.inc on line 513

Warning: Cannot modify header information - headers already sent by (output started at /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php:404) in /homepages/2/d76355920/htdocs/conlib/session.inc on line 513

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/conlib/session.inc on line 514

Warning: Cannot modify header information - headers already sent by (output started at /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php:404) in /homepages/2/d76355920/htdocs/conlib/session.inc on line 514

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/conlib/session.inc on line 515

Warning: Cannot modify header information - headers already sent by (output started at /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php:404) in /homepages/2/d76355920/htdocs/conlib/session.inc on line 515

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/conlib/session.inc on line 516

Warning: Cannot modify header information - headers already sent by (output started at /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php:404) in /homepages/2/d76355920/htdocs/conlib/session.inc on line 516

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/conlib/session.inc on line 517

Warning: Cannot modify header information - headers already sent by (output started at /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php:404) in /homepages/2/d76355920/htdocs/conlib/session.inc on line 517

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/conlib/session.inc on line 518

Warning: Cannot modify header information - headers already sent by (output started at /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php:404) in /homepages/2/d76355920/htdocs/conlib/session.inc on line 518

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/conlib/session.inc on line 153

Warning: Cannot modify header information - headers already sent by (output started at /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php:404) in /homepages/2/d76355920/htdocs/conlib/session.inc on line 153

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/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/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/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/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/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/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/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/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/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/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/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/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/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/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/classes/class.frontend.permissions.php on line 165

Strict Standards: Declaration of FrontendPermissionCollection::create() should be compatible with ItemCollection::create() in /homepages/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/classes/class.frontend.users.php on line 150

Strict Standards: Declaration of FrontendUserCollection::create() should be compatible with ItemCollection::create() in /homepages/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/classes/class.frontend.groups.php on line 111

Strict Standards: Declaration of FrontendGroupCollection::create() should be compatible with ItemCollection::create() in /homepages/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/classes/class.frontend.groups.php on line 228

Strict Standards: Declaration of FrontendGroupMemberCollection::create() should be compatible with ItemCollection::create() in /homepages/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/classes/contenido/class.user.php on line 72

Strict Standards: Declaration of cApiUserCollection::create() should be compatible with ItemCollection::create() in /homepages/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/contenido/classes/UrlBuilder/Contenido_UrlBuilder.class.php on line 55

Strict Standards: Static function Contenido_UrlBuilder::getInstance() should not be abstract in /homepages/2/d76355920/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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/cms/front_content.php on line 201

Warning: Cannot modify header information - headers already sent by (output started at /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php:404) in /homepages/2/d76355920/htdocs/cms/front_content.php on line 201

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/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/2/d76355920/htdocs/contenido/classes/contenido/class.clientslang.php on line 185

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 'CEST/2.0/DST' instead in /homepages/2/d76355920/htdocs/cms/front_content.php on line 954

Warning: Cannot modify header information - headers already sent by (output started at /homepages/2/d76355920/htdocs/contenido/classes/class.properties.php:404) in /homepages/2/d76355920/htdocs/cms/front_content.php on line 954

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

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