Christopher Lenz wrote:
> Am 07.04.2006 um 18:30 schrieb Rudolph:
>> It could be solved by putting the django-admin stuff inside a tag with
>> a django-admin class. Then ".django-admin p" or ".django-admin
>> #content" will format only the admin stuff and not your site.
>
> No, because the admin
On Fri, 2006-04-07 at 17:02 -0600, Joseph Kocherhans wrote:
> django.contrib.auth.models.User has too many methods and too many
> properties. It's tightly coupled to permissions, groups, the admin
> system
>
> has_permission(user, permission)
> is_anonymous(user)
>
> The problem is that we shoul
django.contrib.auth.models.User has too many methods and too many
properties. It's tightly coupled to permissions, groups, the admin
system
has_permission(user, permission)
is_anonymous(user)
The problem is that we should always assume that the user is an
instance of django.contrib.auth.models.U
Am 07.04.2006 um 18:30 schrieb Rudolph:
> It could be solved by putting the django-admin stuff inside a tag with
> a django-admin class. Then ".django-admin p" or ".django-admin
> #content" will format only the admin stuff and not your site.
No, because the admin style sheets use "p" as a selecto
Wow, you fixed this faster than light can travel ;-)
Thanks
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.co
On Apr 7, 2006, at 11:31 AM, James Bennett wrote:
> On 4/7/06, Rudolph <[EMAIL PROTECTED]> wrote:
>> Put this line:
>> {{ app.name }}
>> above the for loop instead of inside it.
>
> Weird... I submitted the patch that added the captions, and that's how
> it is on my working copy, but somehow in ge
On 4/7/06, Rudolph <[EMAIL PROTECTED]> wrote:
> It could be solved by putting the django-admin stuff inside a tag with
> a django-admin class. Then ".django-admin p" or ".django-admin
> #content" will format only the admin stuff and not your site.
It could be, but I think I'm with Wilson in feeli
On 4/7/06, Rudolph <[EMAIL PROTECTED]> wrote:
> Put this line:
> {{ app.name }}
> above the for loop instead of inside it.
Weird... I submitted the patch that added the captions, and that's how
it is on my working copy, but somehow in generating the diff that line
got moved. Best solution for thi
It could be solved by putting the django-admin stuff inside a tag with
a django-admin class. Then ".django-admin p" or ".django-admin
#content" will format only the admin stuff and not your site.
Rudolph
--~--~-~--~~~---~--~~
You received this message because you
Hi,
Magic Removal creates to many "caption" tags on the homepage of admin.
A caption tag should appear only once, right after the table tag, but
Magic Removal puts it above every model-row of the table. In IE6 and
Opera this leads to duplicated captions, in FF and Safari the extra
captions get ig
I'm open to being convinced otherwise, but I don't see it as within
the scope of the admin CSS to accomodate being embedded in other
interfaces.
We've discussed this internally before and the general consensus was
that if you're reusing the admin templates and code in your public
site (which is g
Hi all,
(this one is mostly for Wilson, I guess)
I see there's been some refactoring of the CSS for the admin app
going on, so this might be a good time for a related change:
Many of the style rules used in the admin CSS have very generic
selectors (there are styles for p, ul, etc). In my c
12 matches
Mail list logo
