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

[Bug 28992] New: Resolve warning from undefined BIG_LOOP
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '21

16 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28992 Bug ID: 28992 Summary: Resolve warning from undefined BIG_LOOP Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Argument "" isn't numeric in numeric gt (>) at /usr/share/koha/koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/ addbiblio.tt line 896. Spotted this one while QAing bug 28608 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 28985] New: Negative rental amounts can be saved but not enforced
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '21

16 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28985 Bug ID: 28985 Summary: Negative rental amounts can be saved but not enforced Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: nick(a)bywatersolutions.com Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In item types, one can enter a negative amount for a rental charge. Koha allows this, saves the value, and shows it to you in admin. However, that value gets ignored at checkout. On the one hand, I can see weird use cases for giving patrons credits for checking out items. On the other hand, it would be a lot simpler to just not allow negative values to get set in the first place. Whichever way we go, we should pursue consistency and not let users enter values that don't get used. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 21093] New: Problem when using specify due date with fast add
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '21

16 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21093 Bug ID: 21093 Summary: Problem when using specify due date with fast add 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using the specify due date option and then created a fast add, the checkbox "Remember for sesssion" gets automatically checked and even after unchecking it and using "Clean" the date keeps reappearing until you switch to another patron account. To test: - Set the specify due date option to a date, don't check the checkbox - Enter an unknown barcode - Click on fast add - Add a record - Add an item (don't change the barcode!) - The item is checked out to the patron - Verify: The checkbox is "Remember for session" is checked now - Uncheck checkbox and clear the specified date - Check out another item - Verify that the date is back. So there is 2 problems here: - Checkbox should not check itself - it shoudl be able to clear the date -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 28914] New: Wording in authentication forms is confusing
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '21

16 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28914 Bug ID: 28914 Summary: Wording in authentication forms is confusing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org In most authentication forms we see : Fields "Login:" and "Password:" with a submit button "Log in". In some places submit button contains "Login", which is confusing for translation. Also in opac-user.pl semicolon are missing. I propose we always use : Fields "Login:", "Password:" with a submit button "Log in". It will generate less translation entries. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 28829] New: Useless single quote escaping in value_builder/unimarc_field_4XX.pl
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '21

16 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28829 Bug ID: 28829 Summary: Useless single quote escaping in value_builder/unimarc_field_4XX.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Since Bug 23777 added To.json, single quote escaping in value_builder/unimarc_field_4XX.pl is useless. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 28986] New: Parent itemtype not selected when editing circ rules
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '21

16 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28986 Bug ID: 28986 Summary: Parent itemtype not selected when editing circ rules Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1 - Go to Administration -> Item types 2 - Edit a type to have a parent of another type 3 - Go to Administration -> Circulation and fines rules 4 - Add a rule for the child type 5 - Add a rule for the parent type 6 - Click edit on child type, note dropdown in editor correctly selected 7 - Click edit on parent type - note dropdown menu refers to 'All' itemtypes -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 28845] New: OpacAddMastheadLibraryPulldown does not respect multibranchlimit in OPAC_SEARCH_LIMIT
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '21

16 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28845 Bug ID: 28845 Summary: OpacAddMastheadLibraryPulldown does not respect multibranchlimit in OPAC_SEARCH_LIMIT Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If the OPAC_LIMIT_OVERRIDE and OPAC_SEARCH_LIMIT environment override values are set in apache and OpacAddMastheadLibraryPulldown is enabled, multibranchlimit values are not preselected as they should be: To recreate 1 - Add to OPAC virtual host in apache conf: SetEnv OPAC_SEARCH_LIMIT branch:multibranch-1 SetEnv OPAC_LIMIT_OVERRIDE 1 RequestHeader add X-Koha-SetEnv "OPAC_SEARCH_LIMIT branch:multibranchlimit-1" RequestHeader add X-Koha-SetEnv "OPAC_LIMIT_OVERRIDE 1" 2 - Enable system preference OpacAddMastheadLibraryPulldown 3 - Create a library group enabled as OPAC search group (or make sure existing group 1 is an OPAC search group) 4 - Load the opac - dropdown does not pree-select the search group -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 12029] Patrons should be able to delete their patron messages
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '21

15 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12029 --- Comment #14 from George Williams (NEKLS) <george(a)nekls.org> --- (In reply to Christopher Brannon from comment #13) > Updated per Auto-Parallel's request: > > * A new field (ie patron_read) will be added to the messages table to record > that the patron has read the message. > > * If a message is set to display on the OPAC for the patron, the patron will > have a 'Dismiss' or 'Mark as read' button next to the message. > > * When the patron marks the message as read, the new field (ie patron_read) > will have the current date added to it, indicating the date that they read > the message. > > * If this new field "patron_read" has a value (a date), the dismissed > message will no longer show on the patron user interface (OPAC) only. In the > staff user interface, the dismissed message will still be visible and will > also display a label, such as 'Read xx-xx-xxxx', where x is the date in the > field. (Date will need to be formatted to admin date settings.) > > This functionality will not delete the message. It will allow staff to see > that the patron has read the message, and staff will still have the ability > to delete the message at their discretion. This is an excellent enhancement to the development. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12029] Patrons should be able to delete their patron messages
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '21

15 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12029 --- Comment #13 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- Updated per Auto-Parallel's request: * A new field (ie patron_read) will be added to the messages table to record that the patron has read the message. * If a message is set to display on the OPAC for the patron, the patron will have a 'Dismiss' or 'Mark as read' button next to the message. * When the patron marks the message as read, the new field (ie patron_read) will have the current date added to it, indicating the date that they read the message. * If this new field "patron_read" has a value (a date), the dismissed message will no longer show on the patron user interface (OPAC) only. In the staff user interface, the dismissed message will still be visible and will also display a label, such as 'Read xx-xx-xxxx', where x is the date in the field. (Date will need to be formatted to admin date settings.) This functionality will not delete the message. It will allow staff to see that the patron has read the message, and staff will still have the ability to delete the message at their discretion. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13015] AdvancedSearchLanguages doesn't support all language codes
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '21

15 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13015 Fridolin Somers <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=29256 -- You are receiving this mail because: You are watching all bug changes.

1 0