• strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of image_attach_views_handler_field_attached_images::pre_render() should be compatible with views_handler_field::pre_render($values) in /kunden/96976_23554/relaunch/sites/all/modules/image/contrib/image_attach/image_attach_views_handler_field_attached_images.inc on line 111.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /kunden/96976_23554/relaunch/sites/all/modules/views/handlers/views_handler_argument.inc on line 745.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 149.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /kunden/96976_23554/relaunch/sites/all/modules/views/plugins/views_plugin_style_default.inc on line 25.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of date_plugin_display_attachment::options() should be compatible with views_object::options() in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 33.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 24.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 25.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 26.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 28.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 29.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 30.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 31.
  • strict warning: Declaration of date_handler_field_multiple::options() should be compatible with views_object::options() in /kunden/96976_23554/relaunch/sites/all/modules/date/date/date_handler_field_multiple.inc on line 171.
  • strict warning: Declaration of views_handler_filter_term_node_tid::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/modules/taxonomy/views_handler_filter_term_node_tid.inc on line 303.
  • strict warning: Declaration of date_api_filter_handler::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_api_filter_handler.inc on line 553.
  • strict warning: Declaration of date_api_filter_handler::options() should be compatible with views_object::options() in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_api_filter_handler.inc on line 553.
  • warning: Creating default object from empty value in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_api_filter_handler.inc on line 37.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 24.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 25.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 26.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 28.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 29.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 30.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 31.
  • warning: Creating default object from empty value in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_api_filter_handler.inc on line 37.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 24.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 25.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 26.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 28.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 29.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 30.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 31.
  • warning: Creating default object from empty value in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_api_filter_handler.inc on line 37.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
Einschätzung zum Ausgang des Volksentscheids in Hamburg

Mehrheit für den Rückkauf der Hamburger Netze – ein Grund zur Freude aber noch nicht zum Feiern

Am 22.9. hat eine hauchdünne Mehrheit der Hamburger Wähler_innen per Volksentscheid für den Rückkauf der Netze gestimmt. Was bedeutet dies ?

Das ist zu allererst eine herrliche Ohrfeige für die Gegner des Rückkaufs. Vattenfall & E.ON, SPD&FDP&CDU hatten sich in großer Koalition mit Gewerkschaften & Handelskammer unter enormen finanziellen Aufwand gegen die allgemein vorherrschende Stimmung ins Zeug gelegt. Dabei hatten sie sich gleichermaßen peinlicher wie unverschämter Propagandatricks bedient – erfolglos. Das Image des Quasi-Monopolisten ist bereits zu stark ruiniert. Dem Hauptargument, der Rückkauf sei vor allem zu teuer und das Geld fehle dann anderswo, ist die Mehrheit nicht auf den Leim gegangen. Die enthaltene dumm-dreiste Lüge, Vattenfall und E.ON würden letztlich entgegen ihrer finanziellen Interessen für ein Minusgeschäft kämpfen, lässt sich zum Glück nicht mehr ungestraft auftischen. Dass die Netze eine Gelddruckmaschine sein können, ist im Laufe der Auseinandersetzung wohl allen Beteiligten klar geworden. Auch dass die bisherige Konzernstrategie einer realen Energiewende und somit den hierfür notwendigen Investitionen in das Netz feindlich gegenübersteht, ist allzu offensichtlich geworden.

Doch bekanntlich genügt ja leider sehr oft das richtige Argument nicht. Der Hamburger Presse ist in diesem Falle zugute zu halten, dass weit bis in den bürgerlichen Mainstream hinein (zB. HH Abendblatt) ein formal ausgewogener Diskurs eröffnet wurde, der immerhin die Argumente der Befürworter unverzerrt darstellte. Das hat mit dazu beigetragen, dass die manipulativen Propagandamaterialien, die in Hochglanzbroschüren und fetten Anzeigen über die Hamburger_innen geschwemmt wurden, anscheinend eher gegenteilig wirkten und eine schon verbreitete Skepsis sogar eher noch beförderten. Das alles ist über den Einzelfall hinaus aus Sicht des physisch unterlegenen David hocherfreulich.

Warum dann nicht feiern?

Da ist zunächst die banale Tatsache, dass der Entscheid nur eine Aufforderung zum Kauf darstellt, die Übergabe ist noch längst nicht realisiert. Da wird bis Ende 2014 noch fleißig geklagt, gepokert, genötigt und getrickst werden. Eine völlige Verarschung wird sich die SPD zwar kaum trauen können, aber der Drops ist noch nicht gelutscht.

Als nächstes gilt es anzuerkennen, dass zB. ein Lieferwagen-Verleih in städtischem Besitz zwar seine Einnahmen nicht der Gesellschaft entzieht und in Form „privater Gewinne" enteignet, aber eben doch nur ein Lieferwagen-Verleih ist. Die Einnahmen sind zwar „von allen für alle", doch die gesellschaftlich mindestens genauso entscheidende Frage, was von wem mit welchem Nutzen und zu wessen Lasten wohin transportiert wird, ist damit noch nicht entschieden.

