Strict Standards: Redefining already defined constructor for class wpdb in /homepages/10/d212871047/htdocs/wp-includes/wp-db.php on line 52

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/10/d212871047/htdocs/wp-includes/cache.php on line 389

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/10/d212871047/htdocs/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/10/d212871047/htdocs/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/10/d212871047/htdocs/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/10/d212871047/htdocs/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/10/d212871047/htdocs/wp-includes/classes.php on line 556

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/10/d212871047/htdocs/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/10/d212871047/htdocs/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/10/d212871047/htdocs/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/10/d212871047/htdocs/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/10/d212871047/htdocs/wp-includes/classes.php on line 678

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-includes/theme.php on line 507

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/dofollow.php on line 171

Warning: Cannot modify header information - headers already sent by (output started at /homepages/10/d212871047/htdocs/wp-includes/wp-db.php:52) in /homepages/10/d212871047/htdocs/wp-content/plugins/polls/polls.php on line 1088

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/simpletagging/simpletagging.php on line 49

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/tantan/tantan_reports.php on line 41

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/tantan/tantan_reports.php on line 44

Deprecated: Function ereg() is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/tantan/tantan_reports.php on line 39

Deprecated: Function ereg() is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/tantan/version-check.php on line 201

Strict Standards: Non-static method NAVT::wp_bootstrap() should not be called statically in /homepages/10/d212871047/htdocs/wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt.php on line 1743

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/10/d212871047/htdocs/wp-content/plugins/wp-db-backup.php on line 90

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method NAVT::init() should not be called statically in /homepages/10/d212871047/htdocs/wp-includes/plugin.php on line 160

Strict Standards: Non-static method NAVT::install_check() should not be called statically in /homepages/10/d212871047/htdocs/wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt.php on line 112

Strict Standards: Non-static method NAVT::get_option() should not be called statically in /homepages/10/d212871047/htdocs/wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt.php on line 173
Optimisation PC, composants... communaute de noctambules
Warning: Creating default object from empty value in /homepages/10/d212871047/htdocs/wp-content/themes/dkret2/header.php on line 45

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

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/10/d212871047/htdocs/wp-includes/functions.php on line 14

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/10/d212871047/htdocs/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/10/d212871047/htdocs/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/10/d212871047/htdocs/wp-includes/functions.php on line 27

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/10/d212871047/htdocs/wp-includes/functions.php on line 28

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/10/d212871047/htdocs/wp-includes/functions.php on line 14

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/10/d212871047/htdocs/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/10/d212871047/htdocs/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/10/d212871047/htdocs/wp-includes/functions.php on line 27

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/10/d212871047/htdocs/wp-includes/functions.php on line 28

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-content/plugins/polls/polls.php on line 568

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-content/plugins/polls/polls.php on line 577

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/formatting.php on line 74

LE MATÉRIEL INFORMATIQUE

Ensemble des éléments physiques employés pour le traitement de données. Le matériel informatique (hardware, quincaillerie en anglais) est la partie physique, essentiellement électronique, de l’ordinateur, d’un terminal TNT ou sat…. Il est le complément du logiciel, (software en anglais). De manière analogue aux logiciels, on peut évoquer les termes de mise à jour ou d’architecture matérielle. HARDWARE : Matériel informatique physique, par opposition au software, matériel logiciel.
Un ordinateur est constitué des composants suivants : un ou des processeurs
de la mémoire vive
de la mémoire morte
des bus informatiques pour relier le ou les processeurs aux mémoires et aux périphériques
une alimentation PC

À ces composants il faut ajouter des interfaces de communication :

Connexions aux mémoires de masse
Interfaces de communications homme machine : (clavier, console, imprimante) …
Interfaces de communication avec d’autre ordinateurs

À titre d’exemple, l’architecture de l’unité centrale d’un PC est composée de :

une carte mère accueillant :
un ou des microprocesseurs
de la mémoire vive
de la mémoire morte
bus PCI-Express, PCI, AGP, ISA (connecteurs d’extensions)
bus ATA, SATA, SCSI (principalement dédiés aux mémoires de masse)
bus USB, Firewire (pour connecter des périphériques)
une ou des cartes graphiques
une ou des cartes d’acquisition
une ou des cartes son
une ou des cartes réseau
une ou des cartes modem
un ou des disques durs
un ou des lecteur de disque optique, graveur de disque optique

Tous ces composants sont installés dans un boîtier, pouvant servir à canaliser les flux d’aire de refroidissement et à insonoriser le tout, généralement une tour.

Périphériques informatique

On distingue trois types de périphérique :

les périphériques d’entrée permettent d’entrer l’information dans l’ordinateur ;
les périphériques de sortie permettent de sortir l’information de l’ordinateur ;
les périphériques d’entrée-sortie permettent des communications bidirectionnelles.

