forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Crossley (JIRA)" <>
Subject [jira] Updated: (FOR-95) indirect linking and anchors/fragment identifiers
Date Mon, 07 Dec 2009 22:12:18 GMT


David Crossley updated FOR-95:

    Affects Version/s: 0.9-dev

Following through on that linked discussion, Cameron did some investigation and wondered if
InputModules would be a better approach. We only use SimpleMappingMetaModule, but others are
available (or could be developed) at Cocoon.

The Forrest discussion stopped there. I have not followed through to see if the discussion
did continue at cocoon-dev.

At Forrest, going by my memory, there was no further development here.

The "site.xml" navigation file technique does solve the original question, so this issue could
get pushed to the next version.

> indirect linking and anchors/fragment identifiers
> -------------------------------------------------
>                 Key: FOR-95
>                 URL:
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Core operations
>    Affects Versions: 0.6, 0.7, 0.8, 0.9-dev
>            Reporter: Richard Cao
> I would be nice if Forrest supported anchors with indirect linking. That is, something
like this: <link href="site:somepage#someanchor">. (or something similar, like <link
href="site:somepage" anchor="someanchor">)
> If somepage pointed to somepage.html, then the resultant link would be somepage.html#someanchor.
> Using the above link currently fails with an "invalid xpath" error since "somepage#someanchor"
is not a valid qname.

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

View raw message