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

[Bug 25918] New: Add budget/fund modification history to function added in BUG 25916
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '26

11 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25918 Bug ID: 25918 Summary: Add budget/fund modification history to function added in BUG 25916 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: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org Created attachment 106480 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=106480&action=e… A mock-up of Modify Fund page with the history feature added. The acquisitions SIG discussed this enhancement and came up with this feature that multiple libraries said would help their workflow. The specific feature is to display a history of changes to the fund that is collapsible. I have attached a mock-up of the 'Modify Fund ...' screen that would incorporate the feature the libraries would like. This enhancement is a further enhancement of the function added in Bug 25916. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 25916] New: Create UI to modify budgets and funds.
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25916 Bug ID: 25916 Summary: Create UI to modify budgets and funds. 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: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org Created attachment 106479 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=106479&action=e… Mock-up of Modify Fund page with +/- and transfer function The Koha-US Acquisitions SIG discussed this enhancement and came up with some features that multiple libraries said would help their workflow. The specific features are a need a transfer between funds function as well as a add/subtract function for each account. I have attached a mock-up of the 'Modify Fund ...' screen that would incorporate the features the libraries would like. Page 1 is a suggestion to make the fund modification screen accessible from the 'all available funds... page. Page 2 shows what the current 'Modify Fund....' page looks like. Page 3 shows the mock-up of how we would like it to look. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 28491] New: field 003 not updated after import
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28491 Bug ID: 28491 Summary: field 003 not updated after import 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: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org I import some authority data from e.g. dnb.de, which contains: <controlfield tag="001">11915725X</controlfield> <controlfield tag="003">DE-101</controlfield> After the import, the local authority data looks like <controlfield tag="001">35</controlfield> <controlfield tag="003">DE-101</controlfield> So 001 now contains the internal Koha id (good), but 003 still points to DE-101 (i.e. dnb.de), which I think is bad, because if I look up the ID '35' in the linked DB DE-101, I will now get a bad result. I assume that 003 should be set to my MARCOrgCode Looking at the code, I find (in C4::AuthoritiesMarc, AddAuthority, 568ff) if (!$record->field('003')) { $record->insert_fields_ordered( MARC::Field->new('003', $marcorgcode), ); } So this behavior seems intentional? If so, I still find it very unlogical and buggy. I assume that both 001 and 003 should be overwritten with data pointing to the current Koha instance, and the original 001/003 "archived" in 035 and/or 040 I could easily provide a patch that changes this behavior, but I'm not sure if this would cause confusion / failing tests / etc. Maybe add an option to allow a force-overwrite of 003? Greeting, Thomas PS this seems slightly related to #25603 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40

[Bug 27357] New: Trigger printing of a routing list, when an issue is received
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27357 Bug ID: 27357 Summary: Trigger printing of a routing list, when an issue is received Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment the printing of a routing list happens separately from receiving the issue and requires extra steps and attention to not be forgotten. It would be nice, if the printing of a routing list was triggered by receiving an issue to have a more streamlined process. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28628] New: Elasticsearch - Heading search form does'nt match related indexed heading
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28628 Bug ID: 28628 Summary: Elasticsearch - Heading search form does'nt match related indexed heading Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com When an authority is created using LinkBibHeadingsToAuthorities the heading created "700 $aVidard $bMathieu $f1971-..." (unimarc) is saved as "Vidard Mathieu 1971-..", indexed as "Vidard Mathieu 1971-.." and searched as "Vidard Mathieu 1971" => no match. So the link bib does'nt work. Test plan (UNIMARC exemple): - create a biblio with the following data in tag 700: - $a Vidard - $b Mathieu - $d 1971-... - save. => a new authority is created with the following heading "Vidard Mathieu 1971-.." - create an other biblio with the same value in tag 700. => again a new authority is created with the same heading. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 19852] New: Add message text box in circulation for patrons does not accept HTML tags
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19852 Bug ID: 19852 Summary: Add message text box in circulation for patrons does not accept HTML tags Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 69958 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=69958&action=ed… result after adding HTML tags for a patron message Hi When you add a patron message in circulation.pl, the modal that appears has a text box that does not accept HTML tags. Some libraries use HTML tags in these messages to link to information in Koha and to format the display of the message (see attached). Having this modal accept HTML would allow formatting and linking in messages. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 23978] New: notes field in saved reports should allow HTML
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23978 Bug ID: 23978 Summary: notes field in saved reports should allow HTML Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org In recent Koha 18.11, parsing of HTML tags was removed from many fields for security reasons. However, as also seen in 22938, 22702, 22501, 23194, 23683 there are places where HTML (or at leas line breaks!) are required, or the output is too messy. The 'notes' field in the "Guided reports wizard › Saved reports" displays the data that is previously entered in a textarea. However, the guided_reports_start.tt does not parse the HTML (nor line breaks), so the output in the resulting table is all in one line! As with the other patches, I propose that we allow HTML in report notes, so one can use strong/italics/colors/urls in notes, and most importantly, line breaks! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[Bug 23093] New: Error during upgrade of OpacNavRight preference to Koha news
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23093 Bug ID: 23093 Summary: Error during upgrade of OpacNavRight preference to Koha news Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 22318 Target Milestone: --- Copied from Bug 22318: Moving the contents of OpacNavRight to opac_news fails due to improper (no?) escaping: DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+' at line 1 [for Statement "INSERT INTO opac_news (branchcode, lang, title, content ) VALUES (NULL, 'OpacNavRight_en', '', ' <a class="twitter-timeline" href="https://twitter.com/ETFLibrary" data-widget-id="702160486524186624">Tweets by @ETFLibrary</a> <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+"://platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script> ')"] at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 18220. In this example, OpacNavRight contains a script to embed a Twitter timeline. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22318 [Bug 22318] Extend Koha news feature to include other content areas -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 28183] New: retain patron-deleted suggestions
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '26

08 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28183 Bug ID: 28183 Summary: retain patron-deleted suggestions Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In the purchase suggestions process, when a patron deletes their suggestion, the data is gone from all elements. For instance, a patron makes a purchase suggestion, the library orders the item and notifies the patron it has been ordered, if the patron then deletes the suggestion, there is no record/information for the library about who wanted it, etc. It is completely removed from the purchase suggestion process. This is information that libraries need to be able to view, even if it is only available via reports on deleted tables or something. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 18485] New: REST API: add endpoint for calendar
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '26

08 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18485 Bug ID: 18485 Summary: REST API: add endpoint for calendar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hello, new calendar (bug 17015) works with opening hours, so new endpoint for calendar will be useful for transfer informations about opening hours into other systems. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6