Closed Bug 551748 Opened 15 years ago Closed 14 years ago

Override `user` in template context with the amo user(profile)

Categories

(addons.mozilla.org Graveyard :: Public Pages, enhancement, P5)

enhancement

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: jbalogh, Unassigned)

Details

(Whiteboard: [z])

auth.context_processors injects the current auth.User (or AnonymousUser) into the view. I think the only useful thing we can do with this is access user.is_authenticated(). We want the UserProfile for everything else. 1. Give UserProfile an is_authenticated() method (and make sure it doesn't do more than 1 auth.User lookup). 2. Make apps/users/context_processors.py and inject our user. 3. Make sure the admin still works. If it's having issues, we might have to call our guy amo_user. But I'd prefer to just call it user.
This is kind of already done as amo_user, right?
Severity: normal → enhancement
Priority: -- → P5
Target Milestone: --- → Future
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.