For some reason, I no longer can export files from Scrivener. I have tried exporting different file types, to various locations, and while I do not receive any error message from the program, the supposedly exported file simply does not exist. I have tried restarting Scrivener and restarting my computer, but files still refuse to export.
I can successfully compile an individual chapter to plain text, so I will use that method for now, but I’m wondering what could have caused me to lose the export ability. Since the last time I successfully exported a few weeks ago, I did allow various MacOS updates to install, so I’m wondering if something there is the culprit.
What Mac OS X version are you upgraded to, and which version of Scrivener are you using (as well as whether you bought it from the Mac App Store or directly).
Another question, if you select a folder that contains nothing but PDFs or images (maybe import some just to test if you don’t have any), does that export fine? I’m wondering if perhaps its just the text conversion process that broke somehow.
I actually posted in the bug report forum as well about this; it looks like Scrivener is trying to write properly, but that the OS is denying the program the permission to write. I am using Mac OS 10.8.2 and Scrivener from the Mac App Store.
But, in testing what you suggested, I realized that this may be user error on my part. In the past, the files I have exported did not have any notecards associated with the file. I was looking at a different document within the same project today to test your suggestion, and found that I can export a file, so long as it does not contain notecards. If the file contains notecards, I cannot export, but I can compile.
This probably is a feature, and not a bug–I just didn’t know about the feature as I only recently started using notecards!
Interesting, I did some testing and ran across one case where a container (anything in the binder that contains other items, notecards as you put it) would not export and did not produce an error. When you use the File/Export/Files... command, does the name it provide you with at the top end in a period? My test container was called “Okay.” in the Binder, so when I went to export it, the suggested name was “Okay.” in the export dialogue. If I left everything alone, nothing would export even though it went through the motions. If I removed the dot, so that it just said “Okay” in the dialogue, it worked.
Whatever the case, that isn’t a feature or a function of design. You should be able to export anything and everything from the Binder, no matter what it has beneath it, doesn’t have beneath it, etc.
MAS version. Try a file called “Okay.” with a document beneath it. Select the container, export and leave the name as “Okay.”, you should get a silent failure and no console messages.
No periods in mine. I did have hyphens in the middle of the names, so I tried removing those, but it didn’t make any difference. The only thing that seems to have fixed it is Keith’s suggestion to my post in the bugs forum about specifically giving access to the directories I want to export to in Scrivener. Now, exporting works for these files.
Well that is strange, and certainly atypical. That command doesn’t do anything that the Export dialogue box does already, implicitly. When you use a dialogue box in a sandboxed application, you are giving the software temporary permission to use your hard drive in the location that you pick. The authorization tool allows you to grant explicit permanent permissions to arbitrary locations. Well, at least it is working, but it sounds like there is some kind of sandboxing bug going on there in the OS.
At least we could find a weird quirk with the period in folder names as a tangent.
