Re: no attribute 'save_m2m'

On Jan 18, 10:01 am, GoSantoni wrote: > Hi > > Trying to use save_m2m as described > herehttp://docs.djangoproject.com/en/1.0/topics/forms/modelforms/#the-sav... > Though in run into an attrribute error 'Post' object has no attribute > 'save_m2m' > > *** Model *** >

Re: import json data into my django app

On Jan 17, 4:58 pm, lance wrote: > Python/Django newbie question: > > I need to create a cron job that fetches json data from a URL, parses > it (presumably using simplejson) and then load the data into my > database using the Django models I've defined. > > I'm having trouble

Re: #django :You need to be identified to join that channel

You probably have to register your Nickname with nickserv. http://oreillynet.com/pub/h/1940 On Jan 16, 7:59 am, NMarcu wrote: > Hello, > >     Somebody know why i get this message when I try to join django > channel from freenode irc: > #django :You need to be

Re: newbie questions regarding models and admin

The philosophy of the admin app is that it is a simple CRUD interface for trusted staff members to manage data. If you need data entry for non staff members (i.e. people you do not trust with the admin) you should create public facing forms and setup some permissions for the users to be able to

Re: Per-object permissions

You should look into django-authority. I'm pretty sure that has per- object-permissions. http://packages.python.org/django-authority/index.html On Nov 24, 7:00 am, gamliel roi wrote: > Hello all, > > I have the admin site up and running but I need to create a group of

Recursive ManyToMany?

I'm trying to create a record label website and I'm modeling the music data. I have artists, albums, tracks so far. What I'd like to do is use the artists model for both individual recording artists and groups of recording artists. I'd like to be able to find any singular artist or groups of

Querysets and includes

How would I go about getting a queryset into an include? Say I have a blog and I have a page for the post detail. On the sidebar I would like to have the blog categories dynamically built or have recent articles, or recent comments, etc... What would be the best approach to build these

problems with post_save and sites framework

I've been setting trying to set up a tumblelog using the sites framework and the current site manager and I'm hitting a bug in either my code or Django's not sure which. Basically what's happening is the first time I save an object the tumble item is created, but the site field is not populated

get_next_by_FOO(**kwargs) and get_previous_by_FOO(**kwargs) with on_site

I'm wondering if it's possible to use the current site manager with these two functions or if I'm going to have to write my own? def get_previous_post(self): return self.get_previous_by_publish(status__gte=2) def get_next_post(self): return self.get_next_by_publish(status__gte=2) Has

Re: Using ManytoManyField's in signals

On Sep 3, 4:08 pm, Rajesh Dhawan <[EMAIL PROTECTED]> wrote: > On Sep 3, 3:59 pm, nek4life <[EMAIL PROTECTED]> wrote: > > > I'm using Django Beta 2 > > If, instead of top-posting, you bottom-post your responses, it's > easier for people to see

Re: Using ManytoManyField's in signals

I'm using Django Beta 2 This is my post data bodyu'body' status u'2' allow_comments u'on' _save u'Save' leadu'lead' author u'1' title u'Test Post' siteu'2' publish_1 u'15:04:22' publish_0 u'2008-09-03'

Re: Using ManytoManyField's in signals

created=(not record_exists), raw=raw) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/ site-packages/django/dispatch/dispatcher.py" in send 148. response = receiver(signal=self, sender=sender, **named) File "/Users/nek4life/djcode/publish/../p

Using ManytoManyField's in signals

from django.db import models from django.contrib.contenttypes import generic from django.template.loader import render_to_string from django.db.models import signals from django.contrib.contenttypes.models import ContentType from django.dispatch import dispatcher from django.contrib.sites.models

Re: database relationships

t; > On Aug 27, 11:58 am, nek4life <[EMAIL PROTECTED]> wrote: > > > Well this works great while using the generic detail view, but when I > > return a list view the relationships won't work. > > > in my view > > > def album_list(request, page=0): > >    

Re: database relationships

around. On Aug 22, 11:44 am, nek4life <[EMAIL PROTECTED]> wrote: > Awesome.  I got it to work using this code in my view. > > def artist_detail(request, slug): >     album_list = Album.objects.all() >     return list_detail.object_detail( >         request, >         qu

Re: database relationships

gt; # //artist_list.html > > {{ artist }} > > Albums > > > > {% for album in artist.album_set.all %} > >    {{ album.name }} > >     > >    {% for track in album.track_set.all %} > >      {{ track.name }} > >    {% endfor %} > >     >

Re: database relationships

> >   artist = album.artist > >   tracks = album.track_set.all() > >   ...etc... return a response... > > > def track(request, slug): > >   track = get_object_or_404(Track, slug=slug) > >   album = track.album > >   artist = album.artist > >   ..

database relationships

I'm trying to set up my first Django application and I'm trying to figure out the database relationships. I want to be able to list albums, with their corresponding tracks and album artwork. Right now I only have foreign keys defined in the Track class and on the AlbumArt class pointing to the

Re: Unexpected Keyword Argument 'radio_admin'

I'm getting the same error, and I can't see when the manger isn't being imported... 'Manager' object has no attribute 'published' This is driving me crazy. Any Ideas, I had it working with Django 96.2 but not beta 1 version I'm running now. On Jun 26, 5:24 pm, Alfonso <[EMAIL PROTECTED]>