• 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.
13.02.1945 - 2010. Keine Verdrehung der Geschichte!

Deutschland, Dresden: Alles Opfer

 

Im deutschen Geschichtsbild ist Dresden zu einem Symbol geworden für das Leiden der vermeintlich unschuldigen Zivilbevölkerung während des Zweiten Weltkriegs. Indem die Nazis ihren Aufmarsch in Dresden als Gedenken an den Bombenangriff auf die Stadt inszenieren, gelingt es ihnen, an dieses gesamtgesellschaftlich verbreitete Geschichtsbild anzuknüpfen, demzufolge eben auch die Deutschen im Nationalsozialismus vor allem Opfer waren.

Antifaschistischer Aktionstag am 13. Februar 2010

Am 13. Februar 2010, dem 65. Jahrestag der Bombardierung Dresdens durch die Alliierten wollen sich wieder tausende von Nazis in Dresden versammeln, um ihre Legende von den „alliierten Kriegsverbrechen gegen unschuldige deutsche Opfer“ zu verbreiten. Der alljährlich als Trauermarsch inszenierte Nazi-Event in Dresden hat sich zu dem bedeutendsten deutschen Naziaufmarsch entwickelt. Im letzten Jahr waren es 6.000, darunter auch viele Nazis aus anderen europäischen Ländern, wie z. B. aus Schweden, Dänemark, Österreich, Tschechien, der Slowakei oder der Schweiz. Es ist aber nicht nur die Ungeheuerlichkeit der heutigen Nazis, die nahtlos der NS-Propaganda folgen, sondern die Bombardierung zu einem deutschen Hiroshima oder einem „Völkermord aus der Luft“ stilisieren wollen. Und es ist nicht nur die Größe, die den Aufmarsch in Dresden so bedeutsam macht. Sicherlich stärkt es den Zusammenhalt innerhalb der Naziszene, wenn tausende Nazis aus Deutschland und Europa und aus den verschiedensten, ansonsten oft zerstrittenen Spektren - Autonome Nationalisten, NPD, DVU, und der ganz rechte Rand von Burschenschaften und Vertriebenenverbänden - zusammenkommen und sich gemeinsam als mächtige Bewegung darstellen und erleben. Die große gesellschaftliche Bedeutung der Naziaktionen in Dresden liegt aber in anderen Zusammenhängen begründet.

Mythos Dresden

Um die Bombenangriffe auf Dresden wurde in den letzten 65 Jahren ein Mythos aufgebaut, der sich hartnäckig hält. Die NS-Propaganda nutzte die Angriffe für ihre Gräuelpropaganda eines „Vernichtungskriegs gegen Deutschland“. Nach Kriegsende stellte sich die Haltung der DDR zunächst deutlich anders dar. Die Zerstörung wurde als Resultat des deutschen Angriffskrieges erkannt. Später erklärte die DDR-Führung die Zerstörung Dresdens jedoch zur antisowjetischen Machtdemonstration der Westalliierten. Diese Interpretation sollte die Frontstellung im „Kalten Krieg“ unterstützen. Gleichzeitig verfestigte sie aber auch die Opferinszenierung der DresdnerInnen. In Westdeutschland stand das Dresden-Buch des Holocaustleugners David Irving als Standardwerk in vielen Wohnzimmern. Die Gedenkveranstaltungen der letzten Jahre knüpfen trotz Aufklärung und den Ergebnissen einer extra eingesetzten Historikerkommission an die Opfermythen der Bombardierung an. Statt sich mit der Kollaboration der Stadt und ihrer BewohnerInnen bis in die letzten Tage der NS-Herrschaft auseinander zusetzen, definierte sich Dresden selbst zum doppelten Opfer: Nicht nur Opfer der „unnötigen alliierten Bomben“, sondern auch des Nationalsozialismus. Zum 60. Jahrestag wurde der Angriff auf Dresden bewusst in eine Reihe mit anderen nicht-deutschen Städten gestellt. Diese Gleichstellung z. B. mit Warschau oder Coventry, die von Deutschland im 2. Weltkrieg zerstört wurden, oder mit dem Anschlag auf das World Trade Center in New York, verharmlost die Geschichte des Nationalsozialismus. Die Inszenierung um den Wiederaufbau der Frauenkirche zum Sinnbild der Mahnung gegen den Krieg und der Völkerverständigung diente zudem auch dem Aufbau eines neuen Images für die Stadt als Touristenmagnet - die Frauenkirche ist heute nicht mehr nur „Mahnmal“ gegen Krieg, sondern auch eine zentrale Attraktion des neuen „Elbflorenz“.

Deutschland, Dresden: alles Opfer

