# Removing the concept of "slugs" for some languages

**URL:** https://meta.discourse.org/t/removing-the-concept-of-slugs-for-some-languages/26643
**Category:** Feature
**Created:** [2015 年3 月 23 日 00:36 UTC](https://meta.discourse.org/t/removing-the-concept-of-slugs-for-some-languages/26643 "2015-03-23T00:36:35Z")
**Posts on this page:** 1
**Showing post:** 24

<div class="post-metadata">

### 作者： ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### 发布日期： [2017 年8 月 18 日 20:07 UTC](https://meta.discourse.org/t/removing-the-concept-of-slugs-for-some-languages/26643/24 "2017-08-18T20:07:02Z")

</div>

@fantasticfears I am reopening this cause this needs urgent polish (in fact make this your #1 priority)

Issues I have:

- If a topic has the `test งಠಠง` and slug generation method is “encoded” the slug is `test-งಠಠง`. This is a nasty problem cause the actual UI will cause a fight with the browser. The browser sends over the slug as `test-%E0%B8%87%E0%B2%A0%E0%B2%A0%E0%B8%87` and we perform no decoding on our side which leads to an infinite redirect in the topic page, if you hit reload. It feels to me like “encoded” should be always percent encoded.

- If you change slug generation method there is no way of “fixing” the slug cache in “topics” table. There needs to be some mechanism of clearing out the “slug” column on topics. Maybe if you touch that setting it should automatically null out all cached slugs on topic.

As it stands we are seeing some extreme issues here with infinite redirects and there is not clean way of correcting the customer issues.

---

_[View the full topic](https://meta.discourse.org/t/removing-the-concept-of-slugs-for-some-languages/26643)._