forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: How to find the culprit in case of "BROKEN: No pipeline matched request" ?
Date Mon, 30 Jan 2006 13:41:46 GMT
Thomas Dudziak wrote:
> I have a somewhat large site that is generated via Forrest 0.7, and I
> get the dreaded "BROKEN: No pipeline matched request:" error. Now the
> interesting part is that the page noted in the error message is there,
> in fact three lines before the error message, Forrest did state that
> it successfully processed the file.

That sounds very strange. Please provide more details, such as:

- Forrest version
- execution mode
- request being made
- details of any customisations you have made (project sitemap, skin etc.)
- plugins in use

> Now I wonder, is there a way to get more info from Forrest, e.g. who
> and where did reference the page, etc. ? brokenlinks.xml does not
> really help, it basically states the same info as the commandline
> output.

The broken links file tells you which page had the reference which 
resulted in the break. The command line output just tells you that there 
was a break.

Other info is to be found in the logs which are located in 
build/webapp/WEB-INF/logs (when doing forrest run).

Find out which page contains the broken link.
Do Forrest run
point your browser at the page containing the broken link
click on the link
inspect the logs

(sometimes the browser will give more info as the error as well)


View raw message