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

[Bug 26791] New: Build Mojolicious controller replacement for export.pl
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '25

30 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26791 Bug ID: 26791 Summary: Build Mojolicious controller replacement for export.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org As per my notes on Bug 8437, starting at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8437#c33, any Koha .pl script that needs to stream a large response to a client web browser is never going to work, so long as we're using Plack::App::CGIBin to create a PSGI handler. While I tried to create my own streaming version of Plack::App::WrapCGI, I found a third-party module to be buggy, and that writing my own would be prohibitive in terms of time and energy. It's also architectural glue code that we really might not want to maintain long-term. So I've concluded that an alternative would be to write a Mojolicious controller to replace export.pl. While CGI Koha can still use export.pl, when we're using Starman/Plack, we can redirect to the appropriate Mojolicious endpoint. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 38226] New: Add RPC endpoint for batch filling empty callnumbers
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38226 Bug ID: 38226 Summary: Add RPC endpoint for batch filling empty callnumbers Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Originally proposed on bug 34784, I'm moving the patches here to ease readability and have a smaller testing scope. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 38995] New: Allow to pick an accent color
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '25

29 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38995 Bug ID: 38995 Summary: Allow to pick an accent color Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Style guide Assignee: oleonard(a)myacpl.org Reporter: pablo.bianchi(a)gmail.com QA Contact: martin.renvoize(a)ptfs-europe.com Following Lucas Gass advice on bug 37054#c51; related to bug 31327 and 38550: Right now we can change accent-color by changing hex values on a set of files (CSS/JSON/SVG). #408540 #006100 #418940 #418A40 #589D43 to a dark color (the difference on very similar shades of green seems to be a bug), and #6faf44 #71b443 #7cbb51 #dcefd0 to a light color. By default, using HSL model, the koha's green is around hsl(120, 40%, 40%). I would love to see a syspref to change that hue from 120 to any 0-255 value (or a nicer picker). This would apply to staff and OPAC, and could be overridden by a per library field or custom CSS. Not sure if this could be done independently of a per-user light/dark mode switch (bug 38550). -- You are receiving this mail because: You are watching all bug changes.

1 0

[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