open-ils.circ.checkout.full log_me() uses legacy arg for copy barcode

Bug #1778783 reported by Josh Stompro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Undecided
Unassigned
3.1
Won't Fix
Undecided
Unassigned
3.2
Won't Fix
Undecided
Unassigned
3.3
Won't Fix
Undecided
Unassigned
3.4
Won't Fix
Undecided
Unassigned
3.5
Won't Fix
Undecided
Unassigned
3.6
Won't Fix
Undecided
Unassigned
3.8
Fix Released
Undecided
Unassigned
3.9
Fix Released
Undecided
Unassigned

Bug Description

EG 2.10 and 3.1

http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Circulate.pm#l3960

The log_me sub uses the following to populate the $bc variable, which is supposed to be the copy barcode.

3962 my $bc = ($self->copy) ? $self->copy->barcode :
3963 $self->barcode;
3964 $bc ||= "";

But I believe that $self->barcode should actually be $self->copy_barcode, if the goal is to report on the barcode that was passed into open-ils.circ.checkout.full

The translate_legacy_args sub seems to look for arguments named barcode and change it to copy_barcode. I don't see that $self->barcode/$circulator->barcode is used anywhere but in the log_me sub.
http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Circulate.pm#l339

I would like to have a log of attempted checkouts, with whatever barcode is entered by the user. Currently the '$self->log_me("do_permit()");' call will only report the barcode if it exists in asset.copy, but I think the goal was to report whatever barcode was entered. I think when the translate_legacy_args was created the log_me sub just wasn't updated.

Josh

Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :
tags: added: pullrequest
Michele Morgan (mmorgan)
Changed in evergreen:
milestone: none → 3.3.4
Changed in evergreen:
milestone: 3.3.4 → 3.3.5
Changed in evergreen:
milestone: 3.3.5 → 3.4.2
Changed in evergreen:
milestone: 3.4.2 → 3.4.3
Changed in evergreen:
milestone: 3.4.3 → 3.4.4
Changed in evergreen:
milestone: 3.4.4 → 3.5.1
Changed in evergreen:
milestone: 3.5.1 → 3.5.2
Changed in evergreen:
milestone: 3.5.2 → 3.6.1
tags: added: cleanup
Changed in evergreen:
milestone: 3.6.1 → 3.6.2
Changed in evergreen:
milestone: 3.6.2 → 3.6.3
Changed in evergreen:
milestone: 3.6.3 → 3.6.4
Changed in evergreen:
milestone: 3.6.4 → 3.7.2
Changed in evergreen:
milestone: 3.7.2 → 3.7.3
Revision history for this message
Bill Erickson (berick) wrote :

Issue and fix confirmed. A handy debugging improvement. Thanks, Josh!

Changed in evergreen:
status: New → Won't Fix
milestone: 3.7.3 → none
tags: added: signedoff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.