-
Bug
-
Resolution: Fixed
-
Medium
-
5.5, 5.7, 5.8, 5.9
-
11
-
Severity 3 - Minor
-
1
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
If your space is using the Page Properties Macro and you export the space to PDF, there is a macro error in place of all positions where the Page Property Macro exists.
Note: In the export progress screen, the error message will always name the last page in the export, even if doesn't use the macro.
Search Confluence using macroName: detailssummary* to identify the actual affected pages.
Wokarounds:
- export individual pages to PDF.
- Move pages with Page Properties Macro to a different Space to avoid receiving the error and then back to the same Project.
- relates to
-
-
- Closed
-
-
CONFSERVER-39207 Ignore or diagnose errors / failed attempts to export the whole space as PDF
- Closed
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CONFSERVER-33611] Space exports with Page Properties Report macro contain Error rendering macro 'detailssummary' where page properties should be
We have a similar use case to Meino's description.
We have spaces where we have collaboratively created user guides, which we need to export in PDF format for clients.
The suggested workarounds are time-consuming and impractical for non-technical users without specialist PDF editing software.
Additionally, we raised a support ticket for this and the Atlassian Support rep was able to confirm the issue remains in latest Confluence version (currently 5.9.10).
Meino von Spreckelsen
added a comment - We use the macro inside a space for a documentation of a software during development cycle to keep beta customers informed. The docu contains several 100 pages that are delivered as a preliminary handbook in pdf. The macro tries to summarize the individual chapters - what's new ... I hope you can imagine that the workaround is not possible under such circumstances and that we urgently need a fix of this problem.
Meino von Spreckelsen
added a comment - We use the macro inside a space for a documentation of a software during development cycle to keep beta customers informed. The docu contains several 100 pages that are delivered as a preliminary handbook in pdf. The macro tries to summarize the individual chapters - what's new ... I hope you can imagine that the workaround is not possible under such circumstances and that we urgently need a fix of this problem. About workarounds proposed:
- Export individual pages means exporting "page properties report" individually, merging the two documents then later, manually, right? That's only possible with addn. software (e.g. Acrobat Pro), as far as I'm aware of.
- Move affected pages to another space: How can that work if I need to export an entire page family (to PDF), while some pages are in another space? Am I missing something?
Bradley Bristow-Stagg
added a comment - "easy workaround" is only "easy" for admins and not basic users. Please fix.
Bradley Bristow-Stagg
added a comment - "easy workaround" is only "easy" for admins and not basic users. Please fix. Confirmed for Confluence 5.7.4.
Can someone from Atlassian please up the prio on this item? I agree with some of the other commenters that the "easy workaround" not valid is. If I tell our users to do that, they start looking at me funny. 
Ishan Liyanage
added a comment - Occurring in 5.7.4 too. 
Gerard Hovanessyan
added a comment - how is this a minor issue?
+1 - awful workaround!