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

[Bug 18567] New: Amazon #reader-link feature is not available for all titles, causes error
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18567 Bug ID: 18567 Summary: Amazon #reader-link feature is not available for all titles, causes error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When clicking on an amazon image, if the link includes the '#reader-link' at the end you may get an error messsage: Example: http://www.amazon.com/gp/reader/0773534342/ref=sib_dp_pt/002-7879865-018486… Additionally, it would be nice to make these links open in a new tab/window rather than the current. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 18563] New: Force koha.ics to only show up on first day of created calendar appointment
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18563 Bug ID: 18563 Summary: Force koha.ics to only show up on first day of created calendar appointment 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: jandrews(a)washoecounty.us QA Contact: testopia(a)bugs.koha-community.org This is a follow-up to bug 5456 - create a link to opac-ics.pl. The functionality established by that bug fix creates a file that can be imported to a calendar program. In Outlook, with a due time of 11:59, a 1-hour appointment is created, resulting in a 2-day "date due" appointment in the calendar. The appointment created should be limited to the first (actual due) date. [tag] [reply] [−] Comment 13 John Andrews 2017-05-02 16:16:58 UTC There's a problem with the lack of end time -- when importing this into my outlook calendar, because there's no end time, outlook automatically creates an hour long event. Which means that the due date reminder shows up both on the due date, and on the day AFTER the due date. In our case, the time due is 11:59 pm, so the appointment gets created in outlook as from 11:59 pm on the due date until 12:59 am on the next day. Is there a way to force the appointment to start and end at the same time? [tag] [reply] [−] Comment 14 Magnus Enger 2017-05-03 08:05:18 UTC (In reply to John Andrews from comment #13) Please report this as a new bug/issue. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 18561] New: Use font awesome icons for plus signs in forms
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18561 Bug ID: 18561 Summary: Use font awesome icons for plus signs in forms Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 18558] New: Koha::Clubs::get_enrollable explodes if no patron given
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18558 Bug ID: 18558 Summary: Koha::Clubs::get_enrollable explodes if no patron given Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: kyle(a)bywatersolutions.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 12461 The method should not make $params->{borrower} mandatory. But if not passed, the method explodes with Can't call method "branchcode" on an undefined value at /home/vagrant/kohaclone/Koha/Clubs.pm line 60. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12461 [Bug 12461] Add patron clubs feature -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 18538] New: OPAC database user login internal server error
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18538 Bug ID: 18538 Summary: OPAC database user login internal server error Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Reproduce: 1. Go to OPAC 2. Login with the database user 3. Observe Internal Server Error Check your logs: Can't call method "is_debarred" on an undefined value at /home/koha/kohaclone/opac/opac-user.pl line 96. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 34257] New: Library limitations for item types not respected when batch modding items
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34257 Bug ID: 34257 Summary: Library limitations for item types not respected when batch modding items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Go to Item types administration. 2. Set some items types to be limited to a branch you are not logged in as. 3. Find some items from the branch you are logged in at and go to Batch item modification. 4. Add the barcodes and attempt to edit the item type to the one you limited in step 2. 5. You can change these item types to ones that your branch should not be able to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 34163] New: CSRF error if try OAuth2/OIDC after logout
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34163 Bug ID: 34163 Summary: CSRF error if try OAuth2/OIDC after logout Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org If you do a local log into Koha, then logout, then try to do a OAuth2/OIDC log in, you'll get a CSRF error. The reason is that Koha is generating the CSRF token using an id like "anonymous_58d273f40cb20ff0aacab829aaf935fc" but checking it with an id of "_58d273f40cb20ff0aacab829aaf935fc". This is because we're not properly checking the C4::Context->userenv and/or it seems like it's not getting properly set after a logout. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 34081] New: Contextualization of "Approved" (one term) vs "Approved" (more than one term), and other tag statuses
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34081 Bug ID: 34081 Summary: Contextualization of "Approved" (one term) vs "Approved" (more than one term), and other tag statuses Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N 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: frederic(a)tamil.fr In the case of tags, the statuses are the same for one or more term. For example, in the table of terms, the column "Status" contains the status for the one term. Whereas, on the right, in the "Terms summary", the statuses are for many terms. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 34079] New: The phrase "Displaying [all|approved|pending|rejected] terms" was separated
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34079 Bug ID: 34079 Summary: The phrase "Displaying [all|approved|pending|rejected] terms" was separated Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N 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: frederic(a)tamil.fr The phrase "Displaying [all|approved|pending|rejected] terms" was cut into individual words by bug 30733. However, in French, we need to be able to change the sentence structure (it would become something like "Displaying terms [all|approved|pending|rejected]"). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 32765] New: Retry transfer after cancelling hold
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32765 Bug ID: 32765 Summary: Retry transfer after cancelling hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Circulation Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When trying to manually transfer an item that is on hold, we have the choice to cancel the hold and try the transfer again. When choosing this option, the hold is correctly cancelled but the transfer is not tried again. Steps to reproduce: 1. Place a hold on a specific item 2. Try to transfer it manually (Circulation » Transfer) 3. Choose the option to "Cancel hold and then attempt transfer" 4. See that the hold was cancelled, but no transfer was made -- You are receiving this mail because: You are watching all bug changes.

1 27