Users are discussing issues with URL formatting and accents in Discourse categories. danilomatos reports that category slugs automatically include accents (e.g., dívidas), causing URLs to display incorrectly and preventing edits. Steven suggests avoiding special characters in slugs and using ASCII alternatives like dividas. Falco recommends changing the slug generation method to encoded to preserve accents, but danilomatos clarifies they don’t want accents and still face the issue. Falco provides steps to fix it: switch to encoded, edit the slug to ASCII, then revert the setting. saquetim shares a similar experience, noting that even with ascii slug generation, an accidental accent in the slug breaks editing, and suggests Discourse should validate slug content based on the setting.
however I realized after it was generated, the others I managed to edit, but it gave an error 404 when I was going to edit and this was the only one that doesn’t run out of the accent.
even the questions were being added with accents when I had them. but the questions were normal without touching anything now, I just cleared the cache. this category does not edit, it deletes
The slug generation method is set to ascii but I accidentally typed the slug with an accent. After that I couldn’t enter the edit page of the category.
In the end I fixed the problem entering the rails console and fixing the slug there.
It’s not totally Discourse fault since that depends on the user typing an accent when there shouldn’t be one. But it would be cool if the system checked if the slug typed has only ASCII characters if the slug generation method is set to ascii.