[JIRA] Commented: (FOR-284) 'error:' prepending problems

[is...@cocoondev.org]

The following comment has been added to this issue:

     Author: Rick Tessner
    Created: Fri, 17 Sep 2004 7:07 PM
       Body:
It looks like the problem arises only when there is a link reference to the ".xml" file that contains the "site:" or "ext:" references.

For example, if we have a document called "sample.xml" and there is a link in that document of the form <a href="sample.xml">, the "forrest site" will fail with the broken link message.

This is exactly what we have in the samples/sample.xml.  There is in the "Presentations" section: <a href="samples.xml">.

Removing that link will result in a "forrest site" completing cleanly.  However, that's not the solution.

I'm guessing that the problem resides in the "linkrewriter" transform somewhere.
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-284?page=comments#action_11559

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-284

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-284
    Summary: 'error:' prepending problems
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             shbat distribution - Forrest CLI
   Fix Fors:
             0.7
   Versions:
             HEAD

   Assignee: 
   Reporter: Nicola Ken Barozzi

    Created: Wed, 8 Sep 2004 1:48 AM
    Updated: Fri, 17 Sep 2004 7:07 PM

Description:
'error:' prepending, for site: and ext: links that were not found, causes problems.

For example, if in xdocs/samples I have ext:dtd-docs, Cocoon will search for samples/ext:dtd-docs, which of course does not exist.

@see declare-broken-site-links.xsl in teh core templates for more info.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira