[image: WhatsApp Image 2020-12-15 at 10.55.37 PM.jpeg] On Wednesday, 16 December 2020 at 00:12:40 UTC+5:30 Muskan Vaswan wrote:
> I have the following suggestions and issues with the Django site > administration: > > 1. When deleting or adding items in Bulk (especially deleting), The Recent > Actions should show “Deleted 15 Items” rather than every deleted item > singularly which just occupies space and doesn't make a lot of sense and > put bluntly is a waste of space. (ScreenShot attached). This could also be > in the form of a dropdown which on click would show us every single one of > the logs. Now I know this may not be a major change to the page but I do > think it would improve the quality of the admin page. Do tell me if you > agree or disagree > After looking at the code for this, I realized that this wouldn’t be as > easy it seems because (at least as far as I could understand) the context > picks the action history from the LogEntry Model and passes it into the > context. But a possible solution to this would be changing the query to > give changes made on the same timestamp and tag as a list of actions and > the final context could be the list of all such distinct timestamps. > > > 2. The way the default index template can be overwritten by the user by > specifying admin.index_template, I think it might be possible to give such > an option for singular components of the admin site. For example, the > entire header (Line 30 to 62 > <https://github.com/django/django/blob/master/django/contrib/admin/templates/admin/base.html>) > > could be put inside a block and then use an > *{% include header.html %}* which would contain the code for the entire > header. And we could make this file default and give the option to > overwrite this particular template. We ensure that the components hold > their designated positions and leave the rest up to the user. We could also > do this for other elements and components like the footer. I think this > would increase ease of customization. Please give your views regarding the > same. > > 3. Last and the least, The method for unregistering models form the admin > site is not in the documentation. I only found it existed while going > through the source code and on StackOverflow. Is there a reason for this or > is this a lack of documentation that needs to be fixed? > > Regards > Muskan Vaswan > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/58cf1866-a505-4ced-8ca2-c3aa449f57a3n%40googlegroups.com.
