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

[Bug 24310] New: Use Text::Lorem instead of String::Random in Test::Builder
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '23

27 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24310 Bug ID: 24310 Summary: Use Text::Lorem instead of String::Random in Test::Builder Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org That would help to get something more readable. Currently we generate a string of one word that is the size of the column. It produces a lot of overflow when displayed on the screen. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 31471] New: Duplicate check in cataloguing doesn't work with Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '23

27 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31471 Bug ID: 31471 Summary: Duplicate check in cataloguing doesn't work with Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: michaela.sieber(a)kit.edu The duplicate check in cataloguing doesn't work with Elasticsearch. To test: * With Zebra: Download a record via Z39.50 and save. * Make sure the record is found in the catalog. * Download the same record via Z39.50 again and try to save - duplicate confirm message pops up. * Switch to Zebra * Again, make sure that the record can be found in the catalog. * Download the record again via Z39.50 and try to save - no duplicate warning, the record is saved. If an example is needed we could provide a taget and sample. Note: As I understand FindDuplicate it checks for ISSN and after that a combination of title and author. Is there a thing we might be missing here? Tested in different installations with master and 21.11. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 31411] New: [Omnibus] Set focus to first input field of an add/entry form
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '23

27 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31411 Bug ID: 31411 Summary: [Omnibus] Set focus to first input field of an add/entry form Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org This serves as an omnibus for several other smaller bugs dealing with add/entry forms for configuration and other settings. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 31413] New: Set focus for cursor to Selector when adding a new audio alert
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '23

27 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31413 Bug ID: 31413 Summary: Set focus for cursor to Selector when adding a new audio alert Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Blocks: 31411 When adding a new audio alert from the administration module, the focus should be on the first input field of the entry form: Selector Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31411 [Bug 31411] [Omnibus] Set focus to first input field of an add/entry form -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 31209] New: Add span with class info to enumchron data in circulation.tt, for better styling
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '23

27 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31209 Bug ID: 31209 Summary: Add span with class info to enumchron data in circulation.tt, for better styling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the table issues-table of circulation.tt, enumchron data in added to the title between parentheses. There is no way to style this information differently from the title. We could add a span with a class to isolate this information. Alternatively, enumchron data could be moved in a new column -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 22693] New: ILL "Price paid" column does not appear in column configuration
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '23

27 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22693 Bug ID: 22693 Summary: ILL "Price paid" column does not appear in column configuration 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: --- "Price paid" was added in bug 22121, it seems I forgot to add it to the column configuration list. Doh. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 30993] New: Translation: Unbreak sentence in upload.tt
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '23

27 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30993 Bug ID: 30993 Summary: Translation: Unbreak sentence in upload.tt Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr In translation, the sentence below is broken into 2 parts by the link. This makes it hard to translate as you can't move around words easily before and after the link for good grammar and are missing context: <span>Add values to the <a href="/cgi-bin/koha/admin/authorised_values.pl?searchfield=UPLOAD">UPLOAD authorized value category</a> otherwise all uploads will be marked as temporary.</span> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 31957] New: Translation : Ability to change the sentence structure in branches.tt
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '23

27 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31957 Bug ID: 31957 Summary: Translation : Ability to change the sentence structure in branches.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr I'm having trouble translating the sentences in branches.tt where it says the the default is a system preference. For example, line ~210 [% IF ( CAN_user_parameters_manage_sysprefs ) %] Default: <a target="_blank" href="/cgi-bin/koha/admin/preferences.pl?tab=&op=search&searchfield=ILLDefaultStaffEmail">ILLDefaultStaffEmail</a> system preference [% ELSE %] Default: ILLDefaultStaffEmail system preference [% END %] It comes out like this in translation msgid "%s Default: " msgid "ILLDefaultStaffEmail" msgid "" "system preference %s Default: ILLDefaultStaffEmail system preference %s " However, in French, the order of the words should be inverted, e.g. ILLDefaultStaffEmail system preference becomes system preference ILLDefaultStaffEmail. Can we modify the tt so that we get the whole sentence, or a %s that we can play with to change the order of the words? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 31064] New: Local login is difficult to style using CSS
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '23

26 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31064 Bug ID: 31064 Summary: Local login is difficult to style using CSS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org There are times where it would be nice to style the local login inputs. For my purposes, that's usually to hide them in favour of button/link provided by OpacUserJS, but I'm sure people could use it for other things too. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 29792] New: Transfers created from Wrong Transfer checkin are not sent if modal is dismissed
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '23

26 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29792 Bug ID: 29792 Summary: Transfers created from Wrong Transfer checkin are not sent if modal is dismissed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 23092 To recreate: 1 - have an item in transit from Branch A to Branch B 2 - check the item in at Branch A 3 - get a Wrong Transfer message, click Print Slip or OK 4 - query the branchtransfers table, see that your original transfer was cancelled and a new one was made, confirm that new transfer has a datesent value 5 - repeat steps 1-3, but instead of clicking one of the buttons click outside of the modal to make it go away 6 - query the branchtransfers table, see that your original transfer was cancelled and a new one was made, confirm that new transfer DOES NOT HAVE a datesent value So that transfer is just hanging out as requested and the item needs to get checked in again to get it sent. This is a change in behavior, as before bug 23092 the second transfer would be sent immediately even if one clicked away from the modal without selecting anything. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23092 [Bug 23092] Add 'daterequested' to the transfers table -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35