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

[Bug 29060] New: Use modal for suspending holds until a date from the holds page
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '22

10 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29060 Bug ID: 29060 Summary: Use modal for suspending holds until a date from the holds page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If you view the list of holds on a patron's checkout screen you can click the "Suspend" button to trigger a modal dialog where you can select a date after which the hold should resume. I'd like to make the controls work the same way when viewing the list of holds on a title, e.g. /cgi-bin/koha/reserve/request.pl?biblionumber=XXX -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 28883] New: Koha::Objects->_new_from_dbic doesn't work correctly in list context
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '22

10 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28883 Bug ID: 28883 Summary: Koha::Objects->_new_from_dbic doesn't work correctly in list context 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It will always return a resultset, it should return a list in list context. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 70

[Bug 29693] New: CodeMirror broken on additional_contents.tt
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '22

10 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29693 Bug ID: 29693 Summary: CodeMirror broken on additional_contents.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: -Go to Tools and open either additional contents ( either News or HTML customization ) -Make sure you open it using CodeMirror and not TinyMCE -Code mirror is broken -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 29588] New: Yesterday and tomorrow in datepicker don't translate
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '22

10 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29588 Bug ID: 29588 Summary: Yesterday and tomorrow in datepicker don't translate Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 29478 Tomorrow, Yesterday and or in the new Flatpickr datepicker don't translate. Today does, I am not sure why. I think it should be either only one underscore in an .inc file or it's something else. I tried updating the po files locally, but the strings didn't show up. ++ b/koha-tmpl/intranet-tmpl/prog/en/includes/calendar.inc @@ -34,6 +34,7 @@  [% Asset.js("js/calendar.js") | $raw %] [% Asset.js("lib/flatpickr/flatpickr.min.js") | $raw %] +[% Asset.js("lib/flatpickr/shortcut-buttons-flatpickr.min.js") | $raw %] <script> flatpickr.l10ns.default.weekdays = flatpickr_weekdays; flatpickr.l10ns.default.months = flatpickr_months; @@ -84,6 +85,38 @@ $(on_close_focus).focus(); } }, + plugins: [ + ShortcutButtonsPlugin({ + button: [ + { + label: __("Yesterday") + }, + { + label: __("Today") + }, + { + label: __("Tomorrow") + } + ], + label: "or", Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29478 [Bug 29478] flatpickr misses quick shortcut to "Today" date -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 23149] New: Unsuspend button in staff interface is confusing
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '22

10 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23149 Bug ID: 23149 Summary: Unsuspend button in staff interface is confusing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests 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 Target Milestone: --- When viewing the holds page for biblio in the staff client it initially says: 'Suspend' until [date] - where suspend is a button and date is a datepicker if you choose a date and hit 'suspend' it then says 'Unsuspend' on [date] - where unsuspend is a button and the date is the date set above, but offers a date picker I read 'Unsuspend on date' as an option to set the date the hold will be unsuspended - not as 'Unsuspend now' with an irrelevant date displayed afterwards, which is how it seemingly functions. Does this make sense to others in its current state? I would propose: 'Suspend' until [date] - and if you set a date and click suspend it becomes Suspended until [date] then a new column with 'Unsuspend' as a button -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 21051] New: CGI::param called in list context when editing a patron card layout
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '22

10 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21051 Bug ID: 21051 Summary: CGI::param called in list context when editing a patron card layout Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org To test: - Edit a patron card layout - Save or cancel editing CGI::param called in list context from package CGI::Compile::ROOT::home_vagrant_kohaclone_patroncards_edit_2dlayout_2epl line 186, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. CGI::param called in list context from package CGI::Compile::ROOT::home_vagrant_kohaclone_patroncards_edit_2dlayout_2epl line 186, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. CGI::param called in list context from package CGI::Compile::ROOT::home_vagrant_kohaclone_patroncards_edit_2dlayout_2epl line 186, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. CGI::param called in list context from package Template::Document line 57, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 28982] New: Use Flatpickr on onboarding pages
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '22

10 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28982 Bug ID: 28982 Summary: Use Flatpickr on onboarding pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED 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 CC: testopia(a)bugs.koha-community.org Depends on: 28937, 28376 There is one datepicker instance in the onboarding templates which should be replaced with Flatpickr. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28376 [Bug 28376] Replace obsolete jquery-ui-timepicker-addon https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28937 [Bug 28937] Use Flatpickr on circulation and patron pages -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 29661] New: PreFillItem should not apply to duplicated items
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '22

09 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29661 Bug ID: 29661 Summary: PreFillItem should not apply to duplicated items 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In 21.05.07, the PreFillItem syspref is applied when duplicating an item. This was not the case in previous versions of Koha and is not the case on master. To recreate (on 21.05): - set PrefillItem to "the new item is prefilled ..." - set SubfieldsToUseWhenPrefill to 3 so that the Materials Specified value is prefilled - create an item that has a Materials Specified note - confirm that when the Add Item page reloads after creating your item, the Materials Specified note is prefilled as expected - find an item without a Materials Specified value, duplicate it - confirm your duplicate item's Materials Specified is prefilled with the value from your first item, when it should be null like your second item -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29763] New: Patron information - terminology; borrowernumber
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '22

09 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29763 Bug ID: 29763 Summary: Patron information - terminology; borrowernumber Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On the patron details page the 'Borrowernumber' is shown on the top left patron information section. 'borrowernumber' is used as part of the query/URL and is the assigned number given to a patron in the database. It is also used in other areas of the staff interface, such as the patron batch modification tool (Tools > Patrons > Patron batch modification) - see the tab 'By borrowernumber', where you can enter a list of 'borrowernumbers' to modify. Should this be renamed to something more human friendly rather than what the system uses to identify this field? Such as 'Patron number'. Our terminology list says we should use patron, rather than member or borrower: https://wiki.koha-community.org/wiki/Terminology -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 29237] New: When deleting funds from an inactive budget, the results page returns to a different budget
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29237 Bug ID: 29237 Summary: When deleting funds from an inactive budget, the results page returns to a different budget Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: valerie(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In Administration/Budgets, I am in the "inactive budgets" tab, deleting funds under a specific budget. (In this instance, budget period #29.) When I select "delete" for the fund, it opens a new page to verify that I want to delete this budget. After it completes the deletion, it goes to a different budget, an active budget. (In this case, budget period #30). I confirmed that the fund was deleted as expected from the inactive budget, but with the page going to a different budget when complete, a user could easily delete something unintended. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1