Use of Include Page Plugin breaks Confluence links
Hi all,
we encountered two different behaviours how links get broken.
(1) A link to a heading, on the same page or another page in the same space which is included using "Include Page" plugin, is formatted as link in the exported document, but it is not clickable. When exporting only the page containing the link that points to a heading on the same page, the link is working well. (Of course Include Page is not used in this case)
(2) A link to another Confluence page (within the same space), which is included using "Include Page" plugin, is pointing to the first page after TOC in the exported document.
The links have been inserted using the "Insert link" function and work well in Confluence.
Scroll PDF Exporter release: 4.6.0
Is there anything I can do to the links work or is this a known problem? I found no issue matching my behaviour.
This is very urgent for us because it completely breaks the navigation in our customer documentation.
Thanks in advance for any answers!
Regards
Sören
-
Hi Sören,
Thanks for reaching out to us.
From what you describe, the issues seem linked to some known issues which also occur for the Include+ macro as well. You can track the open issues here:
- https://k15t.jira.com/browse/EXP-2641 – Links provided by Include+ macro are rendered incorrectly in the export
- https://k15t.jira.com/browse/EXP-2624 – Internal links provided by Include page/Include+ macro are rendered incorrectly
Both these issues are included in our next development sprint which would mean that the fix should be shipped with the Scroll PDF Exporter release at the end of the month.
In the meantime, please sign up to our JIRA (via https://k15t.jira.com/) in order to watch, comment and/or vote on this issue. We'll then send a notification for every status update.
I hope this information helps.
Cheers, Thomas (K15t)
-
Hi Sören,
Thanks for the post. Yes, unfortunately the issues were more complex than first thought and required some additional work to make sure the correct export behavior occurred with our integration with Scroll Versions. Both issues mentioned in the previous post are still being looked at in our current sprint and we will endeavor to get them resolved as soon as possible. Please keep an eye on the Fix Version field in the issues to keep up-to-date for the app release that includes the fix.
Thanks, Thomas (K15t)
-
Hi Thomas,
part of the problem seems to be fixed since release 4.6.4. However, there still remains some wrong behaviour (even in 4.6.6):
If you include page a and b into page c, where page a contains a link to page b, then the link in the exported pdf points to the confluence url - not to the pdf page.
Since your two named issues are closed meanwhile, I'd like to see a new one addressing this problem.
A solution for this problem is very appreciated.
Regards
Sören
-
Hi Sören,
Thanks for the update.
Are you able to send us an XML export for the page tree which highlights this problem still? If so, it would be great if you could send this to support@k15t.com and we can take a closer look in a support case.
To export the content of a single Confluence page, please follow these instructions: https://help.k15t.com/creating-a-xml-export-of-a-single-page-111903666.html.
We look forward to hearing from you.
Cheers, Thomas (K15t)
Please sign in to leave a comment.
Comments
6 comments