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/31/d254091149/htdocs/contenido/classes/class.properties.php on line 404

Strict Standards: Declaration of PropertyCollection::create() should be compatible with ItemCollection::create() in /homepages/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/htdocs/contenido/includes/pseudo-cron.inc.php on line 334

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

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

Warning: Cannot modify header information - headers already sent by (output started at /homepages/31/d254091149/htdocs/contenido/classes/class.properties.php:404) in /homepages/31/d254091149/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/31/d254091149/htdocs/conlib/session.inc on line 514

Warning: Cannot modify header information - headers already sent by (output started at /homepages/31/d254091149/htdocs/contenido/classes/class.properties.php:404) in /homepages/31/d254091149/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/31/d254091149/htdocs/conlib/session.inc on line 515

Warning: Cannot modify header information - headers already sent by (output started at /homepages/31/d254091149/htdocs/contenido/classes/class.properties.php:404) in /homepages/31/d254091149/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/31/d254091149/htdocs/conlib/session.inc on line 516

Warning: Cannot modify header information - headers already sent by (output started at /homepages/31/d254091149/htdocs/contenido/classes/class.properties.php:404) in /homepages/31/d254091149/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/31/d254091149/htdocs/conlib/session.inc on line 517

Warning: Cannot modify header information - headers already sent by (output started at /homepages/31/d254091149/htdocs/contenido/classes/class.properties.php:404) in /homepages/31/d254091149/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/31/d254091149/htdocs/conlib/session.inc on line 518

Warning: Cannot modify header information - headers already sent by (output started at /homepages/31/d254091149/htdocs/contenido/classes/class.properties.php:404) in /homepages/31/d254091149/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/31/d254091149/htdocs/conlib/session.inc on line 153

Warning: Cannot modify header information - headers already sent by (output started at /homepages/31/d254091149/htdocs/contenido/classes/class.properties.php:404) in /homepages/31/d254091149/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/31/d254091149/htdocs/contenido/classes/class.frontend.permissions.php on line 165

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

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

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

Strict Standards: Declaration of FrontendGroupMemberCollection::create() should be compatible with ItemCollection::create() in /homepages/31/d254091149/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/31/d254091149/htdocs/contenido/classes/contenido/class.user.php on line 72

Strict Standards: Declaration of cApiUserCollection::create() should be compatible with ItemCollection::create() in /homepages/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/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/31/d254091149/htdocs/contenido/plugins/mod_rewrite/classes/class.modrewrite.php on line 914

Strict Standards: Declaration of ModRewrite::initialize() should be compatible with ModRewriteBase::initialize() in /homepages/31/d254091149/htdocs/contenido/plugins/mod_rewrite/classes/class.modrewrite.php on line 914

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/31/d254091149/htdocs/contenido/classes/contenido/class.categorylanguage.php on line 110

Strict Standards: Declaration of cApiCategoryLanguage::setField() should be compatible with Item::setField($field, $value, $safe = true) in /homepages/31/d254091149/htdocs/contenido/classes/contenido/class.categorylanguage.php on line 110

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/31/d254091149/htdocs/contenido/classes/contenido/class.templateconfig.php on line 99

Strict Standards: Declaration of cApiTemplateConfigurationCollection::create() should be compatible with ItemCollection::create() in /homepages/31/d254091149/htdocs/contenido/classes/contenido/class.templateconfig.php on line 99

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/31/d254091149/htdocs/contenido/classes/contenido/class.containerconfig.php on line 58

Strict Standards: Declaration of cApiContainerConfigurationCollection::create() should be compatible with ItemCollection::create() in /homepages/31/d254091149/htdocs/contenido/classes/contenido/class.containerconfig.php on line 58

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/31/d254091149/htdocs/contenido/classes/contenido/class.container.php on line 82

Strict Standards: Declaration of cApiContainerCollection::create() should be compatible with ItemCollection::create() in /homepages/31/d254091149/htdocs/contenido/classes/contenido/class.container.php on line 82

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

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

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/31/d254091149/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/31/d254091149/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/31/d254091149/htdocs/neu/front_content.php on line 201

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

Strict Standards: preg_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 'CEST/2.0/DST' instead in /homepages/31/d254091149/htdocs/contenido/plugins/mod_rewrite/includes/functions.mod_rewrite.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/31/d254091149/htdocs/contenido/plugins/mod_rewrite/includes/functions.mod_rewrite.php on line 510
Schutzverantwortung -- Was ist RtoP
Schutzverantwortung > Was ist RtoP

Was ist die Schutz­ver­ant­wor­tung oder "Re­s­pons­bi­li­ty to Pro­tect"? 

 

Wie kön­nen Mas­sen­ver­bre­chen wie Völ­ker­mord, Ver­bre­chen ge­gen die Mensch­lich­keit, Kriegs­ver­bre­chen und eth­ni­sche Säu­be­run­gen ver­hin­dert wer­den? Wie kön­nen Men­schen­le­ben ge­schützt wer­den, wenn ein Staat un­fä­hig oder un­wil­lens ist, die­se Auf­ga­be zu über­neh­men? Wer hat die Ver­ant­wor­tung dar­über zu ent­schei­den und ein­zu­grei­fen? Ab wann ist ein Ein­griff von Au­ßen ge­recht­fer­tigt und wie ist dies mit der Staa­ten­sou­ve­rä­ni­tät zu ver­ein­ba­ren?  

 

