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

[Bug 24446] New: Stockrotation: Update to use daterequested in branchtransfers
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24446 Bug ID: 24446 Summary: Stockrotation: Update to use daterequested in branchtransfers 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Bug 23092 adds a daterequested field to the branchtransfers table which better reflects how stockrotation utilises the existing datesent field. This patchset will update stockrotation to take advantage of the new field and in doing so rectify some of the rotation logic. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 116

[Bug 22318] New: Extend Koha news feature to include other content areas
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22318 Bug ID: 22318 Summary: Extend Koha news feature to include other content areas 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- There are many content areas in Koha where we currently use a single system preference to define a block of HTML which is embedded in the OPAC or Staff Client. Using system preferences for this requires that we either use only one language for the content or we use a convoluted system of CSS hiding/showing based on language. We already have a system in place for handling this better: The Koha news feature. We could add additional "display locations" for the various system preferences which could be migrated here: OpacNavRight, opacheader, OpacMainUserBlock, OPACMySummaryNote, OpacNav, OpacNavBottom, etc. This would allow libraries to define both language-specific and library-specific content for these areas of the interface. Being able to define start and end dates for content display would be really useful too. I imagine it would be inefficient to add multiple lines to, for instance, opac-main.pl for each "location," like so: my $OpacNavRight = GetNewsToDisplay( "OpacNavRight_".$news_lang, $homebranch ); Perhaps a template plugin and a block like this? [% PROCESS koha_news news => GetKohaNews( location => news_lang, library => homebranch ) %] I'd love to hear what y'all think. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 72

[Bug 17937] New: Adding item description to Twitter Summary
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17937 Bug ID: 17937 Summary: Adding item description to Twitter Summary 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: caitlingoodger.student(a)wegc.school.nz QA Contact: testopia(a)bugs.koha-community.org When a user posts a link to an item in their library's catalog on Twitter the description will show in the Twitter card. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 22824] New: We depend on both YAML and YAML::Syck
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22824 Bug ID: 22824 Summary: We depend on both YAML and YAML::Syck 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- We should settle on a single YAML implementation rather than requiring two. I would advocate YAML::XS as it's the defacto recommended module by the perl community at the moment (and has been for some time now) and it's available packaged on debian back to our oldest supported release at the time of this comment. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 120

[Bug 24010] New: Number of issues to display to staff accepts non-integer values
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '22

19 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24010 Bug ID: 24010 Summary: Number of issues to display to staff accepts non-integer values 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: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When adding a new serial subscription in the page /cgi-bin/koha/serials/subscription-add.pl one can add to the field "Number of issues to display to staff" a non-integer value like "f" and then when you save this new subscription and go to the "Subscriptions" tab in /cgi-bin/koha/catalogue/detail.pl?biblionumber=XXXX you get the following error in plack-error.log: >DBD::mysql::st fetchrow_hashref failed: fetch() without execute() [for Statement "SELECT serialid,serialseq, status, planneddate, publisheddate, notes > FROM serial > WHERE subscriptionid = ? > AND status IN (2,4,41,42,43,44) > ORDER BY publisheddate DESC LIMIT 0,f > " with ParamValues: 0=2] at /home/koha/kohaclone/C4/Serials.pm line 784. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 42

[Bug 20688] New: Add accesskeys for hold confirmation boxes
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '22

19 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20688 Bug ID: 20688 Summary: Add accesskeys for hold confirmation boxes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When checking out a book that is already checked out to another patron the confirmation boxes display "Yes, check out (Y)" and the HTML has an "accesskey" element to allow confirmation via the keyboard We should duplicate the same functionality for hold confirmation boxes (and probably elsewhere eventually) I suggest: "c" Confirm hold (C) "p" Confirm hold and print (P) "i" Ignore (I) "x" Cancel hold (X) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 18052] New: Show link to the item for an issue on serial collection page
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '22

19 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18052 Bug ID: 18052 Summary: Show link to the item for an issue on serial collection page 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com It would be nice if there was a link to edit the item linked to a specific serial issue from within the serials module. For example, a new column with an 'edit item' link could be added to the serials-collection page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 24991] New: make restart sip start sip if it isn't running
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '22

18 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24991 Bug ID: 24991 Summary: make restart sip start sip if it isn't running 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: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com koha-sip --restart should try to start sip if it is not running. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 22329] New: Parent funds showing incorrect amounts for Ordered, Spent, Available on Acquisitions Home
by bugzilla-daemon＠bugs.koha-community.org 16 Aug '22

16 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22329 Bug ID: 22329 Summary: Parent funds showing incorrect amounts for Ordered, Spent, Available on Acquisitions Home Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- On acqui-home.pl, the amounts for Ordered and Spent for parent funds to no reflect orders charged to their child funds, only orders charged to the parent fund directly. I can see some room for argument here if libraries are are sometimes charging a parent fund directly, but overall it may be more clear if ordered and spent for a parent fund showed totals for all orders charged to the parents AND its children. Total Available for the parent is also based only on orders charged to the parent directly and this is definitely misleading. Total available for a parent fund should display as total allocated to parent minus (total ordered/spent for parent plus total ordered spent for all children). These changes would bring acqui-home.pl in line with the numbers shown on aqbudgets.pl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 17814] New: koha-plack --stop should make sure that Plack really stop
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '22

12 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17814 Bug ID: 17814 Summary: koha-plack --stop should make sure that Plack really stop Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: pongtawat(a)punsarn.asia QA Contact: testopia(a)bugs.koha-community.org koha-plack --stop doesn't ensure that Plack was really stopped before returning. So in case that koha-plack --stop was quickly follows by koha-plack --start (e.g. logrotate), it could leave Plack in stop state. This is due to koha-plack --start think that Plack was already started, while it actually is being stopped. For me I think this is the cause why I got random Plack stop when logrotate is run. It should be similar to the case of Zebra in Bug #16885, and the solution might be the same: adding "--retry=TERM/30/KILL/5;" to start-stop-daemon command. I just try that on our server and will see if the problem goes away. -- You are receiving this mail because: You are watching all bug changes.

1 26