-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ordering actions still rendered in action dropdown even if user don't have change permission. #400
Comments
Fair point. I have to fix that. |
Hi Jrief, I’d like to take this issue. If you could assign it to me, that would be helpful. I have read the Contributor's Guide and will follow it. |
@jrief, By when can we expect the new release? |
@drowsyzen you can come up with a pull request. I then will review it. |
@jrief i am working on the solution and will open pull request soon(by tomorrow). I have one query. There are four permissions for model in admin (add, change, delete, view). For which of these the dropdown should come and for which should it not? Currently I am making it so that users with view permission will not see the dropdowns. |
In my opinion the |
Python: 3.11
Django: 5.0.4
In admin change list, ordering actions [ move_to_exact_page, move_to_back_page, move_to_last_page, move_to_first_page, move_to_forward_page] still rendered in action dropdown even if user don't have change permission.
How can we remove those actions from dropdown on the basis of permission?
The text was updated successfully, but these errors were encountered: