By implementing this module as a regular input format, it would work with any module that allowed filtering of content thus taking advantage the spam module's powerful array of methods to determine whether content is spam. As to whether an input format filter could prevent posting I am not sure but it would let us at least remove the offending content and notify the admin.

I know the module supports filters but they are not input formats as far as I understand it. This would be a superior implementation, at least for some cases and would stop all the hassle of manually adapting modules to work with the spam module.

Comments

mcurry’s picture

mcurry commented

Interesting idea! I'd like to take a crack at this, but not sure when I can get to it.

Has anyone else looked at what it would take to implement this?

solipsist’s picture

solipsist commented

No idea, I haven't got any responses. Perhaps my idea is totally unfeasible, if so, tell me.

jeremy’s picture

jeremy commented

I intend a rewrite of the module soon, making it more modular instead of one monolithic module. At that time, I will look into this feature request further and see if it's possible. I've not played much with input filters so I'm currently not sure whether or not it's possible.

pieterdc’s picture

pieterdc
Primary language Dutch
Location Ghent
commented

A Drupal input format is a set of input filters.
Drupal input filters filter content when it gets shown.
(I read this in the Pro Drupal Development book and found a simular explanation on Lullabot.)

Which means that, as far as I know, you can't use an input format or filter to determine it's spam probability.
But the spam module could indeed remove the 'offending content' using an input format or filter, I think.

solipsist’s picture

solipsist commented

Pieter: Yeah I learnt that later, after I posted this. Still, an input format could work but the content would have to pass through it once. The filter could use block it all out and report the nid as containing spam. I can think of at least one way of doing it.

jeremy’s picture

jeremy commented

This feature is planned in an upcoming version of the module. All form input will then be able to be run through the spam filter.

solipsist’s picture

solipsist commented

Nice! Looking forward to that... no messing with modifying modules then to have them interface with the spam module. :)

jeremy’s picture

jeremy commented
Version: 5.x-1.x-dev » 5.x-3.x-dev

Assigning to the 5.x-3.x development branch, where it does tap into the form api. Support still needs to be added for various content types, but it no longer takes hacking the core module and utilize a simpler API.

jeremy’s picture

jeremy commented
Status: Active » Postponed

I would like to see this feature implemented, but it is not necessary to get us to a beta release. Marking as postponed for now, to revisit after we have a beta release, or when someone submits a patch.

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Postponed » Closed (won't fix)

This would be difficult to do as the current filter system is not context aware.