Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d17632941/htdocs/grizan.com/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d17632941/htdocs/grizan.com/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d17632941/htdocs/grizan.com/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d17632941/htdocs/grizan.com/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/45/d17632941/htdocs/grizan.com/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/http.php on line 61

Strict Standards: Non-static method HeadSpace2::get() should not be called statically in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/headspace.php on line 328

Strict Standards: Declaration of HSM_PageTitle::load() should be compatible with HSM_Module::load($meta = '') in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/modules/page/page_title.php on line 199

Strict Standards: Declaration of HSM_Description::load() should be compatible with HSM_Module::load($meta = '') in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/modules/page/description.php on line 118

Strict Standards: Declaration of HSM_Tags::load() should be compatible with HSM_Module::load($meta = '') in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/modules/page/tags.php on line 346

Strict Standards: Declaration of HSM_Keywords::load() should be compatible with HSM_Module::load($meta = '') in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/modules/page/keywords.php on line 134

Strict Standards: Declaration of HSS_Analytics::load() should be compatible with HS_SiteModule::load($meta = '') in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/modules/site/analytics.php on line 310

Strict Standards: Redefining already defined constructor for class nggdb in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/nextgen-gallery/lib/ngg-db.php on line 60

Strict Standards: Non-static method HS_InlineTags::replace() should not be called statically, assuming $this from incompatible context in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/headspace.php on line 203

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/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php on line 133

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/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php on line 134

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/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php on line 135

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/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php on line 143

Strict Standards: Non-static method HeadSpace_Plugin::specialchars() should not be called statically, assuming $this from incompatible context in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/modules/page/tags.php on line 64

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/plugin.php on line 339

Strict Standards: Only variables should be assigned by reference in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/query.php on line 1465
<br /> <b>Strict Standards</b>: Non-static method HeadSpace2::reload() should not be called statically, assuming $this from incompatible context in <b>/homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/modules/page/page_title.php</b> on line <b>75</b><br /> <br /> <b>Strict Standards</b>: Non-static method HeadSpace2::get() should not be called statically, assuming $this from incompatible context in <b>/homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/headspace.php</b> on line <b>286</b><br /> <br /> <b>Strict Standards</b>: Non-static method HS_InlineTags::replace() should not be called statically, assuming $this from incompatible context in <b>/homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/headspace.php</b> on line <b>203</b><br /> <br /> <b>Strict Standards</b>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. 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 <b>/homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php</b> on line <b>133</b><br /> <br /> <b>Strict Standards</b>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. 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 <b>/homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php</b> on line <b>134</b><br /> <br /> <b>Strict Standards</b>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. 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 <b>/homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php</b> on line <b>135</b><br /> <br /> <b>Strict Standards</b>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. 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 <b>/homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php</b> on line <b>143</b><br /> Kontakt « Dirk Grizan
Strict Standards: Non-static method nggGallery::get_theme_css_file() should not be called statically, assuming $this from incompatible context in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/nextgen-gallery/nggallery.php on line 307

Strict Standards: Non-static method HS_InlineTags::replace() should not be called statically, assuming $this from incompatible context in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/headspace.php on line 203

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/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php on line 133

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/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php on line 134

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/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php on line 135

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/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/models/inline_tags.php on line 143

Strict Standards: Non-static method HeadSpace_Plugin::specialchars() should not be called statically, assuming $this from incompatible context in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/modules/page/tags.php on line 64

Strict Standards: Non-static method HeadSpace2::get() should not be called statically, assuming $this from incompatible context in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/headspace2/modules/page/keywords.php on line 45

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method nggMediaRss::add_mrss_alternate_link() should not be called statically in /homepages/45/d17632941/htdocs/grizan.com/wp-includes/plugin.php on line 339

Strict Standards: Non-static method nggMediaRss::get_mrss_url() should not be called statically in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/nextgen-gallery/lib/media-rss.php on line 14

