---

** [tickets:#7916] Error when handling user-profile URLs of users with invalid 
names.**

**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-current sf-2 
**Created:** Thu Jul 09, 2015 05:28 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 09, 2015 05:28 PM UTC
**Owner:** Dave Brondsema

Some users have usernames that aren't valid as project shortnames (old 
historical usernames probably).  For these users, the Auth Provider can provide 
an alternate user-project name for that user.  When this happens, and you go to 
the URL using the invalid name like `/u/foo_bar/` then you can get errors like 
this:

~~~~
File '/allura/Allura/allura/controllers/project.py', line 111 in _lookup
  user=user, user_project=True)
File '/allura/Allura/allura/model/neighborhood.py', line 129 in register_project
  self, shortname, project_name, user or getattr(c, 'user', None), 
user_project, private_project, apps)
File '/allura/Allura/allura/lib/plugin.py', line 785 in register_project
  project_name, user, user_project, private_project)
File '/allura/Allura/allura/lib/plugin.py', line 828 in validate_project
  '%s already exists in nbhd %s' % (shortname, neighborhood._id))
ProjectConflict: u/foo-bar already exists in nbhd 559d5efa5421060005224016
~~~~


---

Sent from forge-allura.apache.org because [email protected] is subscribed 
to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.

Reply via email to