See
https://stackoverflow.com/questions/987669/tying-in-to-django-admins-model-history
for a better explanation and alternatives
On Tue, 22 Jun 2021 at 18:59, Ryan Kite wrote:
>
> Thanks for the clarification, I didn't realize it only applied to changes
> administered directly from the Django
Thanks for the clarification, I didn't realize it only applied to changes
administered directly from the Django Admin.
Was interested in learning about an objects' change history, but in this
case, the changes were not performed from the Django Admin.
On Tuesday, June 22, 2021 at 5:50:10 AM
I am not sure what you are asking about.
The history works out of the box, but only when you manipulate entries via
the django admin.
When you change the model instance through your own views, you have to
explicitly create the log entry.
On Tue, 22 Jun 2021 at 00:48, Ryan Kite wrote:
> Hello,
>
Hello,
The issue is when clicking the "History" button on an object from the
Django admin site, it opens to the template but says "*This object doesn't
have a change history. It probably wasn't added via this admin site."*
>From reading the docs it appears that: *history_view*() already exists
4 matches
Mail list logo
