[Userscript] Burn Reviews (ver 2.2.5)


#1

It appears that the old version of Burn Reviews is no longer being maintained and no longer works so I am now taking over maintenance of it.

This script adds a section to the WaniKani dashboard that gives random reviews of previously burned items. If you get a review incorrect, it will ask you if you wish to resurrect it.

Like other userscripts you will need Greasemonkey (Firefox) or Tampermonkey (Chrome) to use this script.

This is what it looks like
Cropped screenshot

Language can be set to English or Japanese

Now works with the Mobile layout too!

Get the script on Greasy Fork.

If you find any bugs or have a feature request, open an issue on the github

Known issues:

  • Resurrect button doesn’t work. This is because of a change in Wanikani’s resurrect URLs that uses new item IDs that are currently only present in version 2 of the API. Given that API v2 is still in Alpha, and is subject to change, this issue will likely persist until the new API reaches full stable release, as it is not worth the rewrite until then.

Update Log:

v 2.2.5

  • Fix for bug where english answers ending in ‘n’ weren’t accepted.

v 2.2.4

  • Fixes for changes of URLs that the script relied on
    • WanaKana now included using an @require directive (thanks @rfindley)
    • Fix for url and page layout change when automatically fetching the API key
  • Trailing n in responses is replaced with ん (thanks @Subversity)
  • Fix for capturing Enter key when using WK search field(again thanks @Subversity)

v 2.2.1

  • Fix for new bug that crept in

v 2.2.0

  • Massive amounts of refactoring, like wow.
  • Automatically fetch API key instead of requiring manual user input
  • Actually works with wanikani’s fluid layout now
  • Small styling change to make the buttons more even on both sides.
  • Burn reviews works on not just /dashboard
  • Fix for macOS scaling issue.

Revive burned Items?
The New And Improved List Of API and Third Party Apps
[Unsupported] App Store script
Global review after 10 levels suggestion
Is it ok to forget?
Useful (to me) feature request
About burned items / Burned Reviews... other options besides current API?
Any way to see all burned items?
How do you review burned items?
[Old version][Userscript] Burn Reviews (v1.0.0.3)
[Unsupported] App Store script
#2

edit: (apologies for the double post, I put this on the other thread first, but this is where it belongs)

Hey jonnydark thank you for getting this script running again. I’m encountering a problem whereby kun-yomi readings don’t seem to exist and are therefore marked wrong. Check out the screenshot:



I typed “さま” for 様 and it came up as incorrect. Same with 買 when I typed ”か".

I’m using Safari on a MacBook os x el cap.


#3

Definitely going to give it a try since I like the idea of it and the old one didn’t work anymore when I found it.

Edit:
I just tried it out, entered my API key and it doesn’t seem to work, it just shows me the same as the old script.
I did try it with all other scripts disabled (and there shouldn’t be anything else interfering), but no luck.


#4

@chrispthompson Hey! Thanks for reporting this. Your bug has been filed here: https://github.com/jonnydark/wanikani-burn/issues/1
So far I’ve only managed to fix the issues that were superficially stopping it from working, so it doesn’t surprise me that the code has rotted in a few places.

@
RayderBlitz Thanks for letting me know I’m going to need a bit more information before I can fix that issue, because naturally I can’t reproduce it. For the sake of my own sanity, can you file a bug here https://github.com/jonnydark/wanikani-burn/issues
If you can provide a screenshot of the problem as well as what browser you’re using. Also if you could tell me if there are any errors in the console (press F12), that’d be very helpful.

Thanks :slight_smile:


#5

Oh right, my bad.
For some reason I managed to not even think of that…

Well, now I created a new issue with your requested information and some bits I thought might be helpful.


#6

@RayderBlitz Thanks, I just saw that. I’ll look in to it when I can :slight_smile:

@chrispthompson That issue is now fixed, the API had changed since the script was originally written. If you update to the most recent version (2.0.1) the kunyomi readings should now be correct.


#7
jonnydark said... @RayderBlitz Thanks, I just saw that. I'll look in to it when I can :)

@chrispthompson That issue is now fixed, the API had changed since the script was originally written. If you update to the most recent version (2.0.1) the kunyomi readings should now be correct.
awesome! Thanks again for bringing this script back to life! 

