Maybe we should create some kind of pressure group for this :-)
I don't have any idea who can be consulted for this subject, do you?
Cheers,
Rob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users"
On Monday 18 December 2006 22:49, Rob Slotboom wrote:
> > I'd like to be able to edit Project and News separately with Content
> > inline instead. Do you know what i mean?
>
> Hi Dirk,
>
> I get the point though I think this will not work. I've tried similar
> things when creating a menu, where a
> I'd like to be able to edit Project and News separately with Content inline
> instead. Do you know what i mean?
Hi Dirk,
I get the point though I think this will not work. I've tried similar
things when creating a menu, where a menu "one to oned" to a poll item
or blog entry. I gave up.
In
On Saturday 16 December 2006 12:07, Rob Slotboom wrote:
> Hi Dirk,
> I think it's the other way around, try this
>
>
> class Content(models.Model):
> title = models.CharField('Title', maxlength=255, core=True)
> body = models.TextField('Body text')
>
> class Admin:
> fields =
Hi Dirk,
I think it's the other way around, try this
class Content(models.Model):
title = models.CharField('Title', maxlength=255, core=True)
body = models.TextField('Body text')
class Admin:
fields = (
(None, {'fields': ('title','body',)}),
)
Hello,
i'm having some problems with the OneToOneField. I have a content app with a
class Content that i want to use as base class in several other classes (like
Project in the below example):
class Content(models.Model):
title = models.CharField('Title', maxlength=255, core=True)
Hi,
I have a model like this (which is based on an old system I'm porting):
class Member(meta.Model):
user = meta.OneToOneField(auth.User, core=True)
ipb_id = meta.IntegerField(default=0)
website = meta.URLField(blank=True, null=True)
hide_email = meta.BooleanField(default=True)
7 matches
Mail list logo
