Save problem...

[Baniola]

I got this lately when working on a document. Tried both save as a document and save as a template.

[Gabe]

Hi @Baniola

Is this something reproducible or just a one-off?

[Baniola]

Yes, it is reproducible:

1. Create a new document and save it under the name you choose.
2. Use the place command to place artwork (EPS skater in my example)
3. Choose edit placed image and make any small changes; it reflects just fine in the main document
4. Document cannot be saved anymore

[Old Bruce]

I noticed this last night working on a Photo 2.2.0 [1971] document. In my case it was not an EPS file but an embedded Photo 2.2.0 [1971] file which was causeing me trouble. If I remember correctly any little change to the embedded file would result in the same warning as you show in your first post. Fortunately I had an earlier version I could open and do a  Save As. But again any change to the embedded file resulted in the Can't Save warning.

I am running Mac OS 12.6.8

[Baniola]

Yes, correct. Any change to the embedded file causes you cannot save the file which could bring you to a very bad situation. If you place the file at the beginning of your work and spend a long time adding extras and the end you cannot save your file. The workaround is to open the file in a separate window edit it there and just copy and paste modifications to the first file.

[dcarvalho84]

I'm having this too with Designer, and it's there in todays RC1

For what it seems to me, whenever you make any change in the embedded document the original document won't let you save the file.

[Old Bruce]

1 hour ago, Baniola said:

The workaround is to open the file in a separate window edit it there and just copy and paste modifications to the first file.

Seeing as this is most likely going to bite me again thanks for another workaround. I may not have an earlier copy to start over from.

[Gabe]

Thanks. Issue logged. 

[Affinity Info Bot]

The issue "Editing an embedded document file will cause parent file to fail to save." (REF: AFD-6819) has been fixed by the developers in internal build "2.2.0.1991".
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.