https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41045
--- Comment #4 from David Cook <[email protected]> --- This is an interesting problem. We should fix this atomic update in "main", 24.11, 25.05, and 25.11 so that newly upgraded sites don't suffer this same problem. But for sites that are already upgraded... I don't know that we can do any automated remediation, because we can't know which users we updated automatically and which were given these permissions after the fact. We might just have to add a warning in the release notes telling people to review the permissions of all their users because of this mistake that was made. -- Locally, I created a permission audit tool many years ago within Koha. It doesn't have the best UI but it does provide an overview of all permissions for all patrons. Something like that would be useful in this situation... otherwise perhaps an SQL report we could provide in the release notes so that people can double-check their users. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
