Hidden location prevents registry admins from changing a user's LP ID

Bug #639902 reported by Brad Crittenden on 2010-09-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Curtis Hovey

Bug Description

If a user has hidden his location data then the attempt to change his LP ID by a registry expert will fail since the location information is only visible to the user and LP admins. The failure is:

Module lp.registry.browser.person, line 1749, in change_action
Module canonical.launchpad.webapp.launchpadform, line 414, in updateContextFromData
context, providing=providedBy(context))
Module lazr.lifecycle.snapshot, line 85, in __init__
value = getattr(ob, name, _marker)
Module lp.registry.model.person, line 612, in latitude
return ProxyFactory(self.location).latitude
Unauthorized: (<PersonLocation at 0x10138e50>, 'latitude', 'launchpad.View')<br />

Curtis Hovey (sinzui) on 2010-09-15
Changed in launchpad-registry:
status: New → Triaged
importance: Undecided → High
milestone: none → series-future
Curtis Hovey (sinzui) on 2010-12-03
tags: added: chr
Curtis Hovey (sinzui) wrote :

I fixed this issue indirectly a few weeks ago when I added a rule to no snapshot location.

Changed in launchpad-registry:
assignee: nobody → Curtis Hovey (sinzui)
milestone: series-future → 10.12
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers