Re: MR: [patch] for the comments module to work properly
Malcolm Tredinnick wrote: > I cannot comment much on the patch, not being familiar with the comments > component (although the commented out debugging stuff should probably be > removed), but it would be best to open a ticket for this patch, so that > it doesn't get lost (http://code.djangoproject.com/newticket ). ok, there it is: http://code.djangoproject.com/ticket/1709 :) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Django admin css not fully working in MS IE6 ...
On 4/27/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > On Thu, 2006-04-27 at 13:06 -0400, Sam Tran wrote: > > On 4/27/06, James Bennett <[EMAIL PROTECTED]> wrote: > > > > > > On 4/27/06, Sam Tran <[EMAIL PROTECTED]> wrote: > > > > I have been working with the Django admin using Firefox. > > > > Today I tried MS IE 6 and it looks like the css file used is not fully > > > > compatible with IE. > > > > For instance, the blue submit buttons are grey in IE. > > > > > > IE on XP (if that's what you're using) doesn't always respect certain > > > styles on HTML INPUT elements, in much the same way that Safari always > > > uses the default Aqua form controls. > > > > > > What other problems are you seeing? > > > > > > > Let's say I have a table defined as follows: > > > > > > > > > > > > > > > > The first cell has a blue background. The second cell has a blue > > background and the changelink icon when using Firefox. On IE, the > > second cell has a white background ... > > It's a bit hard to diagnose this without knowing the styles that are > being applied. Is this with a standard Django stylesheet (which one?) or > one of your own or...? > Hi Malcom, It is the Django 0.91 admin stylesheets. Thanks. Sam --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: How can users only edit their own files?
On Thursday 27 April 2006 16:27, Joseph Kocherhans wrote:
> > The idea is that the user can only delete/edit/etc their own
> > postings - anything else is denied. (This is obviously not for all
> > users, there need to be admins, etc who can edit everyones files).
> > The only way I can think of is setting up permission groups in
> > Users and maybe overwriting delete()? I haven't tried it yet, was
> > hoping someone with more mojo could shed some light.
>
> This should help, at least somewhat:
> http://lukeplant.me.uk/blog.php?id=1107301634
Also, another hack I have used is to selectively override parts of the
admin using the url configuration, by using regexes that match URLs
that would otherwise go straight to an admin view, and putting them
before the main 'admin' regex:
urlpatterns = patterns('',
(r'^admin/myapp/mymodel/add/$', 'my.special.wrapper.for.add_stage'),
(r'^admin/myapp/mymodel/([^/]+)/$',
'my.special.wrapper.for.change_stage'),
(r'^admin/', include('django.contrib.admin.urls')),
...
'my.special.wrapper' might wrap an existing admin view, or even
duplicate large parts of it if necessary.
Luke
--
"I married Miss Right, I just didn't know her first name was 'Always'"
Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
get_list() with a ManyToMany relationship
I have the following problem: Give two models and a M2M relationship: class Product(meta.Model): category =meta.IntegerField() ... class Part(meta.Model): products = meta.ManyToManyField(Product) ... I want to find all products that belongs to a certain category (say "3") and includes a particular part "p"; furthermore I'd like to use limit in the search parameters. How to do that? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Django admin css not fully working in MS IE6 ...
On 4/27/06, James Bennett <[EMAIL PROTECTED]> wrote: > > On 4/27/06, Sam Tran <[EMAIL PROTECTED]> wrote: > > I have been working with the Django admin using Firefox. > > Today I tried MS IE 6 and it looks like the css file used is not fully > > compatible with IE. > > For instance, the blue submit buttons are grey in IE. > > IE on XP (if that's what you're using) doesn't always respect certain > styles on HTML INPUT elements, in much the same way that Safari always > uses the default Aqua form controls. > > What other problems are you seeing? > Let's say I have a table defined as follows: The first cell has a blue background. The second cell has a blue background and the changelink icon when using Firefox. On IE, the second cell has a white background ... Sam --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Django admin css not fully working in MS IE6 ...
On 4/27/06, Sam Tran <[EMAIL PROTECTED]> wrote: > I have been working with the Django admin using Firefox. > Today I tried MS IE 6 and it looks like the css file used is not fully > compatible with IE. > For instance, the blue submit buttons are grey in IE. IE on XP (if that's what you're using) doesn't always respect certain styles on HTML INPUT elements, in much the same way that Safari always uses the default Aqua form controls. What other problems are you seeing? -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Django admin css not fully working in MS IE6 ...
Hi All, I have been working with the Django admin using Firefox. Today I tried MS IE 6 and it looks like the css file used is not fully compatible with IE. For instance, the blue submit buttons are grey in IE. Is there a way to fix that? Thanks. Sam --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: How can users only edit their own files?
On 4/27/06, Norbert <[EMAIL PROTECTED]> wrote: > > I remember reading somewhere in the docs a while back that this was not > officially supported. Has this changed in MR, or has someone > implemented this with a hack or two? It's still not supported, and likely won't be until sometime after 1.0 is realeased. > The idea is that the user can only delete/edit/etc their own postings - > anything else is denied. (This is obviously not for all users, there > need to be admins, etc who can edit everyones files). The only way I > can think of is setting up permission groups in Users and maybe > overwriting delete()? I haven't tried it yet, was hoping someone with > more mojo could shed some light. This should help, at least somewhat: http://lukeplant.me.uk/blog.php?id=1107301634 And think about how custom managers might help for limiting what a user can see in a change list. (Filter what non-admins can see.) http://code.djangoproject.com/wiki/RemovingTheMagic#Custommanagersandmultiplemanagers Joseph --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: ordering has no use
found the problem "class META:" should be "class Meta: " :( --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: MR: [patch] for the comments module to work properly
Hey Eric, On Thu, 2006-04-27 at 12:49 +, nkeric wrote: > guys, > > today while I'm using the comments module to implement something, I > guess I found two bugs: > > 1. in the models.py, the get_list_with_karma method should be updated > to use the extra() method to inject the "select" kwargs, otherwise, the > templatetag get_comment_list won't work; > > 2. in the views/comments.py, > self.user_cache.get_comments_comment_count() - the > get_comments_comment_count() api doesn't exist now, should be updated > to use the self.user_cache.comment_set.count() to get the comments > count. I cannot comment much on the patch, not being familiar with the comments component (although the commented out debugging stuff should probably be removed), but it would be best to open a ticket for this patch, so that it doesn't get lost (http://code.djangoproject.com/newticket ). The mailing list archives are a little bit too high volume to also use as a patch tracker. Regards, Malcolm --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Django-based wiki engine
Hi, Has anybody been working on a django-based wiki engine on the lines of django.contrib? I'd much appreciate hints on such projects... TIA, Giorgi --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
