On Monday, 15 September 2008 19:00:39 Steve Holden wrote: > So, as Karen already said, there really doesn't seem to be any need for > a "pluginsEnabled" module. The foreign key implements a one-to-many > relationship between Website and Plugin: many Plugins can have the same > Website, each Website is associated with exactly one Plugin. Thanks for your input. I have started another thread with my latest code, but to answer you: Each Website can have many plugins. I want to be able to: 1. go to a Client and edit/add Website(s) 2. go to a Website and edit/add Plugins.
I invented the PluginsEnabled thing to gather a set of Plugins together under a client and website. I let's me have a boolean active flag for each plugin. Anyway, my new thread has a dpaste of my essential code. Thanks again, always learning! \d --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
