Antonia- I am trying to understand this Ticket field myself. The place I am looking at to fully understand how this is structured is listed below. The structure is based on code written here http://trac.edgewall.org/browser/branches/1.0-stable/trac/ticket/model.py?rev=11830
Look at line 120. I am not sure if this will answer your question, but it a place to look. Pranay B. "He is richest who is content with the least, for content is the wealth of nature."- Socrates On 25 June 2013 14:31, Antonia Horincar <[email protected]> wrote: > Hi, > > I made a basic template for displaying ticket information when > accessing a certain path, but I am having trouble with processing the > ticket. It gives me an error "Ticket <id> does not exist" even though > there is a ticket with the id that I entered. What I did in my api, > after matching the request, in the process_request method was > something like this: > data = {'ticket': model.Ticket(self.env, ticket_id)}, where ticket_id > is the id of the req argument. > > I have checked if the matching does indeed find the correct id, and it > does. I have looked through the other Bloodhound APIs but I found no > clue that could help me determine the cause of my error. If anyone > encountered this error before and knows what might be causing it, can > you please help me? I might be missing something or I might have > misunderstood some concepts. > > Thanks, > Antonia >
