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

[Bug 35545] New: "additional" item
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '25

24 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35545 Bug ID: 35545 Summary: "additional" item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com An "additional" item appears in the staff interface if item = biblionumber. This effect is not observed in OPAC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 23293] New: OPACFineNoRenewals compares against 'balance' not 'outstanding'
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '25

24 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23293 Bug ID: 23293 Summary: OPACFineNoRenewals compares against 'balance' not 'outstanding' 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The OPACFineNoRenewals (and consequently the OPACFineNoRenewalsBlockAutoRenew) feature uses the patrons' account balance (which combines outstanding credits and debits) as opposed to their outstanding debts. This should either be configurable (or perhaps coded to use outstanding debts instead) as it does not accurately reflect what a patron may owe when AccountAutoReconcile is set to 'Do not' apply. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 39731] New: Remove DelSuggestions from C4/Suggestions.pm
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '25

24 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39731 Bug ID: 39731 Summary: Remove DelSuggestions from C4/Suggestions.pm Change sponsored?: --- Product: Koha Version: Main 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23990 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 39718] New: Public note rendering of HTML isn't consistent
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '25

23 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39718 Bug ID: 39718 Summary: Public note rendering of HTML isn't consistent Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This many be other columns other than public note but we have notices it here since many of our libraries add HTML to that field. To recreate: 1. Find an item and add an HTML public note. I am using '<a href="#">TEST</a>'. 2. Now view the record from the OPAC. 3. See the link TEST. ( rendered HTML ) 4. View the link from the staff client. See it as '<a href="#">TEST</a>'. If we can render the HTML on the public side, why can we not on the staff side? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 35836] New: search_for_data_inconsistencies.pl - Search for loops in dependencies.
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '25

23 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35836 Bug ID: 35836 Summary: search_for_data_inconsistencies.pl - Search for loops in dependencies. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: matthias.le-gac(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have guarantors who guarantee individuals who are, in turn, their guarantors. It is not clear if this should be allowed (bz35421), but it works, and has been working for a while. However, it breaks with bz12532, which produces a recursion that disrupts everything. Creation of a code in search_for_data_inconsistencies.pl that identifies loops in borrower_relationships. This must work in both directions for validation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 33087] New: OPACHoldsIfAvailableAtPickup considers On order as available
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '25

23 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33087 Bug ID: 33087 Summary: OPACHoldsIfAvailableAtPickup considers On order as available Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 If OPACHoldsIfAvailableAtPickup is enabled (i.e. if patrons cannot place holds on items that are available at their library), patrons cannot place holds on items that are on order (or any negative not for loan value) for pickup at their library. Technically, those items are not "available", so they shouldn't be affected by this system preference. To replicate: Prerequisites : - Have at least two libraries (I used the sample libraries) - Have a patron in one of the libraries (I used Henry Acevedo), make sure you know the user id and password for that patron - Make sure the circulation rules allow holds for the patron category 1. Turn on OPACHoldsIfAvailableAtPickup 1.1. Go to Administration > Global system preference 1.2. Search for OPACHoldsIfAvailableAtPickup 1.3. Change the value to "Don't allow" 1.4. Click "Save all Circulation preferences" 2. Make an item "On order" at the patron's library (Henry Acevedo is at Midway) 2.1. If needed, create a bibliographic record and item 2.2. Edit the item to assign the "On order" not for loan status 2.3. Change the home and holding library to the patron's library (Midway) 2.4. Click "Save changes" 3. Try to place a hold on the item through the OPAC 3.1. In the OPAC, log in as the patron 3.2. Search for the item 3.3. Click "Place hold" --> Notice the patron's library is greyed out in the pickup location drop-down menu -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 26597] New: Transfer informations from guarantor when adding a guarantor to an existing patron
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '25

23 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26597 Bug ID: 26597 Summary: Transfer informations from guarantor when adding a guarantor to an existing patron 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: maryse.simard(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When creating a new guarantee from the guarantor, the preference PrefillGuaranteeField dictates some fields to be transfered from guarantor to guarantee. We want to transfer those informations also when adding a new guarantor relationship to an existing patron. Note: This was first introduced as part of Bug 12446, but ultimately was split into it's own bug. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 65

[Bug 35029] New: Doubled up entries in notices and slips after update
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '25

23 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35029 Bug ID: 35029 Summary: Doubled up entries in notices and slips after update Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 30555 This was caused by bug 30555: When we insert new entries into the letters table for existing notices (new transport types), we need to make sure that letter.name of the old and new notice entries match. Otherwise we'll see 2 entries in the editor with no way to fix it from the GUI. Both lead to the same notice entry page. name gets translated, so we need to query the existing one with the code of the letter and use it for the new entries. To test: * You will need a non-English installation, with translated installer. de-DE would work. And where the database from bug 30555 has run. * Alternatively you can try and update the name field for one of the entries in letter manually to see the same effect. * Go to tools > notices and slips * Verify there are 2 entries for the DUEDGST and other notices with different description. * When editing, you should see the same text/entries for each. It's also the same URL. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30555 [Bug 30555] Add more sample notice for SMS messages -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 30555] New: Add more sample notice for sms messages
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '25

23 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30555 Bug ID: 30555 Summary: Add more sample notice for sms messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: shi-yao.wang(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 37070] New: Incorrect barcode generation when adding orders to basket
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '25

23 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37070 Bug ID: 37070 Summary: Incorrect barcode generation when adding orders to basket Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When the autoBarcode preference is set to « generated in the form 1, 2, 3 » and the maximum barcode is length 16 (ex 1000000000000000), when adding orders to the basket,the numbers of the copies generated are in the hexadecimal form. to reproduce: 1- Set the system preference autoBarcode to « generated in the form 1, 2, 3 » 2- Search for a biblio record 3- In the record details, click on New -> New item 4- fill the Barcode field to a number with length 16 (1000000000000000) and add the item 5- Create a suggestion 5-1- Go to Acquisitions and click on suggestions 5-2- Create a suggestion and accept it 6- Add a new order to a basket 6-1- Go to Acquisitions and find a vendor 6-2- Create a new Basket 6-3- on the Basket click on 'Add to basket' and select 'From a suggestion' 6-4- Add the order created on 5-2- to the basket 6-5- On the item form click on Add item 6-6- Select a Fund and save the order 7- In the orders table click on the record and check the item Barcode ---> the Barcode is in hexadecimal form 8- Cancel order and delete the catalog record 9- Apply the patch 10- Repeat step 6-4, 6-5, 6-6 11- Check the item Barcode ---> the Barcode is not in hexadecimal form -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21