Excerpt-include macro and links with anchors

Question

I have release notes with a summary section and a details section. I use a link with an anchor to move from the summary to the details:

=========markup===========

h2. Highlights of This Release

{excerpt}

[Feature Label|Release Notes File Name#feature1anchor] --- Brief description of Feature 1.

[Feature2 Lable|Release Notes File Name#feature2anchor] --- Brief description of Feature 2.

{excerpt}

h2. Details

h3.{anchor:feature1}{color:#0c598a}Details of Feature 1{color}

A more detailed description...

h3.{anchor:feature2}{color:#0c598a}Details of Feature 2{color}

A more detailed description...

=====end markup==============

Then I use the excerpt-include macro to include the highlights (surrounded by excerpt tags) in a summary page for all of the releases (similar to Atlassian's Alldoc page). But the excerpts show the links as going to the summary (alldoc) page, rather than the original page. There is no error; the links look like they resolve, but they don't work.

Why is Confluence not using the explicit file name in the links in the original file?

Thanks,
Barbara

Agnese · Answer

This still remains a bug.

If you try to include a Table of Contents in an Excerpt, and then include that Excerpt in another page, none of the TOC links work.

Tom Baker2 · Answer

If you try to include a Table of Contents in an Excerpt, and then include that Excerpt in another page, none of the TOC links work.

This remains a bug.

Alain Moran · Answer

I suspect that this is related to a problem I have been experiencing while making changes to the comment move plugin. What appears to be happening is that the new XML storage format stores links to the current page in a different format to those to other pages (despite the method of entering the link being the same), here is an example of the storage format for my comment:

You will notice that the first link does not contain an tag ... I suspect that because there is no tag then the renderer 'assumes' the current page, I dare say that this may be what's ocurring with the excerpt-include macro.