{"id":75920,"date":"2020-01-20T12:32:59","date_gmt":"2020-01-20T07:02:59","guid":{"rendered":"https:\/\/www.vskills.in\/certification\/tutorial\/?p=75920"},"modified":"2024-04-12T14:17:42","modified_gmt":"2024-04-12T08:47:42","slug":"customizing-admin-templates-2","status":"publish","type":"page","link":"https:\/\/www.vskills.in\/certification\/tutorial\/customizing-admin-templates-2\/","title":{"rendered":"Customizing Admin Templates"},"content":{"rendered":"

Out of the box, Django provides a number of tools for customizing the built-in admin templates, which we\u2019ll go over shortly, but for tasks beyond that (e.g., anything requiring custom workflow or granular permissions), you\u2019ll need to read the section titled \u201cCreating Custom Admin Views\u201d later in this chapter. For now, though, let\u2019s look at some quick ways of customizing the appearance (and, to some extent, behavior) of the admin interface. Chapter 6 covers a few of the most common tasks: \u201crebranding\u201d the Django admin interface (for those pointy-haired bosses who hate blue) and providing a custom admin form.<\/p>\n

Past that point, the goal usually involves changing some of the templates for a particular item. Each of the admin views \u2014 the change lists, edit forms, delete confirmation pages, and history views \u2014 has an associated template that can be overridden in a number of ways. First, you can override the template globally. The admin view looks for templates using the standard template-loading mechanism, so if you create templates in one of your template directories, Django will load those instead of the default admin templates bundled with Django. These global templates are outlined in Table.<\/p>\n\n\n\n\n\n\n\n\n
View<\/strong><\/td>\nBase Template Name<\/strong><\/td>\n<\/tr>\n<\/thead>\n
Change list<\/td>\nadmin\/change_list.html<\/td>\n<\/tr>\n
Add\/edit form<\/td>\nadmin\/change_form.html<\/td>\n<\/tr>\n
Delete confirmation<\/td>\nadmin\/delete_confirmation.html<\/td>\n<\/tr>\n
Object history<\/td>\nadmin\/object_history.html2<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Most of the time, however, you\u2019ll want to change the template for just a single object or application (not globally). Thus, each admin view looks for model- and application-specific templates first. Those views look for templates in this order:<\/p>\n