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

[Bug 24414] New: Can't add/delete funds with only budget_add_del permission
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24414 Bug ID: 24414 Summary: Can't add/delete funds with only budget_add_del permission 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This is very minor, but I was trying out all the permissions to better document them in the manual and I found something weird. There are several permissions granting access to funds. - budget_add_del described as 'Add and delete funds (but can't modify funds)' - budget_manage described as 'Manage funds' - budget_manage_all described as 'Manage all funds' - budget_modify described as 'Modify funds (can't create lines but can modify existing ones)' If I only have budget_add_del, I can't create or delete funds. I have to have budget_manage to access the funds administration page. Which is ok, I can simply add a note in the manual that budget_add_del requires budget_manage. If I have budget_add_del and budget_manage, I have access to the funds administration page, but not the 'New fund' button nor the 'Actions' button to delete an existing fund. So in reality, I can't add nor delete funds... If I have budget_manage and budget_modify (but not budget_add_del), I can't add new funds I can't edit existing ones, but I can delete them. To test : 1) Create a patron and give them the catalogue permission and the budget_add_del permission 2) Log in with this patron (I use a private window to be able to go back and change their permissions later without logging out again) 3) Go to the Acquisitions page 4) Notice you can see the budget, but you can't click on the fund code and you don't have the 'Funds' link in the left menu 5) Go back to edit the user's permissions and grant them budget_manage; save 6) Go back to the Acquisition page with the limited patron (refresh if needed) 7) Notice that you can now click on the fund code and you have a 'Funds' link on the left side of the screen 8) Click on the fund code 9) Click on 'New' and choose 'Add fund for xx'; add the new fund 10) Notice there is no 'Actions' button from which you can delete this fund 11) Go back to edit the user's permissions and remove the budget_add_del permission and add the budget_modify; save 12) Go back to the Acquisition page with the limited patron (refresh if needed) 13) Click on the 'Actions' button and choose 'Edit'; the page refreshes, but nothing happens 14) Click on the 'Actions' button and choose 'Delete' and confirm; the fund is deleted I have trouble imagining a situation where we would want staff to be able to add and delete funds but not modify them, so that's why I said I think this is minor. I think in most cases, the staff member will have at least all three (budget_add_del, budget_manage and budget_modify). But I still wanted to record the weirdness somewhere. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 21266] New: Missing doc-head-close and cssinclude in sco-main.tt
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21266 Bug ID: 21266 Summary: Missing doc-head-close and cssinclude in sco-main.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Custom stylesheet themes set in the OpacAdditionalStylesheet are not applied to the sco-main.tt page because this page is missing the following lines of code in the header: doc-head-close cssinclude -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 19958] New: Allow the system preference AutoMemberNum to include a combination of numbers and letters when creating a new barcode
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19958 Bug ID: 19958 Summary: Allow the system preference AutoMemberNum to include a combination of numbers and letters when creating a new barcode Change sponsored?: --- Product: Koha Version: 17.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 Currently the system preference "automembernum" only allows for the patron's barcode to default the card number field on the patron addition screen to the next available card number (for example, if the largest currently used card number is 26345000012941, then this field will default to 26345000012942). It would be nice for the library to choose the format of the barcode (for example : system preference autobarcode). Then a library could choose to include letters and numbers to their patron's barcode instead of just numbers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 19384] New: [OMNIBUS] Add Selenium tests
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19384 Bug ID: 19384 Summary: [OMNIBUS] Add Selenium tests Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 29602] New: We must be nicer with translators
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29602 Bug ID: 29602 Summary: We must be nicer with translators Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The PO files are really ugly sometimes, the number of %s and the inclusion of TT tags make the translation a nightmare for translators. We can improve that. -- You are receiving this mail because: You are watching all bug changes.

1 115

[Bug 29238] New: Cataloging cron jobs are not logged
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29238 Bug ID: 29238 Summary: Cataloging cron jobs are not logged Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz After a few cron jobs related to authority records (misc/migration_tools/remove_unused_authorities.pl, misc/link_bibs_to_authorities.pl) were set up to run on our instance, I went to check the Log Viewer tool but couldn't tell that they were configured. I was told that only newer cron jobs actually appear in the logs, and on inspecting those two I saw that they lacked the call to `cronlogaction()` which our circulation-related cronjobs have. It'd be helpful to know if/when these jobs ran. I realize this is a bit debatable because those two scripts don't reside in misc/cronjobs and right now the only scripts that call `cronlogaction()` are in that directory. Is it appropriate to add that logging to these scripts? We do run them on a schedule, it's important to our authority records workflow. This is the complete list of ones I'd like to add logging to: - misc/link_bibs_to_authorities.pl - misc/cronjobs/merge_authorities.pl - misc/migration_tools/remove_unused_authorities.pl A side note: there are several scripts in misc/cronjobs, like merge_authorities.pl, that are not logged and probably should be, but that is a larger bug and I'd like to focus on these first since they're relevant to us. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 59

