April 2024 - Koha-bugs - lists.koha-community.org

[Bug 35535] New: Candcel hold -button does not work in pop-up (Hold found, item is already waiting)
by bugzilla-daemon＠bugs.koha-community.org 21 Dec '24

21 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35535 Bug ID: 35535 Summary: Candcel hold -button does not work in pop-up (Hold found, item is already waiting) Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: minna.kivinen(a)hamk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you check in an item having awaiting hold there comes a pop-up window. There is a button saying Cancel hold. This button does not do anything. (you are able to cancel the hold from other hold windows) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 35840] New: Local use is double-counted when using both RecordLocalUseOnCheckin and statistical patrons
by bugzilla-daemon＠bugs.koha-community.org 21 Dec '24

21 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35840 Bug ID: 35840 Summary: Local use is double-counted when using both RecordLocalUseOnCheckin and statistical patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: - enable RecordLocalUseOnReturn - create a statistical patron category and a patron in it - check an item out to your statistical patron - count local use entries with a report: SELECT * FROM statistics WHERE type='localuse' AND itemnumber= (your item) - see that your one checkout has created 2 entries in statistics It seems plausible that a single library might want to use these two features concurrently to count different things, but doing so creates an inflated count. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 64

[Bug 35352] New: Cannot hide SMSalertnumber via BorrowerUnwantedField
by bugzilla-daemon＠bugs.koha-community.org 21 Dec '24

21 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35352 Bug ID: 35352 Summary: Cannot hide SMSalertnumber via BorrowerUnwantedField Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Add a value to SMSSendDriver like 'Emial'. 2. Go to BorrowerUnwantedField and attempt to hide "Mobile phone number (smsalertnumber)" 3. Go to members/memberentry.pl and see the field is not hidden. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 30116] New: When using UseACQFrameworkForBiblioRecords visibility settings have no effect
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30116 Bug ID: 30116 Summary: When using UseACQFrameworkForBiblioRecords visibility settings have no effect Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When UseACQFrameworkForBiblioRecords is active the form for adding a bibliographic record can be configured via the ACQ framework. But you can't hide/preset fields as removing the editor checkbox has no effect. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 31098] New: The option tohe option of "export database" and "export settings" are not available.
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31098 Bug ID: 31098 Summary: The option tohe option of "export database" and "export settings" are not available. Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: vbovictor(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I enabled in instance-conf.xml <backup_db_via_tools>1</backup_db_via_tools> <backup_conf_via_tools>1</backup_conf_via_tools> In Tools --> Export Data The option tohe option of "export database" and "export settings" are not available. Here's the information that appears: "Note: This generated file will be very large, and will be generated daily." "Unfortunately, there are no backups available." -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 30503] New: Ability to include graphic in labels
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30503 Bug ID: 30503 Summary: Ability to include graphic in labels Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org I wonder if koha could include a graphic/image to its labels -even better in overlay form- so that a decent ex-libris label could be produced. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 31284] New: Add a calendar log
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '24

19 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31284 Bug ID: 31284 Summary: Add a calendar log Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Changes to the calendar can affect various things in Koha, including due dates, fine calculation and sending of overdue notices. Sometimes a strange behavior can only be explained by holidays having been added or removed. In order to "debug" these issues, it would be great if changes to the calendar were logged. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 34597] New: Expired patrons can still place ILL requests through OPAC
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '24

19 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34597 Bug ID: 34597 Summary: Expired patrons can still place ILL requests through OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com CC: katrin.fischer(a)bsz-bw.de, magnus(a)libriotech.no, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com Noticed this, not sure if very severe or not. But I wonder if placing an ILL request should be included in BlockExpiredPatronOpacActions. To reproduce, on k-t-d: 1) Enable ILLmodule and install FreeForm, run: bash <(curl -s https://raw.githubusercontent.com/ammopt/koha-ill-dev/master/start-ill-dev.…) 2) Make koha/koha user expired, run mysql-kohadev: update borrowers set dateexpiry = '2020-12-31' where borrowernumber=51; 3) Visit OPAC/cgi-bin/koha/opac-user.pl and verify there's a user expired notification 4) Visit OPAC/cgi-bin/koha/opac-illrequests.pl and create a new ILL request 5) It's created with no issue -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 52

[Bug 19876] New: Koha::Account->pay() does not exit specific fine loop when balance is used up
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '24

19 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19876 Bug ID: 19876 Summary: Koha::Account->pay() does not exit specific fine loop when balance is used up Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If a patron selects specific fines to pay and enters an amount less than all of those fines the loop will continue through all fines. This can be problematic for lost fines which are not paid or not paid fully as they will be marked 'Paid for...' and returned -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 17138] New: UpdateFine() modyfies existing fine records even when there is no need
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '24

19 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17138 Bug ID: 17138 Summary: UpdateFine() modyfies existing fine records even when there is no need Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In C4/Overdues.pm: 574: # we're updating an existing fine. Only modify if amount changed 577: if ( $data->{'amount'} != $amount ) { for some numbers (e.g. 5.60) the comparison in line 577 fails ($data->{'amount'} is decimal(28,6) i.e. a string, and $amount may be a floating point number with no exact binary representation). E.g. when the fine amounts are multiple of 0.20, it fails for the 33.3% of the amounts (on average). Depending on the fine charging settings, this may trigger unnecessary database writes (and a lot of them). If 'Fine Charging Interval' is 1 day, this has very little practical consequences (misc/cronjobs/fines.pl script is usually run once per day, and all fines need an increase anyway). But if the charging interval is longer, e.g. 7 days, in a given day amount changes only for the 1/7 of the fines (again, on average), and over 60% of the database writes would be redundant. To reproduce: 1) run misc/cronjobs/fines.pl 2) add warn "AMOUNT ".$data->{'amount'}." vs $amount"; below line 577 in C4/Overdues.pm 3) run misc/cronjobs/fines.pl again 4) you'll see some warnings like 'AMOUNT 5.600000 vs 5.6' or: dump accountlines table after step 1), run the script 2nd time, dump the table again and compare the contents - some of the records would have a different timestamp. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38