On 5/4/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
That wouldn't work, because you pass the argument in the URLconf, andthe URLconf doesn't have access to request objects. The solution hereis either the global TEMPLATE_CONTEXT_PROCESSORS setting or the"context_processors" keyword argument to
On Thu, May 04, 2006 at 12:43:23PM +0200, [EMAIL PROTECTED] wrote:
> Is if possible to define easily a set of static variables that will be
> available inside the templates ?
I know that you're seeking a solution for generic views, but just fyi
here's what I did for my custom views to do
On 5/4/06, Clint Ecker <[EMAIL PROTECTED]> wrote:
> Looking over the docs here:
> http://www.djangoproject.com/documentation/generic_views/
>
> It looks like you can pass in an argument called "extra_context" which is
> just a dictionary. I don't see why you couldn't pass in " request.GET" in
>
Oops, just now noticed you were specifically talking about Generic Views! I apologize! :DOn 5/4/06, Clint Ecker <
[EMAIL PROTECTED]> wrote:You could pass the "
request.GET" or "request.POST" variable into the template context and then access it as follows. I'm making the assumption that you'd
On Thursday 04 May 2006 11:33, [EMAIL PROTECTED] wrote:
> Hi,
>
> Is there a way (I bet there is) to find GET parameters (?page=3=6)
> inside the template of a generic view ?
>
> Z.
I think I've found my answer using TEMPLATE_CONTEXT_PROCESSORS.
Is if possible to define
Hi,
Is there a way (I bet there is) to find GET parameters (?page=3=6)
inside the template of a generic view ?
Z.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this
6 matches
Mail list logo
