As I said, work is in progress. Now it just shows last two level vocab that <Guru. Give us about a week.
Eekone said... As I said, work is in progress. Now it just shows last two level vocab that <Guru. Give us about a week.Heh... last two levels. I wondered about that. I had been thinking: do people stay on current level long enough to worry about vocab status of current level? Granted, I was a fast leveler, so that probably affects perspective. I hadn't considered adding vocab, since half of it was still locked when I leveled up.
Anyway, in the meantime, the stats page has current vocab status [https://idigtech.com/wanikani/#items.wk.voc], if that helps.
It’s not about worrying about vocab status. Just a comfort way to review your words between reviews (derp).
I just want to have all my stuff together on the dashboard. Why use additional sites and different pages if there is a lot of free space?
Made progress indicator with some weird css.
______
Is it okay I post development notes in your topic, rfindley?
Hmm I have everything installed through tampermonkey but I realised (a few weeks later) that I have no SRS progress rings. Any ideas? ><
SwiftSign said... Hmm I have everything installed through tampermonkey but I realised (a few weeks later) that I have no SRS progress rings. Any ideas? ><Can you post a snapshot?
You're just talking about the circular outline thingies, right? But you are seeing the circles in general?
The progress rings are only on Apprentice 2-4 and Guru 2 items. If everything is at Apprentice 1, for example, you won't see a ring yet.
Hi, thanks for an amazing script. Any chance you could make the circle things bigger? I like to test myself by hovering, but I have to zoom a lot to read the kanji.
Franken said...Hi, thanks for an amazing script. Any chance you could make the circle things bigger? I like to test myself by hovering, but I have to zoom a lot to read the kanji.
Try adding the bold text below to the script, around line 141:
window.wkdpp.progress_css =
'.progression .lattice-single-character li a {font-size:26px;}'+
'.wkdpp-progress {background-position:39px 0px;background-repeat:no-repeat;background-image: url("##PROGRESS_IMG##");}'+
'.progression .lattice-single-character li {padding-top:3px;padding-bottom:3px;margin-top:2px;}'+
'.progression .lattice-single-character li a {font-size:26px;}'+
'.wkdpp-progress {background-position:39px 0px;background-repeat:no-repeat;background-image: url("##PROGRESS_IMG##");}'+
'.progression .lattice-single-character li {padding-top:3px;padding-bottom:3px;margin-top:2px;}'+
I pushed it to 28, works great, many thanks!
rfindley said...Yeah, just the progress rings. I can see the kanji - this is what it looks like (these kanji are apprentice 3/4, but no ring showing). I tried removing/re-adding it to tampermonkey but no change :s:SwiftSign said... Hmm I have everything installed through tampermonkey but I realised (a few weeks later) that I have no SRS progress rings. Any ideas? ><Can you post a snapshot?
You're just talking about the circular outline thingies, right? But you are seeing the circles in general?
The progress rings are only on Apprentice 2-4 and Guru 2 items. If everything is at Apprentice 1, for example, you won't see a ring yet.
SwiftSign said... Yeah, just the progress rings. I can see the kanji - this is what it looks like (these kanji are apprentice 3/4, but no ring showing). I tried removing/re-adding it to tampermonkey but no change :s:Hmm... can't really think of a reason this wouldn't be working. I'd have to take a look at your browser.
I have a screen-sharing server if you want to set up a debug session sometime.
I’m having a similar problem: all my kanji for my current level are bright pink, even though I haven’t learned them yet. They used to be fainter before I had learned them. I do get the ring showing for the kanji I’ve made progress on, though.
1 Like
Same on the bright pink (that used to be just the unlocked apprentice ones. Now it’s locked and unlocked apprentice but the unlocked have the progress ring) But actually they are now all out of sorts in general for me. Guessing it has to do with whatever that update Viet posted about is (but that not one word of it made sense to me lol):
And yes, in case it’s in question, I do have master and enlightened items and that is not part of the mistake. I’ve been on this level for 4 months. Sue me.
1 Like
Same problem here. Probably do to the changes that WK put in recently.
Just in case @rfindley isn’t following this, I’ll tag him.
1 Like
I’m guessing this is related to the above issue, but the timeline refuses to load anymore. It just stops midway and the javascript console pukes out a bunch of 403 forbidden (for some of the requests, around half of them go through fine). Also related to the recent changes in WK, perhaps?
EDIT: For some reason I thought this was the Ultimate Timeline thread…but they’re actually different scripts… 
I’ll look into this in a few days. I’m under a work deadline at the moment.
4 Likes
頑張ってね！
Thanks for your hard work!
@rfindley I took a little bit of a look at your script. I think the WaniKani api changed a little recently. When you are getting the list of radicals and kanji, it looks like it is only returning the list of unlocked kanji/radicals instead of a full list. Since the service isn’t returning all items, the locked list items on the page are ending up undefined in the code.
I was able to fix it locally by updating it to replace undefined references with empty data instead of exiting the loop. I had to add a “meaning” because the capitalize_words function doesn’t check for undefined.
if (data === undefined) {
dlog(1,'wkdpp: Unable to find kanji "'+character+'. Substituting empty data"');
data = {
"meaning": "unknown"
}
//return;
}
I have to say kudos on the rest of the script though. Because of all the null/undefined checks, it was really simple to just add a (mostly) empty object to get the functionality working again. I wish all the code where I work was that resilient…
2 Likes
Thanks so much for the head-start! I was able to jump right to the problem instead of having to hunt down what was going on.
Also, I’m glad you liked the code. As a contractor, robustness is a big part of the job. I like when my code ‘just works’, so my clients get years of use out of it without ever having to open it up. One of my favorite pieces of code is a task scheduler that has been reused in hundreds of places, and not a single line of code has ever had to be changed. If only that happened more often…
Here’s the full fix:
[v1.4.0] - Repair after WK update: API does not return locked items 
4 Likes
Little known fact, but in his spare time, rfindley discovers new prime numbers by hand, feeds the world’s starving using only three fish and solves conflicts in the Middle East just by his mere presence.
(ie, thanks for the fix :))
3 Likes