Template format ignored when using "excerpt include" macro in page properties

Follow

Mike Desilets

January 10, 2019 16:22

Using Scroll Word Exporter.

I want to have a Confluence hierarchy like this:

Full Draft (uses child display to include full excerpts from all child pages)

  Section 1

  Section 2

  ...

  Section N

This will allow us to export the entire document (from Full Draft page) or individual sections (from Section x pages) when we have very long documents (multiple hundreds of pages).

Since page properties must be defined at the export page I have (N + 1) page property tables (one for Full Draft and one each for the individual Sections). 

I'd like to make some (if not all) of the page properties consistent throughout all pages without having to edit (N + 1) pages to, for example, increase a version number. 

However, when I use an "excerpt include" macro to grab a value from another page and add that to my page properties table in a Section page the formatting reverts to "Normal" with an added newline. This ruins things if the page properties are displayed in a header or footer since I use smaller font text with specific line spacing. 

Is there a way to fix this or to workaround the issue such that my page properties can be defined in my Draft page and inherited by my Section pages? 

0

• 

  Thomas Rough (K15t) January 14, 2019 16:15

  Hi Mike, 

  Thanks for reaching out to us. 

  Was I right in thinking that you had added the page property content as shown in my screenshot (below)? 

  

  Cheers, Thomas (K15t Software)

  0

  Comment actions Permalink
• 

  Mike Desilets January 14, 2019 23:50

  Yes, Thomas, that's effectively it. 

  0

  Comment actions Permalink
• 

  Thomas Rough (K15t) January 15, 2019 09:53

  Hi Mike, 

  Thanks for your reply and confirming the export behaviour.

  This issue is something that we are aware of and seems to have been introduced with the new version of Scroll Word Exporter 4. You can track the issue here: https://k15t.jira.com/browse/EXP-2615   

  Since our latest release, v4.0.4 fixed a medium security issue, I would avoid recommending the workaround of reverting to v3.x where this export behaviour does not occur. At the moment, our developers still need to refine this issue to ascertain the best fix for this bug and to calculate the time it'll take to implement. Once this information is available we will be able to plan it into one of our future sprints. 

  In the meantime, please sign up to our JIRA (via https://k15t.jira.com/secure/Dashboard.jspa) in order to watch, comment and/or vote on this issue. We'll then send a notification for every status update. 

  I hope this information helps. 

  Cheers, Thomas (K15t Software) 

  1

  Comment actions Permalink
• 

  Mike Desilets January 15, 2019 16:23

  Voted and followed - thanks for the update. 

  0

  Comment actions Permalink

Please sign in to leave a comment.