Nicht nur mit Blick auf Dresden sondern auch in bezug auf die deutsche Geschichte insgesamt ist ein veränderter gesellschaftlicher Umgang festzustellen. Mit großer Zustimmung wurde in den letzten Jahren ein neues Geschichtsbild verbreitet. So wurde die Opfereigenschaft der Deutschen nicht nur in Dresden, sondern auch anderswo entdeckt - Bücher wie Jörg Friedrichs „Der Brand“ oder Arnulf Bahrings Vertreibungsthesen in der Bild-Zeitung stehen beispielhaft für diese Entwicklung. Fernsehfilme wie „Dresden“, mit der auf jugendliche Popkultur gebuchten Felicitas Woll, oder „Die Flucht“, mit einer bodenständigkonservativen Maria Furtwängler als Hauptdarstellerinnen, ermöglichen es den ZuschauerInnen mit den „armen Deutschen“ während der Bombenangriffe im Luftschutzkeller auszuharren oder vor der russischen Armee zu fliehen. Im neuen deutschen Geschichtsbild wird wieder mit den Deutschen der NS-Zeit gefühlt und gelitten, wirkliche Nazis begegnen einem hingegen nur selten. Wie in Dresden stellte auch gesamtgesellschaftlich die Betonung darauf, „dass die Deutschen eben auch Opfer gewesen seien“, nur den ersten Schritt dar: In einem zweiten Schritt zieht ein „geläutertes Deutschland“ aus der „Aufarbeitung“ die moralische Legitimation für militärische Auslandseinsätze und imperialistische Großmachtpolitik. So konnte die rot-grüne Koalition der Welt erklären, dass deutsche Soldaten „wegen Auschwitz“ wieder auf dem Balkan aufmarschieren mussten. Weil Dresden das Paradebeispiel für diesen Umgang mit der Geschichte ist, fällt es den Nazis hier besonders leicht, mit ihrer den Nationalsozialismus verherrlichenden Propaganda an einen gesamtgesellschaftlichen Diskurs anzuknüpfen. Das weit verbreitete Bedürfnis, der „eigenen Opfer“ gedenken zu wollen, ermöglichte es in Dresden jahrelang, dass am Gedenktag NPD und etablierte Landtagsparteien nebeneinander Kränze ablegten. Gerade deshalb ist es besonders wichtig, dass wir als AntifaschistInnen den Nazis in Dresden entschlossen und politisch eindeutig entgegentreten und dabei alle deutschen Opfermythen knacken.

Antifaschistischer Widerstand

Gegen den Naziaufmarsch hat sich in den letzten Jahren ein immer stärker werdender Widerstand entwickelt. So ist es DresdnerInnen im Zusammenwirken mit bundesweiten antifaschistischen Bündnissen gelungen, den Naziaufmarsch durch zivilen Ungehorsam zu behindern, so dass die Route des Naziaufzugs eingeschränkt wurde. 2009 nahmen nahezu zehntausend Menschen aus Dresden und dem gesamten Bundesgebiet an Gegenaktivitäten teil. Auch im Februar 2010 wollen wir an die Erfahrungen der letzten Jahre anknüpfen. Mit der Stärke einer bundesweiten Mobilisierung wollen wir die Voraussetzungen schaffen, den Naziaufmarsch nicht ungestört stattfinden zu lassen. Deshalb rufen wir zu Massenblockaden nach Dresden auf: Um die Nazis zu vertreiben. Gemeinsam mit antifaschistischen DresdnerInnen und allen antifaschistischen Kräften aus den Gewerkschaften, Parteien, Jugend- und Studierendenverbänden, der Umweltschutzbewegung, der radikalen Linken, globalisierungskritischen Gruppen und gewaltfreien Aktionsgruppen aus dem gesamten Bundesgebiet wollen wir den Aufmarsch der Nazis verhindern. Wir sind uns bewusst, dass es für eine nachhaltige antifaschistische Intervention in Dresden nicht ausreichen wird, nur an diesem Tag massenhaft nach Dresden zu fahren. Vielmehr müssen wir unsere Aktivitäten am 13. Februar als Teil einer längerfristigen Auseinandersetzung begreifen, in der wir einerseits den Naziaufmarsch selbst und andererseits den Dresdner Mythos sowie den gesamtdeutschen Opfermythos angreifen. Nur so kann am Ende auch das Wechselspiel zwischen Naziaufmarsch und verkehrter Stadtpolitik aufgebrochen werden. Dafür braucht es einen langen Atem. Wenn wir es schaffen zu diesem Zwecke im Bündnis mit verschiedensten gesellschaftlich verankerten Gruppen gemeinsam zu agieren und so die Stadt Dresden politisch unter Druck zu setzen, können wir den alljährlichen Naziaufmarsch dauerhaft verhindern.

 

Nazis am 13. Februar entschlossen entgegentreten gemeinsam blockieren!
No pasarán – sie kommen nicht durch!

AnhangGröße
ddaufruf_web.pdf239.99 KB