https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14695
--- Comment #225 from Benjamin Rokseth <[email protected]> --- Seems the behaviour is intentional: method forced_hold_level is implemented in Koha/Holds.pm and used in reserve/request.pl by this patch set, and is also commented: Koha/Holds.pm: >If a patron has multiple holds for a single record, >those holds must be either all record level holds, >or they must all be item level holds. > >This method should be used with Hold sets where all >Hold objects share the same patron and record. > >This method will return 'item' if the patron has >at least one item level hold. It will return 'record' >if the patron has holds but none are item level, >Finally, if the patron has no holds, it will return >undef which indicateds the patron may select either >record or item level holds, barring any other rules >that would prevent one or the other. but I'm not sure of the implementation since it seems to favour 'record' in any other case than existing item level hold? -- 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/
