Hi Nate,
On 1/20/07, natebeaty <[EMAIL PROTECTED]> wrote:
> blog_dict = {
> 'queryset': Blog.objects.all(),
> 'template_object_name': 'blog',
> "extra_context" : {
> "blog_month_list" : Blog.objects.dates("date_added", "month"),
> "current_issue" : Issue.objects.latest(),
> "tag_list" :
> Tag.objects.filter(blog__id__isnull=False).distinct()
> },
> 'date_field': 'date_added',
> }
>
> ..but apparently this will only populate the tags once, when I start up
> Django, correct? Do I need to add the extra_context in a wrapper around
> a generic view in views.py? Or would something like this be best
> implemented as a template_tag?
>
> Am I correct in assuming it would be best to use a template_tag if it's
> needed across many views, but otherwise easier to just populate the
> template w/ extra_context?
That is exactly the same problem I've got for a couple of hours. If you
want to list all tags, then I would recommend using a templatetag, because
you need no filtering.
If you only want to list the tags related to the current blog entry (e.g., on
a object_detail generic view site) I would wrap the generic view instead
of filling the urls.py file with logic. Imho, there should be no logic
in urls.py
And that is what I'm trying to understand... why do I *have to* wrap a
generic view and return the object_detail. When using manage.py shell,
I don't have to. If I access Post.tags, they are there. Why not in the
application?
(I used a ManyToMany-Field to link between Post & Tag.)
> Thanks again,
> Nate.
Greetings
Kai
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
