# Usernames in admin URLs cause routing problems

**URL:** <https://meta.discourse.org/t/usernames-in-admin-urls-cause-routing-problems/31825>\
**Category:** Bug\
**Created:** [6 Agosto , 2015 11:21 UTC](https://meta.discourse.org/t/usernames-in-admin-urls-cause-routing-problems/31825 "2015-08-06T11:21:23Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [7 Agosto , 2015 07:12 UTC](https://meta.discourse.org/t/usernames-in-admin-urls-cause-routing-problems/31825/4 "2015-08-07T07:12:21Z")

</div>

I’m really with @sam in this case:

- So far, the blocked usernames only contain confusing usernames (that look official or unintentional), not ones that break the system.
- This list is admin-editable, nothing is preventing the admin from removing entries. This would have non-obvious side effects.
- If I understand correctly, changing the default won’t affect systems which already customized the list, for example by adding an entry.
- I have a strong feeling that there are more cases like this. I think that `account-created` is safe only by coincidence, not by careful consideration (“there could be a username here, so let’s add an invalid character…”).

Also, I don’t see the drawback: `/admin/users/1/sam` is perfectly fine for the admin’s eyes (heck, `t/usernames-in-admin-urls-cause-routing-problems/31825` is fine for everyone’s eyes!), still has the slug (which is nice), and even works as a permalink across username changes!  
It would also fix some issues for free: For example, after renaming a user, the back-functionality breaks, since the old URLS 404.

---

_[View the full topic](https://meta.discourse.org/t/usernames-in-admin-urls-cause-routing-problems/31825)._