Strict Standards: Non-static method nggGallery::get_theme_css_file() should not be called statically, assuming $this from incompatible context in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/nextgen-gallery/nggallery.php on line 307
-->

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/45/d17632941/htdocs/grizan.com/wp-includes/functions.php on line 41

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/45/d17632941/htdocs/grizan.com/wp-includes/functions.php on line 50

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/45/d17632941/htdocs/grizan.com/wp-includes/functions.php on line 52

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/45/d17632941/htdocs/grizan.com/wp-includes/functions.php on line 54

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/45/d17632941/htdocs/grizan.com/wp-includes/functions.php on line 55

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/45/d17632941/htdocs/grizan.com/wp-includes/functions.php on line 41

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/45/d17632941/htdocs/grizan.com/wp-includes/functions.php on line 50

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/45/d17632941/htdocs/grizan.com/wp-includes/functions.php on line 52

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/45/d17632941/htdocs/grizan.com/wp-includes/functions.php on line 54

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/45/d17632941/htdocs/grizan.com/wp-includes/functions.php on line 55

Kontakt


Strict Standards: Non-static method nggGallery::get_option() should not be called statically, assuming $this from incompatible context in /homepages/45/d17632941/htdocs/grizan.com/wp-content/plugins/nextgen-gallery/lib/shortcodes.php on line 44

Dirk Grizan

Übach-Palenberg/Heinsberg
Wiesenstr.33
52531 Übach-Palenberg, Nordrhein-Westfalen
+49 (2404) 678914

+49 (151) 55339446
management@grizan.com

Haftungsausschluß:

Grizan.com

- im folgenden Anbieter –

§1 Haftung für Inhalte
Der Anbieter ist gemäß § 7 Abs.1 TMG für eigene Inhalte auf diesen Seiten verantwortlich, übernimmt aber keine Gewährleistung für die Richtigkeit, Vollständigkeit und Aktualität der bereitgestellten Informationen. Haftungsansprüche durch Nutzung oder Nichtnutzung fehlerhafter und unvollständiger Informationen des Anbieters werden grundsätzlich ausgeschlossen. Die Angebote des Anbieters auf dieser Webseite sind freibleibend und unverbindlich.

§2 Haftung für Links
Die Webseite des Anbieters enthält Verweise (Links) auf fremde Internetseiten und Inhalte, für die jeweils der Internetbetreiber, Besitzer oder Anbieter verantwortlich ist. Dabei hat der Anbieter keinen Einfluß auf die derzeitige und zukünftige Gestaltung der verlinkten Internetseiten und übernimmt für diese Inhalte keine Gewähr. Der Anbieter hat zum Zeitpunkt der Linksetzung die verlinkten Internetseiten im Rahmen seiner Möglichkeiten geprüft und bestätigt, daß keine illegalen und rechtsverletzende Inhalte festzustellen waren. Dies gilt für alle vom Anbieter gesetzten Links, Verweise, sowie für Anbietereinträge in Portalen, Gästebüchern, Diskussionsforen, Mailinglisten und Bookmarkverzeichnissen. Bei Bekanntwerden von Rechtsverletzungen wird der Anbieter Verknüpfungen, Einträge und Inhalte umgehend löschen, insofern es ihm möglich ist.

§3 Urheberrecht
Das Copyright für veröffentlichte Werke, Inhalte, Grafiken, Tondokumente und Videosequenzen bleibt allein beim Anbieter der Seiten und unterliegt dem deutschen Urheberrecht. Eine Vervielfältigung oder Verwendung der Anbieterwerke in elektronischer oder gedruckter Form und ist ohne ausdrückliche Zustimmung des Anbieters nicht gestattet und bedürfen der schriftlichen Zustimmung. Der Anbieter selbst ist bestrebt, in allen Internetpublikationen die Urheberrechte Dritter zu beachten. Alle vom Anbieter durch Dritte genutzten und geschützten Marken- und Warenzeichen unterliegen den Besitz- und Urheberechten der jeweils eingetragenen Eigentümer. Bei Nutzung von urheberrechtlich geschüztem Material wird der Anbieter die Erlaubnis für eine Publikation beim Urheber einholen.

§4 Datenschutz
Auf den Internetseiten des Anbieters werden personenbezogene Daten auf freiwilliger Basis  registriert. Der Anbieter erklärt, daß diese Daten ohne ausdrückliche Zustimmung nicht an Dritte weitergegeben werden. Allerdings weist der Anbieter darauf hin, daß bei der Kommunikation per Formular oder Email der Zugriff auf die Daten durch Dritte erfolgen kann. Die Nutzung von veröffentlichten Kontaktinformationen des Anbieters für nicht angeforderte Informationsmaterialien ist nicht gestattet. Der Anbieter behält sich rechtliche Schritte für nicht angeforderte Informationen z. B. Spammails vor.

Projektbeispiele

Archives

All entries, chronologically...

Pages List

General info about this blog...