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

[Bug 12032] TinyMCE rewrites urls in a very annoying and unexpected way
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '24

25 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12032 Lari Taskula <lari.taskula(a)hypernova.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |37965 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37965 [Bug 37965] Restore Bug 12032 - TinyMCE rewrites urls in a very annoying and unexpected way -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12032] TinyMCE rewrites urls in a very annoying and unexpected way
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '24

25 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12032 --- Comment #7 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Lari Taskula from comment #6) > Bug reintroduced, I believe by Bug 22661. > > It happens for example when OPAC and staff client are under the same domain > but different subdomain and you are trying to create a link between the two. As this is old and released, please open a new bug and link them! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38002] New: Koha Offline Circulation cuts off part of user address
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38002 Bug ID: 38002 Summary: Koha Offline Circulation cuts off part of user address Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: chanel.wheeler(a)yavapaiaz.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Download the borrowers.db file and import it into the Offline Circ tool. 2. In the Offline Circ tool, put in the barcode of a patron that has a full address and hit enter. 3. The patron's information on the right side will be missing the State and Zip. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 37971] New: Koha Bug Report: Database Access Error During Upgrade 24.05
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37971 Bug ID: 37971 Summary: Koha Bug Report: Database Access Error During Upgrade 24.05 Change sponsored?: --- Product: Koha Version: 24.05 Hardware: PC OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: mdmiansarilib(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 171818 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=171818&action=e… snapshot of terminal During an upgrade of Koha to version 24.05.03-1, the process failed due to a database access error. The upgrade script was unable to connect to the MySQL/MariaDB database, suggesting a potential issue with database permissions or configuration. Steps to Reproduce: Attempt to upgrade Koha-common package to version 24.05.03-1 Run sudo apt-get install mariadb-server Confirm the installation/upgrade process Observed Behavior: The upgrade process fails during the database schema upgrade step An error message indicates that access is denied for the Koha database user Error Message: "DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('database=koha_monirul;host=localhost;port=3306','koha_monirul',...) failed: Access denied for user 'koha_monirul'@'localhost' (using password: YES) at /usr/share/koha/lib/Koha/Database.pm line 91. at /usr/share/koha/lib/Koha/Database.pm line 139" Environment: Koha version being upgraded to: 24.05.03-1 Database: MariaDB (version 1:10.11.8-0ubuntu0.24.04.1) Operating System: Ubuntu (likely 24.04 based on package versions) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 37899] New: Koha ILSDI endpoints expect a CSRF token - so ILSDI requests fail
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37899 Bug ID: 37899 Summary: Koha ILSDI endpoints expect a CSRF token - so ILSDI requests fail Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org In Koha 24.05 CSRF.pm ( https://git.koha-community.org/Koha-community/Koha/src/branch/main/Koha/Mid… ) expects all stateful methods (POST, PUT, DELETE, PATCH requests) to include a CSRF token. This includes requests to ILSDI ( https://wiki.koha-community.org/wiki/ILS-DI ). This requirement for a CSRF token for ILSDI, which is designed to be used cross site, means ILSDI requests do not work on 24.05 onwards. Several third-party systems need to connect to Koha via ILSDI, for example EDS in order to fetch RTAC (Real-Time Availability Check) data. EDS can also fetch RTAC data from Koha via Z39.50. Another is Bolinda (BorrowBox), an eBook platform, which authenticates Koha users via ILSDI. It would be nice to hear the communities views on what could/should be done to get ILSDI working again. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 26122] New: Update item NotForLoan status when checking out to a statistical patron
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26122 Bug ID: 26122 Summary: Update item NotForLoan status when checking out to a statistical patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I've also filed bug 25847 for comparable functionality with the shelving cart. It'd be great if the syspref UpdateNotForLoanStatusOnCheckin was used when checking an item out to a statistical patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 33066] New: We need a KohaTable Vue component
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33066 Bug ID: 33066 Summary: We need a KohaTable Vue component Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Depends on: 23991 The way we deal with DataTables in Vue component is not nice, especially when we need to add buttons/link in the cell and interact with the rest of the Vue app from there. When I started to work on Vue last year there was no good solution from DataTables, now there is a Vue component. It is not perfect, you still cannot add Vue component in the DT component, but it brings something to follow. Agustin implemented something on theke/import_source_vue, but he went too far, and it will need to rewrite the whole ERM module. Additionally he didn't provide a solution that has the same features as what we have now. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23991 [Bug 23991] Move SearchSuggestion to Koha::Suggestions -- You are receiving this mail because: You are watching all bug changes.

