Hi Carlton,
As I understand it, separate admin sites may register different models, but
I'm only going to see the History for instances that are visible to the
current admin no?
The Django admin interface uses a templatetag named get_admin_log. It
renders the content of all entries of model L
Thanks for clarifying Jacob, great.
So, the registered content_types are in the available_apps key to the
context passed to that tag. (Currently that needs reconstructing in a
filter/comprehension, but it could feasibly be added to the
`AdminSite.each_context` method.) Adding the matching `__in` l
I just submitted a proposal to create a Discourse plugin to improve the
accuracy of their inbound email parsing. This would enable two things:
- Folks who prefer to live in their inbox could continue to do so and
contribute by just replying to emails. Discourse currently has
reply-by-emai
Hi Carlton,
that proposal makes a lot of sense.
This means that one could for instance add a custom function to that
context which, if set, would be called
by the AdminLogNode.render method and then overrides the
context[self.varname].
How would you name that extra context variable, maybe "rende
Hey Jacob.
I had in mind literally **just** adding the content-types so that the line
in that render call would be:
# this could be via a proposed context["site_content_types"] or via a
map from
# "available_apps"
site_content_types: [ContentType] = ...
entries = LogEntry.objects.
