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

[Bug 16463] New: OPAC discharge page should warn the user about checkouts before they request
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16463 Bug ID: 16463 Summary: OPAC discharge page should warn the user about checkouts before they request Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/opac-discharge.pl OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org If you have checkouts you cannot request a discharge. The "ask for a discharge" page on the OPAC should warn the user about their checkouts instead of waiting to do so until after they have clicked on the "ask for a discharge" link. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 16204] New: Show friendly error message when trying to edit record which no longer exists
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16204 Bug ID: 16204 Summary: Show friendly error message when trying to edit record which no longer exists Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=X OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you pass a non-existent biblionumber to addbiblio.pl you will get an error message: Can't call method "title" on an undefined value at /cataloguing/addbiblio.pl line 814. This might happen if you click an edit link from search results which are out of date or if you have saved the results of a report. Koha should show a friendlier error message. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 18801] New: Merging authorities has an invalid 'Default' type in the merge framework selector
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18801 Bug ID: 18801 Summary: Merging authorities has an invalid 'Default' type in the merge framework selector Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When merging two authorities and deciding the framework to sue the default is a 'Default' with value 'Default' The issue is that the Default framework actually has code '' - this is picked up in the generated list so we can just remove the line (if this is unclear the patch should be clear) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 17278] New: Limit to available items returns 0 results
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17278 Bug ID: 17278 Summary: Limit to available items returns 0 results Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: Linux Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: erjon.sulaj(a)uart.edu.al QA Contact: testopia(a)bugs.koha-community.org Created attachment 55337 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=55337&action=ed… limit search results to available opac Hi, Another problem I encountered with koha 16.05 is the function "limit to currently available" when trying to narrow down a search. If selected, the search will return 0 results, although there are many titles available. Kindly see attached image. Best regards, Erjon -- You are receiving this mail because: You are watching all bug changes.

1 41

[Bug 18351] New: No warning when deleting budgets that have funds attached
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18351 Bug ID: 18351 Summary: No warning when deleting budgets that have funds attached Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org At the moment, you can delete any budget, regardless of whether there are funds attached. This is bad because it means the funds still exist but the user can't see them and the user can't create a new budget with the same budget ID -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 17834] New: Change library news text for single-branch libraries
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17834 Bug ID: 17834 Summary: Change library news text for single-branch libraries 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org If a library has only 1 branch the 'system-wide' in the text for the news RSS feed can be a bit confusing. Current text: RSS feed for system-wide library news. It would be nice to catch the case of single-branch and show a different text then. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 18692] New: When SMS is enabled the OPAC messaging table is misaligned
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18692 Bug ID: 18692 Summary: When SMS is enabled the OPAC messaging table is misaligned Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 6726 had corrected the fact that when SMS is enabled the messaging table is missing a column. Bug 6458 has broken this. I think the SMS column is missing an else case with cell containing only "-" like other columns. -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 18636] New: Can not save new patron on fresh install ( Conflict between autoMemberNum and BorrowerMandatoryField)
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18636 Bug ID: 18636 Summary: Can not save new patron on fresh install (Conflict between autoMemberNum and BorrowerMandatoryField) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Tested on a fresh install on current master To reproduce: - Go to Koha > Patrons > Add patron (full form) - Verify that label for card number reads: "Card number(leave blank for auto calc during registration):" - Do not enter anything in field card number - Enter surname, try to save - Form does not save because field card number is required Reason: - autoMemberNum is on by default (sysprefs.sql line 65) - BorrowerMandatoryField contains surname|cardnumber by default (sysprefs.sql line 86) - Full form does not save because card number is mandatory and empty Note: With quick add form and settings above, cardnumber is not displayed, form saves properly. What to do? - Better explanation for autoMemberNum and BorrowerMandatoryField - Set defaults for autoMemberNum and BorrowerMandatoryField in a way that they do not conflict? - Ignore cardnumber being a mandatory field if autoMemberNum is on? - Ask for settings in onboarding tool? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 16485] New: collection column in Item search is always empty
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16485 Bug ID: 16485 Summary: collection column in Item search is always empty Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org When in "Item Search", it seems that regardless of the items returned in the result set, the collection name is always empty. This should be fixed and have the collection name displayed as expected. (The issue appears in 3.20, but seems to exists in 3.22 as well...) -- You are receiving this mail because: You are watching all bug changes.

1 39

[Bug 18621] New: After duplicate message system picks category expiry date rather than manual defined
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18621 Bug ID: 18621 Summary: After duplicate message system picks category expiry date rather than manual defined Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: mishravk79(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com After duplicate message system picks category expiry date rather than manual defined, the test is as follows: 1. Try to enter a new member 2. Give member Expiry date which is more than defined in concern category 3. If Koha found similar member than pop up a message 4. Select not a duplicate member (New member option) 5. Koha saved the record but the expiry date will pick from category rather than you assigned the member. 6. If the member is new and no message is populated than it will save expiry date as you defined. Koha version 16.11.07 on debian Jessie installed by package. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17