I cannot open files in backup folders. I get an error message that my file names are too long and I should rename them. I tried that, but when scrivener backs up again, the old long name is resurrected, and I can no longer search for and find the files??? Any suggestions?
Assuming you don’t try to open zipped backups as Projects, check the File > Options > Backup settings for the location of the backup files, and whether date and time are concatinated to the original filename of your Project.
True. The backup name is inherited from your project name. So, if you don’t shorten your project name, your backup will continue with the same error.
On Windows, some files can be opened directly in the zip folder. It’s not a good practice, but hey, it’s possible. However, somewhere along the line, this will not work because of the length of the name, which is way under the norm for filenames on Windows.
- If you want to access the content of your ZIP backup, drag the SCRIV folder out of the ZIP to Downloads. (You can drag it to any folder you like; I just use Downloads for anything I introduce to my computer.)
- Rename the project by renaming the SCRIV folder ProjectName—OLD.SCRIV (i.e. add the —OLD to the filename to identify it apart from your ongoing project).
- Click into the SCRIV folder.
- You’ll find the SCRIVX project file with its former name.
- Open the SCRIVX file and your project will launch, and in the process will be named with the —OLD piece added to the project name.
- Now you can work safely with the former version of your project and open your WIP project at the same time, pulling in what you’d like to from the old project—if that’s a requirement.
- When done, exit to save both. Delete the old version in Downloads and delete the backup with —OLD as part of its filename.
Default windows has a limit of 256 (?) characters for a path/filename for backwards compatibility.
It is possible to enable long path/filenames in Windows by editing the Registry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem and changing the value of “LongPathsEnabled” from 0 to 1.
You should reboot to ensure the setting is active. Do a web search for more information.
Your software may also impose a limitation, so this may not solve your problem.