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

Genocide Alert Policy Brief: Auswirkungen begrenzter Luftschläge  

auf die syrische Zivilbevölkerung 


Nach dem Giftgaseinsatz am 21. August in Vororten von Damaskus wird eine zeitlich begrenzte militärische Reaktion gegen die syrische Regierung erwogen. Eine derartige Intervention wäre in erster Linie eine Strafaktion, die das Regime von Präsident Assad von künftigen, möglicherweise systematischeren Einsätzen chemischer Waffen gegen die Zivilbevölkerung abschrecken soll. Das vorliegende Papier analysiert die Frage, welche Konsequenzen ein Militäreinsatz für den Schutz der syrischen Zivilbevölkerung haben könnte. [Weiter zum Policy Brief]

Die Schutz­ver­ant­wor­tung - "Re­s­pon­si­bi­li­ty to Pro­tect" und Deutsch­land 

 

bosnienIm Jahr 2001 wur­de von ei­ner in­ter­na­tio­na­len Kom­mis­si­on mit dem Prin­zip der Schutz­ver­ant­wor­tung - Eng­lisch "Re­s­pon­si­bi­li­ty to Pro­tect" (RtoP) – ein neu­es Kon­zept zur Ver­hin­de­rung von Mas­sen­ver­bre­chen ent­wi­ckelt. Das Ziel: Staat­li­che Sou­ve­rä­ni­tät und Men­schen­rechts­schutz soll­ten mit ein­an­der in Ein­klang ge­bracht, die Ver­ant­wor­tung der in­ter­na­tio­na­len Ge­mein­schaft zur Ver­hin­de­rung schwers­ter Men­schen­rechts­ver­let­zun­gen fest­ge­schrie­ben wer­den. Nur vier Jah­re spä­ter wur­de das Kon­zept der Schutz­ver­ant­wor­tung auf dem Mil­le­ni­ums-Gip­fel­tref­fen der Ver­ein­ten Na­tio­nen von aus­nahms­los al­len Mit­glieds­staa­ten im Jahr 2005 an­er­kannt.    


In Kenia, Li­by­en und der El­fen­bein­küs­te hat sich die in­ter­na­tio­na­le Ge­mein­schaft ent­schlos­sen ge­zeigt, Mas­sen­ver­bre­chen ver­hin­dert. An vie­len an­de­ren Or­ten zö­gern die UN und ih­re Mit­glieds­staa­ten, ih­rer Ver­ant­wor­tung ge­recht zu wer­den. So­lan­ge aber das Ver­spre­chen ei­ner Welt oh­ne Völ­ker­mord nicht ein­ge­löst ist, bleibt die Um­set­zung der Schutz­ver­ant­wor­tung ei­ne der wich­tigs­ten Mensch­heits­auf­ga­ben des 21. Jahr­hun­derts.

 

 

Über Schutz­ver­ant­wor­tung.​de  

 

Das Por­tal www.​schutz­ver­ant­wor­tung.​de ist ein Pro­jekt der Men­schen­rechts­or­ga­ni­sa­ti­on Ge­no­ci­de Alert e.V. Es ver­folgt zwei Zie­le. 

  1. Das Kon­zept der Schutz­ver­ant­wor­tung ei­ner deutsch­spra­chi­gen Öf­fent­lich­keit nä­her zu brin­gen, über ih­re Ur­sprün­ge und Aus­ge­stal­tung zu in­for­mie­ren und auf die­sem Weg zu ih­rer Ver­brei­tung und Um­set­zung bei­zu­tra­gen.  
  2. Ei­ne über­par­tei­li­che Platt­form zur Dis­kus­sio­nen der Schutz­ver­ant­wor­tung in Deutsch­land und der Welt zu bie­ten. Wie po­si­tio­nie­ren sich Po­li­tik und Par­tei­en zur Schutz­ver­ant­wor­tung? Wie kann Deutsch­land zu ei­ner bes­se­ren Um­set­zung der Norm bei­tra­gen? Was kann und soll­te Deutsch­land zu der Ver­hin­de­rung von ak­tu­el­len und zu­künf­ti­gen Mas­sen­ver­bre­chen bei­tra­gen?  



Menschenrechtszeugnis

Das Menschenrechtszeugnis zur 

Bundestagswahl

Tom Koenigs Robert Schütte ÜbergabeKurz vor der Bundestagswahl veröffentlicht die deutsche Menschenrechtsorganisation Genocide Alert e.V. eine Bewertung der Wahlprogramme. Benotet wurde die Menschenrechtspolitik der Bundestagsparteien. Die Grünen siegen vor den Liberalen, die Linke fällt als einzige Partei durch.

Mehr zum Menschenrechtszeugnis. 

Das Menschenrechtszeugnis in PDF.

 

Zitate


merkel in buchenwald„Für uns Deut­sche bleibt die quä­len­de Fra­ge nach dem "War­um". War­um konn­te so et­was ge­sche­hen, war­um konn­te so et­was von Deutsch­land über Eu­ro­pa und die Welt ge­bracht wer­den? Uns Deut­schen bleibt der un­be­ding­te Wil­le, al­les zu tun, dass so et­was nie wie­der ge­schieht.“ 

An­ge­la Mer­kel, Bu­chen­wald, 5. Ju­ni 2009

 
Facebook
 



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