If you use a custom user that does not include first_name / last_name as a field, searching in the admin will error out as actor__first_name and actor__last_name are not valid fields.
I can think of a few options:
- Unregister the admin using
admin.site.unregister(LogEntry)
- Subclass
LogEntryAdmin, override search_fields
- Register this new admin.
Or simply remove these fields from the built-in admin search_fields.
Or only add these to search if get_user_model + meta ensures they exist.
I generally avoid splitting up first name / last name these days, though I know Django defaults to this.
Let me know which option sounds reasonable and I'm happy to open a PR. Great project, saved me a lot of time. Thanks.
If you use a custom user that does not include
first_name/last_nameas a field, searching in the admin will error out asactor__first_nameandactor__last_nameare not valid fields.I can think of a few options:
admin.site.unregister(LogEntry)LogEntryAdmin, overridesearch_fieldsOr simply remove these fields from the built-in admin
search_fields.Or only add these to search if
get_user_model+ meta ensures they exist.I generally avoid splitting up first name / last name these days, though I know Django defaults to this.
Let me know which option sounds reasonable and I'm happy to open a PR. Great project, saved me a lot of time. Thanks.