[Koha-bugs] [Bug 31391] Staff-side recalls

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

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

--- Comment #17 from David Nind <david at davidnind.com> ---
(In reply to Aleisha Amohia from comment #16)
> (In reply to David Nind from comment #14)
> > Hi Aleisha.
> > 
> > Apologies for Failing QA on this again!
> > 
> > The previous issue reported is fixed (step 7 - can't cancel a recall from
> > OPAC when RecallsInterface = staff interface only).
> > 
> > I've identified a new issue with step 5 - cancelling a recall from the
> > recalls section for a record - record doesn't exist after cancelling a
> > recall using the 'Cancel selected recalls' button and selecting the normal
> > section. 
> > 
> > To replicate:
> > 1. Place a recall
> > 2. Go to the recalls section for the record on the staff interface
> > 3. Using Actions > Cancel works as expected
> > 4. Repeat steps 1 and 2.
> > 5. Cancel the recall by ticking the box next to the item and then selecting
> > 'Cancel selected recalls' button doesn't work as expected:
> >    . The recall is cancelled
> >    . URL = http://127.0.0.1:8081/cgi-bin/koha/recalls/request.pl
> >    . Breadcrumb = Home > Catalog > No title > Place a recall 
> >    . Click on the normal section:
> >       message = The record you requested does not exist ().
> >       URL =
> > http://127.0.0.1:8081/cgi-bin/koha/catalogue/detail.pl?biblionumber=
> > 
> > I'm not sure if I tested this last time. I'm also sure I've seen this when
> > testing something else a while ago, but can't remember or find what bug it
> > was.
> 
> Fixed in latest follow-up

This is still not working for me and doesn't appear to be fixed.

If it helps, there is an entry in
/var/log/koha/kohadev/plack-intranet-error.log:
[2022/11/04 06:36:44] [WARN] Use of uninitialized value $biblionumber in
concatenation (.) or string at /kohadevbox/koha/recalls/request.pl     line 49.

Everything else continues to work as per the test plan.

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