Could probably easily route everything through the rad/kan/voc instead of id. Would probably be better storing it as an object somewhere in the script since what is already used takes up a lot of space in localstorage.
FYI, I’m putting together a framework that uses indexeddb instead of localStorage, since indexeddb allows much more storage and provides indexed lookup. The framework will cache all WK data, including the new IDs, and will have its own simple API for pulling data from cache.
xMunch pointed out the easiest way to fix this temporarily, so here’s a quick attempt at implementing it.
No guarantees that it works 100%, but during the little testing that I was able to do, it seemed to work properly.
Hmm… I wasn’t able to duplicate your error, though I don’t have the developer edition of Firefox. Could you check the Javascript console? Maybe the errors there are more useful.
So, in this fixed version, I don’t have errors, but it doesn’t seem to be ordering them as defined… Do I have to clear out my reviews before it starts being able to work?
There’s no error in the console. My sort criteria is Radical > Kanji > Vocab. I’ve tried all manner of orders and it’s just completely random when I hit force-reorder.