I was not able to describe my problems to ticket on first attempt, so
I try here before creation of another ticket.
We use CSRF protection on almost all POST requests, but we encountered
some limitations of CSRF protection as currently implemented in
django.
- You can not render POST form in unp
Recently I found out that distinct() can not be called on queries that
are ordered as the result query is kind of
SELECT DISTINCT table.id, table.ordering_column FROM table ORDER BY
table.ordering_column ASC
In ticket http://code.djangoproject.com/ticket/11568 was said that
this will not be fixed
That was the problem, thanks a lot.
On Sep 10, 1:14 am, Ramiro Morales wrote:
> On Wed, Sep 9, 2009 at 1:16 PM, Vlastimil Zima
> wrote:
>
> > Neither name nor app_label fixed situation.
> > AdminSite instance django.contrib.admin.site is constructed without
> > any
rote:
> On Wed, Sep 9, 2009 at 4:33 AM, Vlastimil Zima
> wrote:
>
> > Hello,
> > I found out, that if I made derived class of
> > django.contrib.admin.sites.AdminSite admin generated by this AdminSite
> > in unable to to create correct links e.g. for Logout (
Django1.1
On Sep 9, 12:40 pm, Ramiro Morales wrote:
> On Wed, Sep 9, 2009 at 4:33 AM, Vlastimil Zima
> wrote:
>
> > Hello,
> > I found out, that if I made derived class of
> > django.contrib.admin.sites.AdminSite admin generated by this AdminSite
> > in unab
Hello,
I found out, that if I made derived class of
django.contrib.admin.sites.AdminSite admin generated by this AdminSite
in unable to to create correct links e.g. for Logout (http://
127.0.0.1:8000/admin/Nonelogout/), Change Password (http://
127.0.0.1:8000/admin/Nonepassword_change/), etc. (exa
6 matches
Mail list logo