Another thing to note is that groups with a dot in the name are now deemed invalid according to the validation pattern in the group form, but groups with a dot in the name created before the validation was introduced still exist.
Having the same issue for group name uateam.tv.
Quoting my gitter report:
I've registered and gitlab.com just yesterday, created a group and it worked. But today I returned to the page, which was open in my browser, and noticed 404 instead of members list page.I've found out, that /<group_name/ URL is accessible and looks fine, but pages matching /groups/<group_name/<action> all return 404.
So as @DouweM mentioned we cannot change existing group names since that would break gitl clone paths, etc. What we should do instead is change our code to have the dot work again.
Do you know if a decision was made to disallow the creation of groups containing a dot in the name/path?
@markglenfletcher no it should work. So its a bug. We have restriction when . can be first or last symbol of the name but regular name like group.with.dot should work.
OK it appeared to be a simple fix since we just missed constraints in group routing + we dont have tests for those. Once MR is green I will send it to review
This issue is indeed fixed, but the form regex mentioned by @markglenfletcher was not updated.
This currently prevents editing group settings via the webinterface.
Example: Trying to change group-avatar is not possible, since "Group path" complaints about "Please choose a group name with no special characters." while editing an (existing) group containing a dot in its name.
(Tested with "GitLab Community Edition 8.14.0 cde955c9")