Closed (outdated)
Project:
Spamicide
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 Mar 2011 at 22:40 UTC
Updated:
1 Mar 2019 at 14:16 UTC
Jump to comment: Most recent
Comments
Comment #1
lipcpro commentedThat certainly is an interesting idea, however that would only work on the comment form and not on any of the other forms that it supports out of the box, nor would it work on new forms created by other modules. Spamicide would have to somehow know about the variable in every form or print the whole form into watchdog, and quite a few custom forms and webforms can be quite lengthy. Not a practical proposition IMHO.
Comment #2
tumblingmug commentedThis is another version of the watchdog message I actually use:
Notice, that this works for both custom and default spamicide field names. Also this variant utilizes watchdog's automatic ip address logging using it's own column and clears redundant information from the description field.
An additional idea could be to implement a variable_get() which replaces the hardcoded whois lookup url. Then you would be able to configure even a local site lookup by the whois module or any other external service you like. It's also nice to see on a map where the spam comes from :)
Comment #3
hansamurai commentedYeah, I just saw my first non-comment block and it dawned on me that people use this for things other than commenting. This is a really excellent module, though. I set the honeypot comment field to "email" (Drupal uses "mail") and that has worked exceptionally well.
Do you know how screen readers will process the field? I'm assuming a blind user would see it as a normal field and may trigger Spamicide? This isn't a concern for me or my site, just curious.
Comment #4
lipcpro commentedI think this is a good idea in general, however since it's supposed to add to any kind of form in Drupal, not just comments. I would have to come up with a way to store all of the submission, and not just the one field, that could be a very large amount of data to try to stuff in the watchdog logs.
Comment #5
lamp5