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

[Bug 27175] New: Jenkins instance exposed to public
by bugzilla-daemon＠bugs.koha-community.org 14 May '22

14 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27175 Bug ID: 27175 Summary: Jenkins instance exposed to public Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Continuous Integration Assignee: tomascohen(a)gmail.com Reporter: farmankhan977(a)gmail.com Created attachment 114267 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=114267&action=e… jenkins4koha hi team during recon i found here https://jenkins.koha-community.org/view/supported/builds that your jenkins instance is exposed to public which should be private. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 27750] New: Remove jquery.cookie.js plugin
by bugzilla-daemon＠bugs.koha-community.org 13 May '22

13 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27750 Bug ID: 27750 Summary: Remove jquery.cookie.js plugin 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 24623, 24624, 27749, 23944, 23947, 24619, 24621, 24625 As we transition from jquery.cookie.js to js-cookie.js both plugins are included globally in the templates. As soon as all instances of its use are fixed the plugin should be removed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23944 [Bug 23944] Phase out use of jquery.cookie.js in favor of js.cookie.js https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23947 [Bug 23947] Phase out jquery.cookie.js: Authority merge https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24619 [Bug 24619] Phase out jquery.cookie.js: MARC Frameworks https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24621 [Bug 24621] Phase out jquery.cookie.js: Basic MARC editor https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24623 [Bug 24623] Phase out jquery.cookie.js: Advanced MARC editor https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24624 [Bug 24624] Phase out jquery.cookie.js: Receipt summary https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24625 [Bug 24625] Phase out jquery.cookie.js: showLastPatron https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27749 [Bug 27749] Phase out jquery.cookie.js: Search to hold -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 26378] New: Show SerialIssueDisplayCount syspref values in subscription-add.pl
by bugzilla-daemon＠bugs.koha-community.org 12 May '22

12 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26378 Bug ID: 26378 Summary: Show SerialIssueDisplayCount syspref values in subscription-add.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When setting up a new subscription, one can set values for "Number of issues to display to staff" and "Number of issues to display to the public." If you don't set these in a specific subscription, then they fall back to the values in the system preferences StaffSerialIssueDisplayCount and OPACSerialIssueDisplayCount, respectively. It'd be good to add a note along the lines of "If unset, will default to the value in StaffSerialIssueDisplayCount (X)," where X is the value from the syspref. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 25705] New: Viewing all serials issues should not require serials permissions
by bugzilla-daemon＠bugs.koha-community.org 12 May '22

12 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25705 Bug ID: 25705 Summary: Viewing all serials issues should not require serials permissions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com On the "/cgi-bin/koha/opac-detail.pl?biblionumber=X" page, there is a link "More Details" (/cgi-bin/koha/opac-serial-issues.pl?biblionumber=X), which shows the "Full subscription history" (ie received issues) for a subscription for a bib record. The Staff Client does not have an equivalent. The "/cgi-bin/koha/catalogue/detail.pl?biblionumber=X" page has a "Subscription details" (/cgi-bin/koha/serials/subscription-detail.pl?subscriptionid=X) link, but that requires full Serials permissions. Plus, it's not really equivalent. The closest equivalent is "/cgi-bin/koha/serials/serials-collection.pl?subscriptionid=X", but it also requires full Serials module permissions. It does not make sense that an OPAC user can see more data than a Staff Client user. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[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 27575] New: Search "Analytics: Show analytics" broken when records title ends with ":"
by bugzilla-daemon＠bugs.koha-community.org 12 May '22

12 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27575 Bug ID: 27575 Summary: Search "Analytics: Show analytics" broken when records title ends with ":" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In MARC21 XSLT display, link to analytics is composed with a search on "q=Host-item:" + 245$a When 245$a ends with a ":" the search does not find linked records. They contain 773$t not ending with ":". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[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