#8
jonnydark said... @RayderBlitz Thanks, I just saw that. I'll look in to it when I can :)
Thank you.
I look forward to seeing how much of the burns i actually remember now, when the script works.
No hurry though, just work on it whenever you're bored or smth. c(°_:_°)つ

Also, just in case you plan to also add features (and if I didn't just miss that one), an option to prioritize older burns might be pretty neat.
I'm only throwing it out there, no pressure - already happy that someone decided to pick the script up at all.

#9

Probably a stupid question, but should I uninstall the other Burn Reviews and then install this one or does this one overlay/in addition to the previous script (is that what y’all mean by ‘fork’?)

~frankiebluej


#10
frankiebluej said... Probably a stupid question, but should I uninstall the other Burn Reviews and then install this one or does this one overlay/in addition to the previous script (is that what y'all mean by 'fork'?)

~frankiebluej
 Yes you should uninstall the old one. The old one has bugs and is no longer being maintained so remove it and install the new if you want the script to keep working.

As for what a fork means - https://en.wikipedia.org/wiki/Fork_(software_development)

#11
jonnydark said...
frankiebluej said... Probably a stupid question, but should I uninstall the other Burn Reviews and then install this one or does this one overlay/in addition to the previous script (is that what y'all mean by 'fork'?)

~frankiebluej
 Yes you should uninstall the old one. The old one has bugs and is no longer being maintained so remove it and install the new if you want the script to keep working.

As for what a fork means - https://en.wikipedia.org/wiki/Fork_(software_development)
 Thank you for you response, it was very helpful, appreciate you taking the time to do so. ~frankiebluej

#12

Fantastic. Haven’t tried it yet (still neck-deep in regular reviews) but I am glad someone finally got around to fixing this essential piece of wanikani.

Thank you.

May your mushrooms always be sauteed and your onions always grilled.


#13

Sorry this update took so long, there was a shitton of refactoring to do. The codebase should now be more sane such that if I (like the previous maintainer) lose interest in maintaining this script at some point in the future, then it can be picked up easily by someone else. 

Naturally as with any update there will probably be bugs so if you find them, please raise an issue over at the github: 
https://github.com/jonnydark/wanikani-burn/issues


#14

Wow, this is the first time ever this script has worked for me. Have been interested by the idea since I started in November,

Just wanted to say thank you for making the effort, it’s very much appreciated!




#15

FYI, for anyone wanting to get this script working again, add the following line to the header of the script, right before the @grant line:

// @require https://greasyfork.org/scripts/19781-wanakana/code/WanaKana.js?version=126349

And around line 912 or 913, remove the following line:

    importWanaKana();

I played around with this for a moment, and if you answer an item wrong, the popup that asks if you want to resurrect an item doesn’t seem to have a way to cancel it. But you can click on the “New Item” button to close the popup and move on. Kind of goofy, but it is what it is.


#16

Ah, looks like the the location of wanakana moved.

I’ve implemented your fix in to the main branch @rfindley

Looks like this issue had been open for over a week https://github.com/jonnydark/wanikani-burn/issues/20
I totally missed it!

Sorry about it breaking everyone, if you update to the latest version (2.2.2) on Greasyfork it should be fixed


#17

I updated wanakana to 2.0 recently, and if you want a safe target you can always reference:
http://wanakana.com/assets/js/wanakana.min.js
Every npm publish updates that file.

[edit] or for https: https://raw.githubusercontent.com/WaniKani/WanaKana/gh-pages/assets/js/wanakana.min.js


#18

Ahh… I never made the connection between your WK username and your real name. Good to know!

FYI, I linked to a greasyfork.org copy of Wanakana due to greasyfork’s terms-of-service. External links must be to an approved server, and in cases like github (via rawgit.com), the link must be to a commit-specific version… which is probably a good idea anyway, for several reasons.

Thanks for the Wanakana update info! It’s a nice piece of software :slight_smile:


#19

I just grabbed the v 2.2.2 script (first time user) and it doesn’t seem to be working. I see that I no longer need to manually add my API key but it’s just stuck on ‘Retrieving radical data…’ and doesn’t seem to do anything from there…

What am I missing?


#20

Do you have any errors in the Javascript console? (press F12, click on Console tab)
Do you have TamperMonkey or GreaseMonkey script manager installed?
What OS and browser?