When using this script during reviews, I get this popup:
As far as I can tell, it worked fine, but should I enable compatibility mode? The settings menu says that I shouldn’t unless necessary
Double-Check is fine with or without Compatibility Mode. Wanikani is simply reducing support calls by nudging users to consider user scripts as a potential cause for problems before contacting them. I think it goes away permanently if you click the X, though I could be wrong.
Since the umaintained Userscript “Quiz pitch accent in lessons and reviews” ([Userscript] Quiz pitch accent in lessons and reviews) is incompatible with Double-Check…
I wonder if it’s functionality could be integrated in Double-Check, since it is closely related functionality anyways.
Would help a lot with learning pitch accent.
Right now I am using only 6 buttons (not the 7 total possible buttons with this script) and it bothers my OCD that the help messages that pop up don’t appear below the Item Info button but instead between the Item Info and Kana Chart Buttons.
1 Like
Hi, after yesterday’s update to Double-Check, now on “close” answers where previously I would get a shake and a tooltip, now I get a shake but the app goes to the next word and records a fail. Happy to have a look a the JS console next time I have a batch of reviews.
6 Likes
I have the same issue, the script is basically unusable now (not sure if the “shake” marks as fail, i think it just skips to something else, nevertheless very annoying).
The name of last change 2.2.40 is “Added repositioning of answer exception to account for added/removed buttons.” which doesnt seem important at all to me, so I just downgraded to the previous version 2.2.39 (beware if you do so as youll have to manually update it if you want in the future) here:
@Nirgan @mirithil,
I think I’ve fixed the issue. The popup is used for two purposes: the shake warning and the info message. I had mistakenly changed the position for both rather than just the info message. I’m not sure why that caused the shake-and-warn to stop working rather than just be offset, but either way, it should work now.
4 Likes
i can confirm that 2.2.41 works as expected (at least havent encountered any issue), thanks for quick fix!
I noticed the same thing happening to me too, and it just started this morning.
I noticed it was also broken on 2.2.40, anytime I mistakenly had English when WK was looking for hiragana I got marked wrong instantly. Just updated to 2.2.41 and will report if there is still an issue.
Thanks, the update did the trick!
Double check is causing some problems for me - when submitting a vocab word (kanji work fine, it’s only vocab giving this problem) it just shows this loading icon forever and doesn’t progress to the next item:
I’m getting this error in the console:
I can’t see any other scripts I’m using which should cause problems (no reordering script like Omega or anything), but here’s the list just in case:
I’ve got this script right after Open Framework in Tapermonkey, and I don’t have compatibility mode turned on for Wanikani. Any ideas what the problem could be?
I’m in a situation where my installed userscripts just wont appear as possible scripts to run in the tampermonkey pop up menu or in my wanikani settings/cog wheel in lessons. A couple of them show up and work fine, there arent any compatibility issues, even with just the framework and double-check enabled same issue. My compatibility mode is off, on didn’t help either. Everything is installed correctly.
I’m using ungoogled Chromium as my browser. Have wanikani whitelisted on every relevant extension. What I assume to be the main culprit is I’m also running Pi-Hole on my network, but not entirely sure how to troubleshoot any further. Only console errors look like this:
The other errors all look the same and begin with the Google s2 subdomain address.
If you’re running a pihole, and have the admin password, you could try disabling it temporarily to confirm that it is indeed the pihole causing problems:
That being said, that doesn’t look like the kind of error that a pihole would usually result in. In Chrome (at least the Googled one) I get an ERR_NAME_NOT_RESOLVED.
2 Likes
Ah, not sure why i hadn’t considered disabling pi-hole, I ran myself thin watching query logs and gave up.
Disabling sure enough led to everything working perfectly. I have a fairly extensive blacklist and I couldn’t find any info on wanikani whitelists so I’m not too sure where I should go from here. If you happen to have any suggestions I’d gladly hear them, thank you!
(Deleted above post because I apparently didn’t reply)
EDIT
Not sure exactly what happened, but after pi-hole reactivated everything is still working. Will just keep my fingers crossed and hope it stays this way!
2 Likes
I love the double-check script.
However, after carefully perusing the settings and some of the replies to this post, I haven’t found a way to enjoy the features of this script while doing extra reviews on WaniKani. For example, it seems like the double-check script only works during scheduled reviews. But, if I want to do some extra practice, the features are not available.
It seems like it should be easy to enable this. Is there a setting I am missing? Thank you for reading.
Go into TamperMonkey > Dashboard > Edit Double Check and modify the access urls
// @include /^https://(www|preview).wanikani.com/review/session/
// @include /^https://(www|preview).wanikani.com/extra_study/
The hit File > Save
Hit shift refresh on your browser, close and reopen it if to force the cache to accept it.
You can also do this to other add-ons you want to use in those areas. Enjoy!
I’m enjoying this script as well, as I think it’s better to self police what’s important than to have nuisance reviews come up too frequently. I know reorder scripts exist but that seems to heavy handed at my level, at least.
1 Like
Hi MeesterN,
I implemented these changes in both Chrome and Firefox, and unfortunately, I still can’t use the Double-Check features during extra study reviews. I made sure to hit save, shift refresh (on Chrome), and close and reopen the browsers. Also, on Firefox, I have only the Open Framework and Double-Check scripts active in Tampermonkey, so I don’t think there is another script interfering.
Do you happen to know what the trouble might be? And thanks for your suggestion!
I see, sorry about that. Maybe it doesnt like the full url. Try removing all the parameters after the last /
I edited my post above
1 Like
This works. Thanks!!
1 Like