I recall seeing a notice that wanikani was going to be down for today, Nov 25th. I can’t see that message any longer. Can someone recall when it was supposed to be back up and running?
Thanks
I recall seeing a notice that wanikani was going to be down for today, Nov 25th. I can’t see that message any longer. Can someone recall when it was supposed to be back up and running?
Thanks
It should be back up by now.
Oh, so the maintenance is over. Is anybody else having trouble with the functionality?
“We noticed too many userscripts working again after our last maintenance, so we’ve decided to mess up some more stuff today.” - WK Team
If you have userscripts, update them.
Even if you don’t have userscripts, it may be worth clearing your browser cache or doing a force reload as I noticed my browser had cached an old, incompatible version of the review page.
This one will just be a temporary annoyance compared to other recent changes. Though I don’t know all of the changes, from what I can figure out with some debugging, they seem like good changes overall.
That said, the data structure changing means that basically any script using WKOF’s ItemData module to do stuff based on the subjects
API (or even scripts doing it directly) is going to break until that gets fixed.
Read the post above mine instead.
None of the scripts I use seem to be affected, including my own simple one (that does use ‘subjects’)
Might be interesting to compare what’s returned now to what the API reference says, but I’m in no hurry since nothing of mine broke
Almost all the scripts I use are broken becuase of this. sigh
Heatmap, Forecast Details, Golden Burn, Overall Progress Bars, and Reorder Omega to name a few.
Update: and just like that they are all working again?.. I had cleared my cache multiple times and it didn’t help. I then turned off Tampermonkey, quit Chrome, reopend it and turned Tampermonkey back on and it all came back to life.
I am now incredibly confused, since I can’t replicate the error myself anymore. I think it may have been a cache thing, like @araigoshi mentioned.
My guess is the internal APIs were broken, rather the properly documented public API v2 that use API keys.
So mobile apps won’t be broken, but the same cannot be said for userscripts. (Especially ones that intercept the internal right-wrong checker or the turbo things, like queue manipulator.)