forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Crossley (JIRA)" <>
Subject [jira] Issue Comment Edited: (FOR-770) Locationmap logs should show which sitemap the request is coming from
Date Fri, 29 Feb 2008 06:12:51 GMT


crossley edited comment on FOR-770 at 2/28/08 10:12 PM:

Edited description which had a confusing typo (changed "" to ""). Ross,
please say if this was intentional.

      was (Author: crossley):
    Edited description which had a confusing typo. Set Fix-version to 0.9-dev
> Locationmap logs should show which sitemap the request is coming from
> ---------------------------------------------------------------------
>                 Key: FOR-770
>                 URL:
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Locationmap
>    Affects Versions: 0.8, 0.9-dev
>            Reporter: Ross Gardler
>             Fix For: 0.9-dev
> With the introduction of the locationmap it can be unclear which sitemap pipeline is
handling a request. Prior to the locationmap, exceptions would tell us where in the sitemap
we were working. However, this can sometimes get lost in the interaction with the locationmap.
> This makes it very difficult to debug some locationmap problems. For example, I recently
had a situation in which the locationmap was being queried for "". In this hint
the "project." part was being added by the sitemaps, but the error reported was not showing
where. I knew this meant some match was intercepting the request before my plugin sitemap
got hold of it, but the error messages would not tell me which. I had to trace the process
manually, which took an age. In the end it was a catchall match in the raw.xmap
> If the LM logs could report where the request is coming from, I would have known in seconds
what the problem was, rather than hours. We need a log entry something like:
> "Examining Locationmap for "" on behald of /raw.xmap (line XYZ)"

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message