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

[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 37284] New: Place reserve button doesn't respect hold rules when in lists on the OPAC
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37284 Bug ID: 37284 Summary: Place reserve button doesn't respect hold rules when in lists on the OPAC Change sponsored?: --- Product: Koha Version: unspecified 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 reserve button is hidden appropriately based on circulation rules on the search results and detail view pages.. but when the same items appear in lists the button isn't hidden. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 14007] Item types for items hidden by OpacHiddenItems turn up in facet results
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14007 --- Comment #22 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Nick Clemens (kidclamp) from comment #21) > This works in the limited case of hiding itemtypes that are marked "Hide in > OPAC" - for libraries using OpacHiddenItems to hide an itemtype this won't > have any effect. I like how simple this is, however, I feel it is too narrow > and following this path could end up with more post processing to handle all > of the cases. > > Code wise, I submitted a patch to reduce the lookups. > > Moving to in discussion for now, I could be convinced this is better than > not doing anything, but I think it's too late in this cycle for this one Yeah I have similar thoughts. Patch doesn't fix the OpacHiddenItems issue but maybe better than nothing. OpacHiddenItems is almost always one of those "too hard basket" things unfortunately... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37462] New: Serials item type drop-down not in alphabetical order
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37462 Bug ID: 37462 Summary: Serials item type drop-down not in alphabetical order Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: chanel.wheeler(a)yavapaiaz.gov QA Contact: testopia(a)bugs.koha-community.org In serials, when you create or edit a serial, the Item Type drop-down menu is sorted alphabetically by code rather than by the displaying description. We have lots of item types and it makes it hard to find the right one. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[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 37440] New: Add option to never default to Cataloging Search
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '24

24 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37440 Bug ID: 37440 Summary: Add option to never default to Cataloging Search Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 Staff find the Cataloging Search interface unhelpful. It offers relatively little functionality that is not available in the default search interface and is broadly less familiar and therefore less desirable. While one is in the Cataloging module, the header defaults to Cataloging Search but also offers Search the Catalog. We'd love to have the option to make Search the Catalog the default with Cataloging Search available as an option should we ever want it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[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