Genauso verhält es sich bei den Netzen. Eine Einnahmequelle für Vattenfall und E.ON fällt weg – gut und schön. Aber Vattenfall bleibt in seiner Rolle auf dem Hamburger Energiemarkt unangefochten. Die Konzentration auf Großtechnologien sichert die Quasi-Monopolstellung des Giganten gegenüber kleineren Unternehmen. Vattenfall diktiert weiterhin den Strompreis und zieht den Verbraucher_innen das Geld aus der Tasche. Wenn sich jemand das nicht mehr leisten kann, wird der Strom abgeklemmt und schon ist Schluss mit der Teilhabe an den angeblichen Kulturleistungen unserer sogenannten Wohlstandsgesellschaft (in Zahlen: 65.000 Haushalte in Hamburg/ Jahr).

Die Folgekosten des dreckigen Geschäfts – der vor sich hin gammelnde Atommüll, potentielle katastrophale Unfälle, die Auswirkungen des Klimawandels, der zerstörerische Abbau von Uran und Kohle, die Vergiftung mit Feinstaub, etc. pp. – werden auf die Allgemeinheit abgewälzt. An all dem ändert auch das beste Netz in öffentlicher Hand nichts.

Und so führt der gewonnene Entscheid zwar in die richtige Richtung, ist aber eben auch nicht mehr als ein Etappenschritt. Unser Ziel bleibt weiterhin, dass alle gemeinsam entscheiden können, wie Energie produziert und wie sie gerecht verteilt wird. Schließlich müssen alle mit den Folgen leben.

Ein nächster wünschenswerter Schritt für Hamburg

In einer wirklichen Demokratie, in der alle Betroffenen direkt, solidarisch weil unbehelligt von Erpressungsversuchen des Kapitals und last but not least ausgewogen informiert über ein Kraftwerk entscheiden könnten, wären Drecksschleudern wie Moorburg nicht mehr möglich – wer will sich schon vergiften lassen, wem wären die CO2-Emmissionen egal ?

Basisdemokratische Vergesellschaftung ist eine wesentliche Voraussetzung dafür, Wirtschaft und Gesellschaft weg von kurzsichtig-monadischer Kapitalvermehrung als Selbstzweck hin zu langfristig-vorausschauender, global solidarischer Gemeinwohl-Orientierung umzugestalten. Im Falle der Energiewirtschaft würde das u.a. heißen, sofort aus Atom- und Kohleverstromung auszusteigen und stattdessen auf dezentrale und flexible Alternativ-Energien zu setzen. Deshalb bleibt das Ziel, die Energiekonzerne zu enteignen und die Energieversorgung zu vergesellschaften, was seit dem 22.9. immerhin einen, wenn auch zunächst nur kleinen Schritt näher gerückt ist.

In Berlin wird im November darüber abgestimmt, ob nicht nur die Netze sondern auch die Erzeugung in die öffentliche Hand zurück überführt werden sollen. Dort sind in dem zur Abstimmung stehenden Entwurf die Prinzipien der demokratischen Kontrolle, der sozial gestalteten Tarife und der Energiegewinnung aus regenerativen Quellen bereits in das Statut des kommunalen Unternehmens eingeschrieben. Dies wäre auch für Hamburg ein nächster wünschenswerter Schritt. Erforderlich wäre dafür wie in Berlin ein breit angelegtes, konstruktives Bündnis aller verschiedenen Initiativen und Organisationen mit ökologisch-sozialem Anliegen.

Punktsieg für die politische Vernunft

Wir freuen uns über das Ergebnis des Hamburger Volksentscheides. Zusammengefasst lässt sich sagen, dass das Ergebnis entgegen krasser Machtasymmetrie einen Punktsieg für die politische Vernunft darstellt. Der Entscheid hat trotz seiner teils steif-altbackenen Performance und trotz eines sperrigen Themas zu einer politisierenden Auseinandersetzung geführt. Die (hoffentlich anhaltende!) Debatte stimmt uns in ihrer Gesamtbetrachtung verhalten optimistisch: Wir denken, dass es möglich sein könnte, Vattenfall kräftig in die Suppe zu spucken.

Es wäre jedoch nun absolut falsch, es sich schon selbstzufrieden im Lehnstuhl gemütlich zu machen. Etliche gezielte Tritte sind da schon noch nötig, um Vattenfall tatsächlich vom Hamburger Markt zu vertreiben. Wobei wir aber immerhin etwas Licht am Ende des Tunnels sehen. Wir bereiten deshalb schon jetzt für alle unsere Genoss_innen und Mitstreiter_innen eine riesige, dreitägige Bye-Bye Vattenfall-Party mit Freibier, leckerem Büfett und ordentlich Ramba-Zamba vor. Diese wird an dem Tag stattfinden, an dem Vattenfall seinen Rückzug aus Hamburg (Deutschland, Mitteleuropa,...) erklärt. Wegen des Ortes sprecht uns an: wir sehen uns ja vorher noch bei unzähligen kleinen und großen, indirekten und direkten Aktionen gegen Vattenfall & Co...

Avanti/iL - Klima AG HH, 23.9.2013