{"title":"Tindakan admin","version":"6.1","locale":"id","docname":"ref/contrib/admin/actions","url":"/id/6.1/ref/contrib/admin/actions/","canonical":"https://djangodocs.dev/id/6.1/ref/contrib/admin/actions/","summary":"Alir kerja dasar dari admin Django adalah, dalam kulit kacang, \"pilih sebuah obyek, kemudian rubah itu.\" Ini bekerja baik untuk kebanyakan penggunaan kasus.…","html":"

Tindakan adminLink to this heading#

\n

Alir kerja dasar dari admin Django adalah, dalam kulit kacang, "pilih sebuah obyek, kemudian rubah itu." Ini bekerja baik untuk kebanyakan penggunaan kasus. Bagaimanapun, jika anda butuh perubahan sama ke banyak obyek sekali waktu, alir kerja ini bisa sangat membosankan.

\n

In these cases, Django's admin lets you write and register "actions" --\nfunctions that get called with a list of objects selected on the change list\npage.

\n

Jika anda mencari daftar perubahan apapun di admin, anda akan melihat fitur ini di tindakan; Django dikirim dengan tindakan "menghapus obyek terpilih" tersedia untuk semua model. Sebagai contoh, ini adalah modul pengguna dari aplikasi django.contrib.auth pasang-tetap Django :

\n\"/id/6.1/_images/admin-actions.png\"\n\n

Baca untuk menemukan bagaimana menambah tindakan anda sendiri ke daftar ini.

\n
\n

Menulis tindakanLink to this heading#

\n

Cara mudah untukmenjelaskan tindakan adalah dengan contoh, jadi mari kita selami.

\n

A common use case for admin actions is the bulk updating of a model. Imagine a\nnews application with an Article model:

\n
Code
from django.db import models\n\nSTATUS_CHOICES = {\n    "d": "Draft",\n    "p": "Published",\n    "w": "Withdrawn",\n}\n\n\nclass Article(models.Model):\n    title = models.CharField(max_length=100)\n    body = models.TextField()\n    status = models.CharField(max_length=1, choices=STATUS_CHOICES)\n\n    def __str__(self):\n        return self.title\n
\n

Tugas utama kami mungkin lakukan dengan sebuah model seperti ini adalah memperbaharui sebuah keadaan article dari "draft" menjadi "published". Kami dapat dengan mudah melakukan ini di admin satu artikel pada sekali waktu, tetapi jika kami ingin menerbitkan-jumlah besar kelompok dari artikel, itu akan membosankan. Jadi, mari kita menulis sebuah tindakan yang membuat kita merubah sebuah keadaan artikel menjadi "published."

\n
\n

Menulis fungsi tindakanLink to this heading#

\n

First, we'll need to write a function that gets called when the action is\ntriggered from the admin. Action functions are regular functions that take\nthree arguments:

\n\n

Fungsi terbitan-artikel-ini kami tidak butuh ModelAdmin atau obyek permintaan, tetapi kami akan menggunakan queryset:

\n
Code
def make_published(modeladmin, request, queryset):\n    queryset.update(status="p")\n
\n\n

That's actually all there is to writing an action! However, we'll take one\nmore optional-but-useful step and give the action a "nice" title in the admin.\nBy default, this action would appear in the action list as "Make published" --\nthe function name, with underscores replaced by spaces. That's fine, but we\ncan provide a better, more human-friendly name by using the\naction() decorator on the make_published\nfunction:

\n
Code
from django.contrib import admin\n\n...\n\n\n@admin.action(description="Mark selected stories as published")\ndef make_published(modeladmin, request, queryset):\n    queryset.update(status="p")\n
\n\n
\n
\n

Menambahkan tindakan pada ModelAdminLink to this heading#

\n

Selanjutnya, kami akan butuh menginformasikan ModelAdmin kami dari tindakan. Ini bekerja seperti piliha konfigurasi lain apapun. Jadi, admin.py lengkap dengan tindakan dan pendaftarannya akan terlihat seperti:

\n
Code
from django.contrib import admin\nfrom myapp.models import Article\n\n\n@admin.action(description="Mark selected stories as published")\ndef make_published(modeladmin, request, queryset):\n    queryset.update(status="p")\n\n\nclass ArticleAdmin(admin.ModelAdmin):\n    list_display = ["title", "status"]\n    ordering = ["title"]\n    actions = [make_published]\n\n\nadmin.site.register(Article, ArticleAdmin)\n
\n

Kode akan memberikan kami sebuah daftar rubah admin yang terlihat sesuatu seperti ini:

\n\"/id/6.1/_images/adding-actions-to-the-modeladmin.png\"\n

That's really all there is to it! If you're itching to write your own actions,\nyou now know enough to get started. The rest of this document covers more\nadvanced techniques.

\n
\n
\n

Penanganan kesalahan di tindakanLink to this heading#

\n

Jika ada kondisi kesalahan mendatang yang mungkin muncul selagi menjalankan tindakan anda, anda harus anggun menginformasikan pengguna dari masalah. Ini berarti menangani pengecualian dan menggunakan django.contrib.admin.ModelAdmin.message_user() untuk memperlihatkan gambaran yang ramah pengguna dari masalah di tanggapan.

\n
\n
\n
\n

Teknik-teknik tindakan lanjutanLink to this heading#

\n

Ada sepasang pilihan tambahan dan kemungkinan anda dapat menggunakan lebih pilihan lanjutan

\n
\n

Tindakan sebagai metode ModelAdminLink to this heading#

\n

The example above shows the make_published action defined as a function.\nThat's perfectly fine, but it's not perfect from a code design point of view:\nsince the action is tightly coupled to the Article object, it makes sense\nto hook the action to the ArticleAdmin object itself.

\n

Anda dapat melakukan itu seperti ini:

\n
Code
class ArticleAdmin(admin.ModelAdmin):\n    ...\n\n    actions = ["make_published"]\n\n    @admin.action(description="Mark selected stories as published")\n    def make_published(self, request, queryset):\n        queryset.update(status="p")\n
\n

Perhatikan pertama yang kami telah pindahkan make_published kedalam metode dan dinamai kembali parameter modeladmin pada self, dan kedua kami telah sekarang menaruh string 'make_published' dalam actions daripada acuan fungsi langsung. Ini mengatakan ModelAdmin untuk mencari tindakan sebagai sebuah metode.

\n

Defining actions as methods gives the action more idiomatic access to the\nModelAdmin itself, allowing the action to call any of the methods\nprovided by the admin.

\n

For example, we can use self to flash a message to the user informing them\nthat the action was successful:

\n
Code
from django.contrib import messages\nfrom django.utils.translation import ngettext\n\n\nclass ArticleAdmin(admin.ModelAdmin):\n    ...\n\n    def make_published(self, request, queryset):\n        updated = queryset.update(status="p")\n        self.message_user(\n            request,\n            ngettext(\n                "%d story was successfully marked as published.",\n                "%d stories were successfully marked as published.",\n                updated,\n            )\n            % updated,\n            messages.SUCCESS,\n        )\n
\n

This makes the action match what the admin itself does after successfully\nperforming an action:

\n\"/id/6.1/_images/actions-as-modeladmin-methods.png\"\n
\n
\n

Tindakan yang menyediakan halaman menengahLink to this heading#

\n

By default, after an action is performed the user is redirected back to the\noriginal change list page. However, some actions, especially more complex ones,\nwill need to return intermediate pages. For example, the built-in delete action\nasks for confirmation before deleting the selected objects.

\n

To provide an intermediary page, return an HttpResponse\n(or subclass) from your action. For example, you might write an export function\nthat uses Django's serialization functions to\ndump some selected objects as JSON:

\n
Code
from django.core import serializers\nfrom django.http import HttpResponse\n\n\ndef export_as_json(modeladmin, request, queryset):\n    response = HttpResponse(content_type="application/json")\n    serializers.serialize("json", queryset, stream=response)\n    return response\n
\n

Generally, something like the above isn't considered a great idea. Most of the\ntime, the best practice will be to return an\nHttpResponseRedirect and redirect the user to a view\nyou've written, passing the list of selected objects in the GET query string.\nThis allows you to provide complex interaction logic on the intermediary\npages. For example, if you wanted to provide a more complete export function,\nyou'd want to let the user choose a format, and possibly a list of fields to\ninclude in the export. The best thing to do would be to write a small action\nthat redirects to your custom export view:

\n
Code
from django.contrib.contenttypes.models import ContentType\nfrom django.http import HttpResponseRedirect\n\n\ndef export_selected_objects(modeladmin, request, queryset):\n    selected = queryset.values_list("pk", flat=True)\n    ct = ContentType.objects.get_for_model(queryset.model)\n    return HttpResponseRedirect(\n        "/export/?ct=%s&ids=%s"\n        % (\n            ct.pk,\n            ",".join(str(pk) for pk in selected),\n        )\n    )\n
\n

As you can see, the action is rather short; all the complex logic would belong\nin your export view. This would need to deal with objects of any type, hence\nthe business with the ContentType.

\n

Meunlis tampilan ini adalah sisa dari sebuah latihan ke pembaca.

\n
\n
\n

Membuat tindakan tersedia lebar-situsLink to this heading#

\n
\n
\nAdminSite.add_action(action, name=None)Link to this definition#
\n

Some actions are best if they're made available to any object in the\nadmin site -- the export action defined above would be a good candidate.\nYou can make an action globally available using\nAdminSite.add_action(). For example:

\n
Code
from django.contrib import admin\n\nadmin.site.add_action(export_selected_objects)\n
\n

This makes the export_selected_objects action globally available as an\naction named "export_selected_objects". You can explicitly give the action\na name -- good if you later want to programmatically remove the\naction -- by passing a second argument to\nAdminSite.add_action():

\n
Code
admin.site.add_action(export_selected_objects, "export_selected")\n
\n
\n\n
\n
\n

Meniadakan tindakanLink to this heading#

\n

Terkadang anda butuh meniadakan beberapa tindakan -- khususnya itu registered site-wide -- untuk obyek-obyek tertentu. Ada sedikit cara anda dapat meniadakan tindakan:

\n
\n

Meniadakan tindakan lebar-situsLink to this heading#

\n
\n
\nAdminSite.disable_action(name)Link to this definition#
\n

If you need to disable a site-wide action you\ncan call AdminSite.disable_action().

\n

Sebagai contoh, anda dapat menggunakan metode ini memindahkan tindakan "delete selected objects" siap-pakai:

\n
Code
admin.site.disable_action("delete_selected")\n
\n

Sekali anda telah melakukan diatas, tindakan itu akan tidak lagi tersedia lebar-situs.

\n

If, however, you need to reenable a globally-disabled action for one\nparticular model, list it explicitly in your ModelAdmin.actions list:

\n
Code
# Globally disable delete selected\nadmin.site.disable_action("delete_selected")\n\n\n# This ModelAdmin will not have delete_selected available\nclass SomeModelAdmin(admin.ModelAdmin):\n    actions = ["some_other_action"]\n    ...\n\n\n# This one will\nclass AnotherModelAdmin(admin.ModelAdmin):\n    actions = ["delete_selected", "a_third_action"]\n    ...\n
\n
\n\n
\n
\n

Meniadakan semua tindakan untuk ModelAdmin tertentuLink to this heading#

\n

If you want no bulk actions available for a given ModelAdmin, set\nModelAdmin.actions to None:

\n
Code
class MyModelAdmin(admin.ModelAdmin):\n    actions = None\n
\n

Ini memberitahu ModelAdmin untuk tidak memperlihatkan atau mengizinkan tindakan apapun, termasuk site-wide actions apapun.

\n
\n
\n

Tindakan mengadakan dan meniadakan bersyaratLink to this heading#

\n
\n
\nModelAdmin.get_actions(request, action_location=ActionLocation.CHANGE_LIST)Link to this definition#
\n

Akhirnya, anda dapat secara kondisional mengadakan atau meniadakan tindakan-tindakan pada sebuah per-permintaan (dan karenanya berdasarkan per-pengguna) dengan mengutamakan ModelAdmin.get_actions().

\n

This returns a dictionary of actions allowed for the specific\naction_location. The keys are action names, and the values are\nAction objects.

\n

Sebagai contoh, jika anda hanya ingin pengguna yang namanya dimulai dengan 'J' untuk dapat menghapus obyek-pbyek dalam jumlah besar:

\n
Code
class MyModelAdmin(admin.ModelAdmin):\n    ...\n\n    def get_actions(self, request, action_location=ActionLocation.CHANGE_LIST):\n        actions = super().get_actions(request, action_location=action_location)\n        if request.user.username[0].upper() != "J":\n            if "delete_selected" in actions:\n                del actions["delete_selected"]\n        return actions\n
\n\n
\n\n
\n
\n
\n

Pengaturan perizinan untuk tindakanLink to this heading#

\n

Actions may limit their availability to users with specific permissions by\nwrapping the action function with the action()\ndecorator and passing the permissions argument:

\n
Code
@admin.action(permissions=["change"])\ndef make_published(modeladmin, request, queryset):\n    queryset.update(status="p")\n
\n

Tindakan make_published() hanya akan tersedia pada pengguna yang melewatkan pemeriksaan ModelAdmin.has_change_permission().

\n

If permissions has more than one permission, the action will be available\nas long as the user passes at least one of the checks.

\n

Available values for permissions and the corresponding method checks are:

\n\n

Anda dapat menentukan nilai lain apapun selama anda menerapkan metode has__permission(self, request) sesuai pada ModelAdmin.

\n

Sebagai contoh:

\n
Code
from django.contrib import admin\nfrom django.contrib.auth import get_permission_codename\n\n\nclass ArticleAdmin(admin.ModelAdmin):\n    actions = ["make_published"]\n\n    @admin.action(permissions=["publish"])\n    def make_published(self, request, queryset):\n        queryset.update(status="p")\n\n    def has_publish_permission(self, request):\n        """Does the user have the publish permission?"""\n        opts = self.opts\n        codename = get_permission_codename("publish", opts)\n        return request.user.has_perm("%s.%s" % (opts.app_label, codename))\n
\n
\n

Controlling where actions are availableLink to this heading#

\n\n

By default, admin actions are available on the change list page only. You can\ncontrol where an action appears using the location argument of the\n@admin.action decorator.

\n

For example, to make an action available only on the change form, set\nlocation to ActionLocation.CHANGE_FORM:

\n
Code
from django.contrib import admin\nfrom django.contrib.admin import ActionLocation\n\n\n@admin.action(location=ActionLocation.CHANGE_FORM)\ndef make_published(modeladmin, request, queryset): ...\n
\n

To make an action available on both the change list and the change form:

\n
Code
@admin.action(\n    location=[ActionLocation.CHANGE_FORM, ActionLocation.CHANGE_LIST],\n    description="Publish",\n    description_plural="Mark selected stories as published",\n)\ndef make_published(modeladmin, request, queryset): ...\n
\n

Notice that description and description_plural were provided. These are\noptional but the admin action will be labeled by description in the admin\nchange form and description_plural in the admin change list.

\n

You can customize how actions are rendered by overriding admin templates.\nThe change list page uses admin/actions.html and the change form page uses\nadmin/change_form_actions.html. Note that the change form template inherits\nfrom the change list actions template.

\n
\n
\n
\n
\n

The action decoratorLink to this heading#

\n
\n
\naction(*, permissions=None, description=None, description_plural=None, location=ActionLocation.CHANGE_LIST)Link to this definition#
\n

This decorator can be used for setting specific attributes on custom action\nfunctions that can be used with\nactions:

\n
Code
@admin.action(\n    permissions=["publish"],\n    description="Mark selected stories as published",\n)\ndef make_published(self, request, queryset):\n    queryset.update(status="p")\n
\n

This is equivalent to setting some attributes (with the original, longer\nnames) on the function directly:

\n
Code
def make_published(self, request, queryset):\n    queryset.update(status="p")\n\n\nmake_published.allowed_permissions = ["publish"]\nmake_published.short_description = "Mark selected stories as published"\n
\n

Use of this decorator is not compulsory to make an action function, but it\ncan be useful to use it without arguments as a marker in your source to\nidentify the purpose of the function:

\n
Code
@admin.action\ndef make_inactive(self, request, queryset):\n    queryset.update(is_active=False)\n
\n

In this case it will add no attributes to the function.

\n
\n
Parameter:
\n
    \n

  • permissions -- A list of permission codenames that restrict the action\nto users who have at least one of the defined permissions. This sets\nthe allowed_permissions attribute on the function. See\nPengaturan perizinan untuk tindakan for details.

    • \n

  • description -- A human-readable description of the action to be\nrendered in the admin. If description is not provided, Django\nrenders the function's name, converting underscores to spaces and\ncapitalizing the first letter of the first word. This sets the\nshort_description attribute on the function.

    • \n

  • description_plural -- A human-readable description of the action used\nin contexts where plural wording is required, such as on the admin\nchange list. If description_plural is not provided, falls back to\ndescription. This sets the plural_description attribute on the\nfunction.

    • \n

  • location -- Specifies where the action is available. Accepts either a\nsingle ActionLocation value or an iterable of values. If\nomitted, the action is only available on the admin change list. See\nControlling where actions are available for details.

    • \n
\n
\n
\n\n\n
\n\n
\n
\n

ActionLocationLink to this heading#

\n\n
\n
\nclass ActionLocationLink to this definition#
\n

Enum of allowed values for the location parameter of the\naction() decorator.

\n
\n
\nCHANGE_FORMLink to this definition#
\n

The action is available on the admin change form. When an action is run,\nany unsaved changes on the admin change form will be lost.

\n
\n\n
\n
\nCHANGE_LISTLink to this definition#
\n

The action is available on the admin change list.

\n
\n\n
\n\n
\n
\n

ActionLink to this heading#

\n\n
\n
\nclass ActionLink to this definition#
\n

Represents an action. Actions should be defined using the action()\ndecorator.

\n
\n
\nfuncLink to this definition#
\n

The action function. See Menulis fungsi tindakan for details.

\n
\n\n
\n
\nnameLink to this definition#
\n

The action function name.

\n
\n\n
\n
\ndescriptionLink to this definition#
\n

A human-readable description of the action to be rendered in the admin.

\n
\n\n
\n
\nplural_descriptionLink to this definition#
\n

A human-readable description of the action used in contexts where\nplural wording is required.

\n
\n\n
\n
\nlocationsLink to this definition#
\n

A list of ActionLocation values the admin action can be\nrendered.

\n
\n\n
\n\n
","rootId":"admin-actions","toc":[{"title":"Menulis tindakan","anchor":"writing-actions","children":[{"title":"Menulis fungsi tindakan","anchor":"writing-action-functions","children":[]},{"title":"Menambahkan tindakan pada ModelAdmin","anchor":"adding-actions-to-the-modeladmin","children":[]},{"title":"Penanganan kesalahan di tindakan","anchor":"handling-errors-in-actions","children":[]}]},{"title":"Teknik-teknik tindakan lanjutan","anchor":"advanced-action-techniques","children":[{"title":"Tindakan sebagai metode ModelAdmin","anchor":"actions-as-modeladmin-methods","children":[]},{"title":"Tindakan yang menyediakan halaman menengah","anchor":"actions-that-provide-intermediate-pages","children":[]},{"title":"Membuat tindakan tersedia lebar-situs","anchor":"making-actions-available-site-wide","children":[]},{"title":"Meniadakan tindakan","anchor":"disabling-actions","children":[{"title":"Meniadakan tindakan lebar-situs","anchor":"disabling-a-site-wide-action","children":[]},{"title":"Meniadakan semua tindakan untuk ModelAdmin tertentu","anchor":"disabling-all-actions-for-a-particular-modeladmin","children":[]},{"title":"Tindakan mengadakan dan meniadakan bersyarat","anchor":"conditionally-enabling-or-disabling-actions","children":[]}]},{"title":"Pengaturan perizinan untuk tindakan","anchor":"setting-permissions-for-actions","children":[{"title":"Controlling where actions are available","anchor":"controlling-where-actions-are-available","children":[]}]}]},{"title":"The action decorator","anchor":"the-action-decorator","children":[]},{"title":"ActionLocation","anchor":"actionlocation","children":[]},{"title":"Action","anchor":"action","children":[]}],"breadcrumbs":[{"docname":"ref/index","title":"Acuan API","url":"/id/6.1/ref/"},{"docname":"ref/contrib/index","title":"Paket contrib","url":"/id/6.1/ref/contrib/"},{"docname":"ref/contrib/admin/index","title":"Situs admin Django","url":"/id/6.1/ref/contrib/admin/"}],"prev":{"docname":"ref/contrib/admin/index","title":"Situs admin Django","url":"/id/6.1/ref/contrib/admin/"},"next":{"docname":"ref/contrib/admin/filters","title":"ModelAdmin List Filters","url":"/id/6.1/ref/contrib/admin/filters/"},"formats":{"html":"/id/6.1/ref/contrib/admin/actions/","markdown":"/id/6.1/ref/contrib/admin/actions.md","json":"/id/6.1/ref/contrib/admin/actions.json"},"source":"https://github.com/django/django/blob/stable/6.1.x/docs/ref/contrib/admin/actions.txt","official":"https://docs.djangoproject.com/id/6.1/ref/contrib/admin/actions/","inVersions":["6.1","6.0","5.2","5.1","5.0","4.2","4.1","4.0","3.2","3.1","3.0","2.2","2.1","2.0","1.11","1.10","1.9"],"inLocales":["en","sv","zh-hans","ga","fr","ja","id","it","pt-br","ko","es","el","pl"]}