Closed Bug 1011194 Opened 12 years ago Closed 11 years ago

Replace Django User + UserProfile with custom User class

Categories

(Firefox Affiliates Graveyard :: affiliates.mozilla.org, defect)

Product:
Firefox Affiliates Graveyard
Component:
affiliates.mozilla.org
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: osmose, Unassigned)

Details

(Whiteboard: [2.0 post-launch][qa-])

We're already adding like 4 custom methods to the built-in Django user class, plus changing it's __bases__ to get it cached, plus we have a model for user profiles that needs to be joined whenever a user is fetched. Might as well go with a custom user class at this point. This isn't user facing at all, in case you were curious.
Hey mkelly, did we ever move forward with this bug? Do you still want to make the changes? How much of a time cruncher is this and how helpful is it?
It's helpful to keep around as a reminder, and I still want to do this, but we really just can do this whenever. I wouldn't put any priority on it.
All work on Firefox Affiliates is on hold as the Affiliates program is slated to be phased out in 2015.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Product: Firefox Affiliates → Firefox Affiliates Graveyard
You need to log in before you can comment on or make changes to this bug.