• 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.
Avanti Berlin zu Bundestagsbelagerung und Krisenprotesten

Von der Krise zum kollektiven Handeln

 

Viele Bewegungslinke waren zu Beginn der Weltwirtschaftskrise elektrisiert von der Aussicht, einem historischen Moment beizuwohnen. Klar war: Diese Krise ist nicht bloß ein Strohfeuer des Neoliberalismus, sondern Ausdruck einer fundamentalen Krise des Kapitalismus.

 

Es wurde über die Grenzen der realen Kapitalakkumulation und die Flucht des Kapitals in die Finanzsphäre diskutiert und über die Bedeutung der Systemkonkurrenz und der Kämpfe der Arbeiter_innenklasse gestritten. Kaum jemand hat damit gerechnet, dass die Bundesregierung binnen kurzer Zeit 480 Milliarden Euro mobilisieren würde und schon zwei Jahre nach dem Crash der Finanzwelt ein "Jobwunder" und Wirtschaftswachstum verkünden könnte. Bislang ist der Versuch, die ökonomische in eine politische Krise zu überführen gescheitert.

 

Bedeutsam hierfür war die relative Stabilität der bundesdeutschen Wirtschaft und die im weltweiten Vergleich enormen Finanzreserven, aber auch die geschickte Verzögerung der "gefühlten Krise" durch die Regierung. Es ist an dieser Stelle deutlich geworden, dass die Mobilisierungs- und Zuspitzungsfähigkeit der gesamten Linken ausbaubedürftig ist. Viele Menschen empörte zwar durchaus der milliardenteure Kniefall vor den Finanzmärkten, aber die alleinige Tatsache, dass Milliarden in die Rettung von Banken und Finanzunternehmen gepumpt wurden, reichte nicht, um eine Widerstandsbewegung zu mobilisieren.

 

Was fehlte, war ein konkreter Ansatzpunkt für Massenmobilisierungen und deren linksradikaler Zuspitzung. "Die Krise" eignete sich hierfür kaum, da kein direktes Feindbild auszumachen war. Zwar gab es häufig Polemiken gegen "gierige Banker", deren progressiver Gehalt ist jedoch wohl eher bescheiden. "Der Kapitalismus" eignet sich schwerlich als konkretes Mobilisierungsangebot, insbesondere weil es an einem als glaubwürdig empfundenen gesellschaftlichen Gegenmodell, einer konkreten Utopie, mangelt.

 

Die aktuelle Weltwirtschaftskrise hat (in der   Bundesrepublik) also vorerst nicht zu einer nennenswerten Zuspitzung sozialer Kämpfe geführt. Stattdessen sind linke Mobilisierungen weiterhin marginal und müssen zusätzlich mit dem verbreiteten Gefühl, halbwegs heil aus der Krise rausgekommen zu sein, klar kommen. Immerhin ist dabei aber – mehr als sonst – deutlich geworden, wo die Schwächen linker und linksradikaler Politik im Feld der sozialen Kämpfe liegen. Diese gilt es nun herauszuarbeiten und neue Strategien zu entwickeln – auch angesichts der zu erwartenden Umverteilung von unten nach oben in den nächsten Jahren.

 

Das angestrebte Sparpaket, das der Bundestag jetzt beschließen will, setzt die Politik der sozialen Einschnitte fort. Diese Maßnahme zur Abfederung der Krise geht vor allem auf Kosten der Unterschichten. Bei Erziehungs- und Wohngeld für Arme soll gespart werden. Der Regelsatz wurde um lächerliche fünf Euro erhöht, wobei zugleich mit einer eindeutigen Symbolik festgelegt wurde, dass Alkohol und Zigaretten nicht zum täglichen Bedarf gehören. Mit dem Sparpaket findet die Krise – und deren ungebrochen kapitalfreundliche Bearbeitung – nun ihren konkreten Ausdruck.

 

 

Krise und Klassenkämpfe international


