I fell into the obligatory problem where non-public items leak out to public feeds. Sorry to everyone, I've updated the feed.
The root of the problem was not using the custom public Manager I have created to deal with this problem in the django-tagging application. It accepts only Model classes. I'll probably hack it up to suit my needs...
Comments
Comment by Orestis Markou , 3 years, 3 months ago :
It's a Manager on the Entry model, that is used everywhere (feeds, views etc). But the revision I had only accepted Model classes, while I'd like to pass querysets.
It's nothing big- I could hack it up in 10 minutes to accept either querysets or Models. I'll probably do it when I have some time.
Thanks for the tip, anyway!
This post is older than 30 days and comments have been turned off.
Comment by Jonathan Buchanan , 3 years, 3 months ago :
Out of interest, what does your custom 'public' Manager for django-tagging do?
If it's intended to restrict tags displayed to those for posts which are public, you should be able to do something like this as of revision 60:
tags = Tag.objects.usage_for_model(BlogEntry, counts=True, filters=dict(is_public=True))