| 26 | |
| 27 | Q: Help, the tickets on our project are being spammed! What can I do? |
| 28 | |
| 29 | A: Two things. First, you can remove the spam. To do so you have to enable the !TicketDelete plugin; this has to be done only once for the project. Use your TRAC_ADMIN privileges, click on the Admin button and select the General : Plugins item on the left. Amongst the plugins listed, click on the name !TracTicketDelete, tick Enabled and click the Apply Changes button. From now on when you view tickets - and while you have the permission to do so - you will see a Delete button by every ticket or comment added to the ticket. You can use that to delete a comment or a whole ticket. |
| 30 | |
| 31 | Q: OK, but how can I prevent the spam? |
| 32 | |
| 33 | A: That's the second thing. If you give "anonymous" any permission higher than "reader" then any spammer can create a ticket and can comment on an existing ticket. You have to either block all access for "anonymous" or restrict it to "reader". "reader" is a new permission group introduced to address this problem. A "reader" can only read the wiki and tickets, they cannot make or modify tickets and cannot read the repository. |
| 34 | |
| 35 | Q: Hmm, but how then can anyone make tickets that I want them to make? |
| 36 | |
| 37 | A: Since "anonymous" can no longer create tickets, you will have to bite the bullet and find out the Forge user names of all the people that may want to create tickets. Give those named users access level "ticket" (or "user" or "developer"). |