I have a generic view for an object in a basic bug tracker app. It shows things like 'title', 'description', 'resolution', etc.. and that is all working fine with a generic view.
However, I'm trying to send a piece of info that involves a completely different model and not finding a pleasant way to do it. I need to use request.user, which does not seem to be available in urls.py, as well as the object id of the original model. I tried for a while to get extra_context to work, but kept running into the request.user issue. Also, I'm not sure I'll have access to the object id that early in the process--am I wrong here? Is there a nice way to extend the generic view to fit this in? I thought about making my own view that would act as a wrapper for the generic view but was unable to make it work. If it were a standard view, this would be simple--but as a generic view it is so black-boxed I don't know where to start. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
