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

[Bug 20103] New: Remove Readonly::XS
by bugzilla-daemon＠bugs.koha-community.org 12 May '22

12 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20103 Bug ID: 20103 Summary: Remove Readonly::XS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com >From the Readonly CPAN page: "Install this module, but do not use it. ... Programs that you write do not need to know whether Readonly::XS is installed or not. They should just "use Readonly" and let Readonly worry about whether or not it can use XS. If the Readonly::XS is present, Readonly will be faster. If not, it won't. Either way, it will still work, and your code will not have to change." This removes the Readonly::XS from the PerlDependencies. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 24552] New: Koha does not work with Search::Elasticsearch 6.00
by bugzilla-daemon＠bugs.koha-community.org 12 May '22

12 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24552 Bug ID: 24552 Summary: Koha does not work with Search::Elasticsearch 6.00 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Koha doesn't work with the latest version of Search::Elasticsearch (6.00) Steps to reproduce: 1. Install latest version of Search::Elasticsearch 2. Set SearchEngine syspref to 'Elasticsearch' 3. Reload starman 4. Do a search The search fails with the following error message: Error: Can't locate Search/Elasticsearch/Client/5_0/Direct.pm in @INC (you may need to install the Search::Elasticsearch::Client::5_0::Direct module) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 16116] New: Change of issue publication date doesn't reflect on the next issue generated
by bugzilla-daemon＠bugs.koha-community.org 11 May '22

11 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16116 Bug ID: 16116 Summary: Change of issue publication date doesn't reflect on the next issue generated Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: francois.charbonnier(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com I noticed in 3.20, but also in master, that you can't change the next issue publication date when editing a serial subscription anymore. And, that we lost a feature I liked when receiving a new issue. Before 3.20, when receiving a new issue, you could change the "Published on" date and Koha will adjust the subscription's next issue publication date for all the new issues to be received. Test plan : 1. In Cataloging > New with Z39.50, look for issn = 1536-6596 (National Geographic) into the LCC z39.60 server. Add the record. 2. Add a new subscription for National Geographic. Fill-in the form. - use the default values of the first page - for the second page : First issue publication date = 10/01/2016 Frequency = 1/month Subscription lenght = 12 issues Subscription start date = 01/01/2016 Numbering pattern = Number Begins with = 1 - Save 3. Receive the first issue. Change the status to "received". Note that the "Published on" date = 10/01/2016. This date goes to the "Date published" column in the serial collection page. 4. The second issue is generated. Edit serial to receive the issue. 5. Change the "Published on" date to 11/02/2016. Change the status to "received". Save. 6. "Date published" for the next issue generated is : 10/03/2016. Before 3.20, it would have been "11/03/2016". It was a shortcut to change the Next issue publication date from the subscription. 7. Edit the subscription. Change the "Next issue publication date" to : 11/03/2016. 8. Go back to the serial collection page. Date published for the last expected issue = 11/03/2016 9. Receive the issue. Change the status to "received". Save 10. The next issue generated is 10/04/2016. It should have been 11/04/2016. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 20615] New: add the link of number of times the authority are used in edit mode
by bugzilla-daemon＠bugs.koha-community.org 11 May '22

11 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20615 Bug ID: 20615 Summary: add the link of number of times the authority are used in edit mode Change sponsored?: --- Product: Koha Version: unspecified 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: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, in the authorities module, when we consult a record there is a line at the top of the page indicating the number of records for which this authority is being usaed in. But this line disappears when you go into edit mode of the record. It would be convenient to keep this information on edit mode too. Thanks, Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 24787] New: send notices fail if there is no email in borrowers account
by bugzilla-daemon＠bugs.koha-community.org 10 May '22

10 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24787 Bug ID: 24787 Summary: send notices fail if there is no email in borrowers account 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: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org This bug is similar to bug 6302 or perhaps has reproduce again. If there is not a to_address at messages_queue avoids to send any mail, to any other user at message_queue I think desirable behaviour should move to 'failed' thos without to_address and continue with the next one of the list tested in koha 18.11.03 debian 8 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 26015] New: Terminology: staff interface should be used everywhere
by bugzilla-daemon＠bugs.koha-community.org 07 May '22

07 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26015 Bug ID: 26015 Summary: Terminology: staff interface should be used everywhere Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org We agreed that the preferred term is 'staff interface', not staff client, intranet or similar. -- You are receiving this mail because: You are watching all bug changes.

1 41

[Bug 17724] New: Callnumber not copied into serial issue, when callnumber subfield is linked to a plugin
by bugzilla-daemon＠bugs.koha-community.org 06 May '22

06 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17724 Bug ID: 17724 Summary: Callnumber not copied into serial issue, when callnumber subfield is linked to a plugin Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal 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 CC: colin.campbell(a)ptfs-europe.com To test: - Make sure your 952$o (callnumber) is linked to a plugin such as cn_browser.pl in your frameworks - Create a subscription with "create item on receive" and a callnumber - Receive an issue - Verify that the callnumber is not copied into the item on receive - Remove the plugin from the framework - Verify that the callnumber now is copied into the item on receive -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 26305] New: Warn IE users of Staff Interface that it is no longer supported and to use a support browser instead
by bugzilla-daemon＠bugs.koha-community.org 06 May '22

06 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26305 Bug ID: 26305 Summary: Warn IE users of Staff Interface that it is no longer supported and to use a support browser instead Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Browser compatibility Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I frequently get people raising issues about Koha not working because they're using Internet Explorer. While I think it is very sensible for Koha not to support IE, I think it might be useful in this transitional time to show a warning banner on the Staff Interface to tell users that they can't use IE anymore and expect Koha to work. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 26132] New: Improve readability of TooMany
by bugzilla-daemon＠bugs.koha-community.org 06 May '22

06 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26132 Bug ID: 26132 Summary: Improve readability of TooMany Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 21946 This is a follow-up of bug 21946. We need to improve the readability of C4::Circulation::TooMany to prevent regressions. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21946 [Bug 21946] Group circulation by item type -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 21946] New: Group circulation by item type
by bugzilla-daemon＠bugs.koha-community.org 06 May '22

06 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21946 Bug ID: 21946 Summary: Group circulation by item type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: kyle(a)bywatersolutions.com Reporter: jesse(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Group rules based on item type in order to restrict circulation. In other words, not allow more than x items to be checked out across all media type item types (DVD, VHS, Blue Ray) and not just 4 checkouts per type. Currently patrons can bypass the circulation rules and take out 4 DVDs and 4 VHS and still be within the system limitation but in reality have just taken out 8 media items. This development would allow for the grouping of materials in order to keep that 4 media limit across all types. 1 - Extend the itemtypes table to allow an itemtype to have a parent type 2 - When circulating an item the specific itemtype circulation rules will apply unless unset 3 - For itemtypes with a parent the parent rule will apply when child rule is unset -- You are receiving this mail because: You are watching all bug changes.

1 171