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

[Bug 19318] New: Add ability to use custom file upload paths
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '22

02 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19318 Bug ID: 19318 Summary: Add ability to use custom file upload paths Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries don't like the hard coded way uploaded files are all put in the same directory with the hash prefixing the file. We should allow uploaded files to retain their original name, and optionally specify a path to upload to I'm imagining we could accomplish this with something along these lines: 1) Add option on file upload page to not add file checksum to the uploaded filename, modify Koha::Upload 2) Modify Koha::Upload to support this option 3) Create new Authorised Value UPLOAD_PATH to define a set of upload paths 4) Add new 'upload path' option to file upload form as a pulldown of defined upload paths 5) Add new column 'file_path' to uploaded_files table 6) Modify Koha::Upload to support the automatic creation and use of custom file upload paths -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[Bug 30543] New: Decouple DumpSearchQueryTemplate from other template dump preferences
by bugzilla-daemon＠bugs.koha-community.org 30 Sep '22

30 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30543 Bug ID: 30543 Summary: Decouple DumpSearchQueryTemplate from other template dump preferences Change sponsored?: --- Product: Koha Version: master 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using dump search query to debug search issues it would be simpler if we could get only the search query -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 28353] New: regression: Batch Item Deletion no longer shows which items were not removed
by bugzilla-daemon＠bugs.koha-community.org 30 Sep '22

30 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28353 Bug ID: 28353 Summary: regression: Batch Item Deletion no longer shows which items were not removed Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In 19.11 when using the batch item deletion tool, the confirmation screen included the total number of items and bibs deleted, and listed the items that could not be deleted, such as if they were checked out, etc. In 20.05 the user only sees the number of items and bibs deleted and no message that items in the batch were not deleted. The results page should show a list of items in the batch that were not able to be deleted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 29579] New: Show saved SQL report ID in database query
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '22

29 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29579 Bug ID: 29579 Summary: Show saved SQL report ID in database query Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org When users run saved SQL reports, some of them might cause problems on the database end, for example taking too long or requiring too much resources. It would be useful if it was possible to see in the database server end which saved SQL report was the culprit. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 29155] New: upgrade jquery version
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '22

29 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29155 Bug ID: 29155 Summary: upgrade jquery version Change sponsored?: --- Product: Koha Version: master 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha currently jQuery version 2.2.3 on the staff client and 3.4.1 on the OPAC. There are known vulnerabilities in versions less than 3.5.0: https://www.cvedetails.com/cve/CVE-2020-11023/ Perhaps it is time to upgrade to a more secure version. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 27051] New: opac-library.tt should include email
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '22

27 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27051 Bug ID: 27051 Summary: opac-library.tt should include email 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org opac-library.tt omits the branch email address. This information would be nice to show on the page as a 'mailto:' link. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 28131] New: Allow subscriptions to be linked to existing orders
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '22

26 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28131 Bug ID: 28131 Summary: Allow subscriptions to be linked to existing orders Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions 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 workflow for subscription orders is a little "backwards": You have to create a subscription first, before you can create an order for it. It would be nice, if we could also do it the other way around: - Create an order for a serial record in your database, maybe using - When the first issue is delivered, use it to create your subscription and link it to the order This would not also help to streamline the acq process for new subscriptions, it would also be very handy to be able to link older orders to subscriptions that have been created before the feature was available in its current form. Or for migration data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 26559] New: koha-create fails to upgrade database
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '22

26 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26559 Bug ID: 26559 Summary: koha-create fails to upgrade database Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com When I run koha-create, with DEFAULTSQL set to the path of an existing database dump, I get an error when it tries to upgrade the database: $ sudo koha-create --create-db --letsencrypt --configfile student.conf mykoha staff user password is '***' but keep that secret Upgrading database schema for mykoha DBI connect('database=koha_mykoha;host=localhost;port=3306','koha_mykoha',...) failed: Access denied for user 'koha_mykoha'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: Access denied for user 'koha_mykoha'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1520. at /usr/share/koha/lib/Koha/Database.pm line 116 After this, the Apache config file is created at /etc/apache2/sites-available/mykoha.conf, but the symlink at /etc/apache2/sites-enabled/mykoha.conf is not created. I can run koha-mysql and get access to the database, where the data from DEFAULTSQL has been loaded. If I comment out line 734 of koha-create: koha-upgrade-schema "$name" things run as expected, and the Apache config symlink is created. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 29310] New: Add timestamp, updated_on to aqbooksellers
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '22

23 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29310 Bug ID: 29310 Summary: Add timestamp, updated_on to aqbooksellers 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment there is no way to tell when a vendor has been added or last updated. This would be helpful in some cases and we could mimick the fields we have on other tables here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 23301] New: Borrower messaging preferences lost when duplicating patron and changing category
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '22

23 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23301 Bug ID: 23301 Summary: Borrower messaging preferences lost when duplicating patron and changing category Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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 To test: - Create a patron and set their messaging preferences to something other than the defaults - Duplicate the patron - Note that their messaging preferences have been maintained - Before saving the new patron, change their category - Note that their messaging preferences reset to the default for their new category -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6