Rather than rawdogging it, you can use the Jakeipuu app on your phone. It’s a little clunky on IOS but at least it has a working undo button, and some other cool features like a reading list.
3 Likes
Currently, as a workaround, I am using Tsurukame on my laptop. It works fine for my purposes.
4 Likes
As a workaround, I 'm using my phone app, meanwhile. There’s no way I can do the normal wanikani without such vital tools : D
Thank you for all your work!
1 Like
I am just happy that someone is taking time to fix this in the first place.
16 Likes
Thank you, I’ll survive for up to three days I think 
6 Likes
I’ll just go on vacation mode I think. Nothing kills motivation for me more than typo/dumb mistakes. Strictness is good but actually continuing your study is better.
18 Likes
Thank you, @rfindley, for all your hard work on scripts. Your time and dedication is truly appreciated. 
16 Likes
Thanks for getting this updated, three days is nothing! And the communication is super appreciated.
9 Likes
On vacation mode rn ready to start up again as soon as double check is up and running again. Just want to reiterate how much your time and effort is appreciated.
10 Likes
By calendar accident, today is literally the very first day it has been possible for me to Burn items, and I just totally zonked and read 八 as 入 and now I’m like literally shaking—this is TOO MUCH STRESS. And honestly double-check made me go faster, b/c if I just butterfingered it wasn’t a big deal—just like with the IME when I’m typing Japanese. I’m honest with myself, b/c I actually want to learn the kanji, so if I actually didn’t know the rendaku or something I mark it wrong—and I actually mark stuff wrong it lets slide (like “to cry” works for “to pay”?!?), but if I just typed “ki” when I meant to type “ko” and didn’t notice before hitting enter, it wasn’t a big deal. Now it can, like, makes me scream out loud—my husband’s getting very concerned from the other room, lol.
Is vacation mode the only workaround? Is there some way for me to only see my non-Enlightened items for a little while? It’s not so much stress if I’m not burning things. PLEASE Help?!?!?
4 Likes
I think I found a workaround—do 10-item batches by hitting “wrap up” as soon as I start, and then just close WaniKani completely if I butterfinger. It sucks as a solution when I have 100 reviews since last night, but at least it won’t make one wrong key push a kanji from burning back three more months!
p.s. Maybe not—I’m so shaky I just stared at 昨日 (which is obviously not one I’m ready to burn yet) for, like, 90 seconds, sweating over whether it was really the word I’ve known for ten years as “yesterday” or maybe might be a word for “expatriate” (last+old-Japan?!?) that I forgot I learned and yesterday’s actually 日昨 and I’m just stressing out so much!!! Ack!!!
1 Like
I’m stressing out doing reviews without this. When there are hundreds of reviews I have to go fast and mistakes are made regularly. Needless to say, it is appreciated that you are taking the time to update this!
3 Likes
Yup just rawdogged 200 reviews in one go, tons of typos… NOT a good feeling! Also adding the fact that I gotta wait for the item to come back since userscript for sorting ain’t working either. Thank you for planning a fix!
7 Likes
lmao I was trying to avoid using the exact term “rawdog” for it but I see we’re already there with that one
1 Like
Actually, just a note of what level the item’s already at, before I enter my answer would help a lot. I can get that with another WK tab or app, but that’s not realistic to do proactively. Is there a working userscript that shows that? Then, if I see an item is Guru I—which I can get it leveled back to in under a week—I can be more relaxed than if I see it’s about to Burn and a miss will cost months—then I’ll be more careful.
Maybe this is wrong. Maybe it’s really important before you Burn that the item be letter-perfect at your absolute command such that you wouldn’t typo it any more than you’d typo your own name (though I do that too sometimes!)—but, I’d like to make that call on a case-by-case basis after I give it a try.
tl;dr deets about why case-by-case is good for me…
Basically, Double-Check was letting me make value decisions about, “do I think it’s important that I remember this one is better translated ‘expectation’, and that one ‘anticipation’? Or that this noun is almost always used in 〜する, but it is a noun, so I shouldn’t just blindly use the -ing form in English? Or, can I just let it slide?” on a case-by-case basis.
Also, Double-Check let me go, “wait a minute… I definitely learned 紀 was ’era’ in class, years ago—this says ‘account’/‘narrative’ — was I wrong?” And then I look and see that Kodansha calls it “era” with sub-meanings ‘discipline, morals, code of behavior’ and it’s probably “account/narrative” in WaniKani just because it works better for the mnemonics, so I add “era” to the synonyms in another tab and accept it this time.
I shouldn’t have to get it marked wrong once to add what I typed as a synonym—especially since I’ve found that kanji I learned in school >15 years ago sometimes come back to me in their original form (like “era” here) only once I’m at, like, Guru I—until that point, I’ve got the WK lesson stuck in my brain as basically a whole new word.
Like, basically, I can do a lesson and if WK happens to give a kanji or vocab I already know, but in a form different than I’ve internalized it, I can temporarily ingest it into shorter-term memory as two different mental entries, as if it were another language I’m studying, and it only integrates (or the WK-specific version just drops out) after there’s been a few weeks or more of rest.
Anyway, I know the developer’s got it in hand, I’m just looking for the best workarounds in the meantime. Doing everything in wrap-up is one; I don’t see a userscript in active development that shows SRS level before you answer, though—is there one, maybe as part of a larger-function script I may have overlooked? (“Active development”, b/c I’m assuming every userscript that hasn’t been updated recently is now non-functional.)
(Also, I type maybe too fast. I use Dvorak and type English at >130 wpm and I switch to Portuguese QWERTY and Ukrainian several times a day, so I may be a uniquely crossed-wires case… 
)
Looking forward to the fix. WaniKani without the ability to undo mistakes is pain. Thanks for your hard work.
3 Likes
I know this might be a bad idea, but since I’m a developer by trade and have worked on front-end (though it’s not my expertise), and since I have some time today, I figured I might try to get things to work enough until we have an official solution.
The first problem I notice is that the url for reviews has changed. So changing the matchers at the top of the script cause the script to attempt to load on the page, but it immediately triggers an alert that “Wanikani Double-Check script is not working.” It does this (very helpfully, I might add) because it’s attempting to hijack the submit event but it couldn’t find the original event handler location to replace it.
And that’s where I’m a bit lost right now. The jquery method to find the event is no longer working (and jquery is apparently on the way out for wanikani in general), and I’m not sure if I should be looking into Turbo events or something else yet.
So anyway, this workaround project may not be ready before an official solution is available, but I’ll do my best and provide updates when I have any major ones to provide. Also if anyone else has some pointers but not enough time to actually make a fix themselves I would love some pointers to speed this up.
3 Likes
As a quick major update to this, I have good news and bad news.
The good news is I have a better understanding of how things work now with Stimulus and I see that rfindley already mentioned some things in another thread that helped me figure out how to interact with things in a better way.
The bad news is that the script was relying on jStorage, which wanikani was using, and which provided access to current review items, but will no longer be used.
My goal with this project was to provide users of this script who were feeling a little more adventurous with a quick few steps to get the script working in the short-term. Unfortunately, this bad news means that even if I can get it to work, it won’t be easy for the average user of this user script to manually change it themselves. So at this point I’m not sure if I should continue to figure out a quick fix for myself or if I should potentially reach out to rfindley myself to see if I can contribute to the mainline fix.
1 Like
So… rawdog it or go on vacation… Such a dilemma!
That vacation looks very tempting though!
I’ll… give it a cance. But if I fail too many I will hit that vacation while waiting for salvation!
Auto Commit has been fixed!
So workaround for now: NEVER HIT ENTER! 
Get the exact match or don’t commit =P
Or, trigger the Auto commit = win. You got it!
If you don’t trigger it, search up the word and do anki style: Was this what you meant? If so, now you know what you did wrong, get the Auto Commit to trigger.
No? Send through a faulty one and let it go down as it should.
6 Likes