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

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

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 678

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

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

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/wp-db.php:52) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-content/plugins/contactforms/cforms.php on line 61

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/wp-db.php:52) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-content/plugins/contactforms/cforms.php on line 61

Deprecated: Function split() is deprecated in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-content/themes/jr_articles/header.php on line 3
J.R. Photoblog - Articles & Tutorials » Blog Archive » Truc anti-spam pour Pixelpost
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/kses.php on line 446

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

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28

Truc anti-spam pour Pixelpost


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

Je pense que je ne suis pas le seul √† avoir √©t√© totalement mitraill√© de spams avec mon pixelpost, j’en avais parfois jusqu’√† 200 par jour !

Je me suis donc mis √† la recherche d’une solution simple et efficace, et je pense l’avoir trouv√© puisque depuis sa mise en place, il y a un an et demi, les spams ont totalement disparu.

En voici le principe :

Les spammeurs ne vont pas sur votre site (ou alors peut-√™tre juste une fois), ils utilisent la plupart du temps des syst√®mes automatis√©s qui postent directement le commentaire crapuleux vers le script de votre site qui l’enregistre. Conclusion, ils ne passent pas par le formulaire et donc ne cliquent pas sur le bouton “envoyer le commentaire”.

L’astuce consiste juste √† v√©rifier que le bouton √† √©t√© physiquement cliqu√© avant d’enregistrer le commentaire.

La modification s’effectue en deux √©tapes, il faut :

  • Modifier le formulaire pour qu’il soit en mesure de d√©tecter si oui ou non le bouton a √©t√© cliqu√©.
  • Modifier le script d’enregistrement du commentaire pour qu’il re√ßoive le r√©sultat du formulaire et d√©cide de valider ou non l’enregistrement.

1. Modifier le formulaire :

D’abord ce qu’il te faut, c’est localiser la page o√Ļ se trouve ton formulaire de commentaires.
Il est généralement dans ton template soit dans image_template.html soit dans comment_template.html.

  • Voici la modification √† faire avec le template “simple” de pixelpost 1.5 :
    Le template “simple” de la version 1.5 utilise le popup, le formulaire se trouve donc dans comment_template.html

    CODE D’ORIGINE (√† remplacer par le code modifi√© ci-dessous) :

    CODE MODIFI√Č :

  • Pour pixelpost 1.6 :
    C’est exactement la m√™me chose que pour la version 1.5, sauf que pour le template “horizon”, le formulaire √† modifier se trouve dans image_template.html.

1. Modifier le script d’enregistrement :

  • Pour Pixelpost 1.5 :
    Edite le fichier index.php et va √† la ligne 933 au d√©but de la section “SAVE COMMENT”

    CODE D’ORIGINE (√† remplacer par le code modifi√© ci-dessous) :

    CODE MODIFI√Č :

    Ainsi les commentaires ne seront enregistr√©s que si la valeur “ahuman” est re√ßue, autrement dit, si le bouton √† √©t√© cliqu√©.

    Effectue la m√™me modification √† la ligne 1025 au d√©but de la section “EMAIL NOTE ON COMMENTS”. Ainsi les commentaires ne seront envoy√©s par email que si la valeur “ahuman” est re√ßue, autrement dit, si le bouton √† √©t√© cliqu√©.

  • Pour Pixelpost 1.6 :
    C’est exactement la m√™me chose que pour la version 1.5, sauf que les 2 lignes √† modifier se trouvent dans includes/functions_comments.php aux lignes 15 et 225.

Voilà !
Forc√©ment, √ß√† n’arr√™te pas les spams manuels, mais bon ceux l√† sont d√©j√† plus rares. Si d’un seul coup les spams recommen√ßaient, cel√† voudrait dire que les spammeurs ont pig√© le truc et injectent directement la valeur “ahuman” avec leurs scripts, dans ce cas tentez de changer et le nom de la variable “you_are” et sa valeur id√©ale “ahuman” par autre chose.

5 Commentaires »


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

    J’ai longtemps utilis√© ce truc qui fonctionnait parfaitement, mais la version 1.7.1 semble ne plus permettre cette astuce. Je vais regarder √ßa attentivement…

    Julien : Ha… zut, j’essaierais de regarder quand j’aurais un moment

    Comment by Pierre
    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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    April 7, 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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    4:08 pm


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

    Salut Julien,

    merci pour ton truc anti-spam! Apr√®s avoir effac√© des centaines de messages (TOUJOURS LES M√äMES!!!!!) pour des super costumes d’Halloween, j’ai cherch√© une solution et suis tomb√© sur ta “technique”.

    Et, contrairement a Pierre, celà semble marcher chez moi, également en version 1.7.1

    En esp√©rant que cel√† dure longtemps car pour une premi√®re confrontation au spam massif, j’avais du mal a dig√©rer!

    Salutations
    Stéphane - voirvenir

    Comment by Stephane
    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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    October 16, 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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    5:26 am


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

    Super, je teste ! J’utilise la 1.7.1, on verra si √ßa fonctionne. Pour l’instant j’utilise Defensio, mais il me bloque souvent les bons commentaires et c’est tr√®s dur de les d√©bloquer.
    Merci pour cet appui technique, et bravo pour vos images et le développement de votre site.

    ronan

    Comment by ronan
    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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    December 11, 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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    4:03 am


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

    Apr√®s une semaine de test, cette astuce semble tr√®s bien fonctionner avec la version 1.7.1, je n’ai plus que des commentaires valides et aucun soucis de spam.

    (note : dans mon empressement je n’avais pas bien lu la recommandation ‘anti-merci’, supprimez mon commentaire si besoin)

    Comment by ronan
    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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    December 17, 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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    4:34 am


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

    […] Apparemment, il peut ¬†y avoir des probl√®mes de spams avec Pixelpost. Je n’ai pas trop eu le temps de m’en rendre car j’ai appliqu√© de mani√®re pr√©ventive l’astuce de J. Roumagnac que vous trouverez ici. […]

    Pingback by Pixelpost et Wordpress pour un photoblog « Blog.Omartins.com
    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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    July 23, 2009 @
    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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/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 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    2:56 pm

Ajouter un commentaire

S.v.p. ne laissez pas un commentaire pour dire 'merci' mais seulement si vous avez quelque chose d'intéressant à ajouter ou à demander ;) .


» Close
E-mail It