Im Verlauf der Krise sind die Finanzsysteme in vielen Ländern zusammengebrochen und es folgten massive Währungsabwertungen, Milliardenverluste von Kleinanleger_innen und staatliche Sparpakete, mit denen die Löhne und Renten im öffentlichen Dienst drastisch gekürzt wurden. Die Stabilität eines Systems bemisst sich in seiner Fähigkeit, Hegemonie zu erzeugen. Diese wird in Zeiten der ökonomischen Krise auf die Probe gestellt. Die Reaktionen auf die Krise fielen sehr unterschiedlich aus. In den Ländern des Baltikums blieben soziale Angriffe im Wesentlichen unbeantwortet und die Regierungen wurden sogar wieder-gewählt. In Spanien, Frankreich und Griechenland kam es in Folge der Spardiktate teilweise zu mehrtägigen Generalstreiks.

 

Zuletzt stürmten englische Studierende die Parteizentrale der regierenden Konservativen, da die Studiengebühren verdreifacht werden sollen. Diesen Protesten gemeinsam ist, dass es konkrete soziale Angriffe gab, in Spanien auf den Kündigungsschutz, in Frankreich beim Renteneintritts-alters und in Griechenland im Bereich der Gehälter und der Mehrwert-steuer, die eine Vielzahl von Menschen betreffen und eine kollektive Gegenwehr nötig werden ließen. Die Unterschiedlichkeit der Proteste lässt aufhorchen, gerade weil sie sich nicht allein durch den Grad der Angriffe erklären lässt. Zentral ist die Frage, ob es kollektiv handlungs-fähige Großgruppen gibt, ob der politische Gegner klar bestimmt wird und ob es eine Aussicht auf politisch erfolgreiche Aktionen gibt.

In Frankreich oder Griechenland gab es immer wieder kämpferische Widerstände gegen neoliberale Durchdringung der Gesellschaft. Der Staat sah sich mehrfach dazu genötigt, Zugeständnisse zu machen, um den Protesten die Spitze zu nehmen.

 

 

Grund für den politischen Druck war eine rebellische

politische Kultur mit Streiks, Besetzungen und

Demonstrationen, die sich nicht an die etablierten

Spielregeln der sozialpartnerschaftlichen

Aushandlungen gehalten haben. Zudem haben sich die Gewerkschaften nicht so stark der "Standortlogik" verschrieben und ihre Arbeitskämpfe und Forderungen nicht an den Interessen der nationalen Wirtschaft ausge-richtet, weil sie dem Ammenmärchen – wenn nur auf Löhne verzichtet wird, dann geht´s auch der Wirtschaft besser – nicht auf den Leim gegangen sind. Stattdessen haben sie vergleichsweise gute Lohnabschlüsse für ihre Mitglieder herausgeholt.

 


Appeasement statt Klassenkampf in der BRD


Die bundesdeutsche "Standortlogik" hat in den letzten Jahren durch Lohnzurückhaltung und Streikverzicht zu einer so hohen Produktivität geführt, dass ein massiver Außenhandelsüberschuss der deutschen Wirtschaft entstand. In der Folge liegen Produkte „made in Germany“ super-supergünstig in Ladenketten im Ausland aus und sorgen mit diesen dumping-Preisen dafür, dass die dortige Wirtschaft nicht mehr hinterher kommt. Der Außenhandelsüberschuss bedeutet deshalb auch, dass Deutschland (vor allem europäische) Märkte mit deutschen Produkten überflutet und Unternehmen im Ausland systematisch in den Ruin treibt.

 

Trotz der fatalen Folgen dieser Niedriglohnpolitik hat die IG Metall gleich zu Beginn der Krise deutlich gemacht, dass sie niedrige Lohnabschlüsse akzeptieren wird, mit dem Argument, hierdurch würde die Sicherheit von Arbeitsplätzen gewährleistet. In der Krise wurde außerdem deutlich, wie skrupellos die Gewerkschaften Leiharbeiter_innen aufgegeben haben, um ihre vergleichsweise gut organisierten "Kernbelegschaften" zu retten. Letztere wurden durch das Kurzarbeitergeld der SPD/CDU-Koalition protegiert. Den angeschlagenen Automobilkonzernen wurde mit der "Abwrackprämie" ein Geschenk gemacht. Das "Modell Deutschland" basiert auf diesem Kompromiss, der jedoch nur noch den Teil der hochproduktiven Beschäftigten umfasst.

 

