@BJennWare I think this is most likely due to the fact that I removed a redundant CSS width rule in my version. You might also be interested in knowing that I added a setting for whether the user wants the element positioned by the search bar or below the SRS counts.
2 Likes
Hey guys - sorry I was a bit absent from this site. But my motivation for japanese is higher than ever (I guess).
I think the best would be to remove the progression percentages completely from script.
3 Likes
I guess I will leave the critical hightlight as it is - I like it that it’s only a little reminder - not that you should wait 8h for your reviews
You are all right with the lesson information - they are confusing to say the least 
I will try to fix it.
Btw. I removed the progress percentages from my sript and everything should work again
3 Likes
Thank you BJennWare … I appreciate the changes you have made 
Wow love it!
1 Like
For anyone wanting to change the font of the lesson/review count, just add this to the GlobalStyle part of the script.
- Replace RiiTegakiFude with your font.
- Replace normal with bold if you want bold.
- Font-size is self-explanatory.
- Padding is the size of that white border. 5px is the website default.
.lessons-and-reviews__button span {
font-weight: normal;
font-family: RiiTegakiFude;
font-size: 15.0px;
padding-top: 5px;
padding-bottom: 5px;
}
I’m glad you like it @BJennWare and see you made the changes to the original script.
I have however changed double-character labels back to single-character labels.
Definately looks less cluttered, especially when one is drowning in lessons and reviews like I am right now.
Before:
After:
2 Likes
True is a bit cleaner. I’m not completely sure if the meaning of the single kanji is correct so I’m trusting you on that
Here’s an additonal add-on for styling options. Adding fonts is the same process as in Jitai.
Available here: Wanikani Integrated Dashboard Overhaul Settings
Settings Panel is accessed by: Profile Icon > Scripts > Settings > Integrated Dashboard Overhaul
1 Like
Hah thats cool! Now everyone can style it the way he or she wants 
You should add // @include /^https?://(www|preview).wanikani.com to the top of the script though.
If you click on the big WaniKani Icon at the top it forwards you to https://www.wanikani.com/
Oh yes these are good,
we use kanji like this in Japan much like abbreviations are used in the west:
部 for 部首 (Radical)
漢 for 漢字 (Kanji)
語 for 単語 (Word) and 語彙 (Vocabulary)
Spoilt for choice now, nice!
It unfortunately does not work correctly though:
Prior to install:
After install:
Notice the missing 176 Vocab Lessons and 11 Reviews for some reason??
1 Like
Good to know - thx
Oh woops! Yeah there was a new parsing error after the original script was updated. I thought I uploaded the update but I didn’t 
. Anywayyyy the new update is live so feel free to try again 
:
2 Likes
I am getting incorrect results for the critical review feature. It is listing a radical that I have already cleared and have another review for next week as the critical review instead of one of the kanji for the current level that I have yet to pass. It seems to be related to the filtering predicate in lines 207-209. Where is item.data.passed defined? Is that a part of API v1 that didn’t get updated? In that case comparing the current date with item.data.passed_at should work instead for API v2.
const radicals = assignmentResponse.data
.filter((item) => item.data.subject_type == 'radical' && !item.data.passed)
.sort((a, b) => a.data.srs_stage < b.data.srs_stage || (a.data.srs_stage == b.data.srs_stage && a.data.available_at > b.data.available_at) ? 1 : -1);
1 Like
See here
In particular this part (bold added)
We will be dropping the endpoint /srs_stages and the attributes assignment.srs_stage_name , assignment.passed , reviews.starting_srs_stage_name and reviews.ending_srs_stage_name on August 17, 2020 .
Is item.data.passed an alias for assignment.passed? This change went live yesterday.
Looks like the culprit to me. Thanks for the link.
The script works again with the following patch applied.
diff --git a/Wanikani: Integrated Dashboard Overhaul.user.js b/Wanikani: Integrated Dashboard Overhaul.user.js
index ec3bf80..0ac4fee 100644
--- a/Wanikani: Integrated Dashboard Overhaul.user.js
+++ b/Wanikani: Integrated Dashboard Overhaul.user.js
@@ -205,7 +205,7 @@
wkof.Apiv2.fetch_endpoint('assignments', {filters: { levels: [level], subject_types: ['radical', 'kanji'] }}).then(assignmentResponse => {
console.log(assignmentResponse);
const radicals = assignmentResponse.data
- .filter((item) => item.data.subject_type == 'radical' && !item.data.passed)
+ .filter((item) => item.data.subject_type == 'radical' && !item.data.passed_at)
.sort((a, b) => a.data.srs_stage < b.data.srs_stage || (a.data.srs_stage == b.data.srs_stage && a.data.available_at > b.data.available_at) ? 1 : -1);
if (radicals.length > 0) {
I don’t see how this will ever be true?
1 Like
Ah, thanks for catching my time traveling blunder. Boolean coincidentally giving my desired behavior != correct. I’ve updated my previous comment.
1 Like