Feedback - Bug Reports

[ThePurpleOrange]

To get them in your reviews it is a bit hidden, but you can go to Content → Lessons on the web app:

Content -> Lessons

This was what I was raising really, that it looks like a couple of items had made it into the live system but might not be fully hooked up - for example, the structure details are also missing from the new items - which made it feel like a feature switch could have been toggled on by mistake, and whilst they may know new items are in the system they might not know it is currently possible for users to add them to reviews.

Missing Structure

EDIT: Beat me to it - sounds like you found them already. Yeah, I don’t usually do it like that - but I wanted to find the new items.

Hmm, feels like I shouldn’t have been allowed to do this - hints and sounds aren’t present as well:

Review for new item

@Asher Should I have been able to add the new grammar items to my reviews yet? I feel like this might be a bit of an edge case - item added.

[Asher]

Yep, there should be no issue manually adding new grammar points that haven’t officially been released yet. The only ones you can’t add are the N0 ones for which there is no deck yet… Well you could add them, but you’d have to guess the url until we get their deck setup .

[veritas_nz]

Hi there! Thanks for the feedback~

This has been removed temporarily as it was causing some performance issues.
We’re working on getting it added back in as we speak!

[SnowTale934]

Hello, I think this sentence, in the ない内に grammar point, links to an incorrect grammar point.

I think the correct link is

るところだ (JLPT N4) | Bunpro

[HayedenBye]

Starting yesterday when clicking on a Kanji to see furigana, the furigana will turns off by itself sometimes after only a second. Additionally clicking furigana on a word with multiple kanji turns on furigana for each individual kanji in the compound word if also present in the lesson. For example clicking on 駐車場 to see ちゅうしゃじょう will also show くるま over 車.

[LagonKa]

Don’t remember if it’s already been reported :
If you manually add a word (from search) to your reviews, it will be added as “manual input” type, no matter how the deck it comes from is set.

I’m using the webapp.

[veritas_nz]

Very good catch! Thank you.
I’ve updated this accordingly. 🙇‍♂️

[veritas_nz]

Hi there!

Is this on the app or the website?

Starting yesterday when clicking on a Kanji to see furigana, the furigana will turns off by itself sometimes after only a second

I just checked your account and it looks like you have your Furigana setting set to Off.
Did you change this setting recently?

Additionally clicking furigana on a word with multiple kanji turns on furigana for each individual kanji in the compound word if also present in the lesson. For example clicking on 駐車場 to see ちゅうしゃじょう will also show くるま over 車.

The 駐車場 example might be only in one specific location of the site
If you can let me know where you found that bug, I’ll take a look!

[veritas_nz]

Hi again!

An individual Grammar/Vocab can appear in multiple Decks, so the Grammar/Vocab selected from the Search screen has no context about which Deck the item is from.

It will default to using the setting defined in your global Settings, here.

If you click on the item from a Deck page itself , it will add a lil ?deck_id=42 on the end of the page’s URL, and when Add to Reviews-ing, it will use the appropriate Deck’s setting.

Hope that helps clarify things!

[LagonKa]

It does, thank you.
But it means that if I ever want to change the review type of some of these, I’ll have to do it manually for each word, right ?
Kinda annoying. Since there’s no other/better method for now, I’d like to be able to change the review type of a whole deck to test my reading too. Related to this.

Maybe vocab should be linked to a primary level deck (Nx).

[HayedenBye]

This is on the app for android. I’ve had furigana off for a while. Probably around 2 months. Previously if I had tapped a Kanji to see furigana it would stay displayed until I pressed it again or until I finished the question.

As for the 駐車場 example that was just one particular instance. I noticed it happen a few different times each with different multiple Kanji words paired with single Kanji words (maybe 2 or 3 cases). I just started a review of The n5 vocab deck and saw it occur in the hint. The vocab word is 方 (kata). In the hint if I click the kanji 向かう only the furigana for it is shown. However if I click the 方向 then the furigana ほうこう is shown above it as well as む above 向かう. See the screen shot attached.

[HayedenBye]

Another example in the hint for the vocab card 先

Another for the card アメリカ

Another for card 止める

[Sasugasm]

It seems like 車 is receiving the wrong furigana in this example sentence.

[meagstudies]

Not sure if this is a bug or if the styling just changed since I last did grammar lessons, but I noticed the Caution and Fun Fact styling is gone. They used to have a red / blue border, but now they blend in with the rest of the text. Is this intentional?

[veritas_nz]

Hi there!
Fixed~
Thanks for the find 🙇‍♂️

[veritas_nz]

This is intentional. Any thoughts RE this change?
You’re actually the first person I’ve seen that noticed it.

[meagstudies]

@veritas_nz

Any thoughts RE this change?

TBH I like the older version because it was more noticeable. Just at a glance you could tell that there was a caution section, which let me know to pay extra attention. But now it just kinda blends in with the rest of the info. Either way I’ll be taking notes on everything, but it was nice to have the caution part stand out.

I also just preferred the old version aesthetically, but of course that’s completely subjective.

[bunnypro]

On finishing a review session, it says I can cram the 2 missed items.
However, when clicking on that, there is only 1 item.
This is replicated every time I go to the cram page for items missed “In the last 24h”.

Screenshot in case it is helpful:

[KentG]

This is how the four new decks look like to me on Android:

• Star Wars
• Yotsubato
• Super Cub
• Onomatopoeia

[happyhelix]

@veritas_nz, @Jake, what’s the situation with the WaniKani sync? Is there just some back end vocab thing out of sorts, or is this some kind of issue from WK’s API change a while back?