Die Gewerkschaften sehen sich stets zum "kleineren Übel" gezwungen und versuchen zumindest ihrer Stammklientel Gründe dafür zu liefern, ihnen die Treue zu halten. Auf Seiten der Beschäftigten entsteht helle Panik davor, als "Überflüssige" herabgestuft zu werden, die keinen Schutz von Staat und Gewerkschaften erhalten. Überdies wirkt sich die zunehmende Verunsicherung von Arbeitsverhältnissen auch auf einer psychischen Ebene aus. Als Drohkulisse im Hintergrund flankiert sie die Angriffe auf soziale Errungenschaften der Arbeiter_innenklasse.

 

Nach einer Studie des Deutschen Instituts für Wirtschaftsforschung ist die "Mittelschicht" in den letzten zehn Jahren um vier Prozent geschrumpft, während die Armut massiv ansteigt. All diese Faktoren führen dazu, dass sich die Arbeits- und Lebensbedingungen für viele zwar zuspitzen, dies jedoch im Alltag mit dem Ziel verknüpft wird, den status quo irgendwie wahren zu wollen: Lieber Lohnverzicht als den Job ganz verlieren. Es könnte eben immer noch schlimmer kommen… Die zunehmende Prekarisierung und Individualisierung führt zu einer Fragmentierung des gesellschaftlichen Seins. Das Erleben einer kollektiven Identität ist jedoch die Basis von Solidarität und Kampfbereitschaft.

 

 

Rassismus und Krise


Indem der ökonomische Druck auf die "Mittelschicht" wächst, steigt auch der Bedarf nach Ventilen. Wurden zu Beginn der 1990er Jahre noch die "Asylbewerber" für Krisenphänomene verantwortlich gemacht, tritt nun mit Sarrazin ein Vertreter des Establishments auf, der eine neue rassistische Krisenerzählung anbietet.

 

Dreh- und Angelpunkt seiner Thesen sind die Verachtung der Unterschicht und ein althergebrachter biologistischer Rassismus mit antimuslimischem Fokus.

Sarrazins rassistische Überlegungen, dass "die weniger Qualifizierten und weniger Tüchtigen sich tendenziell biologisch stärker vermehren als die Qualifizierteren und Tüchtigeren" führt zu einer Idee des sogenannten social engineering, einer geplanten Bevölkerungspolitik, maßgeschneidert nach den Wünschen der Ökonomie. Die Idee des social engeneering wurde von dem neurechten Philosophen Peter Sloterdijk bereits 1999 in "Menschenpark" vorgedacht und spiegelt mit seinen Aussagen zum Sozialstaat die Verachtung der selbsternannten Eliten für die unteren gesellschaftlichen Schichten. Dabei können die Neuen Rechten an viel Vorarbeit aus der „Mitte“ anknüpfen.

 

Die Abschaffung des Elterngelds für Bezieher_innen von Hartz IV, die im Sparpaket der Bundesregierung festgeschrieben wird, ist beispielhaft. Nachdem das Elterngeld für Besserverdienende augestockt wurde, wird nun versucht, Bezieher_innen von Hartz IV das "Kinderkriegen" auszutreiben. An diesem Punkt besteht kein Dissens zwischen den Zielen von Merkel und Sarrazin. Anlass für die Aufregung über die Sarrazin’schen Thesen war lediglich die Verknüpfung des "Unterschichtsdiskurses" mit den normativen Diskursen um “Islam", "Integration" und vor allem der "Vererbungsdebatte".

 

Das Establishment fürchtet das eugenische und NS-kontaminierte Denken und Sprechen von Sarrazin und sucht Distanz zu dieser offen neurechten Position.