[Bug 27305] New: RSS feed for due dates
by bugzilla-daemon＠bugs.koha-community.org 29 May '26

29 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27305 Bug ID: 27305 Summary: RSS feed for due dates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nicobako(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl As a user, when I browse the books that I am currently borrowing from the library, I can download the due dates as an ical file. This is wonderful, but it would be really nice to be able to have an RSS feed (a url link) to this calendar. That way I can sync the due dates to my personal calendar, like Gmail, for example. I can add an RSS feed to my personal calendar, and it will automagically populate my personal calendar with the due dates. Thank you in advance! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 23665] New: Add option in Patron Extended Attributes to have a checkbox instead of options
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23665 Bug ID: 23665 Summary: Add option in Patron Extended Attributes to have a checkbox instead of options Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be helpful for some libraries to add an option to have a checkbox rather than an authorized value or input box so when people are opting in to something or have signed a waiver/did the class required to use the 3-d printer etc, we can just check a box rather than using a drop down. There was some discussion about this at koha-US conference this week. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 28732] New: Order and claim emails don't work well with repeatable information
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28732 Bug ID: 28732 Summary: Order and claim emails don't work well with repeatable information Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement 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 There is an issue with how the repeatable part of the notice is figured out. This sets some strict limits to how you can write the notice template. It appears that the repeat will happen from first to the last placeholder from an acq table used in the notice. The <order> tags don't appear to be used at all. Test plan: - Create a basket with more than one order line - Set up a notice called ACQORDER for sending order emails (templats below) - Make sure the vendor has an email set and all checkboxes in the contact are checked - Make sure your system can send emails - Click button "send order e-mail" on the basket summary page ------------------------------------------------ ACQORDER TEMPLATE 1: [%- USE Price -%] Dear... <order>Title: <<biblio.title>> Author: <<biblio.author>> Edition: <<biblioitems.editionstatement>> Year: <<biblio.copyrightdate>> ISBN: <<biblioitems.isbn>> Units: <<aqorders.quantity>> Price: [% <<aqorders.listprice>> | $Price %] EUR </order> Thank you! RESULT: Dear and Thank you only appear once. OK. Dear... Title: ... Author: ... Edition: 1. Auflage, Originalausgabe Year: ISBN: 9783839225837 Units: 1 Price: 13.99 EUR Title: ... Author: Edition: Year: 2020 ISBN: Units: 1 Price: 13.00 EUR Thank you! ------------------------------------------------ ACQORDER TEMPLATE 2: Only addition/change is the second line. [%- USE Price -%] <h2>Order: <<aqbasket.basketname>></h2> Dear... <order>Title: <<biblio.title>> Author: <<biblio.author>> Edition: <<biblioitems.editionstatement>> Year: <<biblio.copyrightdate>> ISBN: <<biblioitems.isbn>> Units: <<aqorders.quantity>> Price: [% <<aqorders.listprice>> | $Price %] EUR </order> </hr> Thank you! RESULT: Order:... and Dear... lines are repeated. For information from the basket this doesn't make sense. If you add a field from the branches table, this doesn't appear to cause any additional repeats. Order: 28.4.2021 Dear... Title: ... Author: ... Edition: 1. Auflage, Originalausgabe Year: ISBN: 9783839225837 Units: 1 Price: 13.99 EUR Order: 28.4.2021 Dear... Title: ... Author: Edition: Year: 2020 ISBN: Units: 1 Price: 13.00 EUR Thank you! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29923] New: Do not generate overpayment refund from writeoff of fine
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29923 Bug ID: 29923 Summary: Do not generate overpayment refund from writeoff of fine Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - turn finesmode on 2 - set circ rule a circ rule to charge fines 3 - perform a checkout that follows your circ rule, setting the due date in the past 4 - run the fines cron and confirm that it generates an accruing fine for your patron 5 - write off that fine 6 - edit your circ rule to remove the fine amount and interval 7 - check your item in 8 - see your patron now has a credit in the amount of the writeoff The overpayment credit should only be generated if we've taken payment on the fine. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27