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

[Bug 32768] New: Autocomplete suggestions container should always be on top of other UI elements
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32768 Bug ID: 32768 Summary: Autocomplete suggestions container should always be on top of other UI elements Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 30719 introduces a modal with a patron autocomplete input in it. Because the .modal uses a z-index: 1050 and the autocomplete container with .ui-autocomplete .ui-front CSS classes is picking up z-index: 100 from .ui-front, the autocomplete suggestions appear behind the modal dialog and can't be interacted with. This CSS entry from addbiblio.css should be moved into global-staff.scss for wider use: .ui-autocomplete { z-index: 2000; } -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 31705] New: Option for ILL "Manage Request" button to appear on Left of the screen to improve accessibility
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31705 Bug ID: 31705 Summary: Option for ILL "Manage Request" button to appear on Left of the screen to improve accessibility Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: jeremy.evans(a)ukhsa.gov.uk To improve accessibility and reduce excessive scrolling we would like an option for the "Manage Request" button on the list of ILL requests to appear on the left of the screen. It currently displays on the far right of the screen and normally requires scrolling beyond the columns displaying in the table for each request to be processed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 22714] New: ILL table population call might benefit from being inside the datatable
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22714 Bug ID: 22714 Summary: ILL table population call might benefit from being inside the datatable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- As pointed out by Owen (http://irc.koha-community.org/koha/2019-04-16#i_2134071) the ILL table doesn't display any "loading" message while the API call is in progress. It would be a better experience for the user if it did. We should investigate populating the table from within the datatable object, we will then get the benefit of then in built loading message. If not, we could always add a message manually. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 32563] New: Reservedate becomes expirationdate in some cases
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32563 Bug ID: 32563 Summary: Reservedate becomes expirationdate in some cases Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: slavashishkin(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Database fields DATE/DATETIME/TIMESTAMP in DBIX-Class are automatically available as DateTime objects that we can perform operations on (for example add an interval). But there is a feature: addition or subtraction operations (->add in this case) change the main object in-place and return the new value as the result of the expression. Because of this feature, due to the fact that the address to ->reserve date was passed to the ->add function, ->reservedate itself was changed, and then the result was assigned to ->expirationdate. This implicit feature resulted in an error when both dates after the given operation were the same in the future. Solution: To not change the original DateTime object, it must be cloned: https://metacpan.org/pod/DateTime#$dt-%3Eclone , accordingly, the changes will be made in a temporary copy, and a new value will be assigned to expirationdate, and the original reservedate will not change. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 32567] New: Update plugin unimarc_field_110.pl 'Script of title' and 'Translitteration code'
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32567 Bug ID: 32567 Summary: Update plugin unimarc_field_110.pl 'Script of title' and 'Translitteration code' 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: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Update value builder for unimarc_field_110 with some values -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 33683] New: Hello, I am writing this report in order to know what are the hardware required for install koha 22.11 on a module-server.
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33683 Bug ID: 33683 Summary: Hello, I am writing this report in order to know what are the hardware required for install koha 22.11 on a module-server. Change sponsored?: --- Product: Koha Version: 22.11 Hardware: PC OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: rulyvazquez23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, my name is Raúl Francisco, and I'm studying mechatronics engineering. I'm doing this post because of a project that tries to implement the KOHA software in a physical library, more specifically 22.11 version. I would like to know what would be the hardware requirements to install this version of Koha. In this case, we will use a module-server. Thank you in advance. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 31650] New: We should publish our coding guidelines more openly
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31650 Bug ID: 31650 Summary: We should publish our coding guidelines more openly Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com Our coding guidelines are currently hidden deep in th wiki.. to encourage more reference to them, we could publish them more openly as their own mini-site linked directly from the website.. more akin to our manual and API docs sites. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 33682] New: Logs don't give enough information
by bugzilla-daemon＠bugs.koha-community.org 04 May '23

04 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33682 Bug ID: 33682 Summary: Logs don't give enough information 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I'm not sure what component this should be part of. Looking at the cataloging logs, it records when a cataloging record is changed, and what the record looks like at that moment. But it does not indicate what part was changed, and what it was before the change. This would be VERY HELPFUL. If all I want to know is when the record took on its current form, then the log is useful. If you are not purging old log records on a regular basis, then there is a chance you might have an older record showing the last change. Even if that were the case, you would have to compare it bit by bit to find out what changed. Please consider noting what parts are changed, and their previous state in the logs. This would be incredibly helpful. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15428] Different timeout preference for OPAC and staff interface
by bugzilla-daemon＠bugs.koha-community.org 04 May '23

04 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15428 --- Comment #22 from ddemick(a)oslri.net --- (In reply to Katrin Fischer from comment #21) > I think the patron category is not ideal, but maybe the web based self check > could get its own sessions as well, while we are at it? I would support that too. Basically a way to force an auto-logoff for staff but still be able to keep our self-check machines logged in for the full day. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15428] Different timeout preference for OPAC and staff interface
by bugzilla-daemon＠bugs.koha-community.org 04 May '23

04 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15428 --- Comment #21 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think the patron category is not ideal, but maybe the web based self check could get its own sessions as well, while we are at it? -- You are receiving this mail because: You are watching all bug changes.

1 0