We had the same issues, @Falco fixed those issues yesterday.
You should upgrade your Discourse installation (through https://myforum.example.com/admin/upgrade) and after the upgrade you’ll need to “rebake” the slugs. You can follow @Falco’s directions on that:
Those directions worked perfectly for us (btw thanks @Falco!)
This solution has fixed the problem, I had to rebake the slugs.
Amigo @Falco, thank you so much for putting so much effort for fixing the issue.
Also thank you @codinghorror@sam and everyone else who are putting years of experience for something free like discourse in order to make the internet a better place. Thank you
That is not an issue, it’s how it’s supposed to be.
A lot of places don’t support IRIs (URLs with “special” characters), so we are encoding those (those lots of %XX) so the will work anywhere (like when posting to Twitter).
Your browser is smart enough to show it decoded for you, so you don’t have to stare at it in the location bar.
Several people on community.wanikani.com already noticed the fix for the original issue, and it looks good to me as well. However, I’m seeing the same subcategory issue others have mentioned (404 error for subcategories containing unicode characters). Since it’s a hosted site, can someone deploy the latest fixes and do the rebake (if necessary), so I can verify it’s fully fixed? If not, I guess I’ll check again in a week.