-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
We should have the ability to export child pages using PDF export - rather than having to use 'export space'.
Because we have large spaces, and because Confluence does not handle space export well without it seriously degrading site performance, we have disabled 'space export' for the majority of users. We still allow PDF exports, however. The annoying thing is that you cannot export page with its children using this method.
- is duplicated by
-
- Closed
- is related to
-
- Gathering Interest
- relates to
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-22012] PDF Export should include option for child pages without having to use export space
We put a PDF Icon on each of our End User training wiki pages to allow the user to export a page as PDF.
Link: https://wiki.***.edu.au/spaces/flyingpdf/pdfpageexport.action?pageId=XXXXX
As a lot of pages have child pages of related content, the ability for a user to click on a link and export their own PDF of the content would be very valuable.
Any chance of having this feature added?
Thanks in advance,
Michael Foster.
Hi,
Our add-on Content exporter allows you to export trees of pages to Word or PDF.
It is a 2 in 1 product in this sense.
It gives you the option to select the complete tree, or select pages individually or filter them by label. You can add cover page to the export too.
Furthermore, it supports both Confluence Cloud and Confluence Server.
Tibor
Technical Management
added a comment - me too....... we're still waiting for this feature and keen for it to be implemented
Nadine Payne
added a comment - +1 - why has this (and the linked issue raised to do the same with Word exports) taken so long to action? These issues have literally been languishing for YEARS now!
Nadine Payne
added a comment - +1 - why has this (and the linked issue raised to do the same with Word exports) taken so long to action? These issues have literally been languishing for YEARS now! 
roy simkes
added a comment - +1 
The issue is quite old but we analyzed the pdf export on our instances and found an improvement, that will lead to a more stable functionality.
When a custom export from a small subtree is made on a large space (>20.000 pages), a full export is started instead of exporting the selected subtree. This wrong export cannot be cancelled and blocks system resources.
I analyzed the problem and found in the confluence-flying-pdf plugin, that for each page in the content tree of the space a value is added to the either "contentToBeExcluded" or "contentToBeExported" form parameter but only the "contentToBeExported" parameter is used to filter the content tree for the export. Removing the "contentToBeExcluded" form parameter should lead to a more stable function by avoiding exceed of the request size. We tried this already manually and it works.