Closed (fixed)
Project:
Drupal core
Version:
x.y.z
Component:
user system
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
22 May 2006 at 12:25 UTC
Updated:
7 Jun 2006 at 06:00 UTC
Jump to comment: Most recent file
see full discussion here:
http://drupal.org/node/64861
this simple patch will render registering phony accounts absolutely pointless for spammers.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | spam.diff_0.txt | 633 bytes | beginner |
| #2 | spam.diff.txt | 645 bytes | beginner |
| registration-spam.diff.txt | 634 bytes | beginner |
Comments
Comment #1
killes@www.drop.org commentedThe patch does not comply with coding standards: We use || not OR.
Comment #2
beginner commentednew patch.
I see the different precedence between &&, || and AND, OR.
http://www.php.net/manual/en/language.operators.logical.php
Is there any particular (historical) reason why Drupal must use && and || instead of AND and OR?
Comment #3
drummThis doesn't seem to have much to do with "meta roles"; what does this patch do, concisely?
Comment #4
beginner commentedthe patch is relevant to the discussion about spam registration that I addressed on the 'meta-roles' page:
This page removes that incentive, because an account that is never activated (because created by a spammer with a fake email or an email they don't own) is not accessible by anonymous or normal users, and most importantly from the spammers' point of view, the page is not accessible by search engines...
Comment #5
killes@www.drop.org commentedapplied to 4.7, downgrading as nothign is that broken.
Comment #6
beginner commentedclean patch for head.
Is there any particular (historical) reason why Drupal must use && and || instead of AND and OR?
Comment #7
beginner commentedComment #8
beginner commentedComment #9
killes@www.drop.org commentedWe have decided to use && and || and want to keep it consistent.
Comment #10
beginner commentedthanks :)
Comment #11
drummCommitted to HEAD.
Comment #12
(not verified) commented