http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8260
--- Comment #5 from David Cook <[email protected]> --- (In reply to comment #4) > The only problem is that it is called unconditionally on every load of the > page, even if we just reranked the list by deleting a member, or changing > the rank. > > For that reason i'm hesitant to sign off, does anyone else have a better > idea on how to solve this? I'm thinking fixing the borrower delete to not > delete borrowers who are in a routing list might be better. I agree with the problem, but I think it's still a good idea to be able to delete borrowers who are in routing lists. I think it would be a bit too finicky to have to go into each routing list and remove them before doing a complete delete. Why don't we call the new reorder function on patron delete? I see that there is already a function for handling patron deletes in regards to Lists/VirtualShelves. That probably makes the most sense. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
