I promised I'd do this, so here goes.

In the user access page (/admin/user/access) the old version of the Spam module had three settings:

Administer Spam
Bypass Filters
Report Spam

"report spam" allowed someone to identify potential spam, and the marked item would be unpublished, but it wouldn't be officially flagged as spam unless I went into a queue and made that call.

"Report Spam" is no longer available in the latest version -- there's just "Administer Spam" and "Bypass Filters." I would like my registered users to be able to report spam, but I don't want to give them full admin controls where spam is concerned.

Comments

jeremy’s picture

Thanks for the feedback. Yes, I do fully plan to implement this functionality.

jeremy’s picture

Title: Missing feature in transition from 5.x-1.1-2 to 5.x-3.0-alpha5 » Allow users to report spam
Version: 5.x-3.0-alpha5 » 5.x-3.x-dev
Category: bug » feature

Setting as a feature request.

blooksllc’s picture

I am new to this module, so I don't know how it worked before; but, it would be good to have an option to put "report this" in the links section of the node (similar to how the add-this module works). Not sure if I am stating the obvious.

T

jeremy’s picture

Assigned: Unassigned » jeremy

Note: when implementing this feature, also look at this related feature request. Assigning to myself, as I want this included in the beta release of this module.

jeremy’s picture

Note: also refer to this related feature request, perhaps it can/should be implemented without actions integration.

jeremy’s picture

Note: also refer to this related feature request. If sending notifications, support some sort of throttling.

jeremy’s picture

Status: Active » Postponed

Giving this more thought, I think there are already modules that provide the majority of this functionality. For example, what about using the Flag module? Or, what about the Flag content module? I bet there are others, too. Perhaps some extra integration could be done, but I don't see any reason we need to reinvent this wheel.

Postponing this issue for now, to revisit after the beta release.

ubersoft’s picture

Uh... but the previous version of the spam module had this functionality. And here is what it did:

1. user flags a comment as spam
2. comment is removed from public view and put in a moderation queue
3. admin checks the moderation queue and makes the final decision
4. comment is either verified as spam or returned to its previous setting

Forcing the users of this module to create a workflow that would hook into the spam module seems a bit harsh. I'm pretty sure it's beyond my technical capabilities.

jeremy’s picture

@ubsersoft: actually, it never worked as you described. Users could report spam, but there was no automatic actions -- an administrator had to log in and review the feedback, then could decide whether or not to mark the content as spam. The 'flag' module seems a closer match for what you describe than what was provided in the earlier version of the spam module.

In any case, if integration is required, then that would be provided in the spam module. I'm merely trying to avoid completely re-writing modules that already exist and do their jobs very nicely.

ubersoft’s picture

Ah, I see what you mean. Sorry for the panic. I love Drupal, but it already stretches my technical ability to the absolute limits, so the thought of having to integrate modules together absolutely terrified me. :)

jeremy’s picture

I believe the ability to allow users to report content as spam is very important, and thus I will not abandon this issue. However, I also wanted to get a stable release out, as the 3.x spam module has been in development for far too long as is. Once the first stable release is out, I plan to revisit this, and will document the process for integrating a third-party module, such as the flag module.

jiakomo’s picture

I just upgraded from an older version and was surprised to see this feature gone.

As an alternative, the flag module could be used to work as a "report spam" module but only for registered users, as anonymous flagging is not possible (yet?).

dkruglyak’s picture

There is also abuse module to consider integrating with: http://drupal.org/project/abuse

gnassar’s picture

Status: Postponed » Closed (duplicate)

Marking as duplicate of #448412: Actions integration for Spam module. This functionality will be handled there.