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

[Bug 32031] New: Sidebars and Breadcrumbs
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32031 Bug ID: 32031 Summary: Sidebars and Breadcrumbs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With the staff client refresh I've had a nagging feeling about the breadcrumbs appearing above the sidebar navs.. it feels a bit messy but I hadn't come up with a better solution. I wonder about shifting the sidebar so it goes all the way to just under the top header and shift the breadcrumbs to the right... a bit like gitlab? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 34294] New: Bottom tabs inconsistent with moremember.tt on circulation.tt
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34294 Bug ID: 34294 Summary: Bottom tabs inconsistent with moremember.tt on circulation.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 33528 We streamlined and improved the bottom content block of the member details and circulation pages in bug 33528. But as we don't pass fines as a template parameter in circulation.pl we don't get the benefit of displaying that tab in circulation.tt yet, thus we're still inconsistent with moremember.tt displays. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33528 [Bug 33528] Use template wrapper for tabs: Patron details and circulation -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 34839] New: Shouldn't TinyMCE initialise with the Koha interface stylesheet?
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34839 Bug ID: 34839 Summary: Shouldn't TinyMCE initialise with the Koha interface stylesheet? 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org When we initialise TinyMCE in the HTML Customisation page we pass `content_css : "[% interface | html %]/[% theme | html %]/css/tinymce.css"`. Shouldn't we be passing the stylesheet/stylesheets of the interface we're editing rather than a specific tinymce sheet? That would more accurately represent how your content block is actually going to appear to the end user than it does now.. for example taking account of page-section classes if you add such a div into your markup? Or am I mis-understanding what the content_css option does? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 35459] New: Don't always claim to be 'en' in html notices
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35459 Bug ID: 35459 Summary: Don't always claim to be 'en' in html notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 35285 As highlighted in bug 30287 comment 44 we're continuing to hard code that the html content is 'en' here.. I'm sure we could do better and grab the lang code from GetPreparred letter and pass it along. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35285 [Bug 35285] Centralise notice content wrapping for html output -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 35829] New: Codename for 24.05
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35829 Bug ID: 35829 Summary: Codename for 24.05 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org In bug 35504 I proposed that we add a codename to this cycle's release to celebrate our first female release manager coming into role. At our general meeting on 17 January we opted to open a bug to discus proposals.. I think we all think it's a good idea to mark this cycle :) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 36206] New: Administrative plugins
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36206 Bug ID: 36206 Summary: Administrative plugins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be beneficial to have an 'administrative' plugin type akin to 'tools' and 'reports' plugins. This would allow for adding an administrative plugin to the administration pages as opposed to having to expose it under tools. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 49

[Bug 36051] New: Add option to specify SMS::Send driver parameters in a system preference instead of a file
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36051 Bug ID: 36051 Summary: Add option to specify SMS::Send driver parameters in a system preference instead of a file Change sponsored?: --- Product: Koha Version: master 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If an SMS::Send driver ( such as Twilio ) requires additional parameters, those parameters have to be placed in a yaml file named after the SMS::Send driver, and the path to that file specified in the Koha conf file. It would be good if we had the option to specify those parameters in a YAML system preference instead. This would be less complicated and avoid requiring an administrator to update that data from the backend. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 36593] New: Add support for the `time` column type on TestBuilder
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36593 Bug ID: 36593 Summary: Add support for the `time` column type on TestBuilder Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 6796 introduced the first use of this DB column type, and TestBuilder is just not ready for it: https://jenkins.koha-community.org/job/Koha_Master_D10/lastCompletedBuild/c… we should add support. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 27825] New: Add preference for choosing the default format for patron barcodes
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27825 Bug ID: 27825 Summary: Add preference for choosing the default format for patron barcodes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: barbara.johnson(a)bedfordtx.gov, gmcharlt(a)gmail.com, lisetteslatah(a)gmail.com, magnus(a)libriotech.no, martin.renvoize(a)ptfs-europe.com, testopia(a)bugs.koha-community.org Blocks: 26777 Whether we add scannable barcodes to the OPAC via a JS library (as suggested in Bug 26777) or via an API (Bug 26692), it would be good to provide the library with a way to define the format for the barcode output. This could also be used as the default in the patron card creator. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26777 [Bug 26777] Give the user the option to display their patron card barcode from the OPAC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 34122] New: Updating Shelvingloc changes location of all related records
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34122 Bug ID: 34122 Summary: Updating Shelvingloc changes location of all related records Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Partners have reported that updating the shelving location on one item updates all of the items in the record regardless of their branch location. For example, Branch A has Item A located in the Genealogy department, and Branch B has it in their Reference section. Changing the location in Branch A to Genealogy will also change the shelving location for Branch B to Genealogy even if Branch B doesn't have a Genealogy shelving location. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11