Shazz Posted December 30, 2024 Posted December 30, 2024 I've done a search of the forums, but not seeing any similar problems to this. I imported a PDF into Designer, and was working on it when Designer crashed. Upon relaunching, and trying to open the file, I get the dialog box asking if I want to open the recovery file, which I clicked yes, but whenever it's a PDF, it just imports the original saved file, and the recovery data seems to disappear into thin air. I've noticed this on several different PDF files. Other file types recover as expected. Is this a bug or expected behaviour? I'm new to Affinity (still in trial period), so still learning the differences from other software. And yes, lesson learnt - immediately save an imported file as a new file to avoid this in the future. đ€Šââïž System info: Designer 2.5.3 MacOS Monterey  Quote
Komatös Posted December 30, 2024 Posted December 30, 2024 Hello @Shazz and welcome to the forums. Affinity Publisher is not a PDF editor! It is advisable to save the document in Publisher file format for further editing. The modified document can then be exported again as a PDF file. Quote MAC mini M4 | MacOS Sequoia 15.3.2 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.3194) Affinity Suite V 2.6.1 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF I already had a halo, but it didn't suit me!
Shazz Posted December 30, 2024 Author Posted December 30, 2024 1 hour ago, Komatös said: Hello @Shazz and welcome to the forums. Affinity Publisher is not a PDF editor! It is advisable to save the document in Publisher file format for further editing. The modified document can then be exported again as a PDF file. I wasn't using Publisher. I opened a vector illustration PDF in Designer (because - and this is a separate issue - I opened the original EPS file in Designer but it rendered an empty document. So I had to convert the EPS to something that AD would read and PDF happened to work). I don't want to save as PDF either. I was just working in the opened file and had not yet saved as .afdesign Komatös 1 Quote
Komatös Posted December 30, 2024 Posted December 30, 2024 15 minutes ago, Shazz said: I wasn't using Publisher. No matter which programme you work with, saving after the import is my first recommendation. Quote MAC mini M4 | MacOS Sequoia 15.3.2 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.3194) Affinity Suite V 2.6.1 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF I already had a halo, but it didn't suit me!
Shazz Posted December 30, 2024 Author Posted December 30, 2024 1 hour ago, Komatös said: No matter which programme you work with, saving after the import is my first recommendation. Yeah, I already said that I've learnt that lesson. Still interested to know if this is a bug for anyone else or if it's a known issue or expected behaviour. Quote
Komatös Posted December 30, 2024 Posted December 30, 2024 9 minutes ago, Shazz said: if this is a bug for anyone else or if it's a known issue Whether this is a bug cannot be clarified. You would have to open the same file on another computer and carry out the same editing steps. If the crash is reproducible, it is safe to say that it is a programme error (bug).  Quote MAC mini M4 | MacOS Sequoia 15.3.2 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.3194) Affinity Suite V 2.6.1 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF I already had a halo, but it didn't suit me!
Shazz Posted December 30, 2024 Author Posted December 30, 2024 8 hours ago, Komatös said: Whether this is a bug cannot be clarified. You would have to open the same file on another computer and carry out the same editing steps. If the crash is reproducible, it is safe to say that it is a programme error (bug).  It can, actually. If it's a bug, then other people with other PDF files would be experiencing the same thing. My original post even mentions that I've experienced it with several PDFs. I'd appreciate it if you'd let others weigh in now, and wait to respond until they have. R C-R 1 Quote
Shazz Posted December 30, 2024 Author Posted December 30, 2024 8 hours ago, Komatös said: If the crash is reproducible, it is safe to say that it is a programme error (bug).  You're also completely missing my point. I'm not asking about the crash. I'm asking about the recovery file process, and the fact that recovery data disappears because AD wants to reimport the original file. (Please don't reply. You really don't understand my issue). R C-R 1 Quote
Staff NathanC Posted January 18 Staff Posted January 18 Hi @Shazz, Can confirm I've replicated this issue, the 'Open Recovery File' message will prompt, but the contents of the recovery file are not read and the PDF is just re-imported as a fresh document again. I've logged this with the developers. Quote
Shazz Posted January 18 Author Posted January 18 Thanks @NathanC, that's good news that you could replicate. At least I know it's not user error now đ Quote
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.