]> git.evergreen-ils.org Git - working/Evergreen.git/commit
The absence of holds-triggered recall rules should not break hold targeting
authordbs <dbs@dcc99617-32d9-48b4-a31d-7c20da2025e4>
Mon, 22 Nov 2010 04:46:49 +0000 (04:46 +0000)
committerdbs <dbs@dcc99617-32d9-48b4-a31d-7c20da2025e4>
Mon, 22 Nov 2010 04:46:49 +0000 (04:46 +0000)
commit4d3cf26d5b863afb8ec8ef7814aa96c2d2cb33c9
tree3f4fe04060ded2929b16999893f849fdded42990
parent7cb3b7498aa307e3334a8f29d9492efcd7f41015
The absence of holds-triggered recall rules should not break hold targeting

Thanks to Galen Charlton for pointing out that if rules were not set for
holds-triggered recalls, then all hold targeting would break because of
an assumption the code made that one could invoke the ->{value} member
of the OU settings. But of course the return value for an unset OU setting
is undef, not an object with an undef ->{value} member.

This should unbreak that code path.

git-svn-id: svn://svn.open-ils.org/ILS/trunk@18816 dcc99617-32d9-48b4-a31d-7c20da2025e4
Open-ILS/src/perlmods/OpenILS/Application/Storage/Publisher/action.pm