Guitarzan Posted December 15, 2024 Posted December 15, 2024 (edited) Hello, I’m currently working on my first book, and so far, Publisher has been a dream to work with. However, since the most recent update (2.5.7), I’ve encountered an issue: whenever I save a new version with my changes and attempt to reopen it, I receive the attached error message. I have the file backed up as a PDF, but starting from scratch is not an option at this stage. I would greatly appreciate any assistance you could provide to help resolve this issue. Thank you in advance for your time and support. Best regards, Bryan Edited December 15, 2024 by Guitarzan Quote
MikeTO Posted December 15, 2024 Posted December 15, 2024 Hi @Guitarzan and welcome to the forums. Your screenshot failed to upload so you should try that again. I don't know what error you're receiving, but two common workarounds are: If there are linked resources, make them unavailable to Publisher before opening the file by renaming the folder containing them, or the resources themselves. Doing this might allow the document to open. You can try creating a new document and then choosing Document > Add Pages from File to add the corrupted document's pages to the new document. Good luck Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.3, MacBook Pro (M4 Pro) and iPad Air (M2)
Guitarzan Posted December 15, 2024 Author Posted December 15, 2024 I just tried to open a previous version from 12/8, and get an entirely different message. Quote
Guitarzan Posted December 15, 2024 Author Posted December 15, 2024 8 minutes ago, MikeTO said: Hi @Guitarzan and welcome to the forums. Your screenshot failed to upload so you should try that again. I don't know what error you're receiving, but two common workarounds are: If there are linked resources, make them unavailable to Publisher before opening the file by renaming the folder containing them, or the resources themselves. Doing this might allow the document to open. You can try creating a new document and then choosing Document > Add Pages from File to add the corrupted document's pages to the new document. Good luck Thanks Mike, I saw these suggestions on another thread and tried both of these options with no luck. Quote
MikeTO Posted December 15, 2024 Posted December 15, 2024 Were you able to save the file under a new name as suggested in the prompt? There are known issues saving to pcloud from Affinity. Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.3, MacBook Pro (M4 Pro) and iPad Air (M2)
Guitarzan Posted December 15, 2024 Author Posted December 15, 2024 29 minutes ago, MikeTO said: Were you able to save the file under a new name as suggested in the prompt? There are known issues saving to pcloud from Affinity. Yes, but that turned out to be the "failed to open" message I originally posted. I've been using pCloud for over a year without any issues with my applications. The problem only started occurring after I updated Publisher. Fortunately, I was able to import the latest PDF into Publisher and make my changes. However, if I hadn’t exported the PDF beforehand, I would have had to start from scratch. May I ask where the thread or post is relating to pCloud? Quote
MikeTO Posted December 15, 2024 Posted December 15, 2024 14 minutes ago, Guitarzan said: Yes, but that turned out to be the "failed to open" message I originally posted. I've been using pCloud for over a year without any issues with my applications. The problem only started occurring after I updated Publisher. Fortunately, I was able to import the latest PDF into Publisher and make my changes. However, if I hadn’t exported the PDF beforehand, I would have had to start from scratch. May I ask where the thread or post is relating to pCloud? There are lots of threads here that mention pCloud but it's not just pCloud - Serif recommends not saving to or opening from a cloud drive. It's the same with iCloud. Notwithstanding the advice not to use a cloud drive, a lot of us including me use them anyway. But we've learned to back up our work frequently in case of a corrupted file like this. I back up my work at the end of each day, and just before and after making large changes. Here are some general questions from Serif when you get an error like this: Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.3, MacBook Pro (M4 Pro) and iPad Air (M2)
Guitarzan Posted December 15, 2024 Author Posted December 15, 2024 1 minute ago, MikeTO said: There are lots of threads here that mention pCloud but it's not just pCloud - Serif recommends not saving to or opening from a cloud drive. It's the same with iCloud. Notwithstanding the advice not to use a cloud drive, a lot of us including me use them anyway. But we've learned to back up our work frequently in case of a corrupted file like this. I back up my work at the end of each day, and just before and after making large changes. Here are some general questions from Serif when you get an error like this: Thanks for the good advice, Mike. It's most appreciated! Quote
Komatös Posted December 15, 2024 Posted December 15, 2024 The problem with saving to cloud services is that the files to be saved may not be completely written to the cloud before the programs are closed. Other sources of error can be the settings in the cloud client software. R C-R and Guitarzan 2 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!
Guitarzan Posted December 16, 2024 Author Posted December 16, 2024 22 hours ago, Komatös said: The problem with saving to cloud services is that the files to be saved may not be completely written to the cloud before the programs are closed. Other sources of error can be the settings in the cloud client software. I never thought about that! Thanks so much for the post. 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.