Opened 12 years ago

Last modified 12 years ago

#9659 closed defect

ResourceNotFound error when updating grid on ActiveTickets screen — at Initial Version

Reported by: C. G. Brown Owned by: Björn Harrtell
Priority: normal Component: GridModifyPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.11

Description

Trac 0.11.7 GridModify 0.1.3 and 0.1.5 Firefox 8.0.1 and Chrome 16.0.912.63

I take the following steps as a TRAC_ADMIN with the GridModify plugin enabled:

  1. Go to the View Tickets link
  2. Go to the Active Tickets Screen
  3. Attempt to update compoent

I get a red X back. When I run this in Firebug, I get a 500 error against a URL of the form:

https://server.example.com/path/to/trac/gridmod/update?ticket=323456789101112131415&component=component1

When I run the update link that is fired off as an AJAX call in my web browser, I get the message:

Oops...
Traceback (most recent call last):
  File "/usr/local/lib/python2.5/site-packages/GridModify-0.1.3-py2.5.egg/gridmod/web_ui.py", line 56, in process_request
    ticket = Ticket(self.env, id)
  File "/usr/local/lib/python2.5/site-packages/Trac-0.11.7-py2.5.egg/trac/ticket/model.py", line 50, in __init__
    self._fetch_ticket(tkt_id, db)
  File "/usr/local/lib/python2.5/site-packages/Trac-0.11.7-py2.5.egg/trac/ticket/model.py", line 102, in _fetch_ticket
    'Invalid Ticket Number')
ResourceNotFound: Ticket 323456789101112131415 does not exist.

It appears to be merging the ticket numbers from the entire grid. It renders the plugin unusable, unfortunately.

I'm going to take a look at the CSS selection that the JS is doing and see if I can propose a patch. Is there anything I'm doing wrong or should be considering when evaluating the issue here?

Change History (0)

Note: See TracTickets for help on using tickets.