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

[Bug 31801] New: REST API: PUT endpoint for Biblios
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '23

21 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31801 Bug ID: 31801 Summary: REST API: PUT endpoint for Biblios Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 20670] New: Add markup and standard classes for sidebars and main content areas
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '23

21 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20670 Bug ID: 20670 Summary: Add markup and standard classes for sidebars and main content areas 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 Blocks: 14546 As we move away from YUI grids, it would be helpful if we could consistently add some classes to the primary sections of the page. That would allow us to style elements differently based on their container's class. I've already begun adding a "main" class to the <div> which is the primary "container" for the Bootstrap grid. It typically looks like this: <div class="main container-fluid"> <div class="row"> <div class="col-sm-5 col-md-4"> I would like to add an additional container that wraps the primary content region for the page. This container should have no style attached to it (as it might interfere with grid layout), but can serve as a context for styles within it. ----------------------------------------------- * .main * * ------------------------------------------- * * * * .main-content * * * * * * * * * .sidebar * -------------------------- * * * * * * * * * * * * * .row * * * * * * * .col-* * * * * * * * ...etc. * * * * * * -------------------------- * * * * * * * * ------------------------------------------- * * * ----------------------------------------------- The use I have right away is to style forms differently based on whether they are in the sidebar or the main-content area. Right now we have some CSS which depends on YUI grid classes, and we need to replace that which isn't dependent on the grid system we choose. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14546 [Bug 14546] Make staff client templates responsive -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 31175] New: OPAC Logout should return you to where you were (unless that's a restricted page)
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '23

21 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31175 Bug ID: 31175 Summary: OPAC Logout should return you to where you were (unless that's a restricted page) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The OPAC logout appears to always take you back to opac-main. To test 1) Perform a search 2) Go to the details of a search results 3) Logout 4) Note, you are no longer on the defail page for the record you had searched for. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 33619] New: the "update sql" window isn't showing obsolete fields and their new names.
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33619 Bug ID: 33619 Summary: the "update sql" window isn't showing obsolete fields and their new names. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: marie-luce.laflamme(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org The “update sql” button of an obsolete report has stopped describing fields that need to be fixed. If your report still contains a biblioitems.marcxml field, Koha will warn with a “This report seems obsolete” message. Then, you can click on the “update sql” button to fix the report, and Koha will open up a popup window. Unfortunately, this window is no longer showing obsolete fields and their new names. Instead, there is only a loading cursor on display without any explanations. At this point, you aren't sure if you can click on the "update" button within the window, thinking it may be broken. But if you try, Koha will update the report correctly. Is there a way to bring back the previous version behaviour in this window? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 15977] New: Optional double screen message in Patron Info/Status
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15977 Bug ID: 15977 Summary: Optional double screen message in Patron Info/Status 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com This code in MsgType.pm: $resp .= maybe_add( FID_SCREEN_MSG, $patron->{branchcode}, $server ) if ( $server->{account}->{send_patron_home_library_in_af} ); produces two AFs if you enable that attribute in your config. Not sure if that should be the case and is conform protocol. Also: are we solving a problem here in the wrong place? It looks kind of inappropriate use.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 34680] New: Renewal due date -> different due times (HH:MM) depending on the input method
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34680 Bug ID: 34680 Summary: Renewal due date -> different due times (HH:MM) depending on the input method Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: irina.halminen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 155028 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=155028&action=e… Renewal due date When setting a renewal due date from the bottom of the circulation page (/cgi-bin/koha/circ/circulation.pl? -> Check out) and typing the due date by hand (not selecting it from the calendar) and pressing Enter, the system sets the due time (HH:MM) automatically, and it differs from the default. For example, our due time is set to be 23:59, but when I type in the renewal due date, it sets the due time to be 00:00. So if the due date is October 31st and the due time is 00:00, all the loans are overdue a minute after the midnight on the due date. Using the calendar and using the manual typing method should both end up in the same result (default HH:MM). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 34939] New: When manually entering dates in flatPickr the hour and minute get set to 00:00 not 23:59
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34939 Bug ID: 34939 Summary: When manually entering dates in flatPickr the hour and minute get set to 00:00 not 23:59 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org With flatPickr you can manually enter a date. If that date date allows for the input of hours and minutes and you do not manually specify those the default will be 00:00. When you use the flatPickr calendar to pick a date time and no do specify the hour/minute it will default to 23:59. This should be consistent. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 34884] New: Allow styling and customization of checkout screen by patron category
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34884 Bug ID: 34884 Summary: Allow styling and customization of checkout screen by patron category 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: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, lucas(a)bywatersolutions.com, rcoert(a)arlingtonva.us Created attachment 156077 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=156077&action=e… example screenshot For patron categories with restricted lending privileges, we use jQuery and CSS to color the background of #circ_circulation_issue and insert a short text string describing what a patron in this category is allowed to borrow (screenshot attached). It'd be helpful to be able to define these things in patron categories somehow. Maybe we could save a color code for each category, to be applied to #circ_circulation_issue as a background or border? And also a short text string for each category to be inserted in that area? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 22317] New: Performance issues with large number of funds
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22317 Bug ID: 22317 Summary: Performance issues with large number of funds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions 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: --- The acquisitions landing page displays a summary table for the funds. This can sometimes be very large and cause a significant lag in the page load and display. Ultimately, it would be nice to fix this performance issue at the root. (There is initially a fairly prominent server lag, but there is also a clear difference between rendering time in Chrome/Firefox vs in IE). As a 'quick fix' it may be enough to make the display of that summary table syspref controlled so libraries with a large number of funds defined can choose not to display the summary on that page to improve the performance of page load so they can proceed to Vendor searches and other acquisitions actions available from that page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 22221] New: Changing an item to a Lost Status on an item level hold does not change the hold
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22221 Bug ID: 22221 Summary: Changing an item to a Lost Status on an item level hold does not change the hold Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- If a library is using Item Level holds and a patron places a specific item hold. If the library finds that this specific item is missing, they can change the item to missing, however, the hold is still attached to this item. The library then needs to remove the item level hold and re-attach it to another item or make it a bib level hold. It would be nice, if this change of "Lost" status of this item is altered, the hold can be changed to a bib level hold or an easy ability to adjust the hold as necessary. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6