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

[Bug 27992] New: when recording local use with STAT patron items are not checked in
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27992 Bug ID: 27992 Summary: when recording local use with STAT patron items are not checked in Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When recording local use using a statistical patron, the Lost status updates, but if an item is checked out, it does not get checked in. To replicate: 1. Create a Statistical Patron 2. Check out an item to the Stat Patron, that is checked out to another user 3. See that the local use is recorded, but the item does not get checked in 4. Check out an item that has a lost status and note that the local use is recorded, and the lost status is cleared In this situation, the item should be checked in/available status updated when it is "checked out" to the statistical patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 59

[Bug 38990] New: Statistical patron checkouts don't display alert that LOST value has been cleared
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38990 Bug ID: 38990 Summary: Statistical patron checkouts don't display alert that LOST value has been cleared Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 37505 resolved getting information about items when checking them out to statistical patrons, however lost values (aside from Claims) do not alert or display that it has been resolved when checked out to the statistical patron as of 24.05.06. To test: 1. Create a Statistical Patron 2. Set BlockReturnOfLostItems to Don't Block. 3. Mark an item as missing. 4. Check it out to the Statistical Patron. 5. You get a message "Local use recorded." <- You should see a message, "Item was lost, but has now been found." 6. Check your item - the lost value has been cleared and is now available. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 25530] New: Web installer font size too small to read on some screens
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25530 Bug ID: 25530 Summary: Web installer font size too small to read on some screens Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This may be subjective as I'm on a FullHD (1920x1080) laptop screen, but I noticed that the Web Installer font size is a bit too small to read. To be more specific, v18.11.16 is the last version where the body font-size property is set to 14px in bootstrap.min.css. From v19.05.00 onwards the size decreased to 12px and this makes the textual elements (including the button labels) appear a bit too small, and are harder to read compared to previous Koha versions. Please view the attached screenshots for a side-by-size comparison. I think this may be related to Bug 22023. Possibly relevant excerpt from commit a344b8cf8c: "The modified default CSS resets the base font size in Bootstrap to better match our global CSS. A side-effect of this is that toolbar buttons ended up looking smaller than they should. Changing the button class solves this." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 18983] New: koha-create does not default to --create-db
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18983 Bug ID: 18983 Summary: koha-create does not default to --create-db Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: CJSH(a)CJSHayward.com QA Contact: testopia(a)bugs.koha-community.org I reported in an email on the list that, after clearing away previous and possibly conflicting material, I found a .in file in /etc but didn't see how to make an appropriate koha-conf.xml. The reply I received was that there was apparently an issue that "koha-create library" should, by default, behave as if "koha-create --create-db library" had been entered. However, it did not. When I ran "koha-create --create-db library" it worked further and populated /etc/koha/sites/library with several configuration files. N.B. I got further, but I do not yet have a real site (attempting to configure the webinstaller gets redirected to a maintenance mode page at /cgi-bin/koha/maintenance.pl); however, that may be a separate issue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 13334] Add a warning when a course reserve is checked in
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13334 Hammat wele <hammat.wele(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #36212|0 |1 is obsolete| | --- Comment #11 from Hammat wele <hammat.wele(a)inlibro.com> --- Created attachment 177312 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=177312&action=e… This patch adds the following warning during the return of a document that was reserved to a course: "Please return 'title' to the 'course name' class reserve." Testing: 1) Define a document as a course reserve see manual.koha-community.org/3.14/en/coursereserves.html 2) Checkout and checkin this document. Validade the warning http://bugs.koha-community.org/show_bug.cgi?id=13334 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 38898] New: Cron handling tar vs. deb
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38898 Bug ID: 38898 Summary: Cron handling tar vs. deb Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexander.wagner(a)desy.de QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de The Koha Manual details on cron jobs required by Koha and also refers to `crontab.example` as an example how to set it up: https://koha-community.org/manual/latest/en/html/cron_jobs.html As a newbie I had the impression that I should dive into all those jobs and devise a suitable `crontab` for my instance based on the example file provided. This seems to be correct procedure if Koha gets installed from the source tar balls. Once Koha is installed from pre-complied (deb-)packages, however, a number of cron jobs are added to the system `cron` automatically by means of crontabs named `koha-common`, placed into the respective system paths `/etc/cron.*/` and one might end up with the same job more than once and probably confusing behaviour. - It would be helpful to newbies to point out the automatic setup once deb's are used - It would also be helpful to mark jobs already setup automagically in the subsequent detailed documentation of the jobs. As of 24.11 these jobs seem to be added via deb and `koha-common` crontabs (section headings refer to the path they get added). ## cron.hourly build_holds_queue automatic_checkin ## cron.d process_message_queue ## cron.daily automatic_renewals automatic_checkin expire_recalls overdue_recalls fines overdue_notices serialsUpdate membership_expiry cancel_expired_holds cleanup_database auto_unsuspend_holds merge_authorities plugins_nightly ## cron.monthly share_usage_with_koha_community -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 27234] New: Indicate if item is reserved when loaning to localuse patron
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27234 Bug ID: 27234 Summary: Indicate if item is reserved when loaning to localuse patron 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using the statistical patron to record localuse, there are no indications whether the items is reserved or already on loan. To test: 1) In Administration > Patron categories > New category, create a category called Local use and make sure to choose the Category type 'Statistical' 2) Go to Patrons > New patron and create a Local use patron 3) Place a hold on an item 4) Check out the item to the statistical local use patron --> Message says 'local use recorded' It would be nice if the system could alert the staff that the item is on hold while they have the item in hand. Otherwise, they shelve it and they have to get it again when they check the holds to pull list. In comparison, when using the checkin system to record local use, with RecordLocalUseOnReturn, the hold pop-up appears with the message 'local use recorded' also. Another comparison, if you try to check out an item that has a hold to another patron, the system will alert you that there is a hold. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 30652] New: RPC style action endpoint for choosing matches
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30652 Bug ID: 30652 Summary: RPC style action endpoint for choosing matches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: tomascohen(a)gmail.com Depends on: 22785 In bug 22785 we added endpoint for selecting which match of a record is used at import. I wasn't sure about the API structure as it didn't feel RESTful.. you are changing the state of more than the single resource you are pointing to. I propose the following as an alternative. POST /import/{import_batch_id}/records/{import_record_id}/matches/{record_match_id}/choose POST /import/{import_batch_id}/records/{import_record_id}/matches/{record_match_id}/unchoose Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22785 [Bug 22785] Manage matches when importing through stage MARC record import -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 36655] New: Add ability to requeue a background job from the staff interface
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36655 Bug ID: 36655 Summary: Add ability to requeue a background job from the staff interface Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Sometimes a long_tasks background job fails and a library would like to requeue it, after fixing the erroneous or problematic records. We should allow that. Basically, status Failed -> status New -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 9762] Log circulation overrides
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '25

