Show admin actions on the edit pages too

[Florian Apolloner]

Currently the workflow for comment moderation might look like this (without knowing the comment moderation admin actions ;)):

• Look at the overview page
• If in doubt open the comment in a new page
• if it's spam go back to the previous page, select it and execute the admin action

We could redisplay the admin actions box in the detail views (where they of course would only effect the current object) to prevent the unneeded roundtrip.

[Jannis Leidel]

Interesting idea!

One question though: The current admin actions usually return the user to the object list, what would be the behavior after running the action from the object detail page?

[Florian Apolloner]

See: ​http://groups.google.com/group/django-developers/browse_thread/thread/3fee283ae3695352 for the discussion.

[Aaron Riedener]

Is it possible to give a short input on this ticket? I'd prefer to have a button like "save", "save and add", "save and edit" istead of a drop down list to select the button. Perhaps it possible to make that selectable.
What do you think about that?

[hamlet]

Regarding the design issue let me propose to allow for a list of actions that are offered as individual buttons on the change page next to 'Save', 'Save and add another': 'Save and /action/', e.g. via:

class ArticleAdmin(admin.ModelAdmin):
    list_display = ['title', 'status']
    actions = [publish, unpublish, comments_close]
    save_plus_action = [unpublish, comments_close]
    save_plus_action_done = [publish]

As it's unclear whether the list or change page should display after that, we would need the secondary option, say save_plus_action_done to leave the change page after saving and firing this action.

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Aymeric Augustin]

Revert accidental batch modification.

[Danilo Bargen]

This would be a very nice change. There are some types of changes that shouldn't be done as a batch process, as they might depend on each other, so the order in which they're processed is critical.

[jgmize]

submitted pull request: ​https://github.com/django/django/pull/928

[jgmize]

Admin change action screenshot

[Florian Apolloner]

@jgmize I can't comment about the design but I'd like to propose some changes: It would be nice if one where able to reuse the existing actions, this would mean supporting short_description and short_description_plural and using the correct version depending on the page (+some backwards shim). Also it would be interesting to see how your current stuff looks with save_on_top = True

[Jacob Walls]

A very old patch, but a start nonetheless in f62d6e44dda5f457d8108fbae005e026b82e138e in the PR linked above.

[Marcelo Galigniana]

​PR

[Marcelo Galigniana]

Going to change actions buttons -> dropdown with actions (same as list)

[Marcelo Galigniana]

I'm leaving a message here to let you know that I'm still active and contributing but I don't have enough time to dedicate to this big ticket yet.

If someone has the time to work in it feel free to claim it! If not -> I'll be working on it later for sure, but I don't know exactly when.

Thank you!

[Marcelo Galigniana]

Update: I've started to working again! Pull request in draft, with test passing, but there is documentation and other changes to do!

[Marcelo Galigniana]

Test failing!

Working on fix.

[Marcelo Galigniana]

Tests passing