Publisher crashes when printing pages outside "Include On Export" range.

[Jan Bartnik]

When trying to print a document with multiple sections and at least one section is not marked as "Include On Export" choosing wrong page range ("Pages:") cause a crash when printing.

Example (steps to reproduce):

1. create new document
2. add pages to get 8 total
3. in section manager create second section for pages 5-8
4. uncheck in first section "Include On Export"
5. File -> Print
6. set print range as 1-4 (as the preview shows you only have 4 pages, so 1-4 seems intuitive choice; sidenote... or sidebug: the range appears invisible)
7. press "Print"

Tested on Windows 11 and latest version of AP.

Expected behaviour: message box informing about wrong range input.

[NathanC]

Hi @Jan Bartnik welcome to the forums,

Many thanks for providing detailed steps and screenshots, i've now replicated this issue and logged it with the developers.

 

[Jan Bartnik]

Thank you @NathanC.

Just wanted to extend that bug with:

• If all sections are not "Include On Export" (so for example you have only one section and the option is not checked) going to "File -> Print" (or Ctrl+P) cause an immediate crash (no print window appears).

Steps to reproduce:

• create new empty document
• go to "Section Manager"
• uncheck "Include On Export"
• go to "File -> Print"

Expected behaviour:

• message box explaining no sections are marked as "Include On Export" or/and
• grayed out Print option (might be confusing as the user will not know the reason behind graying)

Edited March 2, 2023 by Jan Bartnik
added handle

[Affinity Info Bot]

The issue "App crash when printing file with pages outside the specified 'Include on Export' range in Section Manager" (REF: AFB-7433) has been fixed by the developers in internal build "2.1.0.1781".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.