404 for actions returned by get_object_actions() but not in objectactions

Currently if an admin view overrides get_object_actions() and returns an action not contained in the objectactions view’s attr, then invoking the action from the admin interface results in a 404.

This occurs because BaseDjangoObjectActions. get_tool_urls uses self. objectactions, not self.get_object_actions().

It seems this might be unavoidable, but is unexpected since it’s not documented, and annoying if you’re trying to create a base/mixin admin view class that use get_object_actions() to provide actions in addition to subclasses that provide their own.

[architux]

I’ve faced the same issue just now.

get_object_actions() method works if every action that it would conditionally enable or disable is listed above in change_actions or changelist_actions attribute. You should pass there everything that you may or may not use later.

I don’t know whether it should be fixed or not, but such a behavior should be mentioned in documentation to avoid same questions in the future.

[psalonen]

Are there any fixes available for this issue? I want to use these actions but i need the runtime customization of available actions per object.