Publisher File shutdown on save failure (linked files)

[levirphillips]

Hi,

I was recently using the Publisher Beta and unfortunately, lost a bit of (thankfully simple!) work due to a disconnection with my work VPN.

We use a VPN to access in-house servers, which has a fairly short timeout period. Whilst working on a Publisher file, the VPN disconnected. When I went to save my work, an error popped up saying that Publisher had lost access to the file (and linked files) and immediately closed. My work was gone and a shock on my face.

Whilst common sense would propose saving frequently, is it silly to suggest a failsafe option of switching to the Save As menu when this happens? My project was using linked files, but surely there's a way around this for those accessing work files remotely?

Thanks and keep up the great work!

Levi

[Alfred]

The efficient memory handling of the Affinity apps is achieved (at least in part) by not loading the entire project file into RAM if it is beyond a certain size, so you need to get into the habit of copying from remote to local storage, working on the local copy and then copying the edited version back across.