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

Strict Standards: Declaration of PropertyCollection::create() should be compatible with ItemCollection::create() in /homepages/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/htdocs/conlib/session.inc on line 508

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

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

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

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

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

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

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

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

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

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

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

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

Strict Standards: Declaration of cApiUserCollection::create() should be compatible with ItemCollection::create() in /homepages/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/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/38/d77179255/htdocs/contenido/classes/contenido/class.templateconfig.php on line 99

Strict Standards: Declaration of cApiTemplateConfigurationCollection::create() should be compatible with ItemCollection::create() in /homepages/38/d77179255/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/38/d77179255/htdocs/contenido/classes/contenido/class.containerconfig.php on line 58

Strict Standards: Declaration of cApiContainerConfigurationCollection::create() should be compatible with ItemCollection::create() in /homepages/38/d77179255/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/38/d77179255/htdocs/contenido/classes/contenido/class.container.php on line 82

Strict Standards: Declaration of cApiContainerCollection::create() should be compatible with ItemCollection::create() in /homepages/38/d77179255/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/38/d77179255/htdocs/contenido/classes/UrlBuilder/Contenido_UrlBuilder.class.php on line 55

Strict Standards: Static function Contenido_UrlBuilder::getInstance() should not be abstract in /homepages/38/d77179255/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/38/d77179255/htdocs/punews/front_content.php on line 199

Warning: Cannot modify header information - headers already sent by (output started at /homepages/38/d77179255/htdocs/contenido/classes/class.properties.php:404) in /homepages/38/d77179255/htdocs/punews/front_content.php on line 199

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/38/d77179255/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/38/d77179255/htdocs/contenido/classes/contenido/class.clientslang.php on line 185
PU-News

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

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

Strict Standards: Declaration of cApiModuleCollection::create() should be compatible with ItemCollection::create() in /homepages/38/d77179255/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/38/d77179255/htdocs/contenido/classes/contenido/class.module.php on line 1045

Strict Standards: Declaration of cApiModuleTranslationCollection::create() should be compatible with ItemCollection::create() in /homepages/38/d77179255/htdocs/contenido/classes/contenido/class.module.php on line 1045

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Strict Standards: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you 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/38/d77179255/htdocs/punews/front_content.php(924) : eval()'d code on line 741

Seite 1 von 7

  • Auf den Punkt gebracht – Teil 2:
    Energiesparrecht für Gebäude ab 2017

    Wer heute ein Haus oder ein sonstiges Gebäude baut, modernisiert, kauft oder erbt, stößt früher oder später auf die Anforderungen der Energieeinsparverordnung (EnEV). Im zweiten Teil des Interviews habe ich mit der Herausgeberin und Autorin des Expertenportals www.EnEV-online.de Melita Tuschinski über das kommende Energiesparrecht ab 2017 gesprochen.

    » Artikel anzeigen

  • Auf den Punkt gebracht – Teil 1:
    EnEV und Energieausweis für Gebäude

    Wer heute ein Haus oder ein sonstiges Gebäude baut, modernisiert, kauft oder erbt, stößt früher oder später auf die Anforderungen der Energieeinsparverordnung (EnEV). Ich habe mit der Herausgeberin und Autorin des Expertenportals www.EnEV-online.de Melita Tuschinski über die wichtigsten Fakten der Verordnung und den Energieausweis gesprochen.

    » Artikel anzeigen

  • Nachhaltiges Bauen

    Vom Baustoff bis zum Gebäude und seinen Bewohnern

    Wer sich mit den Themen Bauen und Sanieren beschäftigt, kommt am Begriff „Nachhaltigkeit“ nicht vorbei. Uns interessiert, wie die Merkmale eines nachhaltigen Gebäudes aussehen und wie es bewertet wird. Welche Rolle spielen Dämmstoffe bei dieser Bewertung? Gibt es auch ein Bewertungsverfahren für Dämmstoffe? Antworten und Denkanstöße zum nachhaltigen Bauen liefert dieser Beitrag.

    » Artikel anzeigen

  • Damit die Dachgeschosswohnung nicht zur Sauna wird

    So hilft eine effiziente Dachdämmung im Sommer

    Zum Thema „Sommerlicher Wärmeschutz“ haben wir in unserem Blog schon öfters berichtet. Auch dieses Jahr ist das Thema aktuell, da sich insbesondere Dachräume an heißen Sommertagen auf über 80 Grad aufheizen können und die Wohnung dann zur Sauna mutiert. Die Kühlung über mobile Klimageräte ist energieintensiv, was dem Sinn der Energieeinsparung zuwiderläuft. Ein optimaler Hitzeschutz sollte daher bei einer Dachsanierung gleich mitberücksichtigt werden. Oft wird in diesem Zusammenhang jedoch über die Wärmespeicherung von Dämmstoffen und ihre Auswirkung auf die Dachraumtemperatur diskutiert. Im folgenden Beitrag erklären wir, welche Aufgabe eine effiziente Dachdämmung im Sommer hat.

    » Artikel anzeigen

  • Auf der Suche nach Energieeinspar-Potenzialen - aber:
    
