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

[Bug 31790] New: REST API: CRUD endpoints for Authorities [omnibus]
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '23

13 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31790 Bug ID: 31790 Summary: REST API: CRUD endpoints for Authorities [omnibus] Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature 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 -Single Record per Call -Accept data as marcxml -Support POST, GET, PUT, DELETE -Return ID upon successful creation -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 23068] New: Add ability for Koha to handle X-Forwarded-For headers so REMOTE_ADDR features work behind a proxy
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '23

13 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23068 Bug ID: 23068 Summary: Add ability for Koha to handle X-Forwarded-For headers so REMOTE_ADDR features work behind a proxy Change sponsored?: --- Product: Koha Version: unspecified 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Koha has a number of features that rely on knowing the IP address of the connecting client. If that server is behind a proxy these features do not work. We can use Plack::Middleware::RealIP to automatically convert the X-Forwarded-For header into the REMOTE_ADDR environment variable so no Koha code need be modified. A future enhancement could be to take advantage of the module's trusted_proxy setting to allow Koha to use these feature even after going through *multiple* proxies. This would require being able to read configuration from the plack.psgi file and is beyond the scope of this enhancement. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 77

[Bug 27452] New: Create GUI for patron_emailer cron
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '23

13 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27452 Bug ID: 27452 Summary: Create GUI for patron_emailer cron 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, katrin.fischer(a)bsz-bw.de, nick(a)bywatersolutions.com Depends on: 16149 It would be nice to have a GUI for this cron so folks don't need to install the plugin (https://github.com/bywatersolutions/koha-plugin-patron-emailer) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16149 [Bug 16149] Generate and send custom notices based on report output -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 29486] New: _koha_marc_update_bib_ids no longer needed for GetMarcBiblio (?)
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29486 Bug ID: 29486 Summary: _koha_marc_update_bib_ids no longer needed for GetMarcBiblio (?) Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org C4::Biblio::_koha_marc_update_bib_ids is adding biblionumber and biblioitemnumber to the MARC record. When it may still be needed when a bibliographic record is added/edited, why do we need it for GetMarcBiblio? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 32464] New: Koha::Item->as_marc_field obsolete option mss
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32464 Bug ID: 32464 Summary: Koha::Item->as_marc_field obsolete option mss 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Since Bug 28445 the method Koha::Item->as_marc_field has the option mss not anymore. It is still existing in Koha::Filter::MARC::EmbedItems -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 32060] New: Improve performance of Koha::Item->columns_to_str
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32060 Bug ID: 32060 Summary: Improve performance of Koha::Item->columns_to_str 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: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When creating a new item for a biblio with many items, for example serials which can have several hundreds, the table of existing items that is shown is currently very performance heavy to generate. The main culprit is Koha::Item->columns_to_str that can be sped up substantially by caching data that is looked up repeatedly for each call. With this patch columns_to_str will run about ~70x faster, reducing the load time of /cataloguing/additem.pl?biblionumber=... to about one fifth for a biblio with about 150 items (and even more with increasing number of items). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 33411] New: SIP2 includes other guarantees with the same guarantor when calculating against NoIssuesChargeGuarantees
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33411 Bug ID: 33411 Summary: SIP2 includes other guarantees with the same guarantor when calculating against NoIssuesChargeGuarantees Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 29755 seems to have made a bad assumption when moving code to use Koha::Patron->relationships_debt for calculating fine thresholds It seems that routine finds the patrons guarantor, and adds all related guarantees when called like: $patron->relationships_debt({ include_guarantors => 0, only_this_guarantor => 0, include_this_patron => 0 }); It seems NoIssuesChargeGuarantees should only count a patrons direct guarantees, not the fines of patrons sharing their guarantor -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 33247] New: Deleted authority still on results list
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33247 Bug ID: 33247 Summary: Deleted authority still on results list Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fribeiro(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl After deleting an authority from authorities home, the page loaded after the operation still contains the deleted authority. To reproduce: 1 - Go to authorities home and perform a search; 2 - Delete any authority; 3 - After the confirmation, the page is refreshed but still contains the deleted authority; If you reload the page, that row disappear. It seems that the authorities search is performed before the index is deleted. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 33314] New: Link to bibliographic record incomplete in default TICKET_NOTIFY notice
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33314 Bug ID: 33314 Summary: Link to bibliographic record incomplete in default TICKET_NOTIFY notice Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When reporting a catalog concern, an email is sent to the cataloging team with a link to the bibliographic record in question. However, this link seems to be incomplete. (Might be linked to bug 33313, but I think the source of the problem is different...) To reproduce: 1. Make sure staffClientBaseURL is filled correctly 2. Enable CatalogConcerns 3. Enter an email address in CatalogerEmails 4. Go to a bibliographic record in the staff interface 5. Click New > New catalog concern 6. Fill out the form and click Submit 7. Check the message_queue table for the message --> In the message, the link base to the record is empty a href="/cgi-bin/koha/catalogue/detail.pl?biblionumber=61" Unfortunately, it's not as easy as changing the pref name to staffClientBaseURL because the line in the notice is [%- INCLUDE 'biblio-title.inc' biblio=ticket.biblio link = 1 -%]. So I'm guessing it's taking the baseURL somewhere else, but I don't know where. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 33313] New: TICKET_NOTIFY looking for IntranetBaseURL rather than staffClientBaseURL in default notice
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33313 Bug ID: 33313 Summary: TICKET_NOTIFY looking for IntranetBaseURL rather than staffClientBaseURL in default notice Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org While I think IntranetBaseURL is a better name for it, the system preference is still called staffClientBaseURL ;) To reproduce 1: 1. Go to Tools > Notices and slips 2. Look for TICKET_NOTIFY 3. Click 'Edit' next to TICKET_NOTIFY 4. Click 'Email' --> In the message body is this line a href='[%- Koha.Preference('IntranetBaseURL') -%]/cgi-bin/koha/cataloguing/concerns.pl To reproduce 2: 1. Make sure staffClientBaseURL is filled correctly 2. Enable CatalogConcerns 3. Enter an email address in CatalogerEmails 4. Go to a bibliographic record in the staff interface 5. Click New > New catalog concern 6. Fill out the form and click Submit 7. Check the message_queue table for the message --> In the message, the link base is empty <br><br>You can mark this concern as resolved from the concern management <a href='/cgi-bin/koha/cataloguing/concerns.pl'>page</a> -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32