Le 25/09/2010 14:52, werefr0g a écrit :
You're assuming that form are called only from views. Some Form
methods are mostly used inside templates like as_p for example.
Sorry for the double post but this statement is far from accurate (to be
kind with myself). You can use form in a template
Hello,
You're assuming that form are called only from views. Some Form methods
are mostly used inside templates like as_p for example. Another
assumption you made is that all url point to html ressources. Images,
javascripts can have their url. Generation of pdf, csv and AJAX
mechanics are
isn't it unnatural to force user go around the site before going to the
right place? Anyway, i will go around with all the ways first before making
decision
Thanks everybody
On Sat, Sep 25, 2010 at 1:30 AM, Nick Arnett wrote:
> I was tackling this problem recently and
I was tackling this problem recently and found several approaches by
searching for Django login form. I ended up using a middleware solution
that brings up a login page no matter where the user tries to go, then
redirects them to the page they were trying to view... but that only makes
sense if
a little bit search ends up with django-annoying. Is there anyone using it ?
which one is better ?
On Sat, Sep 25, 2010 at 1:25 AM, Shawn Milochik wrote:
> Context processors will do this for you.
>
>
>
Context processors will do this for you.
http://docs.djangoproject.com/en/dev/ref/templates/api/#writing-your-own-context-processors
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
Hello all,
I have a login form that should appear in every pages of the site. How can i
create it from the views file ? Since every form is triggered by calling a
function in the views file, do i have to create the form in every function?
--
You received this message because you are subscribed
7 matches
Mail list logo