Multiple actions in lists about flask-admin

[mrjoes]

Hi,

I pushed my changes. You can see how mass delete action was implemented
for SQLA models here:

https://github.com/mrjoes/flask-admin/blob/master/flask_admin/contrib/sqlamodel/view.py#L553

So, if you want to add your custom action:

1. Create method which accepts list of ids
2. Decorate it with @action
3. Change is_action_allowed to do some fancy logic

Checkboxes won't be displayed if no actions are visible (drop down element
won't be displayed either).
I also separated actions library into separate file, so file admin is now
using it and can mass-delete files too.

Hope it helps.

Serge.

On Sun, Aug 19, 2012 at 6:02 AM, F. Gabriel Gosselin <
[email protected]> wrote:

I agree that Flask-Peewee's approach is not ideal (the delete and export
are hard coded).

Please do look at the code I contributed. It does have the potential to be
flexible. Actions can be added to self._actions through a setter instead
to make it more flexible on a per-AdminModel basis.

In particular I'm curious how you would handle universal actions
(available to all Admin lists).

—
Reply to this email directly or view it on GitHubhttps://github.com/mrjoes/flask-admin/issues/44#issuecomment-7850159.

[mrjoes]

I took a look and will think how to implement this functionality in a
robust way.

Probably tomorrow I will create a dev branch and will commit my thoughts to
it. What's in Flask-Peewee is not really flexible - mass updates are
disconnected from the administrative view, they don't really fit into
flask-admin ideology.

[evidens]

I agree that Flask-Peewee's approach is not ideal (the delete and export are hard coded).

Please do look at the code I contributed. It does have the potential to be flexible. Actions can be added to self._actions through a setter instead to make it more flexible on a per-AdminModel basis.

In particular I'm curious how you would handle universal actions (available to all Admin lists).

[mrjoes]

Closing this one, actions were implemented.

[vladi-dev]

I wish this was included in docs and not just in API section. Spent much time trying to figure this out by reading the source code.

[petrus-jvrensburg]

@emve-dev Yes definitely!

Would you mind adding a couple of paragraphs and code snippet to https://github.com/flask-admin/flask-admin/blob/master/doc/advanced.rst?

[vladi-dev]

My pleasure. #970
Let me know if this is good enough.

[petrus-jvrensburg]

Thanks, that's perfect!

[boolbag]

@emve-dev
Wondering if you would happen to have thoughts on this related functionality (custom actions in list view)?

Thanks in advance to anyone who might share insights.

[R2calex]

Hi,

I pushed my changes. You can see how mass delete action was implemented
for SQLA models here:

https://github.com/mrjoes/flask-admin/blob/master/flask_admin/contrib/sqlamodel/view.py#L553

So, if you want to add your custom action:

1. Create method which accepts list of ids
2. Decorate it with @action
3. Change is_action_allowed to do some fancy logic

Checkboxes won't be displayed if no actions are visible (drop down element
won't be displayed either).
I also separated actions library into separate file, so file admin is now
using it and can mass-delete files too.

Hope it helps.

Serge.

On Sun, Aug 19, 2012 at 6:02 AM, F. Gabriel Gosselin <
[email protected]> wrote:

I agree that Flask-Peewee's approach is not ideal (the delete and export
are hard coded).
Please do look at the code I contributed. It does have the potential to be
flexible. Actions can be added to self._actions through a setter instead
to make it more flexible on a per-AdminModel basis.
In particular I'm curious how you would handle universal actions
(available to all Admin lists).
—
Reply to this email directly or view it on GitHubhttps://github.com/mrjoes/flask-admin/issues/44#issuecomment-7850159.

Page not found :(, could you make it post it again please?