The first one is just appending the CSS right? that’s the one I didn’t remove, so it makes sense why it’s working yeah.
Thanks for the help, I appreciate it I spent a bit of time before trying to work out why it was working for the New tab but not the all categories tab I use. I even went to the greasy fork @require link to see if it was something there that was only making it work for the new tab.
I haven’t done programming in years really since I was studying it in uni and so I remember the basic principles. But just removing .has-topics never occured to me lmao such a simple fix T.T again - appreciate it.
@Kumirei I’m wondering about the Regular Tracker. Ever since I installed it, the base number for “Posts Read” was 20,000, but a few days ago, it dropped and is now at 19,547 for me.
This somewhat coincides with the new Book Clubs section, so I wondered whether your script needed to include that new section. But looking through the code, it looks like you just look at the numbers that WK provides you, without even knowing about sections and stuff…
Now I’m wondering about two things:
Has there been a mass deletion of threads that I am not aware of and that would justify the significant drop in numbers?
Is it maybe possible that the WK team does not yet include the new section in the stats?
I don’t think a deletion or new section could be the cause. The number should be 25% of posts created in the last 100 days, with a cap of 20k, and since it’s calculated by discourse the category really shouldn’t matter. From what I can tell the script retrieves the stats directly from the stats generated by discourse. Maybe the forums are just slightly less active than usual?
Oh! Thank you for setting this straight. I somehow confused “posts” and “threads” and so I couldn’t imagine it being 20,000 new threads in 100 days, therefore I somehow thought it’s something like “visiting existing threads”. But yeah, if it’s about created posts, then that’s much more plausible.
Thanks!
@Kumirei,
Do you have a sense for which scripts (yours and otherwise) are using the Reviews table?
I know Heatmap and Ganbarometer. At first, I thought some of the Leech scripts were, but I went looking and discovered that they’re mostly using review_statistics. I see you have a Review Cache library, but I don’t know of a way of seeing what scripts call it.
Oh, I just found your “Longest Review Session” and rwesterhof’s “Wanikani Workload Graph”.
I think several stats apps and sites also use the Reviews table.
Yeah, that’s the most important use that I can think of. I noticed that prouleau is “cheating” (quite cleverly) by looking for a ‘correct’ streak of 1, which means they missed it on the last review. That’s efficient, but it also doesn’t tell you how long ago you missed it unless you combine it with the last review date. And as soon as you answer correctly once, you can no longer tell that it was missed ‘recently’, even if it was only 4+ hours ago (for Apprentice 1).
If I remember correctly, “Extra Study: Recent Mistakes” tracks mistakes in the 24hrs prior to your most recent review, which probably means they’re extracting Reviews data from [your_last_review_timestamp - 24hrs] to [now].
It says “Likes Left 200” and “Next Like N/A,” when I like a post the “Likes Left” counter goes down but the “Next Like” countdown doesn’t update and when I refresh the page “Likes Left” reverts back to saying “200” (while the posts I’ve liked remains liked).
My regular status has also started to show up as 0% from time to time with nothing happening when howering my cursor over the percentage (while normally it will show “Days visited” “Posts read” etc), I can get it back by refreshing the page (which resets my Likes Left to 200 at the same time as stated earlier).
I’m also having issues with the Regular Tracker right now… I usually am somewhat close to the 20,000 posts mark so I like to monitor that and take countermeasures (e.g. scroll through some long thread). But in the past week or so, the number keeps going down although I have scrolled through several thousand posts in that period. I mean it could be the case that my number dropped at the same rate as I was scrolling (because I did the same thing 100 days ago already) but it still feels somewhat odd…
Regular status is pretty helpful for the book clubs, and so I’d like to maintain the status if possible, and the script was of enormous help in that respect.
Which is to say thanks for all your work so far @Kumirei
If the script is not repairable, then be it so, but if something can be done to it, that would be amazing.
I’m noticing the same thing. In fact, I’m also noticing that the like counter is stuck at 0 Received, 150 Left for me as well. The number of posts read is stuck at about 4k, despite my reading a lot of threads over the last week. My topics viewed is also stuck.
I wonder if something has changed in the way these statistics are reported by Discourse.
@Beyond_Sleepy@NicoleIsEnough (nice name change, btw) @Joeni (welcome back!!!)
I took a look at it today and it looks like Discourse changed some of the HTML such that I was not finding the username on the page anymore. I think fixing this should resolve the issues with both the like counter and regular tracker. Let me know if you keep experiencing issues after updating the scripts
My like count is correctly reflecting my clicks now (after liking your post, hehe).
My Regular Tracker isn’t updating as far as I can tell, but I guess maybe it’ll take time to reflect the updated numbers - I’ll let you know if they still say the same thing tomorrow. Thanks for updating them so quickly <3
Pre-edit
Still saying visit streak of 1, which is very much not the case, hehe
EDIT!
10mins later and it’s updated a bunch of the status, though it’s still very much wrong on the streak.
If I recall correctly, this is an internal count from the script though, right?
Thanks a lot for the quick and successful fix! After two page reloads it now shows me the correct number of posts read (and thanks to all the scrolling in my desperate attempt to bump my numbers I’m now at a whopping 117% )
That’s rather suspicious actually because it’s exactly where I’ve been at for the last couple of days
Edit: Hey, it just changed completely! It seems it took a few minutes for the update to kick in. Thanks for all your hard work and continued support, @Kumirei !
I spent a bit of time before trying to work out why it was working for the New tab but not the all categories tab I use. I even went to the greasy fork @require link to see if it was something there that was only making it work for the new tab.
)
