On Tue, 2009-03-10 at 20:18 -0700, Joshua K wrote: > Hello, > > Is there a way to filter all requests before URLS.py dispatches the > request? > > I am developing a Pinax application. I have some custom menu tabs > across the top, and I limit the visibility of those tabs depending on > flags present in the user's account. I do this by enabling custom > fields in the rendered context; the template contains a series of 'if' > statements to enable the correct tabs. > > On my custom tabs, the URLS of which dispatch to my custom views, > everything works because I set the proper variables in the context. > However, for other Pinax-basic stuff, those routines do not contain > code to set the variables in the context - so the tabs never show. > > How might I go about writing code that handles ALL requests, adding > the required variables, and then dispatches to URLS.py?
You could use middleware to set up things in the session or add things to the request object, I guess. But, really, stop messing with other people's views. It doesn't sound like a good solution to any problem, since those views are already set up to handle particular parameters being passed to them, etc. It sounds like you're futzing about at the wrong layer. Your description of the problem doesn't sound like something that needs to be done on the path into the view. Rather, it's something that needs to be set before the templates are rendered, based on the contents of the "request". Context processors are designed for this purpose. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
