Hi,
After upgrading to Catalina (and having to re-enter my license), the word count has stopped working. It is stuck on 4196 words. I am on the current version of 3.1.3
Does anyone know how to fix this?
Thanks,
JimC
Well, after messing with it all morning, deleting the original installation and reinstalling Scrivener, the issue was still there. I got around it by starting a new project and copy/pasting my files into it. Now everything works again.
I am probably going to have to do the same for all my projects as they all seem to have the same problem. I’ll just do it one at a time as I get to them.
That was a waste of an entire morning. Grrr…
JimC
Apple sprung Catalina’s final release on the world without notifying the 3rd party developer community like they usually do. This means that there are a number of companies out there scrambling to finalize their Catalina updates and get them pushed out.
Since you’ve already upgraded, you will need to do this for your current project, but likely the update that Keith is working to bundle up and distribute will hopefully fix the issue. So I wouldn’t do this for every project that you have, unless you really need to work on them all right now.
I am unable to reproduce this with a simple test:
- Create a new blank project on macOS .14 with 3.1.3.
- Paste in 1,266 words of junk text.
- Hit ⇧⌘T to open the Project Targets panel.
- Type “1800” into the draft goal field (not sure if that is necessary, you only mention a count not a target).
- Close project and reopen it on my testing partition, running macOS .15 with 3.1.3.
- Press ⇧⌘T to open the Project Targets panel.
- In the main editor, type in the phrase “this is a test”.
Word count reads, “1,270 of 1,800” words.
It might help to know what you mean by “word count”, though. There are around half a dozen different places where Scrivener would count words up. Granted I don’t see any of them reporting incorrectly, but I might have overlooked one of them.
I’d also go through each setting in the related options area for the tool you mean, doing a side-by-side comparison of the new project with the old one. If you see any differences from default, are you noticing that setting changing spontaneously in all of your projects as well, and does switching it back make a difference?
Also, might it not be simpler to Time Machine roll back to 10.14 for now, rather than spend hours upon hours moving your project content into new containers? Either way it would be nice to figure out what is wrong before you do that, if you do.
Hi,
Thank you for the detailed response. I am referring to the target word count.
If I open a new file then it works. However, every single one of my existing projects has the target word counts frozen and will not work, so my issue is with existing files, not new ones.
I may have to roll back if I can’t find a reason for this. I’m not savvy with these things, but it seems as if all my projects corrupted overnight. I reinstalled Scrivener, nut other than that I don’t know what else to do.
Thank you again for your help.
JimC
Got it, that’s why I performed my test the way I did, by first setting up a project on 10.14, and then taking it over to 10.15 to see if the target feature still worked.
Well with the Targets panel you can open two of them at once, one for each project (the one that works and the one that does not), and go through each tab in the Options button looking for differences. Let me know if anything pops out as being wrong to you.
P.S. If you do go down this road of migrating projects, I’d highly recommend using File ▸ Import ▸ Scrivener Project… from the new blank project, rather than copy and paste. The latter will do a much more thorough job of it, and automate the mind numbing tasking of rebuilding the outline from scratch. There are other considerations to be made as well, such as migrating metadata, compile settings and so forth.
I restored an earlier file from a few days ago. This works perfectly. I don’t know what happened, but I seem to have it under control now. Whatever it was, it had to have been caused by the update. Nothing else has changed.
I only use the Mac for Scrivener and nothing else, so no other program could have corrupted my projects.
JimC
Yeah I don’t think I would consider this a case of corruption, even if a setting did revert or something odd.
So am I to understand that this morning the problem is not present in your exist projects? I suppose it must have just been a temporary UI glitch or something. We’ll have to keep an eye out for similar reports, but if that’s the case, those are very hard to track down since we need to see bugs happen in a debugging environment to fix them.
Hi Amber,
The problem still exists in all my projects except the one I restored from a previous backup last night. I am going to have to restore all my other ones to a previous version for them to work properly again.
I have absolutely no clue how or why this happened. Everything was fine until the update.
JimC
Amber,
I found the issue! For some reason, the compile function had changed so only three chapters were checked. This meant that every chapter not ticked wasn’t working with the target word count. When I rechecked everything in the manuscript folder it all started working again.
I don’t know what caused the compile function to do that, but that was both the cause and the cure.
JimC
Huh, yeah that definitely would not have come about by updating your OS. Those checkboxes are stored in Scrivener’s custom internal format.
Well at least we know what happened! And yeah, by default that’ll do it, since anything unchecked is considered “notes” instead of output material; stuff you wouldn’t want counted as progress.
HI,
I’m having this same problem and I have had for quite a while. I don’t know what JimC means by ‘checking all the folders in the manuscript file’.
Thanks! This just happened to me! And since a big part of my motivation is hitting daily word targets it was crippling! :<<< But yes, I had to go to the document’s compile tool, select the enter manuscript (all folders and scenes) and click compile. Even though I didn’t export or print, the count started working again. I am so relieved.