PDF Export page breaks Gliffy and warning boxes

Comments

6 comments

  • Avatar
    Nils Bier

    Hi Rolf,

    Thanks for reaching out.
    Which version of Scroll PDF Exporter are you currently using? The mentioned issue should be fixed in Scroll PDF Exporter 4.x.

    To further investigate it would be great if you could send us your PDF template, information about which version of the app you're using, and a XML export of an affected page to support@k15t.com.
    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'll then have a closer look and will come back to with further details.

    Best,
    Nils

  • Avatar
    Rolf

    Hi Nils!

    Confluence is 6.2.2, Gliffy is 7.1.0 (offers upgrade to 8.05), Scroll PDF Export is 4.08 (offers upgrade to 4.0.17), Scroll Versions is 3.75 (offers upgrade to 3.8.3), Scroll Translations is 3.7.5 (offers upgrade to 3.8.3) 

    I will send the files today.

     

    Thanks a lot for your efforts!

     

    Rolf

  • Avatar
    Benoit Plet

    Any update here? I have just installed Scroll pdf exporter on our Cloud Confluence instance and show the same issue for Gliffy diagrams.

  • Avatar
    Nils Bier

    Hi Benoit,

    The described behavior is tracked in a separate issue here: https://k15t.jira.com/browse/EXP-2174

    We need to further investigate, if this can somehow be improved on our side, or if this is a current limitation of our library.
    We'll update the mentioned improvement as soon as we have any news to share.

    Please sign up at https://k15t.jira.com/secure/Signup!default.jspa to watch, comment on or vote for this issue. We'll then send a notification for every status update.

    For the time being you can insert a Scroll pagebreak macro before the affected Gliffy diagrams, to start the Gliffy diagram on a new page, so they do not break across pages.
    Would that be a workaround?

    Best,
    Nils

  • Avatar
    Benoit Plet

    For short exports, it is a valid workaround.

    For a 60 pages exports, this is a pain... especially when you have to use the same workaround for note, tips, warning, info and gliffy macros. For every problem, you need to add the page break, reexport and see where the next issue is, then cycle until your export is fine. Eventually, as soon as somebody adds a single line somewhere, then you have to redo the same crap. This is the kind of pain we are facing with the regular Confluence PDF export already and was hoping paying for your addon would reduce our pain. It solves some problems but create new ones... a bit disappointed. I hope you can address this quickly.

  • Avatar
    Nils Bier

    Hi Benoit,

    We'll try to come up with a more satisfying solution for this as soon as possible.

    Cheers,
    Nils

Please sign in to leave a comment.

Powered by Zendesk