Detail page: per-object (single-pk) actions missing — only the changelist multi-select actions render (follow-up to #555 / PR #562)

[martin-castro-laminr-ai]

Symptom

On the detail page of a single object (/admin2/<app>/<model>/<pk>/change/), the action toolbar shows the changelist multi-select actions (the ones declared on ModelAdmin.actions = [...]) but does not show the per-object actions registered via django-object-actions (change_actions = [...]) — the single-pk operations that should appear on the detail page only.

Confirmed on django-admin-react==1.0.1 (latest stable), django-object-actions declared correctly on the ModelAdmin (verified via the legacy /admin/ HTML detail page, which renders them as expected).

Expected

On a detail page, two distinct sets of buttons should be visible:

1. Per-object actions (change_actions): operations meaningful on the single object being viewed (e.g. "Reprocess", "Approve", "Mark as reviewed"). These are declared on the ModelAdmin via django-object-actions.DjangoObjectActions.change_actions. They take no multi-select — they always operate on the current pk.
2. Edit / Delete standard admin buttons.

The bulk changelist actions ("Delete selected …", "Disable All Selected …", "Reprocess selected …") should not appear on the detail page, or at minimum should be visually demoted — they're list-page semantics applied to a "selection" of one, which is confusing.

Actual

Detail page renders, in order:

• All ModelAdmin.actions (bulk operations), worded "selected files" / "selected items".
• Edit.
• Delete.

No change_actions (single-pk buttons) appear, even when the ModelAdmin declares them and the REST API exposes them at /api/v1/admin/<app>/<model>/<pk>/change-actions/ (or equivalent).

PR #562 ("detail-page admin action buttons reusing the changelist actions API") shipped the wrong primitive: it surfaces the changelist action endpoint (multi-select, list semantics) on the detail page instead of the single-pk change-action endpoint (django-object-actions).

Probable cause

DetailPage.tsx is wired to the changelist actions endpoint (POST /api/.../actions/) with pks=[currentPk] rather than the change-actions endpoint that surfaces ModelAdmin.change_actions from django-object-actions.

The REST API side appears to already expose change_actions (see #540 / be589ad feat(api): object-level change-page actions (django-object-actions)), so the gap is on the SPA side: it's calling the wrong endpoint.

Suggested fix direction

In DetailPage.tsx, fetch and render change_actions from the per-object endpoint introduced in #540 instead of (or in addition to) the changelist actions. The bulk "selected files" actions should either be removed from the detail page entirely, or rendered only in a clearly separate group ("Apply to this object as a list of 1") for parity with the legacy admin — but per-object actions must take precedence and be present.

Repro

1. Declare a ModelAdmin with both actions = [bulk_op] and change_actions = ['per_object_op'] via django-object-actions.
2. Open the SPA detail page for any instance: /admin2/<app>/<model>/<pk>/change/.
3. Observe: bulk_op button is present; per_object_op button is absent.
4. Open the same instance in the legacy admin: /admin/<app>/<model>/<pk>/change/.
5. Observe: per_object_op IS present in legacy, confirming the ModelAdmin declares it and the API surfaces it.

References

• Original issue: Detail page: per-object action buttons reusing the changelist actions API (single-pk runs) #555
• Closing PR (incomplete): feat(spa): detail-page admin action buttons reusing the changelist actions API (#555) #562
• Related (back-end side, appears complete): feat(api): object-level change-page actions (#236) #540, commit be589ad
• Affected file: frontend/apps/web/src/pages/DetailPage.tsx

[MartinCastroAlvarez]

Shipped in v1.0.2 (PR #573, commit e3cdd34). Live on PyPI: https://pypi.org/project/django-admin-react/1.0.2/

The detail page no longer renders the changelist (bulk) actions — those were the wrong primitive for a single-object view. Per-object actions from django-object-actions (change_actions) continue to render via <ObjectActionButton> against POST <app>/<model>/<pk>/action/<name>/, which is the correct single-pk endpoint. Side effect: ~1.4 kB SPA bundle reduction from removing the unused useList + runAction + confirm-modal code paths.

[martin-castro-laminr-ai]

Additional observation on 1.0.2: the gap is broader than first reported. On some detail pages the action toolbar shows nothing action-related at all — only History, Edit, Delete. No bulk actions, no per-object actions, even when the ModelAdmin declares both actions = [...] AND change_actions = [...] (via django-object-actions).

So the symptoms across detail pages are inconsistent:

• Some models: bulk actions surface, per-object change_actions don't. (Original report.)
• Other models: neither bulk nor per-object actions surface — toolbar shows only standard History / Edit / Delete.

This suggests the SPA's detail page isn't reliably calling the per-model actions endpoint, or that the endpoint returns different shapes for different ModelAdmin configurations and the SPA's renderer silently ignores responses it doesn't recognize. Either way, the expected behavior is the same as the legacy /admin/ detail page: render every action the ModelAdmin declares.