Ticket Custom Fields break View Tickets

[dicianno@…]

Trying to add a quick and dirty "personal sorting" feature using Ticket Custom Fields. Followed the directions here: TRAC_ROOT/wiki/TracTicketsCustomFields

First tried this in trac.ini:

[ticket-custom]                                                                 
order = select                                                             
order.label = Manage ticket order                                                 
order.options = 0|1|2|3|4|5|6|7|8|9                                        
order.value = 5

… which resulted in this when I added the new field to the search updates for View Tickets and clicked 'Update':

Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/lib/python2.4/site-packages/trac/ticket/query.py", line 414, in process_request
    req.redirect(query.get_href(req))
  File "/usr/lib/python2.4/site-packages/trac/ticket/query.py", line 189, in get_href
    format=format, **self.constraints)
TypeError: <lambda>() got multiple values for keyword argument 'order'

I figured 'order' was a bad name all of a sudden so I changed trac.ini to:

[ticket-custom]                                                                 
order_help = select                                                             
order_help.label = Ticket order                                                 
order_help.options = 0|1|2|3|4|5|6|7|8|9                                        
order_help.value = 5 

… which results in the same error.

Also of note, I change 'label' form "Manage ticket order" to "Ticket order" but now both appear in the 'Add filter' list in the 'View tickets' search page — which I'm afraid to try to click on, as I don't want to make things worse by clicking on a non-existent Ticket Custom Field.

Now for the kicker: anytime "Update" is clicked on the page, I get this same error — even if I don't add any fields at all to the default query.

For this reason I am marking Priority and Severity to the highest marks, since I've now completely broken my company's Trac setup following procedures in the published documentation.

Advice on removing the ticket-custom fields from the database itself (I'm guessing), so the database rights itself would be greatly appreciated, even before this bug itself is resolved.

[dicianno@…]

I found the "ticket_custom" table in the database, but it is empty.

I'm going to keep looking until I un-break our system, so if anyone has a suggestion, please send it my way.

---

I'm adding more text to this ticket because the Spam-Bayes filter on this Trac-trac is saying that this is spam. Hopefully this will be enough actual English to get by the Spam filter. Am I ruining the chances of getting by it since I said the S-word twice now? Let's find out.

---

Nope not enough text, however it did get down from 94% or so, to 54%. Do you think that this Spam filter might be too restrictive? Considering that I'm sitting here writing extemporaneously, trying to defeat it, when I had a 1-line addendum to make to the submission — to hopefully help anyone else that has this issue — is kind of silly. Let's try again.

[dicianno@…]

This bug is possibly/likely a duplicate of 1449. I'll let someone who know better close it as such, if it is.

[dicianno@…]

Unlike duplicate ticket 5494, I cannot simply change the trac.ini — the error persists.

[dicianno@…]

I apologize if I'm seemingly over-posting here, but I like to keep people up to date, in case anyone is actually working on this.

So, I've resolved it. I didn't realize I had to restart apache. This may seem obvious to some, but it wasn't to me, since the new fields appeared in trac when I editted trac.ini, but did not disappear when I removed them.

So, again, I'll leave this bug open to be closed by someone in the know, but it looks like I can rest soundly now.

[Christian Boos]

Replying to dicianno@obtech.net:

I apologize if I'm seemingly over-posting here, but I like to keep people up to date, in case anyone is actually working on this.

No problem.

So, I've resolved it. I didn't realize I had to restart apache. This may seem obvious to some, but it wasn't to me, since the new fields appeared in trac when I editted trac.ini, but did not disappear when I removed them.

This is considered a bug as well, see #2099, #5135 and #3833.

Closing this ticket as a duplicate of #1449.