This morning I attempted to restore a Scrivener project using Time Machine (10.6.1). I found what I was looking for but when the restoration process began I got an errors saying “The operation can’t be completed because you don’t have permission to access ‘file-name.scriv’”.
The project was then created but it wouldn’t open correctly.
The file names in the error messages don’t match because they came from multiple attempts.
Seems like I remember something like this being reported in the Mac news. I’ll report back what I find.
The file in question hasn’t been modified in a few months—pre 10.6. It is a “template” file that I normally duplicate and rename. This morning I unintentionally modified it. I was attempting to go back and get the version from yesterday. I assume that Time Machine would have made a copy of most recently closed and non-corrupted project.
Looking at the permissions of the package contents of the file I modified doesn’t show anything unexpected and nothing is locked. This file should be nearly identical to the problematic one.
Looking at my backup disk in Disk Utility, Verify and Repair Disk Permissions aren’t available.
Right now I’m attempting to Repair the backup Disk. It is taking a long time.
After waiting a few days, I thought I’d test Time Machine again.
Projects were saved, Scrivener quit, and Time Machine was run mannually.
Scrivener is NOT running.
Attempting to restore a different project. Get Info in Time Machine indicates that the Modified date and size matches the Finder. Project opens successfully from local drive. Almost immediately after clicking Restore button in Time Machine I get the “Scrivener warning” that I don’t have permission (see image in my initial post). Then the operation completes but with Zero project size.
This does look like a permissions problem, yes - the very first message screenshot you posted in fact said “you do not have permission…”. Scrivener files aren’t really comparable to OmniOutliner files in that OO files are “flat”, whereas Scrivener files are packages - that is, they are essentially folders of files. Thus if you can, in Time Machine delve into the entire package (Ctrl-click on the .scriv file and select “Show Package Contents”) and check that you have the correct permissions on all the files inside. Or change them on the whole package.
I have to admit that I am flying blind here as I have never used Time Machine, so I’m hoping another TM user can steer you better.
To find out what would happen if I changed the group of a newly created project from “world” to “staff” I used FileXaminer. I confirmed the change of both the package and its contents using Finder Info. I’ll add a few new documents to see if the group change sticks or whether Scrivener changes them. Also I’ll test to see if I can restore it tomorrow. I’ll report back later.
I compressed a copy of this project and the zipped file’s permissions changed to “wheel.” I tested compressing jpg file and its permissions remained the same as the source file.
Right now I have File Sharing turned off. I’m going to turn it on and see if I can restore a “world” group project to my Public forlder.
That’s not a Scrivener message - it is generated by the OS, or by Time Machine. The system is just using Scrivener’s file icon because that is the file you are trying to access - but Scrivener isn’t providing that message.
This is absolutely possible. What I’m not sure about is how Time Machine works with package files, which is what I was trying to say.
Sorry, no, I mean in the Finder. I assume you can access the contents of Time Machine in the Finder, or that these files have already been restored to the Finder? As I say, I have never used Time Machine and don’t have it set up, so I’m just guessing here.
Is “wheel” an account on your computer? And which account are you accessing Time Machine from? Are you accessing it from the “bobby” account or from another account?
Me being the nerd that I am, I have verified that if you are not in a group the OS tosses an error when you try to set the perms from an archive. not sure how this would look from the TM perspective, but I suspect that it is the group being “wheel” that is your problem.