This probably has a quick and easy fix, but I’ve been searching the forum, user manual and internet at large for the last two hours and haven’t found it, so I am asking actual human beings instead.
Running: Most recent trial version (as of 7/24) of scrivener, windows 7 home premium with service pack 1. I would like to open files created in Scrivener for Mac version 1.5.4.
Problem: Scrivener will not open .scriv files, either on double-click in windows explorer or from the open (ctrl+o) menu within scrivener. This is consistent across the tutorial files which came with scrivener, .scriv files created in the latest release, and .scriv files created in 1.5.4 for Mac.
I can open .scrivx project files by going into the .scriv folder and opening the “project” file, but only through the open menus within scrivener – not through windows explorer. When I try, it gives the following error:
Is this intentional/a feature or a bug?
Is there a way to make windows and/or Scrivener recognize that Scrivener should open .scriv files?
I can also provide screenshots, if that would be helpful.
Ditto on the issues boosette reports, i’m on Scriv for Windows 1.2.1.
I am trying to locate the nanowrimo template and found some other templates I would like to have. When I download them, I can’t open/save them. I get ‘file is not writable: Access is denied. Auto-saves must have write permission to your project.’ How do I change? How do I access inside Scrivener, or from windows?
There are several different issues here, so although farwyn has already found one relevant post, I’ll just run through everything.
On Windows, Scrivener projects appear as a regular folder with a .scriv extension, and it is necessary to open that and then double-click the .scrivx inside in order to open the project (or, when going through the menus, to select the .scrivx to open rather than the .scriv folder). On the Mac they will appear as a single file and there double-clicking the .scriv is all that’s necessary, though in fact it is still a folder of files just as on Windows, and is merely being presented as a single file for convenience. So if you’re working back and forth between platforms, you will see this difference, and it’s important that you always deal with the entire .scriv folder on Windows (not just the .scrivx) when you’re moving or copying your project.
This is a bug that crept into the last release of Scrivener on Windows (1.2.3) whereby it is not possible to open a project from Windows Explorer when Scrivener is closed. Once you’ve launched the program, you should be able to open projects from Windows Explorer by double-clicking the .scrivx file, as well as of course via the Scrivener menus.
This is not possible, as the Mac 1.54 version used a different format for projects. You will need to first use the Mac 2.x version of Scrivener to update your 1.54 projects to the new format; they will then be compatible with the Windows version (though not backwards compatible with 1.54).
This message means that the project you’re trying to open is read-only or is contained in a read-only directory. At a guess, you may have downloaded these templates as .zip files and are attempting to open the project directly from within the .zip folder, which is read-only. In that case, just right-click the .zip file and choose “Extract All” or double-click the zip to open it and then drag the .scriv folder from it to a new location to create a writeable copy of the folder on your drive. You should then be able to open that in Scrivener (keeping in mind the current bug with opening .scrivx files while Scrivener is closed).
Also, you should update to 1.2.3 by downloading from the website. The auto-updater was broken in 1.2.1 and so you’re not getting notices of new releases. 1.2.3 has a few fixes from 1.2.1 (notably, the auto-updater!) and the next release, fixing the .scrivx opening bug among others, should be out soon too, so you’ll want to get alerted to that as well.
The auto-updater was broken in 1.2.1 and so you’re not getting notices of new releases. 1.2.3 has a few fixes from 1.2.1 (notably, the auto-updater!) and the next release, fixing the .scrivx opening bug among others, should be out soon too, so you’ll want to get alerted to that as well.