On 1/3/07, James Tauber <[EMAIL PROTECTED]> wrote:
Or are people using template-only flatpages just going ahead and making flatpage database records with dummy title/content just to specify the template to use? (and is this indeed what djangoproject.com itself is doing?)
Off the top of my head, I'd say it depends on how many "template-only" pages you want and how programmatically predictable their URLs will be: * If you've got a lot of these pages, or if they're at lots of random URLs, or both, using flatpages to drop a "template-only" page at a particular URL is probably the simplest thing. * If you don't have very many of these pages, or if they're all in easily-targeted locations in your URL structure, using the direct_to_template generic view is probably the simplest thing (since that gives you the ability to capture parameters out of the URL and pass them to the template, you could then muddle the logic/presentation distinction a bit and trigger different content using nothing but the template system). -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