28 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9762 William Lavoie <william.lavoie(a)inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #176742|0 |1 is obsolete| | --- Comment #41 from William Lavoie <william.lavoie(a)inLibro.com> --- Created attachment 177296 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=177296&action=e… Bug 9762: Log circulation overrides This patch allows you to save commands that have been overridden by someone. The patch has been updated but is not yet completed. Tests 10, 13, 14, and 17 are still not functional. Tests 15 and 16 need to be fixed as they do not display the barcode. All other tests should be functional. To test: --After each step, a message will be displayed in the action_logs table and in Tools > Log viewer -- Circulation -- Checking out 1) Check out an item that is age-restricted (AgeRestrictionOverride syspref) 2) Check out an item that has a “not for loan” status (AllowNotForLoanOverride syspref) 3) Check out an item that has a “lost” status (IssueLostItem syspref) 4) Check out an item to a patron who has reached the checkout limit (AllowTooManyOverride syspref) 5) Check out an item to a patron who is not allowed to borrow this item type 6) Check out an item to a patron who has unpaid fines (AllFinesNeedOverride and/or AllowFineOverride + noissuescharge sysprefs) 7) Check out an item on hold for someone else 8) Check out an item on hold ready for pickup by someone else 9) Check out an item already checked out to someone else (AutoReturnCheckedOutItems syspref) 10) Check out to a patron who has restrictions Circulation -- Checking in 11) Ignore a hold upon check in 12) Ignore a hold and transfer upon check in Circulation – Renewing 13) Renew an item on hold for someone else (AllowRenewalOnHoldOverride syspref) 14) Renew an item that has reached the maximum number of renewals (AllowRenewalLimitOverride syspref) Holds 15) Place a hold for a patron who is not allowed to place this item type on hold (AllowHoldPolicyOverride syspref) 16) Place a hold for a patron who has reached the maximum number of holds 17) Place an item-level hold when rules dictate that this is not allowed (In circulation rules put "On shelf holds allowed" to "If any unavailable") -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0