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

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

22 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 31630] New: Batch item deletion no longer shows which items were not removed
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '23

21 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31630 Bug ID: 31630 Summary: Batch item deletion no longer shows which items were not removed Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lnilsson(a)lewistonschools.net QA Contact: testopia(a)bugs.koha-community.org The only warning > given is an unclicked box and when deleting long lists it is hard to notice. > The follow up page use to have a notification stating some barcodes were not > deleted, please help. Thanks, LeeAnn Same problem I had with closed Bug 28353 -- You are receiving this mail because: You are the assignee for the bug. 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 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

[Bug 31424] New: Prompt to change patron messaging if email/SMS absent or changed
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31424 Bug ID: 31424 Summary: Prompt to change patron messaging if email/SMS absent or changed Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: arm(a)hanover.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Suggesting a prompt to staff or patron to update the messaging preferences if a new member is registered with no email/SMS number and the messaging prefs default to 'on', or if an existing user account is edited and the SMS or email contact info is changed. The lack of this reminder leaves many accounts with failed/unsent messages or pending 'print' messages. Also when an email address is added, notices are not sent because staff/patron may not turn on messaging preferences. There are a couple of old bugs about SMS / failed email. This might help with those. Related: 14964 23497 14590 14872 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19098] New: Additional logic for 260/RDA 264 fields
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19098 Bug ID: 19098 Summary: Additional logic for 260/RDA 264 fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If we have implemented 10306 and 19096, we can add some additional logic for multiple RDA 264 fields. Making e.g. the place and year picked more accurate than just glueing together or picking the first one. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3