Compile not working in 3.2 [Workaround: pg. 2]

[suavito]

@Maureenm61

I feel upset and angry and people should have some warning before they purchase something like this,

Angry at whom? At the person who obviously did not try the 30 days trial version of “something like” this before buying?

[kathryn]

Me, too. Help!

[bodsham]

@Maureenm61

I feel upset and angry and people should have some warning before they purchase something like this, which the concepts behind are great-but sticks and stumbles too much in reality -for me its given me hours of wasted time.
I though software was supposed to ease time and help people.

There’s a very generous trial for Scrivener which ought to be enough to allow people to understand what it’s like. And yes it is complex as any review of the app on the web will tell you
Honestly I don’t feel you should threaten to go around bad mouthing the app on the web because it hasn’t worked for you. Perhaps you should have done a bit more research beforehand.

[HeidiU]

@KB

I’ll be releasing 3.2.1 tomorrow to fix this bug.

All the best,
Keith

Thank you, Keith!!! I appreciate it along with your support!

[KGUK]

@Skilful Scribe

I have a dedicated writing profile on my mac - I can get rid of clutter and temptation that way) .

I came here to find out why Compile had stopped working, and then found this genius idea! I’m TOTALLY copying this. Thanks!

[niassa]

@KB

I’ll be releasing 3.2.1 tomorrow to fix this bug.

All the best,
Keith

Thank you so much, Keith!!

[samiahayes]

I’m on Catalina 10.15.7 and have the same issue. All was great, then updated to Scrivener 3.2, now I cannot compile. No errors, just no action after pressing the icon or using the drop menu or the keyboard shortcut.

[paineju]

Same problem here after installing the latest Scrivener update. I’m running MacOS Catalina 10.15.7 and am no longer able to compile. I click on the menu option and nothing happens! Help please!

[RLFelty]

Same here with Catalina on my Mac. Sure am glad I wasn’t getting ready to publish this week! Please let us know when there is an update to fix it. I would prefer that than to delete the 3.2 and reinstall. Something always seems to get messed up with reinstalls for me!

[jthrill]

Mac user. Just upgraded to Big Sur and installed 3.2 update this afternoon. Compile function also not working for me. Thanks.

[Fitch]

@AmberV

Ah, I found something that looks promising, it may have to do with having set a global font override in the past (if you created your test project from a template, it may have had that set as well). You could try this:

1. In Finder, right-click on the test project that you created, and select “Show Package Contents”.
2. Drill down into the Settings folder, and delete the ‘compile.xml’ file.
3. Now restart Scrivener, load the project, and try compiling.

That unfortunately wipes out all compile settings, as you would imagine. So if that is not something you could afford to do in a live project, there is a more surgical approach that would involve editing the XML file to remove the font setting.

If you’re comfortable doing so, open the .xml file in a plain-text editor (TextEdit will work if that’s all you have), and search for “”. You’re looking for instances that directly follow a “” line. Delete the whole line containing the Font declaration, for each format that has one.

Obviously, I’d strongly recommend setting aside a backup copy of your project before doing this.

Or… if you can, just wait until the fix is out. We’ll have this fixed soon since it is obviously going to impact fair number of users.

The .xml file deletion work around worked for me.

I sent in two reports, then went to the work around.

Fitch

[AmberV]

Great, and thanks for copying the entire post in a quote, as some people seem to be having difficulties in finding page two of this thread.

[WoolyPinkFox]

Looking forward to 3.2.1 Keith!
Silver lining for those who also have Final Draft: It’s really easy to export the scenes of a screenplay to Final Draft using File/Export/Files/Final Draft (FDX). All the formatting matches perfectly in Final Draft. It’s possible to continue to work in Scrivener and then just export to Final Draft to print.

[KB]

3.2.1 is now available via our site and has been submitted to the App Store. If you bought from us, please go to Scrivener > Check for Updates to grab the fix!

[Sandra_Gulland]

Relieved that the 3.2.1 update has fixed this very serious problem. Too bad I lost a half-day struggling with it. I suggest Scrivener post the fix in a banner at the top of the threads reporting this issue.

[nontroppo]

@Sandra Gulland

Is there a workaround? I’ve not seen one yet.

DESPERATE.

Install V3.2.1 (the post before yours) which IINM fixes this and other problems!

[WoolyPinkFox]

@KB

3.2.1 is now available via our site and has been submitted to the App Store. If you bought from us, please go to Scrivener > Check for Updates to grab the fix!

Just installed it. Yes, it works! Compile is back. Thank you, Keith!