#4064 closed enhancement (fixed)
Submit spam button
Reported by: | anonymous | Owned by: | Dirk Stöcker |
---|---|---|---|
Priority: | normal | Milestone: | plugin - spam-filter |
Component: | plugin/spamfilter | Version: | 0.10 |
Severity: | normal | Keywords: | |
Cc: | Ryan J Ollos | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I'd like a button or something where someone with the right permissions may decide whether a ticket in trac is a spam ticket or not. If the ticket is a spam ticket, Akismet (when used) should be automatically notified and/or a Bayes filter (if available) should be updated. This might also be interesting for wiki sites.
Attachments (0)
Change History (12)
follow-up: 3 comment:1 by , 18 years ago
Milestone: | → none |
---|
comment:2 by , 15 years ago
Milestone: | not applicable → spam-filter-plugin |
---|---|
Owner: | removed |
This should eventually hijack the new Delete button if present [9270], so that one can submit spam and delete the comment in one go (and also the submit spam can not be abused).
comment:3 by , 14 years ago
Replying to cboos:
That button should simply redirect to the spamfilter admin module, to the corresponding entry.
That would be a nice feature, and additionally, for a user that is not an administrator, it would be nice if the button flagged the post for review by an administrator.
The specific application I have in mind for this feature is discussed in th:#6557.
comment:4 by , 11 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:5 by , 11 years ago
Cc: | added |
---|
comment:6 by , 11 years ago
In r12482: Add a table entry to take data. Now only the UI is missing :-)
follow-up: 10 comment:7 by , 10 years ago
Voteplugin has nice example code how to handle and how to place a spam report button. Simply handling it alike to voting arrows should be a good idea.
follow-up: 12 comment:10 by , 10 years ago
Replying to dstoecker:
Voteplugin has nice example code how to handle and how to place a spam report button. Simply handling it alike to voting arrows should be a good idea.
Locating the Report spam button in the contextual navigation seems to be inconsistent with the interface design for Trac, simply because the items are intended to be navigation items. The VotePlugin doesn't feel quite as inconsistent because the arrows have a unique styling. If the Report spam link was replaced with a stylized button (example), it might not look out of place.
Alternatively, on the ticket page it would seem to make sense to place a button in the ticket description box (next to Reply and Delete), and to also have buttons for reporting ticket comment spam in the ticket comment box (next to Reply, Edit and Delete). On the wiki pages it would seem to make sense to locate the Report spam button in the div.buttons
(i.e. in the row of buttons with Edit this page, to the right of div.delete
when it is displayed).
comment:12 by , 10 years ago
Replying to rjollos:
Alternatively, on the ticket page it would seem to make sense to place a button in the ticket description box (next to Reply and Delete), and to also have buttons for reporting ticket comment spam in the ticket comment box (next to Reply, Edit and Delete). On the wiki pages it would seem to make sense to locate the Report spam button in the
div.buttons
(i.e. in the row of buttons with Edit this page, to the right ofdiv.delete
when it is displayed).
I considered different places and multiple buttons for individual ticket comments also, but
- that would mean much more individual code for different pages
- destroy the "one method for all" feeling
- doesn't help the admin, as when he clicks on the page and doesn't see the spam right away (together with the comment a user can enter for submit), then probably the report is anyway wrong.
I agree thought, that the design of the report link can be improved.
That button should simply redirect to the spamfilter admin module, to the corresponding entry.