Guy Beckett Posted September 6 Share Posted September 6 A colleague and I have been sharing a publisher file on Google drive for six months - last opened successfully yesterday afternoon. However now it won't open - says "appears to be corrupted but we have managed to recover an older version". The recovery file has the right document size but is blank. I have downloaded earlier versions of the file from Google but they all open with the same error message. Also tried opening files on my ipad, but again get "appears to be corrupted" - oddly the preview is fine - both in the finder on mac and Affinity's ipad document window. This file is an event floorplan that has months of work in it so I really would appreciate ideas about how to recover it. Quote Link to comment Share on other sites More sharing options...
Hangman Posted September 6 Share Posted September 6 Hi @Guy Beckett, It does sound as though your file/s are corrupted and may not be recoverable but can you upload the latest version and a couple of the previous backup files so we can take a look to see if they can be recovered... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
Guy Beckett Posted September 9 Author Share Posted September 9 Thanks for looking into this. Attached is the latest file plus some numbered backups. If they can't be opened I can reconstruct the file from a pdf - but it would be great if we could get the publisher file open. Going forward do you have any workflow suggestions for how to collaborate on affinity files - any preferences - google drive / apple or dropbox? We try not to open at the same time, would that be what corrupted it? Also why have older files also become corrupted? Are they actually different? I suspect that google's file version system is not robust... ISS Master Floor Plan 2024 Guy.afpub 04.afpub 04b.afpub 05.afpub Quote Link to comment Share on other sites More sharing options...
Hangman Posted September 9 Share Posted September 9 Hi @Guy Beckett, Many thanks for the files... Unfortunately, as you've already seen, they all just open a blank canvas with a single empty Layer and indicate they are corrupted files... Were these originally PDF files opened in Publisher? What is slightly odd is that they open as 426 pt x 95 pt, 72 dpi Greyscale Documents which is counter to both the dimensions and colourspace of the original documents... 9 minutes ago, Guy Beckett said: Going forward do you have any workflow suggestions for how to collaborate on affinity files - any preferences - google drive / apple or dropbox? We try not to open at the same time, would that be what corrupted it? The general advice is to work on your internal Hard Drive and then upload to Google Drive, iCloud, Dropbox etc., after saving but there have been numerous reported issues with file corruption when using cloud drives so until these are resolved it's difficult to be able to provide any failsafe method for file collaboration... 9 minutes ago, Guy Beckett said: Going forward do you have any workflow suggestions for how to collaborate on affinity files - any preferences - google drive / apple or dropbox? We try not to open at the same time, would that be what corrupted it? That's difficult to know but again, this is not the first time this has been reported in the forums so I think it would require some feedback from the Development team... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
PaoloT Posted September 9 Share Posted September 9 It's not just a matter of not working on the same shared file at the same time. It is also a matter of leaving Dropbox complete synching. As a general rule, working on shared files is dangerous, unless the program itself is managing collaboration. Paolo Quote Link to comment Share on other sites More sharing options...
Guy Beckett Posted September 9 Author Share Posted September 9 Hi Paolo These were created in Publisher NOT from a pdf - though there was a pdf file then imported into one layer... Fortunately we have a recent pdf export from publisher - so will recreate it, and put in place a download / local copies / upload workflow. I appreciate that collaboration is not a feature yet - maybe with your new owners it might be on a roadmap! Guy Hangman 1 Quote Link to comment Share on other sites More sharing options...
Alfred Posted September 9 Share Posted September 9 2 minutes ago, Guy Beckett said: maybe with your new owners it might be on a roadmap! Paolo is an ordinary user, just like you and me. Serif staff are identified by a ‘Staff’ badge, and they all have Moderator status, but I’m not sure whether you can see that if you’re viewing the site on a phone. Quote Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen) Link to comment Share on other sites More sharing options...
thomaso Posted September 9 Share Posted September 9 49 minutes ago, PaoloT said: It's not just a matter of not working on the same shared file at the same time. It is also a metter of leaving Dropbox complete synching. As a general rule, working on shared files s dangerous, unless the program itself is managing collaboration. Therefore a separate "Server" application was developed by a competitor, – not to be confused with its earlier "Story Editor" feature, which allows editing text in a separate interface but not independently of the layout and, for example, the available space. Since this problem of corrupted or completely lost files occurs quite often in Affinity, I wonder if it would at least be possible to implement a warning message when an Affinity document is opened from a non-local drive – to make the user aware of the risk of such a workflow and thus help to avoid data loss? PaoloT 1 Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
walt.farrell Posted September 9 Share Posted September 9 2 hours ago, Alfred said: Paolo is an ordinary user, just like you and me. Serif staff are identified by a ‘Staff’ badge, and they all have Moderator status, but I’m not sure whether you can see that if you’re viewing the site on a phone. On a phone, you see a Staff badge, and the Moderator status is denoted by the username being displayed in red: Alfred 1 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 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 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.