forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [issues] New comment: (FOR-156) broken links building forrest site
Date Thu, 01 Jan 1970 00:00:00 GMT
The following comment has been added to this issue:

     Author: Nicola Ken Barozzi
    Created: Wed, 9 Jun 2004 9:01 AM
<jefft>In normal use, why would Cocoon's CLI ever encounter untranslated site: and ext:
URLs </jefft> 

Good question. 

Now it does, as *all* links that pass in any cocoon pipeline are traversed now.
For example, in a single pipeline I get the links from the css in chaperon and then serialize
to text; well, these links are traversed. 

<jefft> except if the author mistyped a link, or forgot to add a site.xml entry? In
that case, it is an error, and the CLI should report it as such instead of quietly ignoring
what is a broken link. </jefft>

The link would still be reported as broken IIUC, as this would come out in the translation
or when they are outputted already resolved.

Basically, assing an exclude we are doing exactly what the CLI does before, as it does not
traverse them. What makes this exclusion different from the previous implicit exclusion?
View the issue:

Here is an overview of the issue:
        Key: FOR-156
    Summary: broken links building forrest site
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Forrest
  Component: shbat distribution - Forrest CLI
    Fix For: 0.6

   Assignee: Nicola Ken Barozzi
   Reporter: Dave Brondsema

    Created: Tue, 1 Jun 2004 4:41 AM
    Updated: Tue, 8 Jun 2004 2:40 PM

I removed the forrest site's cli.xconf since it's only significant differences from the default
cli.xconf were ignoring ext:** and site:** which we didn't want anyway.

Now there are many broken links reported when building the site.  However, it seems that there
are no broken links on the generated pages.

So there's a bug in the CLI I think.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message