BillKress Posted September 20, 2023 Share Posted September 20, 2023 PC: Windows 11/64 Application: Affinity Publisher 2.2.0 also with previous versions of Publisher. When PDF files (attached) is dragged into Publisher, I get the Error message: This file type is not supported. Same error when right click on PDF and Open With Publisher and with Publisher Open -> File -> pdf file Note that the attached PDF files can be opened by the newest Acrobat Reader for PC (2023.006.20320). It cannot be opened by older versions of Acrobat Pro (e.g., 9). Affinity Publisher can open older versions of PDF files. family_tree_magazine_nov-dec-2022.pdf family_tree_magazine_jul-aug-2023.pdf Quote Link to comment Share on other sites More sharing options...
MikeW Posted September 20, 2023 Share Posted September 20, 2023 The type of password security means it can only be opened in Acrobat/Reader version 10 or newer. This pdf also technically has fillable form fields--I took a quick look and didn't find any so this is just how InDesign created the pdf. Both those things make the pdf not gonna open or place in APub for different reasons. First is the interactive form issue. Once that has been removed they should place. But you'll need to remove the password to change the type of pdf from interactive to say a print pdf. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 20, 2023 Share Posted September 20, 2023 46 minutes ago, BillKress said: Affinity Publisher can open older versions of PDF files. Those PDFs have restricted editing capabilities, based on their security settings. Here's what Acrobat Reader shows for the July-August one, for example: Given those "Not Allowed" restrictions, I'm not surprised that Publisher can't make use of those files. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
MikeW Posted September 20, 2023 Share Posted September 20, 2023 I was wrong. Once the password is removed, the files will open/place in APub. APub will strip the ghost form fields. Quote Link to comment Share on other sites More sharing options...
David in Яuislip Posted September 20, 2023 Share Posted September 20, 2023 2 hours ago, walt.farrell said: Those PDFs have restricted editing capabilities, based on their security settings. It's not too difficult to modify these files so that they can be opened/placed in Publisher or opened in a browser with copying enabled but this stuff is copyrighted and that should be respected, so no hints from me Quote Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10 Link to comment Share on other sites More sharing options...
Dan C Posted September 21, 2023 Share Posted September 21, 2023 Thanks for your report @BillKress! I can confirm that there is a known issue logged with our development team regarding the error message shown when trying to open a PDF that has been password protected using Acrobat. I'll be 'bumping' this issue with our dev team now to bring it to their attention once again - I hope this helps MikeW 1 Quote Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted November 6, 2023 Staff Share Posted November 6, 2023 The issue "Unable to place/open password protected PDF created by Acrobat" (REF: AF-121) has been fixed by the developers in internal build "2.3.0.2106". 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.