Could be as simple as: {% csrf_token %}{{ form }}
On Tuesday, March 3, 2015 at 9:32:48 AM UTC-5, Ilya Kazakevich wrote:
>
> I agree: adding template from example is good idea! And I believe it will
> be used at least by newbies who just study Django auth system and by people
> who just need prot
You're correct, the first app has priority. Only management commands used to
work the other way round. (Remind me who made that change?)
--
Aymeric.
> Le 3 mars 2015 à 20:07, Marc Tamlyn a écrit :
>
> I believe we standardised priority order such that earlier in the list always
> takes prior
I believe we standardised priority order such that earlier in the list
always takes priority. Historically we had different orders for different
things (templates, template tags, static files etc).
In any case, I don't think this should be a blocker and I'm in favour of
including it as `registrati
I agree: providing a default login template would help. Getting started with
contrib apps should be as easy as possible.
However the current proposal is backwards incompatible for users who define the
login template in one of their apps that comes before django.contrib.auth in
INSTALLED_APPS (i
So, should I create a ticket?
On Tuesday, March 3, 2015 at 4:05:01 PM UTC+3, Ilya Kazakevich wrote:
>
> Hello,
>
> When I use Django auth, I need to provide login.html myself. But Django
> encourages applications to have default templates which can be overwritten
> by user (via filesystem.Loader
I agree: adding template from example is good idea! And I believe it will
be used at least by newbies who just study Django auth system and by people
who just need prototype. Providing default is better than copy/pasting
example from docs.
On Tuesday, March 3, 2015 at 5:26:10 PM UTC+3, Marc Tam
I can see the merit of including our documented example as an actual
template as a starting point. It's unlikely to be used exactly as is very
often but it reduces getting started friction for some users - "huh this
view doesn't work, better go read the docs"
I'd perhaps be inclined to include it
I do not think admin templates should used. But something very simple and
dumb (that looks similar to browser HTTP auth window). Here is example:
http://pastebin.com/nnX36RB6
Css should be moved to static files, of course, to make this template
cleaner and slightly more customizable.
Imagine I
The admin templates extend "admin/base_site.html" and rely on the presence
of specific template blocks so I don't think it's appropriate for those
dependencies to be added to contrib.auth. I'm curious to see what content
you would propose for a default template. Typically I've seen login
templa
Yeah, or default to admin/login.html. The admin ships with all necessary
"registration" templates, but for some reason only the login.html is
included in the admin directory.
On Tue, Mar 3, 2015 at 2:05 PM, Ilya Kazakevich
wrote:
> Hello,
>
> When I use Django auth, I need to provide login.html
Hello,
When I use Django auth, I need to provide login.html myself. But Django
encourages applications to have default templates which can be overwritten
by user (via filesystem.Loader, for example).
I suggest to provide default login.html with simple HTML form. User may
always overwrite it.
11 matches
Mail list logo
