> Working on my query augmentation > (http://trac.edgewall.org/ticket/10983), I've hit a brick wall. I > have a more complete example which starts to support augmenting the > query form. I get the plugin's fields in the "And" and "Or" drop downs > and they add items in the Filters frame but when I click Update, the > plugin fields have no effect and they disappear from the Filters > section. > > I've added code to process_request in trac/ticket/query.py but even at > the beginning of that function, my plugin fields are already missing. > I'm guessing there's magic in the query template or query.js but I > can't find it. Can someone point me at what gets executed when I click > Update?
OK. Everyone is back from Easter and I still need help. I read the Genshi introduction and tutorial and I sort of understand the weird py: syntax a little better but I still don't see where /query is discarding my custom fields. It would help if I could log things along the way to see what values are used or what happens in what order. What's the Genshi equivalent of "self.env.log.debug()"? -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
