Thanks! I love how it counts the time so I can stop scrolling Insta and get back to my 174+ lessons! Appreciate your work!
1 Like
This should only happen when the page is newly loaded: either by refreshing the page or by navigating to it from a WaniKani page that is not using Turbo yet. I did not have time to follow the WaniKani developments in the last couple of weeks, but I think the dashboard is not yet using Turbo? Once they change that, the problem you described should be gone (unless you go to the lesson/review pages directly, and not via the dashboard).
1 Like
I’ll take a look at it when I get the time. Might take a while because I just bought a house today, but I’ll try to make some time this weekend
5 Likes
Thank you Kumirei, and congrats on your house! 
2 Likes
Button should be back once you update
3 Likes
Getting some weird behaviour, happened before and I think it was a problem with queue manipulator, but idk so I’m reporting it here. Active scripts are open framework and omega, on firefox.
Two things, it’s showing the wrong colour and also not converting text to kana. Here’s my reorder preset:
At first the vocab is purple, but after a second when the preset loads instead of ordering to a radical (There are apprentice radicals in my queue) it just changes the colour.
Not sure what’s going on but as always I greatly apprecieate any time you spend looking into these things and let me know if there’s any extra info I can give!
Also, if I just keep refreshing the review page it sometimes works as expected so I can still do reviews using omega 
1 Like
This does indeed sound like a Queue Manipulator issue. @Sinyaven is this a known issue?
1 Like
It’s neither a known issue, nor am I able to replicate it (I just tested it in Firefox with Tampermonkey and Violentmonkey on Windows).
@nazan, can you go through the steps in this guide (especially step g) to gather more information on the problem? I’m especially interested in the script manager you are using and if there are any errors in the console. And did you have this problem for the entire time since WaniKani changed the review pages, or did it start again only recently?
2 Likes
Thanks for having a look at this! It’s started again recently, I’ve been away from wk for a couple weeks… and also started using my pc for reviews… out of curiosity I just checked and lo and behold no problem on my laptop. That is until I let tampermonkey update and now getting the same behaviour there, so do you think reverting the tampermonkey update will fix? Is there a way to do that?
Here’s the console anyway:
I’ve got to head to bed now but will check in tomorrow after work. Cheers!!
1 Like
Most of the warnings and errors in your console are the usual stuff and not related to the problem, but the very last message says that Queue Manipulator tried to fall back to modifying the queue by renewing the quiz-queue Stimulus controller. This means that the first attempt at modifying the queue by changing the Stimulus controller variables has failed. And seemingly, the fallback fails as well.
Next time this happens, can you run this code snippet in the console?
Stimulus.getControllerForElementAndIdentifier(document.querySelector(`[data-controller~="quiz-queue"]`), 'quiz-queue').quizQueue;
It should return an object with a bunch of properties like maxActiveQueueSize, minBacklogQueueSize, …
And after that, can you run the following snippet in the console:
let element = document.querySelector(`[id="quiz-queue"]`);
element.replaceWith(element.cloneNode(true));
It should trigger the queue reordering.
1 Like
So Stimulus is not defined globally, and the Stimulus controller also does not react to the DOM change? Does vanilla WaniKani even work at that point? I am quite confused.
Can you load your reviews with Tampermonkey disabled, check in the console if Stimulus is still not defined, and then try to do some reviews to see if the reviews are working?
And, just to make sure, have you tried it with all other browser extensions disabled?
1 Like
Just thought it is worth raising that I’ve also started to see the same issue within the past day - reviewing works fine without any scripts enabled.
Will investigate and see if there are any console logs at all.
EDIT: I say that and then immediately can no longer replicate it - will monitor.
2 Likes
It’s fixed and is working as usual now, I randomly enabled my antivirus’s OPTIONAL browser extention and that seemes to have fixed everything. Turns out it wasn’t a problem with omega or queue manipulator so sorry for getting you guys involved, but also thanks so much because it was while preforming @Sinyaven 's troubleshooting that I stumbled upon this.
I have no idea why or how all of this works but I’m just glad I can review again! 
Cheers!
1 Like
I’m glad to hear that you got it working again!
1 Like
Hi! Is there a way to sort or filter by unlock date? Specifically, I want to guarantee that I pull either the oldest or newest unlocked vocabulary lessons from my lesson queue.
1 Like
i’m going to report this issue as still not working: i posted about it here Reviews not starting properly, is this a known problem with a specific script?, and rfindley pointed me at this thread.
should i run the tests you mentioned above?
I think the important things to check are whether Stimulus is defined by entering Stimulus in the browser console and hitting Enter (if it returns an error then it is not defined), and to check whether vanilla WaniKani reviews still work for you if you completely disable Tampermonkey.
1 Like
i have a bunch of fresh reviews, so i tested it.
first time round, reviews started normally.
i decided i was testing, and as the problem is intermittent, another attempt at reproducing it might be worthwhile. so i returned to the frontpage, returned to reviews, and the issue occured again.
console looks like this, endlessly repeating, at speed (like, 100 lines per second, or something thereabout). the last line with the error repeats 3 or 4 times per second, was tricky to catch it in a screenshot.
typing “Stimulus” gives this result, after hitting enter it continued as before.
with tampermonkey disabled, reviews work fine.
so now i wanted to do my reviews, with tampermonkey enabled again (because i like the scripts). error re-occured. checking console, i noticed that it had much shorter chunks of texts right at the beginning, so i’m posting these too in case it’s helpful to you:
collapsed for convenience
first mention of Stimulus:
other stuff, then Stimulus again:
then tens of entries like this:
then they start getting longer:
and end up as in the first screenshot
edit: tried disabling just the queue manipulator and reorder omega scripts, individually and together, problem persisted.
edit: after a dozen or so attempts (possibly more), it suddenly decided to work normally again.