Changes between Version 5 and Version 6 of DeveloperDoc


Ignore:
Timestamp:
Apr 10, 2008 1:07:35 PM (16 years ago)
Author:
Horst Meyerdierks
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperDoc

    v5 v6  
    2121A: Developer access includes some *_ADMIN permissions, but not TRAC_ADMIN itself. You can reconfigure milestones, ticketing and the wiki, but you cannot reconfigure access rights. Find a project admin and ask them to give you TRAC_ADMIN permission in addition to the developer permission you already have. Be sure you keep the explicit developer permission, otherwise you will lose write access to the repository.
    2222
    23 Q: I am an admin on our project, how do I make !NewUser and admin?
     23Q: I am an admin on our project, how do I make !NewUser an admin?
    2424
    2525A: While logged onto the project as a user that has TRAC_ADMIN permission on the project there will be an "Admin" button, click it. Select General : Permissions on the left. At the top right you then have a panel "Grant Permission". The subject is "!NewUser" and the action is "TRAC_ADMIN". Once filled in hit the "Add" button in that panel.
     26
     27Q: Help, the tickets on our project are being spammed! What can I do?
     28
     29A: 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
     31Q: OK, but how can I prevent the spam?
     32
     33A: 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
     35Q: Hmm, but how then can anyone make tickets that I want them to make?
     36
     37A: 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").