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

[Bug 9596] Allow longoverdue.pl to be configured per library on the command line
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '24

19 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to main -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9596] Allow longoverdue.pl to be configured per library on the command line
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '24

19 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)| |24.11.00 released in| | --- Comment #29 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hm, we missed the wrong bug number on the commit message: Subject: [PATCH] Bug 37613: Follow-up to bug 9596 to change the option and documentation to match Terminology Guidelines Content-Type: text/plain; charset="utf-8" Need to keep that in mind for manually editing release notes later. Michael: it looks like you are not using git bz? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4850] CheckReserves does not respect holds circulation policies
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '24

19 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4850 --- Comment #11 from Lucas Gass <lucas(a)bywatersolutions.com> --- Still relevant and effecting many libraries. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 37668] New: Add HTML customization to OPAC detail page
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '24

19 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37668 Bug ID: 37668 Summary: Add HTML customization to OPAC detail page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org This could be below the "navigation" on the right side. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37660] New: Cannot login to SCO module when cardnumber is NULL
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '24

19 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37660 Bug ID: 37660 Summary: Cannot login to SCO module when cardnumber is NULL Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Remove cardnumber for BorrowerMandatory system preference. 2. Create a patron without a cardnumber 3. Try to login into the SCC module, you cannot. 4. The user is redirected back to the SCO login page with no indication of what went wrong. This happens when SelfCheckoutByLogin is set by cardnumber OR userid + password. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37667] New: q_errors in export phase is wrong data type
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '24

19 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37667 Bug ID: 37667 Summary: q_errors in export phase is wrong data type Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org In reports/guided_reports.pl, when you do an export, there is a test for "$q_errors and @$q_errors", but in most cases $q_errors will actually be a hashref returned by execute_query and not an arrayref. I think this probably hasn't been caught because it's hard to initiate the Export phase for a report with errors, since it won't do the Run phase correctly. But if you have a bad report and manually go to the export link, you can get guided_reports.pl to return a 500 because of the $q_errors data type being wrong. Anyway, quite low severity, but raising it anyway... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37539] New: Improve the documentation for the OCLC Connexion Daemon / Gateway in the manual
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '24

19 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37539 Bug ID: 37539 Summary: Improve the documentation for the OCLC Connexion Daemon / Gateway in the manual Change sponsored?: Sponsored Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: rudolfbyker(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de Depends on: 37538 Patch incoming. This is a follow-up for https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37538 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37538 [Bug 37538] Improve documentation printed by connexion_import_daemon.pl --help -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 37665] New: Add a warning when a borrower having is deleted
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '24

17 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37665 Bug ID: 37665 Summary: Add a warning when a borrower having is deleted Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Not sure of that, but I think it could be good to display a warning and ask a confirmation when staff is deleting a borrower who has created a list of books -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37663] New: Bugs/Erratic Website Data/Poor Web Design
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '24

17 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37663 Bug ID: 37663 Summary: Bugs/Erratic Website Data/Poor Web Design Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: sarahgood(a)tutamail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It seems imperative that Koha, ByWater Solutions & Aspen Discovery should: 1.) Already be aware . . . 2.) Should be fixing BUGS & PATENT MALFUNCTIONS on the websites you support library catalogues for. Why? Here's why: A website, which belongs to the three (3) entities listed above (in the U.S.) still malfunctions (as much as it had since its inception): – Incorrectly miscounts books on HOLD; requires refresh/restart & still miscounts & omits books reserved for borrowing. – UNDER "Show Editions" the (black & blue) data (publication date, size, # pages, &c.) overlap & is illegible – BOOKS SAVE SINGULARLY TO "LISTS" (not any digital formats: Hoopla, eBook, Audio, &c., but as JUST BOOK FORMAT) — WHEN OPENED IN THE "CREATED LIST" nevertheless, display ALL VERSIONS (electronic) OF THE TITLE when the "LIST" is accessed, opened, & employed for reference. – & there is no means or method (no software you have created) to revert the SAVED LIST TO DISPLAY ONLY BOOK FORMAT – The website is overloaded with colours, redundant "boxes" – The website is a VISUAL PARADOX to persons with disabilities & is consequently confusing & complicated to use — NOT FACILE – Within the "Your Account" box (bordered in red in the upper left corner) the grey circles (next to "Titles on Hold", & every other line-item within that box) DISPLAY erratic numbers/count/record of how many Titles on has placed on hold – Said same grey circles with numerals enclosed are too close & too large to the adjacent text – The same grey circles should smaller & square – The general proximations of data in the same "Your Account" box are simply too close to each other & are disproportionately sized – & there are other software malfunctions & utilities that work with consistent erraticism on the websites used by libraries designed by Koha, ByWater Solutions & Aspen Discovery I am acquainted with Graphic Design & I submit that your website/s are poorly (amateurishly) assembled, not well organized, redundant, & are very very much overly convoluted with multiple colours, unwanted or deleted data, & a run-on of DESIGN issues. BUT THE MOST IMPORTANT ERROR YOU HAVE OMITTED IS TO HAVE SUCCESSFULLY RUN BETA TESTING ON YOUR WEBSITE TO VERIFY THAT THESE ISSUES ARE REAL — & TO FIX THEM. It rather seems you marketed a website (seemingly designed by Wordpress, or Blogspot) with SOFTWARE that has been very insufficiently tested & resolved. Don't take this personally! I am attempting to be forthright & honest. Your websites, apparently global (if Koha is N-Zed), are abundant & should not be exhibiting these fundamental & preliminary software issues to such an enormous base of patrons of these libraries who (through no sensible choice of their own) are forced to utilise a website that is not yet fully developed — nor is seemingly OUT OF BETA TESTING. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37664] New: Batch deleting patrons using a patron list - can't delete staff patrons
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '24

17 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37664 Bug ID: 37664 Summary: Batch deleting patrons using a patron list - can't delete staff patrons Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org When batch deleting patrons from a patron list, and the list includes staff patrons, it doesn't let you delete the staff patrons in the list. To replicate: 1. Create a patron list (Tools > Patrons and circulation > Patron lists > + New patron list). 2. Add two patrons to the list, with one of them a staff patron (such as Henry): 2.1 Enter at least three characters in the patron search field and select a patron (examples: hen, mar) 2.2 Repeat until you have two patrons that are listed under the 'Patrons to be added' heading 2.3 Select 'Add patrons' to add to the list 3. Go back to the patron lists (Tools > Patron lists). 4. For the list you created, select Actions > Batch delete patrons. 5. Note that the warning message - the count is wrong (should be 2 patrons will be deleted): Warning 1 patrons will be deleted 0 patrons' checkout histories will be anonymized 6. Repeat steps 1-5 where the patrons in the list are not staff patrons. The count of patrons to delete should equal the number of patrons in the list. Other notes: 1. I added patrons from all patron category types to the patron list (where there are patrons in that category). 2. I also checked the staff patron information, and they weren't protected. 3. I testing using koha-testing-docker and was logged in as the koha user. 4. I couldn't see any options in the patron category form that would prevent deletion. I'm not sure if I am right that you can't delete staff patrons this way - there may be another reason why this is happening. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2