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

[Bug 9596] Allow longoverdue.pl to be configured by library
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '24

13 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 Michael Hafen <michael.hafen(a)washk12.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael.hafen(a)washk12.org --- Comment #5 from Michael Hafen <michael.hafen(a)washk12.org> --- Created attachment 162070 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=162070&action=e… Add branch and skip-branch options to cronjobs/longoverdue.pl Test plan: 1. apply patch 2. identify two books at different branches the same number of days overdue. 3. run the longoverdue.pl script specifying one of the branches in the --branch command line parameter. 4. observe that the book at the specified branch has been or would be affected by the script while the other book is not. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 15565] Place multiple item-level holds at once for the same record
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '24

13 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15565 --- Comment #282 from David Cook <dcook(a)prosentient.com.au> --- (In reply to David Cook from comment #281) > I've rewritten the staff-interface code to be much more minimal yet still > effective. Its error handling is patterned off the OPAC, which makes it > consistent across the interfaces as well. The difference with the past patches is that we don't get the warnings/restrictions in the UI *before* placing the hold. We only get the warnings about failures *after* trying to place the hold. I think warning *before* the hold is actually a separate feature. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15565] Place multiple item-level holds at once for the same record
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '24

13 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15565 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=35754 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15565] Place multiple item-level holds at once for the same record
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '24

13 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15565 --- Comment #281 from David Cook <dcook(a)prosentient.com.au> --- I've rewritten the staff-interface code to be much more minimal yet still effective. Its error handling is patterned off the OPAC, which makes it consistent across the interfaces as well. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15565] Place multiple item-level holds at once for the same record
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '24

13 Feb '24

1 0

[Bug 34890] New: Cannot delete plugin with error
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '24

12 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34890 Bug ID: 34890 Summary: Cannot delete plugin with error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org We have a plugin on our system that is showing the message "Error found whilst attempting to load plugin." The styling applied to the plugins list for the error removes the Actions button so the faulty plugin cannot be deleted. This is not ideal. I would like to delete the plugin. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 6796] Overnight checkouts taking into account opening and closing hours
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '24

12 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6796 --- Comment #105 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- Coming back to comment #88 > and it would be great to have a fallback to default for opening hours so you could set at the global level and override at the branch level.. like many of our other options of this style. I think this is the resolution we need for tests.. if we allow library_id to be nullable in library_hours and add a row for each day with default opening hours to fall back to, then handling this in code should mean we can get tests passing more easily. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6796] Overnight checkouts taking into account opening and closing hours
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '24

12 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6796 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6796] Overnight checkouts taking into account opening and closing hours
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '24

12 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6796 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6796] Overnight checkouts taking into account opening and closing hours
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '24

12 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6796 --- Comment #104 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- I've fixed a whole bunch of little issues to get this vaguely working now, but as I run the test suit against it I see there are more issues hidden. I've fixed some array indexing issues where your code worked in opposition to how Koha's calendar indexes days of the week already.. but Circulation tests still fail. This is because, as far as I can tell, your code expects every branch to always have opening hours set.. i.e. there MUST be rows for days 0 to 6 for every branch, even if those rows have hours of null-null. I've fixed the database update to handle this, however the failing tests expose the lack of treatment for this in t/lib/TestBuilder. We'll need that resolving before this can work it's way through QA. I'm not sure whether we should be adding this handling to TestBuilder (i.e. to always ensure there's 7 rows per branch for any time a branch is added in testing), or whether really we should not be making this assumption in the first place and instead we should be allowing for missing rows in the library_hours table. -- You are receiving this mail because: You are watching all bug changes.

1 0