[Koha-bugs] [Bug 32563] Reservedate becomes expirationdate in some cases

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

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

Anneli Österman <anneli.osterman at koha-suomi.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Signed Off                  |Patch doesn't apply
                 CC|                            |anneli.osterman at koha-suomi.
                   |                            |fi

--- Comment #3 from Anneli Österman <anneli.osterman at koha-suomi.fi> ---
I tested this in PTFS-Europe's sandbox and noticed that if
DefaultHoldExpirationdate is set and I trap a hold and revert the hold's
waiting status and then try to cancel the hold, I get an error.

{UNKNOWN}: Can't locate object method "clone" via package "2023-01-27" (perhaps
you forgot to load "2023-01-27"?) at /kohadevbox/koha/Koha/Hold.pm line 898. at
/kohadevbox/koha/Koha/Hold.pm line 762
 at /usr/share/perl5/DBIx/Class/Exception.pm line 77

The hold's expirationdate should have been set back to the original
expirationdate but it becomes empty. When I check reserves table the hold does
not have expirationdate or patron_expiration_date set.

If DefaultHoldExpirationdate is not set cancelling the hold works fine after
these same steps.

To reproduce:

1. Go to
/cgi-bin/koha/admin/preferences.pl?op=search&searchfield=DefaultHoldExpirationdate
2. Setup default expiration date to be 1 year from reserve date for example.
3. Switch to catalog to any biblio with item for example
/cgi-bin/koha/catalogue/detail.pl?biblionumber=1 and place a hold for any
borrower.
4. Check in an item from the biblio you reserved and your hold gets trapped.
5. Go to the biblio and to it's holds page and revert the waiting status of
your hold.
6. Notice that expiration date is empty.
7. Cancel the hold and get an error.

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