On 6/3/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 6/3/06, Derek Hoy <[EMAIL PROTECTED]> wrote:
> > Here's an example of what works for me:
> >
> > {% get_free_comment_list for workgroups.workgroup group.id as
> > comment_list reversed %}
> >
> > workgroups is the appname
> > workgroup is the module name - (model is WorkGroup, I don't know where
> > Django gets 'workgroup' from- presume it's just the model name in
> > lowercase)
> > group is the object passed into the template, so group.id is a key to
> > fetch the comments
> >
> > I figured this out by looking in the db tables for freecomments and
> > contenttypes- maybe that will help you check if that's the problem?
>
> Yeah, Django looks at the contenttypes table to hook into comments, so
> make sure what you're putting in the {% get_free_comment_list %}
> template tag matches what you have in the contenttypes table.OK, I think I see it. The freecomments have a content_type_id that (for me) is refering to an entry in django_content_type where the model column is "entries," not "entry." Looks like I need to clean that table up, becaues there is another row that has "entry" for the model. Hmm... Thanks for the tips. Bryan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
