-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
fix role update #13025
fix role update #13025
Conversation
src/OrchardCore.Modules/OrchardCore.Roles/Controllers/AdminController.cs
Outdated
Show resolved
Hide resolved
…troller.cs Co-authored-by: Mike Alhayek <[email protected]>
Thanks for re-opening this PR but maybe I will open a new PR as I already started to work on it locally to check different things as per my comment #13024 (comment) @MikeAlhayek maybe a different approach for example to not execute the RoleUpdater on each shell activation if possible, I think I will ask you some questions to confirm what was intended to be done. Hmm, one question on the fly, yes in the controller, dynamic permissions was not taken into account, hmm maybe we need to take them into account also in the RoleUpdater, will see. |
@jtkech I in the In the Admin I agree we should not be using We should be using the following as per your suggestions.
or
|
Even if here all So okay the other breaking change, as stated by @gvkries #13035 (comment), is that on an existing installation not having yet the permissions history, some permissions get back to some roles on startup. |
fix : #13024
Planned to also fix #13035.
chrome_HV9oeSsdLF.mp4