neu
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
26
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
26
admin •
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 26
21. Februar 2011 • Aktuelles, Konfliktmanagement, neu
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/formatting.php on line
82
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/formatting.php on line
82
Konflikte gibt es solange es Menschen gibt, die in Gemeinschaften miteinander auskommen müssen. Archaische Muster der Konfliktaustragung sind dabei heute alles andere als überholt. Nimmst du mir, was mir wichtig ist, gebe ich dir die Keule – so scheint es häufig auch noch in der Berufs- und Arbeitswelt zu sein, auch […]
Tags: Grabenkämpfe, Heckenschützen, Konflikt, Konflikt im Team, Konflikt-Coaching, Konfliktkultur, Konfliktmanagement, Konfliktvermeidung, Mediation, Meinungsverschiedenheit, Problemverdrängung, Streit, Streit unter Kollegen, Streitkultur, Team-Coaching, Teamentwicklung, Teamkonflikte, Unternehmenskultur
Aktuelles, Konfliktmanagement, neu |
Deprecated: Function eregi() is deprecated in /homepages/39/d39529389/htdocs/wordpress/wp-includes/gettext.php on line 288
Keine Kommentare »
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
26
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
26
bb •
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 26
12. März 2008 • Change Management, Führung, neu
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/formatting.php on line
82
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/formatting.php on line
82
Führen in Veränderungsprozessen
Führungsfeedback, auch unter 360°- oder 270°- Feedback bekannt ist seit längerem ein gebräuchliches Instrument, die Kompetenz von Führungskräften zu erhellen. So weit so gut. Wenn heute der “Permanente Wandel” als Ist-Situation und als Anforderung an alle im Unternehmen formuliert wird, sollten wir uns mit dem Thema “Führen in Veränderungsprozessen”befassen . Welches Ziel und welchen Nutzen […]
Tags: Erfolgsfaktor Führung, Feedbackbericht, Feedbackgespräch, Führungsfeedback, Führungskräfte-Entwicklungsprogramm, HBC Führungsfeedback, Kompetenzprofil, Permanenter Wandel
Change Management, Führung, neu | Keine Kommentare »
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
26
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
26
bb •
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 26
7. März 2008 • Change Management, Kultur, neu
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/formatting.php on line
82
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/formatting.php on line
82
Ein interessantes Thema, mit dem wir uns schon länger beschäftigen. Wenn man etwas googelt, findet man etliche Fundstellen mit Meinungen und Kommentaren zum Thema (Links siehe unten).
Die Grundtendenz aller Reflexionen ist realitätsnah, bezogen auf die Beratererfahrungen in Change-Prozessen: Häufig wird ein Change-Prozess gar nicht erst gestartet, weil der Ablauf und die Ergebnisse dem potenziellen Auftraggeber […]
Tags: Change Management, Fusion, Kulturentwicklung, Messbarkeit, Post Merger Integration, qualitative Messkriterien, Veränderungsprozess, Zielvereinbarung
Change Management, Kultur, neu | Keine Kommentare »
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
26
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line
26
admin •
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 12
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 21
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 23
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 25
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/39/d39529389/htdocs/wordpress/wp-includes/functions.php on line 26
5. März 2008 • neu
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/formatting.php on line
82
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in
/homepages/39/d39529389/htdocs/wordpress/wp-includes/formatting.php on line
82
Der betreffende Bereich im Code ist “leftcol”. Du musst die Kategorie im Aufruf query_posts festlegen. Wobei “showposts=3? bedeutet, dass die drei letzten Beiträge dieser Katagorie hier angezeigt werden. “cat=7? bedeutet, dass es sich um die Kategorie mit der ID 7 handelt. Die ID musst Du noch einmal im Template Tag wp_list_catagories festlegen. Erneut werden hier […]
neu | Keine Kommentare »
