Tart Posted July 24, 2023 Share Posted July 24, 2023 Hello! I use Publisher to combine multiple PDFs, but it sometimes does not work. I get a notification I should specify a valid target. I have clicked all possible options and non of them works. PDfs have different sizes, but I believe this should not affect, or? Anyone has similar issue and could guide me to a solution? Quote Link to comment Share on other sites More sharing options...
Dan C Posted July 24, 2023 Share Posted July 24, 2023 Hi @Tart, Sorry to hear you're having trouble and thanks for your screenshot provided! I can see that there is currently no Page Number entered in the 'Pages' dialog box - although you have set the document to be added 'After Last Page', this dialog still requires the dialog box to have a valid value, in order to add the page from file. Please change the 'Add Pages' option to any other option in the list, then type any value in the 'Pages' box (such as 1), then change back to 'After Last Page' and you should find the document is added to the file as expected. Of course, this value should not be required for this specific 'Add Pages' option, therefore I will be logging this as a bug with our development team now. I hope this helps Quote Link to comment Share on other sites More sharing options...
thomaso Posted July 24, 2023 Share Posted July 24, 2023 16 minutes ago, Dan C said: I can see that there is currently no Page Number entered in the 'Pages' dialog box FWIW, on mac (V1) a page number is automatically set when this dialog window opens, even in a file with only 1 page. To trigger this error message I need to manually delete the page numbers + press the OK button, whereas pressing Tab or Enter key after deleting the field gets re-filled with the previous / auto-set number(s) again. Dan C 1 Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
Dan C Posted July 24, 2023 Share Posted July 24, 2023 Thanks for letting me know thomaso - I also noticed this difference, as well as a few other oddities with the dialog (such as entering '0' for the Page, causing a crash on Windows!) and I'm getting these all logged with our team now Quote Link to comment Share on other sites More sharing options...
R C-R Posted July 24, 2023 Share Posted July 24, 2023 5 hours ago, thomaso said: To trigger this error message I need to manually delete the page numbers + press the OK button, whereas pressing Tab or Enter key after deleting the field gets re-filled with the previous / auto-set number(s) again. FWIW, in APub V2 on my Mac it works the same way, which is as I think it should since deleting the page number(s) does mean no valid page range is specified. Also, no crash when (for instance) entering 0, which also means no valid page range has been specified & thus correctly triggers the error. Thus, it appears this is a Windows only issue? Dan C 1 Quote All 3 1.10.8, & all 3 V2.5.6 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
Dan C Posted July 24, 2023 Share Posted July 24, 2023 5 hours ago, Dan C said: such as entering '0' for the Page, causing a crash on Windows already noted above, thanks R C-R Quote Link to comment Share on other sites More sharing options...
R C-R Posted July 24, 2023 Share Posted July 24, 2023 2 minutes ago, Dan C said: already noted above, thanks R C-R Yes, that's why I said it appears to be an Windows only problem.... Quote All 3 1.10.8, & all 3 V2.5.6 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted October 19, 2023 Staff Share Posted October 19, 2023 The issue "[Win] Add Pages from File dialog allows for invalid values, causing crashing or failure to add document" (REF: AF-330) has been fixed by the developers in internal build "2.3.0.2083". 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. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.