-
Bug
-
Resolution: Cannot Reproduce
-
Medium
-
8
-
Severity 2 - Major
-
0
-
NOTE: This bug report is for Confluence Cloud. Using Confluence Server? See the corresponding bug report.
Information
Linking to anchors in Confluence 3.5 used to work fine with Space PDF Export (clicking on the link will automatically navigate to the part of page in PDF). But in 4.0, clicking on the link with anchors (in PDF) launches the browser instead, which navigates to the part of page (but in the browser, and not PDF). Links to the page itself (without anchors) works fine though.
Steps to Reproduce
- Create 2 pages named "Page A" and "Page B"
- Page A has this content (if inserted in Wiki Markup):
h3.Subsection h3.Subsubsection
- Page B links to Page A's Subsection and Subsubsection anchors:
[Page A#Subsubsection] [Page A#Subsection]
- Generate PDF Export (Notice that the links in Page B links to Page A's anchors by launching the browser instead of directly moving to the section within PDF as it normally does in Confluence 3.5)
Workaround
Instead of linking to the page's anchor, link to the page itself. This is not exactly a workaround, but it fixes the links (so that at least the link leads to the page in the PDF).
- is related to
-
-
- Long Term Backlog
-
- relates to
-
-
- Closed
-
[CONFCLOUD-23324] Space PDF Export - links to page anchors does not work properly
Hi everyone,
This is Kateryna from the Confluence team. Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know by posting a comment and we will review.
Thank you again for providing valuable feedback to our team!
Best,
Kateryna
Hi fsim and everyone,
This is Kateryna from the Confluence team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the behavior within our instances. We would like to get to the root cause of what you’re experiencing. Could you provide some more details or a screenshot to help us narrow down this case?
We will keep this issue open for another 14 days, but if we don’t hear back by then we will need to close this out to focus on our upcoming roadmap for all Confluence users.
Best,
Kateryna
This is still a problem in Confluence Server 6.0.2. It would be great to have a resolution on this.
Mihkel Tammsalu
added a comment - Also looking forward to see this bug fix. 
Dimitrios M
added a comment - Yeah...for years! 
Xiaoxi Pang
added a comment - Agree with @James 
James Dunlop
added a comment - If this issue has been in the backlog for four years, please either mark it as "Will Not Be Resolved" or do something about it? Cross-referencing content in other sections of a generated PDF document seems like basic behaviour.
James Dunlop
added a comment - If this issue has been in the backlog for four years , please either mark it as "Will Not Be Resolved" or do something about it? Cross-referencing content in other sections of a generated PDF document seems like basic behaviour. Unfortunately, the link above doesn't seem to work anymore - page has been deleted.
My conclusion so far is that, even in the most recent version of Confluence, there is no way to create PDF links to anchors which are not on the same page. Am I missing something?
This is still affecting us. Is there a solution or work around we can implement. It's causing extra work to have to edit PDFs for anchor links to work.