Der von Sarrazin beschworene "Untergang des Abendlandes", den seinerzeit der Kulturphilosoph Oswald Spengler vorherzusehen meinte, knüpft an die kulturpessimistische und katastrophistische extreme Rechte der Weimarer Republik an. Der gefallene Banker Sarrazin gefällt sich in der Pose des Märtyrers und macht fleißig von der Titelseite der Bild-Zeitung aus gegen die vermeintlichen "Meinungstabus" mobil.


Kristallisationspunkt der Hetze ist ein antimuslimischer Rassismus. Dabei wird das Feindbild eines aggressiven Fremden, eines nichtsnützigen und integrationsunwilligen Moslems gezeichnet, was zur rassistischen Kanalisierung der Krisenerzählung in der Bundesrepublik entscheidend beiträgt. An Muslimen und „faulen Griechen“, die „über ihre Verhältnisse gelebthaben“, wird den Beschäftigten so stellvertretend die Lektion erteilt, was ihnen selbst droht, sollten sie sich im kapitalistischen Weltmarkt einmal mangels Disziplin und Bereitschaft, den Gürtel enger zu

schnallen, als „überflüssig“ erweisen. Das von Sarrazin gleichzeitiggegebene Versprechen aber, qua ihrer Gene fleißiger und produktiver zusein als der Rest, sorgt für die illusorische (Selbst)Sicherheit, an die sich die Rassisten in der Krise klammern und die ihre alltäglich erlebte Unsicherheit in das Geschwafel vom Untergang des „Abendlandes“ verwandelt.

 


Die Bedingung der Unmöglichkeit ist gleichzeitig die Bedingung der Möglichkeit

 

 

Keine Frage: Der aktive Konsens zum herrschenden System bröckelt. Den meisten ist klar geworden, dass es ein Zurück zu der wohlfahrtsstaatlichen Sonderperiode der Blockkonfrontation nicht geben wird. Die Geschichtlichkeit des Kapitalismus ist in seiner Krise aufgeblitzt. Um jedoch auch den passiven Konsens zu kippen, muss es in den nächsten Jahren gelingen, die Aktualität eines kommunistischen Projekts zu entwickeln. Dies bedeutet, das Bild einer anderen Gesellschaftsform zu zeichnen und sich zugleich in den konkreten Klassenkämpfen durchsetzungsfähig zu erweisen. Wer kein Sozialticket durchsetzen kann, braucht nicht in Träumen vom Kommunismus schwelgen. Es fehlt bisher im Bereich der sozialen Kämpfe an Erfolgserlebnissen und an Vorbild-Aktionen.

 

Trotz Massenmobilisierung ist es 2003 nicht gelungen, die Hartz-Gesetze zu stoppen. Wie wichtig kollektive Erfolge sind, konnte in diesem Jahr durch die Blockaden von Dresden erlebt werden, die quer durch das Land zu neuem Mut und Entschlossenheit im Kampf gegen Nazis geführt haben. Seit dem G8-Gipfel in Heiligendamm 2007 entsteht eine neue Welle von kollektivem Ungehorsam, die zuletzt ihren Höhepunkt beim Schottern & Blockieren der Castortransporte gefunden hat. Auch wenn die Trägerschichten dieser Kampagnen unterschiedlich sind und subalterne Milieus schwerer zu mobilisieren sind als besorgte Mittelschichten: Diese neue Entschlossenheit, ein solidarisches Miteinander in breiten Bündnissen und das gegenseitige Lernen der Bewegungen kennzeichnet die Erfolge der linken Bewegungen in den letzten Jahren. Das Aufbrechen von Stellvertreterpolitik, Individualisierung und Passivität ist eine wesentliche Erfahrung dieser Aktionsformen. Es muss gelingen, zivilen Ungehorsam auch bei sozial- und arbeitspolitischen Auseinandersetzungen „salonfähig“ zu machen und ihn schließlich in sozialen Ungehorsam zu überführen.

 

Ein wichtiger Markstein bei dieser Frage ist die Abstimmung über den Haushalt 2011 am 26.11. Es darf nicht gelingen, dass die Regierung bei Friedhofsruhe über die Abwälzung der Krisenlasten auf die unteren Schichten befindet.