Users can't create tickets

[anonymous]

After updating from 0.10dev to 0.10b1 our users are not able to create new tickets. This is the error message they are receiving:

Traceback (most recent call last):
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 335, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 220, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/local/lib/python2.4/site-packages/trac/ticket/web_ui.py", line 109, in process_request
    del req.args['owner']
KeyError: 'owner'

We have updated regularly throughout 0.10dev and this is the first time we have encountered this problem. The usual update procedure steps were taken:

svn update
sudo python setup.py install
sudo trac-admin /path/to/trac upgrade
sudo /usr/local/etc/rc.d/apache restart

Thanks for any pointers on this.

[Christian Boos]

This problem was recently introduced by r3672. Should be fixed by r3681.

[anonymous]

This has been confirmed by our users. Thanks!

[pg@…]

I'd like to have anonymous users be able to create tickets, but not to modify any ticket later on. So I tried to set

permission remove anonymous TICKET_MODIFY

which leaves the following permissions TICKET*

anonymous  TICKET_CREATE  
anonymous  TICKET_VIEW    

but then I get the error that is mentioned above. Any idea?

[Matthew Good]

Replying to pg@levana.de:

I'd like to have anonymous users be able to create tickets, but not to modify any ticket later on. So I tried to set

permission remove anonymous TICKET_MODIFY

which leaves the following permissions TICKET*

…snip…

but then I get the error that is mentioned above. Any idea?

As cboos mentioned the fix was made in r3681, so you need at least that revision of Trac. The fix is not included in Trac 0.10b1, so you will need to get Trac from SVN or wait until a new release is made.

[mwigge@…]

I have the same problem with RC1 which should be revision 3773 I think… it only works with TICKET_MODIFY for anonaymous.

[mwigge@…]

maybe I was too fast or the error came from the cache but now it works… sometimes it helps to make a lunch break ;-)