forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: todo.xml restriction
Date Thu, 10 Apr 2003 10:17:48 GMT
On Thu, Apr 10, 2003 at 10:46:53AM +0200, Johan Andries wrote:
> Hi,
> I'm trying to use several todo.xml files in our content xdocs using the
> current cvs build of Forrest (d'loaded yesterday). When previously
> built using Forrest-0.4 this wasn't a problem at all and every todo.xml
> was correctly converted to a todo.html. However with the current build
> I keep getting the error below for each todo.xml file I've created:
> "No pipeline matched request: subdir/todo.xml"

That is because the raw *.xml pipelines aren't exposed by default:

    <!-- ============================================================ -->
    <!-- SOURCE FORMATS                                               -->
    <!--                 Raw XML sources, typically doc-v11 format    -->
    <!-- ============================================================ -->
    <map:pipeline internal-only="true">

Change that to 'false' to see *.xml sources.  Or just update CVS: I've
changed the default to false.

Anyway, CVS Forrest's default stylesheet claimed all todo.xml files for
generation from status.xml.  I've just changed this so that apart from
the root directory todo.html and changes.html, all other todo/changes
files (with the appropriate DOCTYPE declaration) will be treated

      <action dev="JT" type="fix" context="core">
        Add automatic (doctype-triggered) handling of todo and changes XML
        files, regardless of file name or location in the directory tree.  The
        root changes.html and todo.html files are still generated from

Does this solve the problem?


> I know that normally a todo.html file is automatically generated from
> the status.xml file. Has the current Forrest build added a restriction,
> defining that it is no longer "allowed" to have one's own todo.xml in
> one of the subdirectories of xdocs? If I rename the todo.xml files to
> "todo1.xml" or something like that the problem's gone.
> regards,
> Johan

View raw message