Why is Scroll PDF Export exporting pages with exclude labels?

[Jonathan Stefanczyk]

I believe that I have followed all instructions to label child pages for exclusion when exporting using Scroll PDF.

It's structured / labelled like this:

> Parent Page (no label)

+> Child Page (label: "no-pdf-export")

Then in Scroll PDF I have set up a template, which explicitly has "no-pdf-export" entered in the "Exclude" field.

However, it should be noted that when I added it, it did not prompt me for existing labels as the rest of Confluence usually does. It instead treated it as if I were creating a new label. So the problem may lie here, or perhaps I'm misunderstanding how it's used.

When I go to export the page from Document Toolbox, it correctly offers me the template I've created. And if I look at More Details it clearly shows the "no-pdf-export" in the Exclude field.

However, when I actually run the export it does NOT exclude the child page from the PDF.

Any ideas as to what I may be doing wrong? Thanks in advance for any help.

[Tom Rough · Accepted solution]

Hi Jonathan,

Thanks for the post. As @Bill Bailey has suggested, could you submit a support ticket to us via emailing help@k15t.com. Specifically, it would be good if you could share the content of the space that you are exporting via an XML export. To export the content of your Confluence pages, please follow these instructions.

Additionally, can you confirm the steps you have taken? From your post it seems you are exporting a Scroll Document - was this correct? If so, could you confirm if you are using/exporting a specific variant of the document (via Variants for Scroll Documents).

Furthermore, it seems you are exporting from the Document Toolbox but does the same issue also occur when exporting the page tree from the Confluence page view? It would be great if you could also send us your export template that you've configured with the label - this is downloadable as a *.data file from the template list. 

Please note, in regards to the label behaviour (ie. it did not prompt you for existing labels when entering in the template label field), this is a known issue. This behaviour is currently blocked due to not being able retrieve the required label information from Confluence Cloud. Atlassian have a known related issue for this, however, they currently don't plan to fix this. We have our own open tracking issue which you can track here.

Once we have received your support ticket we can respond accordingly.

Cheers, Thomas (K15t)

[Jonathan Stefanczyk]

Thanks Thomas. I have submitted a ticket.

[Bill Bailey]

Hello @Jonathan Stefanczyk , just as a sanity check, when you were typing in the Exclude box in the template, did it find your label? And do you only have one label in the field?

And ensure that page you want to exclude does have that label?

But otherwise, it seems you are doing it correctly.

[Jonathan Stefanczyk]

Hi Bill

Thanks for the reply.

Yes, as above, it should be noted that when I added it, it did not prompt me for existing labels as the rest of Confluence usually does. It instead treated it as if I were creating a new label. 

I should add that the label is available if I go to label a new page. I start typing no-p ... and it shows up no-pdf-export in the predictive text.

This is not the case in the document template. I type the whole thing and never get prompted along the way. It says "Create New Label" as if it never existed.

And only one label in the field, yes.

Jonathan

[Bill Bailey]

I always believe in trying stupid stuff first, While label syntax does allow for hyphens, they just using a label with no punctuation to see if it still errors the same way. For example, I just use the label "exclude" in our instance for this purpose.

[Jonathan Stefanczyk]

Thank you Bill. It was a good suggestion, but unfortunately the result is exactly the same behaviour.

[Bill Bailey]

Well time to file a support case with K15t.