1 159

[Bug 36263] New: Incorrect subscription renewal dates
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36263 Bug ID: 36263 Summary: Incorrect subscription renewal dates Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: wainuiwitikapark(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org A user on 23.05 tried to renew a subscription in the serials module via the renew button in the subscription details page. After the renewal is submitted, the new date is incorrectly calculated. For example, when trying to renew a subscription, they entered the subscription start date of 1/03/2024, and renewed for the length of 12 months, but when attempting to renew again, the new start date calculated to 01/01/2025. They retested other renewal lengths (such as 4 weeks, 6 months etc), and in various scenarios the date continued to miscalculate. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 36795] New: Authority record identifier source codes (024$2) - code for Web of Science ResearcherID
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36795 Bug ID: 36795 Summary: Authority record identifier source codes (024$2) - code for Web of Science ResearcherID 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: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org I'm not sure whether a new identifier source code is required or not for Web of Science ResearcherID (previously Publons ID). Background ~~~~~~~~~~ System preference OPACAuthorIdentifiersAndInformation (added in bug 29948, which replaced OPACAuthorIdentifiers added in bug 29897), enables the display of authority record information about authors and contributors on OPAC record and authority detail pages.[1] The information that can be displayed includes identifiers for authors and contributors recorded in the authority record 024$2 and 024$a. The 024$2 requires valid codes to be set up with URL patterns so that when displayed they go to the website with that identifier. The current valid values are: - orcid (ORCID) - scopus (ScopusID) - loop (Loop ID) - rid (Publons ID) - viaf (VIAF ID) When these were created in bug 29897, rid was used for the Publons ID. rid is listed in the Library of Congress Standard Identifier Source Codes (https://www.loc.gov/standards/sourcelist/standard-identifier.html) as ResearcherID. Existing Publons IDs are redirected to the Web of Science ResearcherID. However, the new Web of Science ResearcherID URL and number used is different from the Publons ID - we can't just replace the URL pattern for rid with the new one, as it won't work with the older Publon IDs (see example below). Options: 1. We could just change the OPAC display name: . Don't change the exiting URL pattern, would redirect (see example) . Display name in OPAC: Web of Science ResearcherID (previously Publons ID) . The new WoS IDs would work with the old Publons ID URL pattern 2. Create a custom source value for Web of Science ResearcherID. However, if authority records are shared or imported, and they have 024$2 and 024$a information, then the data will end up being "messy". Example ~~~~~~~ - Monika Hestad (IDs from Wikidata https://www.wikidata.org/wiki/Q6900190) - Publons ID: 2601748 - Current URL pattern: https://publons.com/researcher/XXXXX (where XXXXX = Publons ID) - Publons ID URL: https://publons.com/researcher/2601748/ - Redirects to: https://www.webofscience.com/wos/author/record/16447 - New Web of Science ResearcherID is: K-8011-2013 - New Web of Science URL pattern works with the new ID: https://www.webofscience.com/wos/author/record/K-8011-2013 - Note that https://www.webofscience.com/wos/author/record/2601748 (using the old Publons ID) goes to a completely different person - Using the new Web of Science ResearcherID with the old URL pattern: . https://publons.com/researcher/K-8011-2013 . Redirects to https://www.webofscience.com/wos/author/record/16447 I've managed to confuse myself with this, and not sure what is the right way forward now! Hopefully, someone who is more familiar with the history with this ID will have a better approach.... [1] Displayed on the bibliographic record detail page in the holdings section under a new 'Author information' tab; and on the authority record detail page under the 'Author information' heading. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 37994] New: Expand ItemsDeniedRenewal system preference description to include a link to the database schema
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37994 Bug ID: 37994 Summary: Expand ItemsDeniedRenewal system preference description to include a link to the database schema Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucy.vaux-harvey(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be useful for library staff who may not be familiar with database field names to be able to link to the items table from the description - https://schema.koha-community.org/main/tables/items.html. Or perhaps include more examples, for example for itemlost, location? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0