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

[Bug 21941] New: Incorrect GROUP BY in circ/reserveratios.pl
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21941 Bug ID: 21941 Summary: Incorrect GROUP BY in circ/reserveratios.pl 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com DBD::mysql::st execute failed: 'koha_kohadev.reserves.reservedate' isn't in GROUP BY [for Statement "SELECT reservedate, reserves.borrowernumber as borrowernumber, reserves.biblionumber, reserves.branchcode as branch, items.holdingbranch, items.itemcallnumber, items.itemnumber, GROUP_CONCAT(DISTINCT items.itemcallnumber ORDER BY items.itemnumber SEPARATOR '|') as listcall, GROUP_CONCAT(DISTINCT homebranch ORDER BY items.itemnumber SEPARATOR '|') as homebranch_list, GROUP_CONCAT(DISTINCT holdingbranch ORDER BY items.itemnumber SEPARATOR '|') as holdingbranch_list, GROUP_CONCAT(DISTINCT items.location ORDER BY items.itemnumber SEPARATOR '|') as l_location, GROUP_CONCAT(DISTINCT items.itype ORDER BY items.itemnumber SEPARATOR '|') as l_itype, reserves.found, biblio.title, biblio.author, count(DISTINCT reserves.borrowernumber) as reservecount, count(DISTINCT items.itemnumber) as itemcount FROM reserves LEFT JOIN items ON items.biblionumber=reserves.biblionumber LEFT JOIN biblio ON reserves.biblionumber=biblio.biblionumber WHERE notforloan = 0 AND damaged = 0 AND itemlost = 0 AND withdrawn = 0 AND reservedate >= ? AND reservedate <= ? GROUP BY reserves.biblionumber ORDER BY reservecount DESC" with ParamValues: 0='2017-12-04 00:00', 1='2018-12-04 00:00'] at /home/vagrant/kohaclone/circ/reserveratios.pl line 150. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 15792] New: Double-clicking the 'renew' button on circulation.pl will double-charge account management fee
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15792 Bug ID: 15792 Summary: Double-clicking the 'renew' button on circulation.pl will double-charge account management fee Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com PREREQUISITES 1) Create an account type that has an enrollment fee, and create a borrower of that type. 2) Write off any account management fees charged to that borrower by the account creation. STEPS TO RE-CREATE 1) Change borrower's dateexpiry to make the borrower expired. 2) Paste borrower's card number into 'Check out' bar 3) A warning will appear saying that the borrower's account has expired, including a 'Renew' link. 4) Double-click the link 5) Check the borrower's fines. You will see two account management fees in a row. distinct from the fee that was written off just after the patron was created. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 32652] New: Standardize slots selection between staff interface and opac
by bugzilla-daemon＠bugs.koha-community.org 23 May '26

23 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32652 Bug ID: 32652 Summary: Standardize slots selection between staff interface and opac Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, Now that thanks to BZ31265, we have nice slots selection for the curbside pickups at OPAC, it would be nice to have the same in the staff interface. It's quite disturbing to have a different way to count the pickup (number of pickup already taken in staff interface and number left in OPAC). And it would be more intuitive to have radio button to select a slot. Thanks, Sonia -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 33296] New: Linker should search for authority records with an appropriate 008/14, 15, 16 value
by bugzilla-daemon＠bugs.koha-community.org 23 May '26

23 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33296 Bug ID: 33296 Summary: Linker should search for authority records with an appropriate 008/14,15,16 value Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 33277 In an authority record, 008/14 = 'a' says it's appropriate for use as a main or added entry (1xx, 7xx), 008/15 = 'a' says it's appropriate for use as a subject entry, and 008/16 = 'a' says it's appropriate for use as a series entry (800-830, 440 since we still support it). In a world where we support multiple subject thesauri, we need a way to tell the difference between a name entry which intends to be used as a main entry and one which intends to only be used as a subject authority, and the way the subject-only one should say that is by having 008/14 = 'b' Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33277 [Bug 33277] Correctly handle linking subfields with no defined thesaurus -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 21555] New: Merging Patrons allows for all patrons to be selected
by bugzilla-daemon＠bugs.koha-community.org 23 May '26

23 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21555 Bug ID: 21555 Summary: Merging Patrons allows for all patrons to be selected Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The feature of merging patrons (bug #9302 ) did include a fail safe, according to the bug, if/when using this feature, the option of "selecting all" patrons from a search was chosen, then the option to merge could not be used. When testing this feature, if a few patrons were chosen and then "select all" is chosen, the merge feature is still available to use. If no patrons are chosen and then "select all" is chosen, merge option is not available. Test: how it currently works 1. Search for Patrons by Last Name by Letter 2. From this list, choose patron a, patron b, patron c 3. See that merge patron option available 4. Now select all patrons - merge patron option still available Test: (how it should work) 1. Search for patrons by last name by letter 2.From this list choose patron a, patron b, patron c 3. See that merge patron option avail 4. Now "select all" patrons 3. See that merge patron option not available (greyed out) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 24949] New: Show password in staff login screen on user's demand
by bugzilla-daemon＠bugs.koha-community.org 23 May '26

23 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24949 Bug ID: 24949 Summary: Show password in staff login screen on user's demand Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client 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 A lot of applications allow you to see the password you typed in on demand, often requiring you to click on an "eye" symbol or similar. This would also be helpful for the staff interface to help people check for typos when trying to log into Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 34971] New: Permission to close a serial subscription
by bugzilla-daemon＠bugs.koha-community.org 23 May '26

23 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34971 Bug ID: 34971 Summary: Permission to close a serial subscription Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: pierre.genty(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hi, With only receive_serials permission it is possible to close a serial subscription. This should require edit_subscription permission. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 19558] New: Link 130 uniform title authority record to 240 tag
by bugzilla-daemon＠bugs.koha-community.org 22 May '26

22 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19558 Bug ID: 19558 Summary: Link 130 uniform title authority record to 240 tag Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jbeno(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Uniform titles will link only to 130, 630, 730, and 830 tags. 240 tags are uniform title tags and should also be linked. In addition, the auto create function should but does not create a 130 uniform title authority from a 240 bibliographic entry. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 22622] New: Add Koha::Object method _new_from_hashref
by bugzilla-daemon＠bugs.koha-community.org 22 May '26

22 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22622 Bug ID: 22622 Summary: Add Koha::Object method _new_from_hashref Change sponsored?: --- Product: Koha Version: unspecified 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- It may be useful to be able to instantiate a Koha::Object from data already fetched from the database. This might be used for compatibility with legacy code, or perhaps for use with optimized queries. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 27066] New: Implement Hooks for patron's updates
by bugzilla-daemon＠bugs.koha-community.org 22 May '26

22 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 Bug ID: 27066 Summary: Implement Hooks for patron's updates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: eric.begin(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org Some of our clients use external systems to populate Koha's patron information. They can use Koha's API to update patron info, however, we don't have any way (that I know of) to notify an external system when a patron info is changed in Koha. In order to allow bidirectional communications, we are planning to add hooks. This will allow creating plugins to send messages to external systems in order to fulfil the following requirements : - Update patron information stored in the borrowers table (name, address, email, etc.) - Notify an external system when a restriction is placed on a user (fines, manual restrictions, overdues, etc.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32