Edgewall Software
Modify

Opened 18 years ago

Closed 10 years ago

Last modified 10 years ago

#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)

comment:1 by Christian Boos, 18 years ago

Milestone: none

That button should simply redirect to the spamfilter admin module, to the corresponding entry.

comment:2 by Christian Boos, 15 years ago

Milestone: not applicablespam-filter-plugin
Owner: Matthew Good 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).

in reply to:  1 comment:3 by ryano@…, 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 Dirk Stöcker, 11 years ago

Owner: set to Dirk Stöcker
Status: newassigned

comment:5 by Ryan J Ollos, 11 years ago

Cc: Ryan J Ollos added

comment:6 by Dirk Stöcker, 11 years ago

In r12482: Add a table entry to take data. Now only the UI is missing :-)

comment:7 by Dirk Stöcker, 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.

comment:8 by Dirk Stöcker, 10 years ago

See r13225 - added user side, admin side still missing.

Last edited 10 years ago by Dirk Stöcker (previous) (diff)

comment:9 by Dirk Stöcker, 10 years ago

Resolution: fixed
Status: assignedclosed

In r13228.

in reply to:  7 ; comment:10 by Ryan J Ollos, 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:11 by Dirk Stöcker, 10 years ago

Feel free to provide improvement patches…

in reply to:  10 comment:12 by Dirk Stöcker, 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 of div.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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Dirk Stöcker.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Dirk Stöcker to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.