Console returns this to me:
As for the “ground” radical - what is this? I have migrated to Lv24 last night, so it is like below
1 Like
Wait, are you on Firefox?
Nope, on Google Chrome.
Well, then I’m not sure what the cause is. It seems to me that WKOF is not managing to cache the items, maybe? We’ll see what @rfindley thinks
I tried the script with Kawazoe’s api key, and it’s working fine for me (on latest Chrome on Windows).
First thing I would suggest: If you are running a lot of scripts – especially ones that work with parts of the API that wkof doesn’t cache, such as review history, it’s quite possible you’ll hit WK’s API rate limit. In that case, the wkof ‘loading’ window may pause without progress for a while. But rest assured, wkof is still querying the server periodically until the rate limit opens back up, and then it will finish gathering data. It may take up to a minute before it starts making progress again.
If you want to confirm whether that’s happening, open the Network tab in the dev tools (Press F12, then click the Network tab) and take a look at what’s happening. You should see some error responses from the WK server.
Second thing I would suggest, since I’m not familiar with the internals of Heatmap, is to clear the wkof cache. Enter this in the Javascript console, and press enter:
wkof.file_cache.clear()
Then refresh the page and see if that fixes it (keeping in mind, again, about the rate-limiter).
1 Like
By the way, @Kumirei, I noticed you have some CSS in Heatmap:
// CSS that makes the settings dialog look like it should in dark mode
[...]
It also does some things when not running dark mode.
Since I don’t have reviews anymore, I don’t normally have Heatmap enabled, nor do I run ‘dark mode’ (is that referring to the Breeze Dark script?). But when I turned on Heatmap, I noticed the tabs on the Settings window (of all scripts) were a bit ‘off’.
Here’s with Heatmap’s CSS rules:
And with them disabled:
In the first image, it’s hard to tell which tab is selected.
Does ‘dark mode’ have a marker in the CSS, such as an attribute on the <body> tag, that your dark-specific CSS rules can be keyed to?
2 Likes
Ah, thank you for noticing this. Breeze Dark (and possibly other themes) doesn’t have any styling for the settings dialog, so it looks pretty bad with the rules that just happen to apply; I intended to remedy that. Not sure if something changed in either Breeze Dark or WKOF since then, or whether I just messed up from the start, but the CSS is supposed to ensure that it looks the same regardless of theme. I made it apply to all settings dialogues because I figured it would be nicer for the users if other scripts’ dialogues looked normal too. I’ll make sure it looks right, though.
1 Like
I was wondering why Heatmap didn’t run on my Safari, and managed to get it working by whitelisting https://www.wanikani.com at Tampermonkey Settings > Security (You may need to switch Config mode to Beginner if you don’t see the Security ob Settings page).
So if someone else had the same problem, this might help (in addition to re-installing etc.)
1 Like
PS: erased the version and posted the message on the right place
Hey guys,
this is the error i get with the heatmap
I already tried everything you suggested before in this thread but it still does not work…
The user script in the first box is the heatmap. It just says so when you hover on it.
any idea?
1 Like
Thanks! I would eventually have seen it here as well, but when you post in the Heatmap thread I get a notification and look into it asap
1 Like
Now I get this
Sorry for my bad luck lol
1 Like