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

[Bug 18528] New: Patron card creator: switch form fields for card height and card width
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '17

09 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18528 Bug ID: 18528 Summary: Patron card creator: switch form fields for card height and card width Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org The form to create or edit a card template has a confusing sequence of fields for page and card height and width: Page width - Page height - Card height - Card width Switch Card height and Card width to make it more intuitive. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 18449] New: Renewal limit button on renew.pl misleading
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '17

09 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18449 Bug ID: 18449 Summary: Renewal limit button on renew.pl misleading Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com If you hit the renewal limit on the renewal tab, the message gives you a message like: "Windows 8 / ( 50610018249545 ) has been renewed the maximum number of times by Johnny Test ( 12345678 )" And has a button that reads: "Ignore and continue" This button is misleading, as it may be interpreted as "ignore the limit and continue to renew the item". I think the button needs to be relabeled: "Continue without renewing" or "Ok" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 17998] New: Notice ISSUEQSLIP changes do not take effect consistently
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '17

09 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17998 Bug ID: 17998 Summary: Notice ISSUEQSLIP changes do not take effect consistently Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: arm(a)hanover.ca QA Contact: testopia(a)bugs.koha-community.org Changes made the the ISSUEQSLIP template text may eventually happen but not quickly. When the slip is printed, for some time older versions appear instead. This might not happen in later versions, tested in 3.22. We have not tested this in any other notice templates - only ISSUEQSLIP. Details: I make a change (in the 'email' tab), submit, and then open another tab to view or print the change in patron checkout, and my changes are not there. After making several changes to the layout in the 'email' tab, and then attempting to print the slip - newest changes are not there in the print for some time and the preceding versions continue to appear - not the same older version every time but alternating different versions. I did this all in both our 'sandbox' test system, and in our live system. Eventually got the layout I wanted in the test system and copied it to the live system, but still changes did not happen once submitted. I also created a Hanover Library rule (as opposed to the 'all libraries' one), and that seemed to make things worse. I have deleted it. I tried closing browser, using a different browser... and still I would get the version before last or the one before that instead of the most recently submitted. I tried submitting, closing the edit page, waiting, opening and submitting again three times. John at Equinox tested the issue and reported that: I was able to duplicate the issue you described, although this is the first I've heard of it. Some things I found while examining this: 1) the changes do register immediately in the database where the templates are stored. 2) In my testing, every other time I printed a quick slip it would reflect the change, until eventually it would show the change every time. 3) Different browsers made no difference. 4) Restarting Apache between changes appeared to make no difference either. 5) I was not able to duplicate it on 16.05 system It does seem like this is a bug. Katrin asked whether we are using Plack (yes) and caching (I don't know), and she asked that we submit a new bug for this. If anyone could test it on your local 16.05 setup and report whether this can be duplicated, or comment on whether it is related to Plack or caching setup that would be great. We will hope that it is gone in the next release but provide this information for anyone who might run into it or in case it indicates a larger underlying issue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19211] New: Error when trying to link an authority that has nothing entered under the 'Heading' tag (Tab 1)
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '17

08 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19211 Bug ID: 19211 Summary: Error when trying to link an authority that has nothing entered under the 'Heading' tag (Tab 1) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To reproduce 1) Go to Authorities -> Make a new authority. Save all the automatically filled answers by clicking the Save button, don't add anything under tab 1 2) Edit a record 3) Go to tab 1, go to the Main Entry for whichever authority type you created (i.e. personal name or corporate name) and click on the Tag Editor icon for that field 4) Search for your authority. You do not have to enter any search terms 5) Your authority should show up in the results. Click Choose 6) Notice software error. What suggestions do we have towards a fix for this? I think a good one would be to ensure that at least the 11_a field is filled (the authority name or jurisdiction name for entry element) by making it a required field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 18027] New: Added a new item which does not appear in catalogue search but appears in acquisition report.
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '17

07 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18027 Bug ID: 18027 Summary: Added a new item which does not appear in catalogue search but appears in acquisition report. Change sponsored?: --- Product: Koha Version: unspecified Hardware: PC OS: Windows Status: NEW Severity: critical Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: clouca(a)cpl.org.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Added the item three times (with different barcodes)and these show in report but cannot be found in catalogue search or by a patron on their platform. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 18839] New: suggestion.pl: 'unknown' in spelled 'unkown'
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '17

07 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18839 Bug ID: 18839 Summary: suggestion.pl: 'unknown' in spelled 'unkown' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: chris.kirby(a)ilsleypubliclibrary.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 64496 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=64496&action=ed… screenshot of the Suggestion Management On the Suggestion Management page, 'unknown' is spelled 'unkown'. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 19198] New: Renewal as issue causes too many error
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '17

06 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19198 Bug ID: 19198 Summary: Renewal as issue causes too many error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com To recreate: 1 - Set a rule to limit checkouts to a single issue, allowing renewal 2 - Issue an item to a patron 3 - Issue the same item 4 - In staff client you get a confirm to renew and a notice of Too Many checkouts 5 - VIA Sip - you get a renewal response, but in logs the renewal fails as a 'too many' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 19172] New: Undefined subroutine &C4::Members::Attributes:: SearchIdMatchingAttribute when searching patrons
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '17

06 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19172 Bug ID: 19172 Summary: Undefined subroutine &C4::Members::Attributes::SearchIdMatchingAttribute when searching patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When "ExtendedPatronAttributes" is enabled the following error occurs when searching patrons: "Undefined subroutine &C4::Members::Attributes::SearchIdMatchingAttribute called at ../C4/Utils/DataTables/Members.pm line 124" I assume this is because a missing "use C4/Utils/DataTables/Members.pm;". I have fixed and tested this in my local instance and will supply a patch shortly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 18897] New: Koha_Elasticsearch_Indexer.t doesn' t skip when ES module not installed
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '17

06 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18897 Bug ID: 18897 Summary: Koha_Elasticsearch_Indexer.t doesn't skip when ES module not installed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: ldjamison(a)marywood.edu QA Contact: testopia(a)bugs.koha-community.org Running "prove t/db_dependent/Koha_Elasticsearch_Indexer.t" fails instead of skipping if Catmandu::Importer::MARC is not installed. -- You are receiving this mail because: You are watching all bug changes.

1 41

[Bug 19004] New: Patrons.t fails when item-level_itypes is not set
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '17

06 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19004 Bug ID: 19004 Summary: Patrons.t fails when item-level_itypes is not set 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Problem is that TestBuilder generates two biblio records, one via item.biblionumber and one via items.biblioitemnumber => biblioitem.biblionumber. (Which actually is bad design; the biblionumber should not be in the items table.) The biblio generated via items.biblionumber has no biblioitem. AddReturn is called in Patrons.t. When item-level_itypes is false, it gets the itemtype from $biblio->biblioitem->itemtype. Which generates an error on the biblio since it has not biblioitem. -- You are receiving this mail because: You are watching all bug changes.

1 33