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

[Bug 22843] New: Finer control of who receives purchase suggestion notifications
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22843 Bug ID: 22843 Summary: Finer control of who receives purchase suggestion notifications Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Bug 5770 adds the ability to send emails to various addresses when a patron makes a purchase suggestion. It uses the existing email address fields at either the branch or whole library level (or the option to add a single alternate address). It might be nice to be able to define a 'Acquisitions librarian' per branch rather than re-using the branchemail address. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 21017] New: Plugins: Allow for post-install configure flag
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21017 Bug ID: 21017 Summary: Plugins: Allow for post-install configure flag Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Some plugins, such as the CLA Check Permissions plugin, require configuring before they can be used. I propose a flag, probably in the plugin's $metadata hashref that indicates whether the plugin should redirect the user to the configure page immediately after installation. This would provide better UX, particularly with plugins that where it's not immediately obvious that configuration is required before use -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 17528] New: Holds to pull: check button Solved by
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17528 Bug ID: 17528 Summary: Holds to pull: check button Solved by Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hello, we really like "Holds to Pull" in Koha. We miss function that bring possibility to set hold as solved. In our case it means that we need often to create transport order and give some signt to others that case is solved. So new column with checkbox "Solved by" name_of_staff and date, time would be nice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 18440] New: tmp_holdsqueue should have a timestamp
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '22

28 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18440 Bug ID: 18440 Summary: tmp_holdsqueue should have a timestamp Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If the holds queue builder doesn't run for some reason (cron job disabled, or job crashes), it's not possible to tell when the last entry was made in tmp_holdsqueue. It would be very nice to have a timestamp available for this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 22983] New: New default local NotoSans font copy lackck glyphs for (some) Roman letters with diacritics
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '22

28 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22983 Bug ID: 22983 Summary: New default local NotoSans font copy lackck glyphs for (some) Roman letters with diacritics Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 90054 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=90054&action=ed… NotoSans rendered incorrectly (missing) for Polish letters The patches of Bug 20554 introduced a new pretty NotoSans font family as basic font for OPAC. A decision was taken to serve the font files from Koha installation, not from Google font API. Unfortunately, the copy of the font files in Koha lacks non-standard (probably those outside iso 8859-1 set?) accented Roman letters (among others, Polish). As a result the user is presented with the page which is--typographically--hard to accept (cf. attached screenshot -- Windows 10, Chrome 74.0.3729.169; BTW, on my Android 9 everything seems to be OK -- probably thanks to the local, system copy of the font?). Possible solutions could be: 1) update the Koha copies of the font files with the up-to-date version 2) let css get the font from Google font API (href="https://fonts.googleapis.com/css?family=Noto+Sans&display=swap") Can be tested--for instance--with Polish letters: ACELNOSZZ ĄĆĘŁŃÓŚŻŹ acelnoszz ąćęłńóśżź -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 22323] New: cronjob runreport.pl CSV encoding issue
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '22

27 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22323 Bug ID: 22323 Summary: cronjob runreport.pl CSV encoding issue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Target Milestone: --- Cronjob runreport.pl runs SQL reports and can export as CSV. This export needs to be UTF-8 encoded. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 19540] New: opac-reserve does not correctly warn of too_much reserves
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '22

26 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19540 Bug ID: 19540 Summary: opac-reserve does not correctly warn of too_much reserves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.bourgault(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When attempting to place more holds than allowed, opac-reserve.pl only checks against the SysPref 'maxreserves' and not the issuingrules 'holdsallowed'. If the issuing rule's limitation is lower than maxreserve, the opac-reserve page shows a message saying you cannot place any more holds but the explanatory message does not show. To reproduce: 0) Set MaxReserve to a high value (50 is default); 1) Set an issuing rule's "Holds allowed" to a low number (1 or 2); 2) Place as many holds as you can (for the corresponding (categorycode, itype, branchcode, etc). When you reach the maximum allowed by the issuing rule, you'll see a message telling you cannot place any more holds, but the explanatory message saying that you cannot place more than %d holds will not show. (It will show "No items available instead". Bug is present on 16.05 and master -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 22343] New: Add SMTP settings
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '22

24 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22343 Bug ID: 22343 Summary: Add SMTP settings Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: fv(a)spots.school QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- I would like to add fields to Koha>Administration for SMTP settings to make it easy to use external mail servers without having to edit files on the server. I am thinking that we could edit koha/C4/Letters.pm adding $mail{smtp} = 'my.mail.server'; I am not sure how the settings are passed to Letters.pm however. What does everyone else think? Is this the right way to do it? Thank you! FV -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 351

[Bug 18445] New: Tests in t stumble over Auth's BEGIN block
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '22

19 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18445 Bug ID: 18445 Summary: Tests in t stumble over Auth's BEGIN block Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: gmcharlt(a)gmail.com We should be able to run the tests in t without the database. But if some module loads Auth.pm via C4/Serials or Koha/Virtualshelf directly or indirectly, this will trigger execution of Auth's BEGIN block. This block contains three calls for systempreferences (one from Auth_with_cas). Note that loading Biblio.pm also starts a chain going to Auth.pm. This report changes two use C4::Auth statements into requires. This will prevent or postpone execution of this code. Note also that this will resolve a few failing tests like (Matcher.t and Prices.t) where the schema mock actually was too late and the database was accessed instead of defined fixtures. Along the way we fix a few minor issues in t where database access should be eliminated. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 20116] New: Cache language list
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '22

19 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20116 Bug ID: 20116 Summary: Cache language list Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 20115 C4::Languages::getTranslatedLanguages calls _get_language_dirs that list directories to know the available themes. It sounds like we could avoid that and cache it instead. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20115 [Bug 20115] Languages appear in a different order in the footer -- You are receiving this mail because: You are watching all bug changes.

1 78