Sinnvolle Energieberatung gibt´s nicht von der Stange

    Mehr Komfort, weniger Energieverbrauch und dauerhafter Werterhalt - das sind wichtige Gründe, die für die energetische Sanierung eines Gebäudes sprechen. Eine passende Energieberatung hierfür zu finden ist jedoch nicht so einfach. Schließlich soll die Sanierungsplanung auf das Gebäude und die Wünsche des Hausbesitzers zugeschnitten sein und der Berater auch unabhängig beraten können. Unser Beitrag erklärt, wo man nach qualifizierten Energieberatern sucht, welche Informationen weiterhelfen und wie die Energieberatung abläuft.

    » Artikel anzeigen

  • Gastbeitrag

    Energiesparen ist das eine, Behaglichkeit das andere. Letztere kommt in der Diskussion über die Wärmedämmung von Gebäuden eher selten zur Sprache. Dabei sollten sie bei der Sanierungsplanung ein wichtiges Entscheidungskriterium sein. Denn zum einen ist den meisten Menschen Behaglichkeit und Komfort etwas wert und sie sind bereit, dafür zu bezahlen. Daher greift es zu kurz, den Nutzen einer Dämmung allein durch die Einsparung von Energie zu beschreiben. Zum anderen gibt es einen direkten Zusammenhang zwischen Behaglichkeit und möglichen Energieeinsparungen.

    » Artikel anzeigen

  • Gastbeitrag

    Bauen verändert sich mehr und mehr. Nach dem das Niedrigenergiehaus im Neubau bereits zum Standard geworden ist, können wir uns bald an neue Gebäudeklassen gewöhnen. Ab dem 01. April 2016 gibt es bei der KfW eine neue Effizienzhaus-Klasse: das Effizienzhaus 40 Plus. Damit kann künftig jeder Bauherr eine Förderung beantragen für ein Haus mit einem sehr geringem Energiebedarf, das auch noch Strom erzeugt und speichert.

    » Artikel anzeigen

  • Gib mir 5!

    Die überzeugenden Vorteile für den Neubau

    » Artikel anzeigen

  • PU-News: Hält eine dicke Wand immer warm?

    Warum Dämmwirkung und Wärmespeicherfähigkeit nicht verwechselt werden dürfen.

    Wenn dicke Außenwände von alten Gebäuden energetisch saniert werden sollen, zögern inzwischen einige Bauherren und fragen sich: Ist bei einer dicken Wand die Dämmung überhaupt notwendig? Auch aus Medienberichten erfährt man, dass Wandstärke und Wärmespeicherfähigkeit alleine ausreichen würden, um die Räume im Winter warm und im Sommer kühl zu halten. Im folgenden Beitrag erfahren Sie, warum dicke Wände nicht ausreichend dämmen und Wärmespeicherfähigkeit keinen wesentlichen Beitrag zur Energieeinsparung liefert.

    » Artikel anzeigen

  • Wie funktioniert eigentlich ein Steildach?

    Funktionsschichten, Dämmung, Checkliste zur Sanierungsplanung

    Ein gute Steildachsanierung läuft nicht von allein. Hier müssen einige Faktoren ineinandergreifen. Das gilt für die einzelnen Baumaterialien, wie auch für den ganzen Dachaufbau. Wie überall, wo zusammen gearbeitet wird, „menschelt“ es auch auf einer Baustelle. Deshalb ist schon bei der Planung eine gute Zusammenarbeit von Bauherr, Energieberater und Fachhandwerker von Vorteil. Wie ein Steildachsystem funktioniert, welche Aufgaben eine Dämmung übernehmen kann und welche Schritte unternommen werden müssen, damit die Dachsanierung gefördert wird, erklärt dieser Beitrag.

    » Artikel anzeigen

Seite: 1 2 3 4 5 6 7


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