Heads up: Permissions problems when importing old file


My mother (the owner of this account) had some trouble importing a Scrivener 1 file into Scrivener 2. I’ve fixed the problem, but I wanted to let you know what happened in case you want to modify Scrivener to be robust against this kind of thing.

Basically, creating the backup file failed with this Console message:

It turned out that some of the permissions for files in the package file got trashed somehow; in particular, 47.rtfd lost its write bit. Apparently Scrivener copied the incorrect permissions bits to the backup, so it couldn’t write into the packages it was creating.

I managed to fix the file with a command line incantation:

chmod -R u+rwX,g+rX,o+rX .

But of course if she hadn’t had a registered Mac developer living downstairs, Mom would have been totally lost. I just wanted to let you know that Scrivener seems to be susceptible to this sort of thing. Perhaps it should do some sort of permissions repairing within the package, or at least show an error message that correctly indicates the cause of the problem?