Admin's Recent Actions broken for multiple admin site instances with unique registered models

[Steven MacLeod]

The Recent Actions list contains actions carried out from all admin site instances a user has access to. This causes problems when there exists a model which is not registered in all instances, and a User with access to multiple instances. If an action is carried out on this model it will appear in the recent list of all admin sites. If the model is not registered to an instance, the link generated will be invalid.

Ex:

• AdminSite1 has model Model1 registered
• AdminSite2 does not have Model1 registered
• User has access to both admin sites
• User adds a Model1 in AdminSite1 (Action1)
• User visits AdminSite2, and clicks the Action1 link
• User is directed to an invalid URL (url for Model1 in AdminSite2)

[Julien Phalip]

Thanks for the report, however this is a duplicate of #9151, which was wontfixed. If you disagree with this resolution, please take this question to ​django-developers.

[Carl Meyer]

I don't believe this is actually a duplicate of #9151, though it is similar. #9151 is about django.contrib.sites; this ticket is about creating multiple instances of django.contrib.admin.Site. Despite the confusing naming, those are two completely separate things. And I don't think the wontfix reasoning applied in #9151 applies here; while there may be nothing about django.contrib.sites.models.Site that warrants special treatment in the admin, I think it's reasonable to expect that the admin's *own* multiple-admin-site feature won't break the admin's own recent-actions feature.

Reopening.

[Mariusz Felisiak]

#34162 was a duplicate for resolving URLs for a custom admin site.

[Al Mahdi]

Still not fixed in 4.1

​https://github.com/django/django/blob/d3edac6c071c544c7d2208baf13d6d0fdc5e58fe/django/contrib/admin/models.py#L182

LogEntry.get_admin_url method reverse(s) entries with default admin: prefix