Nach den scho­ckie­ren­den Er­eig­nis­sen in Ru­an­da und in Sre­bre­ni­ca, so­wie der um­strit­te­nen In­ter­ven­ti­on im Ko­so­vo in den neun­zi­ger Jah­ren fand in der in­ter­na­tio­na­len Ge­mein­schaft ei­ne kon­tro­ver­se De­bat­te über die Prä­ven­ti­on mas­si­ver Men­schen­rechts­ver­let­zun­gen statt, die in der Ent­wick­lung des Kon­zep­tes der "Re­s­pon­si­bi­li­ty to Pro­tect", zu Deutsch "Schutz­ver­ant­wor­tung", mün­de­te.  

Auf dem Welt­gip­fel der Ver­ein­ten Na­tio­nen im Jahr 2005 ver­pflich­te­ten sich aus­nahms­los al­le Staa­ten zur Wahr­neh­mung ih­rer Schutz­ver­ant­wor­tung, um Be­völ­ke­run­gen vor Völkermord, Kriegs­ver­bre­chen, eth­ni­schen Säu­be­run­gen und Ver­bre­chen ge­gen die Mensch­lich­keit zu schüt­zen. Die Schutz­ver­ant­wor­tung be­inhal­tet fol­gen­de Prin­zi­pi­en:  

  1. Je­der Staat hat die Ver­ant­wor­tung, sei­ne Be­völ­ke­rung vor Völ­ker­mord, Kriegs­ver­bre­chen, eth­ni­schen Säu­be­run­gen und Ver­bre­chen ge­gen die Mensch­lich­keit zu schüt­zen.  
  2. Die in­ter­na­tio­na­le Ge­mein­schaft hat die Aufgabe, Staa­ten in die­ser Ver­ant­wor­tung zu un­ter­stüt­zen.  
  3. Die in­ter­na­tio­na­le Ge­mein­schaft muss an­ge­mes­se­ne di­plo­ma­ti­sche, hu­ma­ni­tä­re oder an­de­re fried­li­che Mit­tel an­wen­den, um Be­völ­ke­run­gen vor die­sen Mas­sen­ver­bre­chen zu schüt­zen. Wenn ein Staat zum Schutz sei­ner Be­völ­ke­rung nicht fä­hig ist oder selbst die ge­nann­ten Ver­bre­chen be­geht, muss die in­ter­na­tio­na­le Ge­mein­schaft be­reit sein noch stär­ke­re Mit­tel ein­zu­set­zen, in­klu­si­ve durch den Si­cher­heits­rat be­schlos­se­ne kol­lek­ti­ve mi­li­tä­ri­sche Mit­tel. In die­sem Fall geht die Schutz­ver­ant­wor­tung auf die in­ter­na­tio­na­le Ge­mein­schaft über. 



News

Resolution ohne Schutzwirkung: Warum die Zerstörung der syrischen Chemiewaffen nicht ausreicht   Als 190. Mitglied ist Syrien am 14. Oktober 2013 der Chemiewaffenkonvention beigetreten. Die...

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/31/d254091149/htdocs/contenido/classes/contenido/class.module.php on line 70

Strict Standards: Declaration of cApiModuleCollection::create() should be compatible with ItemCollection::create() in /homepages/31/d254091149/htdocs/contenido/classes/contenido/class.module.php on line 70

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/31/d254091149/htdocs/contenido/classes/contenido/class.module.php on line 1045

Strict Standards: Declaration of cApiModuleTranslationCollection::create() should be compatible with ItemCollection::create() in /homepages/31/d254091149/htdocs/contenido/classes/contenido/class.module.php on line 1045
[mehr...]

Politische Bekenntnisse ohne Folgen. - Die deutsche Politik und die zögerliche Umsetzung der internationalen Schutzverantwortung. Gregor Hofmann von der Hessischen Stiftung Friedens und...
[mehr...]

The Responsibility to Protect and Germany's 2013 Elections      12 September.2013 The Responsibility to Protect (RtoP) or 'Schutzverantwortung' has made significant inroads in terms of...
[mehr...]

Genocide Alert Policy Brief: Auswirkungen begrenzter Luftschläge auf die syrische Zivilbevölkerung  von Robert Schütte und Christoph Schlimpert   29.08.2013 Nach dem Giftgaseinsatz am...
[mehr...]

`Ein syrisches Srebrenica' - Zur aktuellen Diskussion um Syrien, ein Beitrag des Vorsitzenden von Genocide Alert, Robert Schütte   28.08.2013   Lassen die Vereinten Nationen Assad mit seinen...
[mehr...]

 





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/31/d254091149/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/31/d254091149/htdocs/conlib/ct_sql.inc on line 103