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

[Bug 12133] Guarantor requirements when registering a patron
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '23

15 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12133 --- Comment #66 from Jonathan Druart <jonathan.druart+koha(a)gmail.com> --- The test is still failing koha_1 | # Failed test 'No tests run for subtest "Test where parameter for SendQueuedMessages"' koha_1 | # at t/db_dependent/Letters.t line 1274. koha_1 | [Child patron needs a guarantor]# Looks like your test exited with 11 just after 97. koha_1 | [19:28:21] t/db_dependent/Letters.t .................................................... koha_1 | Dubious, test returned 11 (wstat 2816, 0xb00) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12133] Guarantor requirements when registering a patron
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '23

15 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12133 --- Comment #65 from Jonathan Druart <jonathan.druart+koha(a)gmail.com> --- I don't understand why this has been designed in a so limited way. Why only children? This should have been a patron's category flag, or the syspref should accept a list of patron's categories. At some point only children were allowed to have guarantor, but since bug 12446 this limitation should not persist. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35024] New: PO files wrap differently depending on versions
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '23

15 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35024 Bug ID: 35024 Summary: PO files wrap differently depending on versions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Looks like (thanks Julian!) it's coming from libunistring, between 0.9.10 and 1.0 I am seeing a change in how the strings in the PO files are wrapped. Debian 11 (using libunistring 0.9): "%s %sPrintemps%s %s %sÉté%s %s %sAutomne%s %s %sHiver%s %s %sPrtps%s %s %sÉté" "%s %s %sAut%s %s %sHiv%s %s %s %s" Debian 12, Ubuntu 22.04(using libunistring 1.0) "%s %sPrintemps%s %s %sÉté%s %s %sAutomne%s %s %sHiver%s %s %sPrtps%s %s " "%sÉté%s %s %sAut%s %s %sHiv%s %s %s %s" It *could* come from this changes: https://git.savannah.gnu.org/gitweb/?p=libunistring.git;a=blob;f=NEWS;h=5a4… * The functions u*_possible_linebreaks and u*_width_linebreaks now make it easier to work with strings that contain CR-LF sequences: In this case, in the returned array, it will return UC_BREAK_CR_BEFORE_LF followed by UC_BREAK_MANDATORY (instead of twice UC_BREAK_MANDATORY). The command used is: % msgmerge --backup=off --quiet -F --update misc/translator/po/fr-FR-staff-prog.po misc/translator/Koha-staff-prog.pot No matter the value of --width. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 35333] New: Koha::Patron->add_guarantor not checking anything
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '23

15 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35333 Bug ID: 35333 Summary: Koha::Patron->add_guarantor not checking anything Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal 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 This method should receive a `guarantor` parameter, and check if it is a valid guarantor, the same way we later check when saving patrons that the guaratonrs are valid (which I think was put in the wrong place). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 35283] New: XSLT 583 Action note is missing subfield h in staff interface
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35283 Bug ID: 35283 Summary: XSLT 583 Action note is missing subfield h in staff interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org In the staff interface, the 583 action note should show subfield "h". -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 15279] Deprecate bespoke syntax for Slips and Notices
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15279 --- Comment #5 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I believe this is not only a technical issue but also an issue of better documentation. We need to enable people to achieve at least the same results as with 'hungry alligators' in an easy to understand way. Then we can build on it for more complex things. And we will need a deprecation period. But I think we should do it :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15279] Deprecate bespoke syntax for Slips and Notices
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15279 --- Comment #4 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- This has been stuck for a very long time with minor flurries of activity over the years. I'd love to see a concerted effort some time. I've added it to the roadmap, but we need a commitment from multiple parties to actually work on it, test etc. we -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15277] Add Template Toolkit syntax for slips and notices to editor
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

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

1 0

[Bug 15279] Deprecate bespoke syntax for Slips and Notices
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15279 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |31510 CC| |martin.renvoize@ptfs-europe | |.com Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31510 [Bug 31510] The notice template tag helper still uses <<>> sytnax.. we should move to TT instead -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35337] New: Patron flags should be transitioned over to restrictions
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35337 Bug ID: 35337 Summary: Patron flags should be transitioned over to restrictions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The existence of patron flags seem arbitrary, like leftovers from before restrictions. It seems like you could accomplish the same thing with just restrictions. I would suggest removal of the flags, and incorporate a Authorized Value that could be customized with preset restrictions, including the former flags. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0