Assign a User/Group to a Site
Ok, so I can have an article associated with multiple sites. That's pretty sweet! But how about ensuring that a user I create can only work on a certain site? --~--~-~--~~~---~--~~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: ManyToMany Model Inline?
After tooling around with it a bit, I simplified it so that each Vegetable/Animal has a ManyToMany relationship with a Tag. But I still would like to find a way of consolidating the editing of where a Tag points on the actual TagAdmin page. On Mar 30, 1:24 pm, Liquidrums <ericclemm...@gmail.com> wrote: > In the documentation for Generic Relations, a Vegetable and Animal can > be Tagged via a GenericInline for each model. > > I want to be able to choose a tag and subsequently add/remove which > models have that tag via a ManyToMany-style inline. > > Is this already available, or do I have to roll my own? I want to > have fine-grained control over what a tag points to, rather than > editing each separate model on its own & remove that tag. --~--~-~--~~~---~--~~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
[Django Admin + Generic Relations] ManyToMany Model Inline?
In the documentation for Generic Relations, a Vegetable and Animal can be Tagged via a GenericInline for each model. I want to be able to choose a tag and subsequently add/remove which models have that tag via a ManyToMany-style inline. Is this already available, or do I have to roll my own? I want to have fine-grained control over what a tag points to, rather than editing each separate model on its own & remove that tag. --~--~-~--~~~---~--~~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Admin / Model - "Page" model has many "Component" models
After digging some more (trying every combination of keywords in Google & these forums), I found this: >> http://www.djangoproject.com/documentation/models/generic_relations/ This seems to be what I need. In the example in the URL, a single tag could be assigned to many objects, in the same way that many "components" would be tied to a single "Page". On Oct 28, 2:14 pm, Liquidrums <[EMAIL PROTECTED]> wrote: > This may be beyond the reach of Django, but I figured it was worth a > shot. > > I have a site tool not unlike many blogs or CMSs for adding/editing > pages. Recently, to enable common components to pages (such as > contact forms, site-maps, carts, pre-filled content pages, etc.), the > needs for the "Page" administration has changed from: > > >> Title: Foo > >> Content: Bar Baz > > to > > >> Title: Foo > >> Content: Bar Baz > >> Components: > >> |- Header > >> |- Footer > >> |- Sitemap > >> |- Contact Form > > Where each "Component" is its own inherited model that defines any > config settings needed. For example, the Contact Form model may have > a "To:" field defaulted, while the Footer component has no config > settings. The components are assembled in the view. > > Is there a way to achieve this, or is this beyond the scope of Django? --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
Admin / Model - "Page" model has many "Component" models
This may be beyond the reach of Django, but I figured it was worth a shot. I have a site tool not unlike many blogs or CMSs for adding/editing pages. Recently, to enable common components to pages (such as contact forms, site-maps, carts, pre-filled content pages, etc.), the needs for the "Page" administration has changed from: >> Title: Foo >> Content: Bar Baz to >> Title: Foo >> Content: Bar Baz >> Components: >> |- Header >> |- Footer >> |- Sitemap >> |- Contact Form Where each "Component" is its own inherited model that defines any config settings needed. For example, the Contact Form model may have a "To:" field defaulted, while the Footer component has no config settings. The components are assembled in the view. Is there a way to achieve this, or is this beyond the scope of Django? --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
