Workaround/plugin for applying pdf custimizations to single page export?

Wim Deblauwe

Hi,

Is there anybody who has come up with a hack/plugin to make the single page export redirect to the flyingpdf thing until Atlassian fixes CONF-17853 ?

It seems that if you create a PDF via the advanced section, a HTTP POST is done with the id of the page against this URL:

http://confluence.mycomp.com/spaces/flyingpdf/doflyingpdf.action?key=SPACEKEY

with this form data:

1. atl_token:
   G3vRXONLa2
2. contentToBeExported:
   31031379
3. synchronous:
   false
4. confirm:
   Export

Where 31031379 is the id of the page.

Given this information, it seems very likely that somebody who created a Confluence plugin before can hack together something to fix this

regards,

Wim

PS: I am aware of the Atlassian proposed workaround to define the styles 2 times in different ways, but for me, I cannot get them to match exactly, so I would like to have this as workaround.

Alejandro Conde Carrillo

Single page exports still use the PDF stylesheets. You could apply your customizations using CSS instead than the HTML layouts as explained in Adding Headers and Footers to Single Page Exports.