Thanks for the input guys. I'm kind of approaching this from a client
perspective, so was fishing around for the simplest use case from an
inexperienced admin user's point of view.
The suggestions of using a Page and "chunk" schema makes perfect
sense, and a quick Google threw up a good example[
On 12/4/06, Phil Powell <[EMAIL PROTECTED]> wrote:
> I have a "Homepage" which has fields such as "Page Title",
> "Introduction Text", "Footer Text" etc. I want to be able to edit
> these fields just like I'd edit a standard model instance, but because
> there is only one instance of my "Homepage
On 04/12/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> 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 give
3 matches
Mail list logo