[Koha-bugs] [Bug 29877] MaxReserves should be enforced consistently between staff interface and API

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29877

--- Comment #7 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
(In reply to Kyle M Hall from comment #6)
> (In reply to Jonathan Druart from comment #5)
> > Shouldn't we fix the staff interface's behaviour instead?
> > Considering 0 as infinite looks like a bug.
> 
> I see your point, but that would break untold numbers of Koha installs.
> There is long historical precedent of having zero = blank = feature is
> disabled. If you want to change that, it should be on a separate bug report
> and will need a database update and many large warnings all over the upgrade
> notes.

I am actually confused with this one... for holds, we here always assumed 0 to
mean 'no holds allowed' - otherwise there would be no way to turn this off. 

I agree that leaving empty is often meant to mean "infinite", like for the
number of checkouts. But also 0 there means no checkouts. 

So there is definitely an inconsistency.

I believe we totally need a way to say 'no holds' in the rules - and also
believe that it has worked at some point... are we sure there this was not a
regression with switch to circulation_rules or similar?

-- 
You are receiving this mail because:
You are watching all bug changes.