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

[Bug 19237] New: PERSO_NAME authority file ignores first indicator value of new headings saved
by bugzilla-daemon＠bugs.koha-community.org 03 May '21

03 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19237 Bug ID: 19237 Summary: PERSO_NAME authority file ignores first indicator value of new headings saved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: imingchan(a)yahoo.com.au QA Contact: testopia(a)bugs.koha-community.org When saving new headings to PERSO_NAME authority, first indicator value is not saved. So when you selected such authority heading (as part the cataloguing), you have to manually re-enter the indicator value concerned. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 25969] New: Checking in a found hold at a different branch then confirming the hold causes internal server error
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '21

30 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25969 Bug ID: 25969 Summary: Checking in a found hold at a different branch then confirming the hold causes internal server error 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a record level hold is filled and waiting at Library A, and the item is checked in at Library B, AddReturn() calls RevertWaitingStatus(), which unsets found, and itemnumber ( if the hold was record level ). AddReturn() then retuns the message 'ResFound', which triggers the hold fulfillment dialog, which passes the reserve_id back to circulation.pl. Then, circulation.pl attempts to get the biblio via the itemnumber, which the hold doesn't have, causing an ISE. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 17202] New: Deleting a rotating collection with items should either be prohibited or items should be removed
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '21

30 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17202 Bug ID: 17202 Summary: Deleting a rotating collection with items should either be prohibited or items should be removed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: Create a rotating collection Add an item Delete the rotating collection View the db (SELECT * FROM collections_tracking;) The item is still in the collection -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 16787] New: 'Too many holds' message appears inappropriately and is missing data
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '21

29 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16787 Bug ID: 16787 Summary: 'Too many holds' message appears inappropriately and is missing data 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com bug 11250 changed the holds message to be and if,elsif loop, falling through to catch the first appropriate message bug 13116 changed the reporting from CanItemBeReserved causing tooManyHolds to trigger when no holds are allowed A side effect is that 'maxreserves' is only passed to the template when there are too many reserves, but the too many reserves message is called when no holds are available To recreate: Set maxreserves to 50 Set some item type to allow 0 holds Attempt to place a hold on a record with that itemtype Message will be "Too many holds: [Firstname Surname] can only place a maximum of total holds." Message should be "[Firstname Surname] cannot place any holds on these items." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 100

[Bug 24594] New: Rewrite MARC21 mandatory data to YAML
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '21

29 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24594 Bug ID: 24594 Summary: Rewrite MARC21 mandatory data to YAML 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: bgkriegel(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr A complete rewrite of MARC21 mandatory instalation files from SQL to YAML is presented, one patch for each file, the result could be squashed. The goal is to allow the translation of the installation files In this case the patches are too big, they will be uploaded compressed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 21944] New: Fix waiting holds at wrong location bug
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '21

29 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21944 Bug ID: 21944 Summary: Fix waiting holds at wrong location bug Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests 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 To Test: 1) Place a hold on an item. 2) Check in the item to trigger the hold. Item is now listed as waiting. 3) Set branch to a different library. 4) Check in the item to trigger the hold. Notice that nothing but a local use is recorded. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 69

[Bug 17717] New: Can't locate Authen/CAS/Client/Response/Failure.pm
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '21

29 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17717 Bug ID: 17717 Summary: Can't locate Authen/CAS/Client/Response/Failure.pm Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: mjnkml(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz On Ubuntu, output of /usr/share/koha/bin/cronjobs/process_message_queue.pl in an email from cron: ourlib: Can't locate Authen/CAS/Client/Response/Failure.pm: ./Authen/CAS/Client/Response/Failure.pm: Permission denied at /usr/share/perl/5.22/base.pm line 97. ourlib: ...propagated at /usr/share/perl/5.22/base.pm line 106. ourlib: BEGIN failed--compilation aborted at /usr/share/perl5/Authen/CAS/Client/Response.pm line 68. ourlib: Compilation failed in require at /usr/share/perl5/Authen/CAS/Client.pm line 8. . . . process_message_queue.pl is currently invoked from /etc/cron.d/koha-common I don't find any Failure.pm on the system. This only started happening after a recent update which resulted in Bug 17234. Not sure if issues with that may have also affected this. Have done a full reinstall (without Purge) of the packages. -- You are receiving this mail because: You are watching all bug changes.

1 91

[Bug 24378] New: Change wording on AUTO_RENEWALS notice template
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '21

28 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24378 Bug ID: 24378 Summary: Change wording on AUTO_RENEWALS notice template Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On the template of AUTO-RENEWALS the wording is grammatically incorrect: Currently this line states: [% IF checkout.auto_renew_error == 'too_many' %] You have reach the maximum of checkouts possible. This should say [% IF checkout.auto_renew_error == 'too_many' %] You have reached the maximum of checkouts possible. Note: It should be eb installed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 20757] New: Capture a screenshot on selenium errors
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '21

28 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20757 Bug ID: 20757 Summary: Capture a screenshot on selenium errors 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 It can be a real pain to debug selenium errors, especially when it is not reproducible locally. It would be great to capture a screenshot when an element is not found on the page for instance. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 25811] New: authentication.t is failing randomly
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '21

28 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25811 Bug ID: 25811 Summary: authentication.t is failing randomly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org Two recent failures in the CI https://jenkins.koha-community.org/view/19.05/job/Koha_19.05_D8/244/console… https://jenkins.koha-community.org/view/19.05/job/Koha_19.05_U18/239/consol… And I could reproduce locally in Debian 10 on master. -- You are receiving this mail because: You are watching all bug changes.

1 37