-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
It would be nice if the custom PDF stylesheet can be set at the global level, just like the custom layouts. This will ensure that every space export will fall back to this global template, if there is none defined in the individual space.
This would certainly be useful for a company-wide template, where enforcing this template for each individual space is very tedious.
- relates to
-
- Closed
- mentioned in
-
Page Failed to load
[CONFSERVER-16210] Global custom PDF stylesheet
@Ellis Pratt: I was thinking the same thing. We really should upgrade to 4.x now.
Ellis Pratt
added a comment - Hooray! 
Lise Kemen
added a comment - It could be really helpful, and make export customization really simple for administrators.
It will be consistent with the global Themes and Stylesheets working as well.
The ideal point will be that the HTML export have the same behavior.
Best Regards
Lise Kemen
added a comment - It could be really helpful, and make export customization really simple for administrators.
It will be consistent with the global Themes and Stylesheets working as well.
The ideal point will be that the HTML export have the same behavior.
Best Regards I'd also like to see this issue resolved. We use a customized PDF stylesheet and every small change in this stylesheet needs to be applied to every space. This is very admin-unfriendly.
Ideally, this stylesheet could be set globally and if a space needs a different stylesheet, the global default can be overridden at space level.
Heliodor Macko
added a comment - It would also help to have possibility of a list of standalone PDF layout definitions, that user could choose to format any particular space export.
Heliodor Macko
added a comment - It would also help to have possibility of a list of standalone PDF layout definitions, that user could choose to format any particular space export. 
Andy Brook (Javahollic Software)
added a comment - I just setup a 3.x test environment to migrate settings, and found that the feature I was making use of to set global page PDF export header/footers was missing. Apparently this is due to the improved flyingpdf implementation that allows space exports to PDF and space admins to set their own stylesheets, fabulous for those clamouring for such stuff, for my org, I just need what we have in 2.10, and now don't have in 3.x
This is a feature regression, it isn't a feature request. The ability was present in 2.10, in 3.x its not. The work involved to go through every space and set up a default, then do it for every new space is just silly.
The lack of this ability may actually stop me upgrading, argh!
Andy Brook (Javahollic Software)
added a comment - I just setup a 3.x test environment to migrate settings, and found that the feature I was making use of to set global page PDF export header/footers was missing. Apparently this is due to the improved flyingpdf implementation that allows space exports to PDF and space admins to set their own stylesheets, fabulous for those clamouring for such stuff, for my org, I just need what we have in 2.10, and now don't have in 3.x
This is a feature regression, it isn't a feature request. The ability was present in 2.10, in 3.x its not. The work involved to go through every space and set up a default, then do it for every new space is just silly.
The lack of this ability may actually stop me upgrading, argh!
Teemu Qvick
added a comment - This is a must for us: it is not feasible to advise users to create corporate designs per space.
Teemu Qvick
added a comment - This is a must for us: it is not feasible to advise users to create corporate designs per space. 
Kevin Williams [Atlassian]
added a comment - Question from a customer who would like this feature:
So my question is: Where can I set the default value (standard corporate design), if there is no custom layout?
The editpdfconfig.vm gets the default value somehow from the com.atlassian.confluence.extra.flyingpdf.config.ConfigurePdfExportAction
<h4>PDF Export Header</h4>
#tag("Textarea" "theme='notable'" "template='widetextarea.vm'" "label='decorator'" "name='header'" "id='style'" "rows=30" "cols=80")
I say somehow, because as far as I have seen the source of the confluence flying pdf is not published.
I assume that the ConfigurePdfExportAction.java tries to get the custom layout from bandana. If there are no entries the text area will shown empty. Which means I can't set a default value without modifying the java source code.
Kevin Williams [Atlassian]
added a comment - Question from a customer who would like this feature:
So my question is: Where can I set the default value (standard corporate design), if there is no custom layout?
The editpdfconfig.vm gets the default value somehow from the com.atlassian.confluence.extra.flyingpdf.config.ConfigurePdfExportAction
<h4>PDF Export Header</h4>
#tag("Textarea" "theme='notable'" "template='widetextarea.vm'" "label='decorator'" "name='header'" "id='style'" "rows=30" "cols=80")
I say somehow, because as far as I have seen the source of the confluence flying pdf is not published.
I assume that the ConfigurePdfExportAction.java tries to get the custom layout from bandana. If there are no entries the text area will shown empty. Which means I can't set a default value without modifying the java source code.
Yippieh!