Forrest
  1. Forrest
  2. FOR-95

indirect linking and anchors/fragment identifiers

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.6, 0.7, 0.8, 0.9
    • Fix Version/s: None
    • Component/s: Core operations
    • Labels:
      None

      Description

      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.

        Activity

        Richard Cao created issue -
        David Crossley made changes -
        Field Original Value New Value
        issue.field.fixfor 0.7
        Dave Brondsema made changes -
        Fix Version/s 0.7 [ 10031 ]
        Fix Version/s 0.8 [ 10040 ]
        Hide
        David Crossley added a comment -
        The Cocoon LinkRewriter Transformer block needs enhancement.
        http://forrest.apache.org/0.7/docs/sitemap-ref.html#linkrewriting_impl

        The workaround is to add an entry like this to site.xml to explicitly declare the fragments ...

        <upgrading_07 label="Upgrading to 0.7" href="upgrading_07.html">
          <raw href="#raw"/>
        </upgrading_07>

        and then refer to those as site:upgrading_07 and site:upgrading_07/raw
        Show
        David Crossley added a comment - The Cocoon LinkRewriter Transformer block needs enhancement. http://forrest.apache.org/0.7/docs/sitemap-ref.html#linkrewriting_impl The workaround is to add an entry like this to site.xml to explicitly declare the fragments ... <upgrading_07 label="Upgrading to 0.7" href="upgrading_07.html">   <raw href="#raw"/> </upgrading_07> and then refer to those as site:upgrading_07 and site:upgrading_07/raw
        Ross Gardler made changes -
        Fix Version/s 0.8-dev [ 12310040 ]
        Environment
        Description 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.
        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.
        Priority Major [ 3 ] Minor [ 4 ]
        Hide
        David Crossley added a comment -
        See discussion about a more complete solution and a Cocoon patch contributed by Cameron McCormack via the Forrest user@ mail list.
        Re: site: URIs with fragment identifiers
        http://article.gmane.org/gmane.text.xml.forrest.user/3557
        Show
        David Crossley added a comment - See discussion about a more complete solution and a Cocoon patch contributed by Cameron McCormack via the Forrest user@ mail list. Re: site: URIs with fragment identifiers http://article.gmane.org/gmane.text.xml.forrest.user/3557
        David Crossley made changes -
        Priority Minor [ 4 ] Major [ 3 ]
        Affects Version/s 0.8-dev [ 12310040 ]
        Summary indirect linking and anchors indirect linking and anchors/fragment identifiers
        Affects Version/s 0.7 [ 12310031 ]
        Hide
        Brian M Dube added a comment -
        Is this fully supported and resolved now?
        Show
        Brian M Dube added a comment - Is this fully supported and resolved now?
        Hide
        David Crossley added a comment -
        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.
        Show
        David Crossley added a comment - 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.
        David Crossley made changes -
        Affects Version/s 0.9-dev [ 12310041 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Richard Cao
          • Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development