If I am wanting to save a different file version I usually do “Save as” so I can rename the file and keep the original in tact to go back to. I do this in all other programmes.
DO NOT DO THIS!!! Scrivner does NOT save parts of the file but for some reason reverts back to an earlier file type. I have wasted days on lost work.
We do not have enough service to work from the cloud.
Please fix this huge bug.
Thank You
I don’t recommend using Save As except for renaming a project, or cloning a project to kickstart a sequel etc. It’s potential disaster if you lose track of which version of a project you are supposed to be working on - easy to do apparently.
What exactly do you mean by ‘reverts back to an earlier file type’?
I have used Save As as needed with zero problems in Mac (you don’t mention your platform) and if I remember correctly also Win.
I don’t understand your comment about working from the cloud. Scrivener projects should never be opened from or saved direct to the cloud, always a local drive…
I suspect this is what is happening:
The user is opening a project, working in it, then Saving As. Then, when the user opens the original project, there appears to be a reversion where there is none.
Agree, once use save as diverge from original project and any changes in the “new” project will NOT be saved to the original. You need to use File> Back up to retain a project that reflects changes you make in the original project. This is not a bug, you used the wrong process to save to maintain continuity.
If you use “Save As,” Scrivener creates a new copy of the project and continues working in the copy. This is not a bug, it is the expected and documented behavior. (And is also how Save As works in many applications.)
As noted, File → Backup → Backup To is a good option for creating “milestone” backups, with the added ability to ZIP them so they can’t be opened by mistake.
Save As will also work fine for your purpose, you just have to use a naming convention that allows you to tell which version of the project is which.
I would like to add that since I started using Scrivener, I no longer have version chaos with different edited copies of manuscripts or parts of manuscripts. Snapshots, revision management, and automatic backups have made it unnecessary to create copies of copies of copies of project files. In my opinion, snapshots are still one of the most important features Scrivener offers.