Du 16 au 20 Novembre 2009 à Tunis (Tunisie)

  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • warning: include_once(./includes/unicode.entities.inc): failed to open stream: No such file or directory in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: include_once(): Failed opening './includes/unicode.entities.inc' for inclusion (include_path='.:/usr/lib/php5.6') in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 333.
  • warning: preg_replace_callback(): Requires argument 2, '_decode_entities("$1", "$2", "$0", $newtable, $exclude)', to be a valid callback in /homepages/13/d149292364/htdocs/ifme.org/includes/unicode.inc on line 314.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/theme.inc on line 170.
  • warning: Parameter 2 to viewfield_field_settings() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/module.inc on line 386.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/theme.inc on line 170.
  • warning: Parameter 2 to viewfield_field_settings() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/module.inc on line 386.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/theme.inc on line 170.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 23.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 24.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 25.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 26.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 27.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 28.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 29.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 30.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 31.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 32.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 33.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 34.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 39.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 40.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 41.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 42.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 43.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 44.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 45.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 46.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 47.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 48.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 49.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 50.
  • warning: Creating default object from empty value in /homepages/13/d149292364/htdocs/ifme.org/modules/pathauto/pathauto.module on line 112.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 81.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 81.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • strict 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 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 153.
  • strict warning: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/date/date.inc on line 69.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /homepages/13/d149292364/htdocs/ifme.org/includes/theme.inc on line 170.

 

 

 Cette formation à Tunis a été
l’occasion pour SAAS de mandater un auditeur d’accréditation pour évaluer la
formation d’auditeur de 5 jours qu’IFME dispense depuis début 2005. 

L’audit a porté sur l’analyse
documentaire du système de formation en conformité avec la procédure 250 de
SAAS ainsi que sur la validité du contenu et de la pédagogie appliquée durant
ces 5 journées.

L’auditeur (Peter) a très
fortement apprécié les jeux de rôles, les échanges opérationnels d’expérience
de façon transverse, et très impressionné par la diversité des photos projetées
en témoignage de ce qu’un auditeur peut découvrir comme situations lors de ses
interventions.

 

Lors de cette session, encore
très peu de consultants ou d’auditeurs, mais plutôt des représentants
d’entreprises Tunisienne ou mondiales présentes en Tunisie. Bon nombre étant
issus des diverses Directions des Ressources Humaines.

 

La plupart des participants
avaient une grande connaissance de ce qu’est un Système de Management car
presque toutes les entreprises représentées étaient certifiées ISO 9001,
quelques unes ISO 14001 et/ou OHSAS 18001.

 

Cela s’est fortement ressenti lors
des échanges et des jeux de rôles où la maîtrise des situations d’entretien est
apparue comme l’élément clé de la réussite d’un audit SA8000. Ces difficultés à
mener des entretiens a été ressentie surtout par ceux qui avait déjà une
expérience d’audit (essentiellement ISO 9001).

.

Il est apparu une autre
difficulté propre à l’audit social, vécue par ceux ayant une expérience ISO,
c’est le « flou » et l’autorité qui est donné au responsable d’audit
SA8000 pour qualifier une situation rencontrée en audit en la modulant selon
les situations, les intentions, les volontés rencontrées. En effet, ces
participants ont admis être habitués à une démarche « plus binaire »
- c’est conforme ou ce n’est pas conforme selon la présence ou l’absence
d’éléments recherchés.

 

Il a été rappelé qu’en audit
social SA8000, la charge de la preuve était subie par l’entreprise. L’auditeur
n’avait qu’à poser les bonnes questions pertinentes pour s’assurer de la
conformité.

 

Les résultats obtenus lors de
l’examen final sont également très représentatifs de la population de
participants présente et sont très décevants : 57, 14% de réussite pour
cette session, taux le plus faible depuis Février 2005.

 

Mais, plusieurs entreprises Tunisiennes ayant fait former leurs cadres auprès d'IFME par cette formation sont dorénavant certifiées SA8000 ou sur le point de l'être. 

2010 sera l'année des entreprises certifiées SA8000 en Tunisie.... et cette formation accréditée continuera d'y apporter sa contribution