klembot
commented
5 years ago It seems plausible that this might be fixable by clearing cache upon opening a story for editing... the downside would be, if you lost your network connection between when you opened Twine and when you started editing, you'd be stuck. We could add a manual refresh button to the story format dialog, but that feels annoying to put the onus on the user.
Of course, the other workaround is to have unique URLs for each version. But that's annoying and possibly unwanted behavior, especially if you're doing just bugfixes and you want people to get them without having to fiddle with settings.
StoltHD
HiEv
I updated the version of one of my proofing formats from 1.1.0 to 1.1.1. The change was reflected immediately in the online twine at the Twinery, but due to issue #563 I couldn't test there so I was testing in a download of 2.3.1 (Mac OS). The format never updated automagically, and even when I deleted and re-added it, the old format # appeared, not the new one.
I tried 2.3.2 after that to see if the problem was fixed, but had the same issue of the old version being cached. Note, I also had to close and reopen Twine to get a deleted story format to leave the list; if I added it without doing that I'd get two copies in the list. (Their button states remained amusingly in sync with each other.)
I should mention that this wasn't a superficial numbering issue; the bug fix from the updated story format was not present, either.
I read a bit about unwanted Electron caching, including some SO advice about how to clear the cache programmatically, but I didn't find a manual workaround for the problem.