Update: I just got my Cram 50 badge after my 55th session.
I’m having this issue right now, I think it’s a vocab item I added manually. Also, when the question repeats without info, it asks me to use kana when I answer (for vocab asking for the English translation)
Edit: Managed to do the review on mobile, no problems there.
I’ve noticed something similar, at least when I was using the old cram feature.
In my case, I think it has to do with cram sessions where I exited a new session without doing any reviews—they seemed to count toward my user stats but not to badge achievement.
btw, are you using cram 2.0?
Yes, I am using cram 2.0. And I have not exited any cram sessions without doing any reviews that I can remember. But now that you mention the old and new cram, could it be that I had used the old cram 5 times before switching to cram 2.0? I honestly don’t remember, but I just started cramming more frequently, so it would not surprise me
I switched to beta reviews today and it’s mostly resolved the issue for me; my Reviews count constantly shows a 1 from whatever broken review is in there, but I have zero issues during the review session now.
My previous session count carried over from the old cram, so it is definitely possible!
I did a lot of cramming before 2.0, so I haven’t had a chance to see whether the old session count carries over towards badge achievement… I would assume so, but you bring up a good point! I hadn’t thought of that.
FWIW, I asked a question in November about how the new cram (doesn’t) integrate stats on crammed items (# correct/incorrect). Session stats seem fine though.
The tool we use internally for marking up furigana (JV Furigana) unfortunately doesn’t allow us to do this.
I think it’s because the character 「ヶ」isn’t counted as kanji, and isn’t available as a candidate for furigana-ization.
We could potentially switch to a more robust furigana system in the future (e.g. curly braces + normal braces).
The N5 vocabulary word " いらっしゃいませ" (welcome) is not accepted when it is written like so.
however when it is typed as " いらしゃいませ" it seems to get accepted. I tried reporting via the review screen, but the report button was not working.
On the Dashboard, in the “Your Progress” section, the “beginner” tab and “beginner” button aren’t working for me. The rest of the levels are working.
Hello. The new Cram function is very good but i don’t know if i’m doing something bad or not, but when i cram a little bit it stopped and i’m then on this page.
If i click on continue session it freeze indefinitely on “loading cram session”, basically cram is not usable for me.
[Edit] : So it maybe have to do with the complete mode option, i will now cram with it checked, but i don’t think i understand really how the craming session work when this option is off.
Not sure why “+0” experience sometimes appears when doing reviews - I think perhaps these might be the vocab which I’ve already got right in the review session but come around for testing again and get them right again.
As far as I know, ghosts and items you get wrong display nothing in the experience bar, rather than “+0”.
Example (I have other examples if it helps):
Is this something you just noticed happening very recently? I remember discussing this bug when I was internally testing Review Beta 2.0 prior to public testing, but it seemed like it got squashed back then. Is this happening only with vocab?
Been happening for a while, I think, in the order of weeks.
Not sure whether it’s only for vocab though - I’ll try to look out for it when doing grammar reviews and post back if I notice it!
I’ve just trying Bunpro’s vocab learning feature for the first time, I’m using the N5 deck set to “Bunkpro Cloze” mode, however unlike for grammar study I can’t seem to undo and retry when I make a mistake.
Is there a way to enable this?
I opted out of beta and the new review system and it works fine now. I had another problem with the beta “review 2.0” system where it would tell me that there weren’t any reviews left (when there were).
I looked at the bad JSON reply again and found the problem word and was able to remove it from reviews in vocab and fixed the issue
@melisma and @ThisIsntTheWay ,
Are you still getting this error? I’m looking into it now, and I’m not getting it but my request to the server is pretty slow, so I think you might be getting timed out.
Yes, still getting the error