-
-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customizable LogEntry model #346
Comments
You might want to look at how django-oscar (https://github.com/tangentlabs/django-oscar) handles model overrides, it works pretty effectively. |
+1 for DJADMIN2_LOGENTRY_MODEL I'm thinking.. when extending the LogEntry, sometimes I'll have to override things like ModelHistoryView, model_history.html, history.html. So, I'm just wondering if would be interesting to have some features as "extensions/plugins"? I mean, a package, so I can implement my needs and register on djangoadmin2. It is something to consider, (worth to discuss), or am I just complicating things? |
Is there a way to still implement this? I know it's been quite sometime (almost a decade tbh) but has this been resolved? |
+1! |
This is just a thought, but it would be similar to how the new Django auth.User model works:
With this, developers can extend the LogEntry model to do whatever they want. We might even enable them to log to it from regular model saves via signals. The downside is this is a performance hit.
More thoughts:
The text was updated successfully, but these errors were encountered: