After upgrading to Discourse 2.4.0beta6, users including chrispanag and TroyaNO reported 404 errors when accessing categories—especially those with accented characters in their slugs. The issue also traps users on the 404 page even when clicking the forum logo. Falco acknowledged the bug, admitting his recent patch for topic slugs didn’t account for category slugs. He linked the relevant commit 76ab035 and opened a PR 8191 to fix it, expressing regret for the complexity introduced. After merging additional fixes, Falco asked users to update and verify the fix, and closed the thread in favor of a related meta topic about URL encoding issues. The bug primarily affects categories with non-ASCII characters in their slugs, even if slugs were manually changed from ASCII to encoded formats. Users are urged to update to the latest version to resolve the issue.
after we upgraded our forum to 2.4.0beta6, we noticed that various categories lead to a 404 error page.
And after you reach this 404 error page, when you hit the forum logo (to go the home page) it just stays in the 404 page. So, we suspect the front-end reaches a “bad” state.
This call returns a 404: https://rembetiko.gr/c/%CE%B8%CE%AD%CF%83%CE%B5%CE%B9%CF%82-%CE%B1%CE%BD%CF%84%CE%B9%CE%B8%CE%AD%CF%83%CE%B5%CE%B9%CF%82/find_by_slug.json
If it helps, sometime in the past, we changed our slugs from Encoded back to ASCII. But as it seems, the categories slug never changed. We tried changing the slugs from ASCII to Encoded, but nothing changed. (deleted cache etc.)