Save as error

[GeirSol]

Hi! I get quite a few of these when choosing save-as.

It's linked to prior save-error and freeze.

[walt.farrell]

Was it right that the file is opened Read-Only?

[GeirSol]

3 minutes ago, walt.farrell said:

Was it right that the file is opened Read-Only?

Yes, the file was opened read-only by Publisher. On Save-as this message appeared.

[walt.farrell]

And when you used Save As, did you give it a new name (or location) or try to save to the old name & location?

[walt.farrell]

Also, what OS are you using, and what release of the application?

[R C-R]

5 hours ago, walt.farrell said:

Also, what OS are you using, and what release of the application?

From the X in the corner of the screenshot of the error message, it has to be Windows, right?  Also, more of a guess but from the squared off edges of the APub logo it probably is V1.

[GeirSol]

16 hours ago, walt.farrell said:

Also, what OS are you using, and what release of the application?

 

10 hours ago, R C-R said:

From the X in the corner of the screenshot of the error message, it has to be Windows, right?  Also, more of a guess but from the squared off edges of the APub logo it probably is V1.

Win 11, Pub 2.2.1

[stokerg]

Hi @GeirSol,

Where are you saving to, locally, network drive or cloud drive?

I've tried replicating the same error and I'm unable to, when I open a Read Only file, using File>Save brings up the Save As window and this saves without issue, once I've given it a new name.  So it must be something to do with your afpub file or linked resources.  Could you attach the afpub file and any linked images or upload them to our Dropbox here and I'll see if I have any luck replicating the issue.

[GeirSol]

1 hour ago, stokerg said:

Hi @GeirSol,

Where are you saving to, locally, network drive or cloud drive?

I've tried replicating the same error and I'm unable to, when I open a Read Only file, using File>Save brings up the Save As window and this saves without issue, once I've given it a new name.  So it must be something to do with your afpub file or linked resources.  Could you attach the afpub file and any linked images or upload them to our Dropbox here and I'll see if I have any luck replicating the issue.

Local

The issue happens when saving as same name (that I need to do to get on with crashed file)

Save as different name usually is ok.

[walt.farrell]

36 minutes ago, GeirSol said:

The issue happens when saving as same name (that I need to do to get on with crashed file)

It's generally safer and recommended to regularly Save As using a new name, as that helps ensure you have good backup copies periodically.  That will also help keep the Affinity files smaller.

[GeirSol]

36 minutes ago, walt.farrell said:

It's generally safer and recommended to regularly Save As using a new name, as that helps ensure you have good backup copies periodically.  That will also help keep the Affinity files smaller.

Ok, but normal behavior is that save as same name is allowed.
And it's far more convenient in my case. But, I'll consider your arguments.

Why does this give smaller files?

[stokerg]

Hi @GeirSol,

If you exit Publisher and check the properties of the file you had open, is it set to Read Only?  If so, then this error is kind of to be expected as you are trying to save over a read only file, which is why giving the file a new name works, as it's creating a new file.  If it isn't set to Read Only, can you please upload the afpub file so I can try to replicate this and see if it needs logging with the Developers, as there must be something in the file causing it to open as read only?

 

[walt.farrell]

43 minutes ago, GeirSol said:

Why does this give smaller files?

Because when you use Save As with a new name the application will remove wasted space that accumulates within the file as you make changes.

[Pšenda]

38 minutes ago, stokerg said:

If so, then this error is kind of to be expected as you are trying to save over a read only file

I think it shouldn't cause an "error" - at least not for Windows.
The ReadOnly flag should only cause an additional query (do you really want to overwrite the file with the ReadOnly flag?), not Error.

[stokerg]

Hi @Pšenda,

7 minutes ago, Pšenda said:

The ReadOnly flag should only cause an additional query (do you really want to overwrite the file with the ReadOnly flag?), not Error.

Not seeing that here in Affinity or NotePad, i get told the file is set to read-only and try again with a different filename. 

This is why it would be great if @GeirSolcould upload their .afpub file so I can see if I can get the same error shown in the first post of this thread, which so far i haven't been able to  

[Pšenda]

1 hour ago, stokerg said:

which so far i haven't been able to  

For me "🙂"

Yes, this error cannot be caused by setting the file flag to ReadOnly - the file cannot be overwritten:

(This file is read-only. Repeat the action with a different file name.)

I consider this a reasonable solution.

Edited November 7, 2023 by Pšenda

[GeirSol]

19 hours ago, stokerg said:

Hi @GeirSol,

If you exit Publisher and check the properties of the file you had open, is it set to Read Only?  If so, then this error is kind of to be expected as you are trying to save over a read only file, which is why giving the file a new name works, as it's creating a new file.  If it isn't set to Read Only, can you please upload the afpub file so I can try to replicate this and see if it needs logging with the Developers, as there must be something in the file causing it to open as read only?

 

This is not normal behavior. Normal is allowing save over same file, with prompt.

Sorry I can't upload this file.

[stokerg]

2 hours ago, GeirSol said:

This is not normal behavior. Normal is allowing save over same file, with prompt.

 

I'm going to have to disagree with you on that point.  It would seem Microsoft also disagree with you as well here.

2 hours ago, GeirSol said:

Sorry I can't upload this file.

Then isn't much more help we can offer, as the issue will be related to the file you are working with.

 

[R C-R]

5 hours ago, GeirSol said:

This is not normal behavior. Normal is allowing save over same file, with prompt.

It is not at all normal behavior for files marked Read Only! Maybe you are thinking about overwriting files that are not so restricted, where you do get a prompt asking if you really want to do that?

[walt.farrell]

What is really "not normal" here is the message that the first post shows: Internal Error.

[stokerg]

1 minute ago, walt.farrell said:

What is really "not normal" here is the message that the first post shows: Internal Error.

I agree and that's why I've been trying to get a copy of the file and also created @GeirSola private Dropbox link to upload the file to.  But without the file, there isn't much more I can do to look into the error  

[GeirSol]

20 hours ago, stokerg said:

I agree and that's why I've been trying to get a copy of the file and also created @GeirSola private Dropbox link to upload the file to.  But without the file, there isn't much more I can do to look into the error  

Sorry, the file is not in same state now. However I can upload it when it happens again.