I have jitai installed, but I disabled it on this computer since I was troubleshooting the previous issue and haven’t reenabled it. It’s happening with both kanji and vocab; anytime there’s a custom review due it takes at least five attempts to get it to load.
This topic is temporarily closed for at least 4 hours due to a large number of community flags.
This topic was automatically opened after 4 hours.
The plural of kanji is not kanjis
I’m unfortunately still having trouble replicating the issue… To try and get some more info could you try the following please:
- Right click where the characters should be, then click inspect. It will open up a panel with all the “elements” on the page. If you look slightly above the highlighted one there should be one which says
class="character-header ...
. Could you take a screenshot like the one below so I can see what other classes it has? (e.g. in the case of my screenshot the other classes would becharacter-header-kanji
etc.)
- You might have already tried this but if not, disable all other scripts to see if it works then, in case it’s a compatibility issue.
Hopefully from one of those I might be able to work out what the issue is!
Also, a very weird new error - I did a set of reviews that included some custom items, then when I went back to the dashboard, it showed two reviews remaining. Just to make sure, I clicked on reviews again, and it showed a kanji (not a vocab!!) for a second before redirecting back to the home screen. I thought that was odd so I disabled the script and checked again, and sure enough, it had captured a kanji instead of a vocab. I was pretty sure I read it was set to only capture vocab items, so wanted to bring it up as a potential issue that could be a symptom of whatever else is going on currently.
Thank you - I finally figured out the issue I think! Do you have the custom items set to not appear all at the start of the review session, but distributed throughout? I.e. have this setting set to something other than “Start”?
If so then the 0.6.0 update I just released should fix it. If not then… try it anyway just in case it fixes it

EDIT: Also, in reply to your other question, it’ll currently capture any item it can find, including kanji (and cycle the captured kanji just the same as it does vocab). It is however weird that it showed two reviews remaining for you if there was only one - in that case it should have been showing 0 reviews as that one item would have been the captured one. I’ll look into it as well!
I’ve just finished a couple of weeks with a ton of work to do - so I should now have a few weeks where I can dedicate a lot more time to this script and hopefully get it to a 1.0 release!
That looks great!
A couple of small pointers just to guide you on best practices with how I internally handle stuff:
- For items that don’t have a meaning/reading explanation, instead of
"meaning_expl": "no explanation",
I’d recommend just not including those fields at all. If they’re not included the script will assume there’s no meaning/reading explanation and show a short message saying that (much like your “no explanation”) - and that way it doesn’t take up extra storage space in the json or the imported pack. I did just realise though that you said you’ll be adding mnemonics to them - so if you left them in to make that easier then just ignore this of course! - The items don’t need to (and again for the sake of space saving shouldn’t) include the
"last_reviewed_at"
field in cases like these where you’re not trying to save your progress in the shared pack.
I’ll write some better documentation to link in the top post in the next day or two, but for now here’s a rough guide:
In any case, your joyo kanji pack is looking great! I just wanted to give you some pointers in case you want to improve it even more
Question 1: Is it possible to tell the script to only capture a vocab in the reviews if available?
E.g. if the next review pile only contains kanji and/or radicals, it will still capture that one vocab item from the last review pile until another review pile contains vocab so it can release that item and capture another vocab?
Would that be possible, maybe as an option in the settings to activate if one wants to use it that way? And if so, would it be possible that the user could choose between “capture only vocab / only kanji / only radicals” to fit for different usage styles?
Question 2: When I use the conjugation reviews, I sometimes get asked the same vocab twice. Would it be possible to mark an already asked vocab as such, so it doesn’t show up again, at least within the same session?
Q1: Not yet, but planned. I didn’t end up having time this week to work on this script much but I’ll get that done over the weekend / early next week!
Q2: Hmm, that definitely sounds like a bug, it should only be using each vocab once. I’ll see if I can get that fixed in the same update. Thanks for checking out the script!
Q1: Thank you, but please don’t feel the need to hustle! Take your time as needed.
Q2: Hm, it may be even a current bug on WK’s side. Just did my regular reviews a few minutes ago and got the same item twice, too (your script is currently deactivated). So if you can’t replicate the bug, it may not be your script’s fault in the first place. Never experienced that happening, so I’ll keep an eye on it and test a bit more around as soon as I have new reviews ready.
Finally will have some time in the next few days to look at this - but I just had a glance at them and am wondering how I can word it to make it clear which form it’s asking for… e.g. this one and this one are both “must do”. Do you think in this case for example having “must do (formal)” and “must do (standard)” would be good enough?
I think the best way to differentiate between ~ならない and ~いけない is to put a hint with なる and いく, as ならない is the negative of なる and いけない is the negative potential form of いく. For ~なければならない / いけない we can also add a hint that we want something related to conditionals (ないと is also conditional, but here we can add that it is a “strong” must), and for なくちゃ / なきゃ, we can say that it is the shortened form.
Also, regarding testing the drive feature: I’m now dual-booting Windows and Linux, so I’m now able to test the importing as well
0.6.1 released with some minor changes:
- Added links to relevant Tofugu page in the conjugation reviews info
- Added example context sentences to conjugations
- Added setting to choose which items can be captured (must be at least 1 selected) @MurasakiChou
- Remove text flash when first item doesn’t change (still working on when first item does change…)
I so far haven’t been able to replicate your Q2 bug @MurasakiChou - and if it happened with the script deactivated as well it sounds like a WK / different script issue.
@NeoArcturus thanks for the ideas, I’ll get those added in the next couple of days!
Thank you! Will check out the new setting.
The bug didn’t occur since then, neither with nor without your script activated. Who knows, maybe my foot stood on my WLAN cable in a weird angle that day.
So are they supposed to just be thrown into the reviews section right when you add them? Or is there a way to learn them like a lesson before having to know them for review?
They’re currently just thrown into the reviews - but I’m actually right now making progress on getting them to go through lessons first! That way they won’t suddenly all show up in reviews like they do currently.
When they show up can also be controlled by giving the kanji levels etc. but that specific pack doesn’t currently have any levelling set on it (everything’s set to show up on level 1).
The update for lessons should be released tomorrow afternoon!
Oh, wow! That timing, lol. In that case, would there be something I have to do to make them shift to the lesson area or will they be recognized as “lesson” SRS level? I also don’t mind restarting as it’s pointless to go through 144 of them getting all of them wrong on the first 2 passes (reading and meaning).
If you haven’t reviewed them yet they’ll automatically go to the lessons! So you could just temporarily turn off the script or something if you want to hide them until the update and then they’ll all go into the lessons on their own.