Phil Powell wrote: > I want to have a series of pages, with certain areas of content which > are editable. I don't want to use flatpages, as I'd like the editable > content to be broken down into chunks, rather than one big lump of > content. > > Is there a way to easily set a model to have one singleton instance? > I've thought about adding some pre-save code to check and only allow > for one instance, but wondered if there was a more graceful way to do > this?
I'm not sure I get how a singleton would solve the "pages generated from multiple chunks" problem. why not just use a model that holds (pagename, chunkname, chunk data) triplets, and use a view that brings up all the chunks for a given page ? </F> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