La plupart des périphériques sont amovibles, c’est-à-dire qu’ils peuvent être déconnectés de l’unité centrale sans empêcher celle-ci de fonctionner (il faut parfois éteindre l’ordinateur avant de retirer le périphérique).

Sur les micro-ordinateurs, tous les périphériques sont reliés à la carte mère par un connecteur que l’on insère :

soit dans un port directement soudé à la carte mère
soit dans un port disponible sur une carte d’extension, elle-même enfichée sur la carte mère. La carte d’extension étant amovible, il est facile de la remplacer en cas de panne ou d’évolution technologique.

Périphériques d’entrée

Clavier, Joystick, Manette, Souris, Trackball, Tablette graphique, Scanner, Camescope numérique, appareil photo numérique, Webcam, Micro

Périphériques de sortie

Moniteur, Imprimante, Enceinte acoustique, Sortie tv.

Périphériques d’entrée-sortie

K7, Disquette, DVD Rom, CD Rom, Lecteur zip, Modem, Ecran tactile, Clé usb, Carte réseau.

LE MONITEUR
LA CARTE MÈRE
LE PROCESSEUR
LA MÉMOIRE VIVE
LA CARTE GRAPHIQUE
LE DISQUE DUR

Comment surfer sur Internet ?
Ce dossier va vous permettre de parfaitement connaitre les bonnes références pour surfer vite et bien. Vous étudierez les moteurs de recherche, les annuaires, ainsi que les bases de données !
Vive le web rapide et efficace !

Tout savoir sur les mails
Toutes les infos concernant les mails, configurer une adresse. Le principe d’utilisation du courrier électronique est relativement simple, c’est ce qui en a rapidement fait le principal service utilisé sur internet. le courrier électronique permet d’envoyer instantanément un courrier à plusieurs personnes simultanément.

Sécuriser son pc
Ici, vous trouverez toutes les solutions contre les agressions extérieures, pour maintenir son pc en bon état de fonctionnement. Vous protègez de toutes les agressions du web: vers, virus, chevaux de troie et autres spywares. Pour combattre au quotidien ces attaques sur Internet et les moyens de s’en protéger…

Lexique-glossaire informatique
Voici un petit lexique destiné à mieux connaître la signification des principaux termes employés dans le jargon informatique…Vous pouvez rechercher une définition particulière en utilisant l’index thématique. Tous les termes de A à Z.

aucun

2 Commentaires

Ecrire un commentaire»
Olivier
  1. 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/10/d212871047/htdocs/wp-includes/functions.php on line 14
    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/10/d212871047/htdocs/wp-includes/functions.php on line 14

    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/10/d212871047/htdocs/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/10/d212871047/htdocs/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/10/d212871047/htdocs/wp-includes/functions.php on line 27

    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/10/d212871047/htdocs/wp-includes/functions.php on line 28
    15 mars 2008 |
    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/10/d212871047/htdocs/wp-includes/functions.php on line 14

    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/10/d212871047/htdocs/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/10/d212871047/htdocs/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/10/d212871047/htdocs/wp-includes/functions.php on line 27

    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/10/d212871047/htdocs/wp-includes/functions.php on line 28
    2:18

    1


    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/10/d212871047/htdocs/wp-includes/functions.php on line 14

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/formatting.php on line 74

    au fait j ai eu du mal à comprendre la protection anti spam mais bon je suis pas fin…

    Bah alors Jeff, tu sais plus faire une addition ? ;-)

  2. jeff


    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/10/d212871047/htdocs/wp-includes/functions.php on line 14
    jeff


    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/10/d212871047/htdocs/wp-includes/functions.php on line 14

    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/10/d212871047/htdocs/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/10/d212871047/htdocs/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/10/d212871047/htdocs/wp-includes/functions.php on line 27

    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/10/d212871047/htdocs/wp-includes/functions.php on line 28
    29 février 2008 |
    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/10/d212871047/htdocs/wp-includes/functions.php on line 14

    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/10/d212871047/htdocs/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/10/d212871047/htdocs/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/10/d212871047/htdocs/wp-includes/functions.php on line 27

    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/10/d212871047/htdocs/wp-includes/functions.php on line 28
    11:01

    2


    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/10/d212871047/htdocs/wp-includes/functions.php on line 14

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/formatting.php on line 74

    Sympa la partie “hard” (au fait j ai eu du mal à comprendre la protection anti spam mais bon je suis pas fin …)

Ecrire un commentaire








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/10/d212871047/htdocs/wp-content/plugins/math-comment-spam-protection/math-comment-spam-protection.classes.php on line 77

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/10/d212871047/htdocs/wp-content/plugins/math-comment-spam-protection/math-comment-spam-protection.classes.php on line 163