On Mon, Feb 25, 2008 at 11:06 AM, Daniel Roseman
<[EMAIL PROTECTED]> wrote:
>
> On Feb 24, 12:29 am, Jonathan Lukens <[EMAIL PROTECTED]>
> wrote:
>
> > I am building a site for a customer, a restaurant owner, who wants to
> > be able to edit virtually all of the text on the site, including the
> > home page introductory text, etc. It would be simple enough to create
> > a model with a single field like
> thishttp://groups.google.com/group/django-developers/browse_frm/thread/2c...
>
> > for every chunk of text he wants to have control over, or one model
> > with multiple fields and and a global context processor... I have
> > ideas of how this *could* be done, but am interested in how it
> > *should* be done. What are other people doing in this situation?
>
> Sounds like a job for dbsettings:
> http://code.google.com/p/django-values/
As the author of dbsettings, I wouldn't personally recommend it for
this task. It's considerable overkill for this situation, and it
intentionally doesn't allow any string values greater than 255
characters in length anyway.
As James suggests, flatpages is a better option, thought that would
require the content manager to deal with the entire template, rather
than just snippets of text. Personally, I'd go with something
in-between.
You could set up an editabletext app, with a model like so:
class EditableText(models.Model):
slug = models.SlugField(primary_key=True)
text = models.TextField()
def __unicode__(self):
return self.slug
class Meta:
verbose_name_plural = 'editable text'
class Admin:
pass
Then write a template tag like this:
class TextNode(template.Node):
def __init__(self, slug):
self.slug = slug
def render(self, context):
try:
return EditableText.objects.get(slug=self.slug).text
except EditableText.DoesNotExist:
return "[[ No text found for %s ]]" % self.slug
@register.tag
def text(parser, token):
return TextNode(token.split_contents()[1])
Of course, your tag could include markdown or textile formatting,
control over autoescaping, maybe a link to the admin interface where
an undefined bit of text could be created, etc. Then, in your
templates, you'd use the tag like this:
{% load editable_text %}
<html>
<head>
<title>{% text home-title %}</title>
</head>
<body id="widget-detail">
<h1>{% text home-title %}</h1>
<p class="intro">{% text home-introduction %}</p>
<p class="body">{% text home-body %}</p>
<p class="footer">{% text page-footer %}</p>
</body>
</html>
Personally, I'm not a fan of the whole thing, but that's a way you
could get the job done, anyway.
-Gul
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
