> On Mon, Apr 1, 2013 at 11:51 AM, Christopher Nelson
> <chris.nelson.1...@gmail.com> wrote:
>>
>> > 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.
>
> When you say the fields are "missing" at the beginning of process_request,
> what variable are they missing from? Do you mean that they're actually
> absent from req.args?
Yes. But after cleaning this up to post, I find that it is in args
but has no effect. I'll try to track it down a bit more from this new
clue.
>> 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()"?
>
> I can't come up with any built-in way to do it, but you can add the Python
> logging object to the template context and then just call it from your
> templates. Here's a patch to trac/web/chrome.py that will insert
> "chrome.logging" into all template contexts, which you can then just use
> like ${chrome.logging.debug("foo")} in the templates:
> https://gist.github.com/ejucovy/5293261
Thanks. But now that I see it in `query.py`, I may not have to worry
about debugging templates.
> If you want to post the current patches and sample code you're working with
> somewhere, I'd be happy to try to look into it as well.
Thanks. I updated http://trac.edgewall.org/ticket/10983#comment:17
but let's see what the next hour brings.
--
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.
