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

[Bug 12298] New: The "feed" MTT does not seem to be used
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12298 Bug ID: 12298 Summary: The "feed" MTT does not seem to be used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 12865] New: Text in payment box
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12865 Bug ID: 12865 Summary: Text in payment box Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: jesse(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We have come across a possible bug or issue with the note boxes in the pay fines tab on the staff clients. Here is a a few test cases to understand the issue. This test case works for single line payments. 1. Clear all check boxes and select the check box of the fine you would like to pay. Add a note and select the Pay Selected box. (see image Paymentbox1) 2. You should be in the confirmation screen and the note text should be brought over. (see Paymentbox2) 3. Hit the confirm button and the note now displays in the notes fields. (see Paymentbox3) This test case does not work. 1. Select the Pay Amount button, change and add a note in the note box. (see Paymentbox4) 2. Select confirm and the note does not display. The work around test case. 1. Select the check boxes of the fines the are choosing to pay and select the Pay Selected button. 2. Add a note in the notes box and select confirm. 3. The note displays. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 10956] New: Series of OPAC searches can cause a browser crash
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10956 Bug ID: 10956 Summary: Series of OPAC searches can cause a browser crash 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org In my tests this series of OPAC searches will result a browser crash (Firefox) or an endlessly loading tab (Chrome): 1. Perform a keyword search which will return a good number of results. 2. Click on a title in those results which will have a good number of works by that author. 3. Click on the author link on the detail page to perform a search by author. 4. Click on a facet on the author search results page (I tested by clicking on a library facet). 5. Click on a title in the refined search results. I've tested this procedure with XSLT on and off, with OpacBrowseResults on and off, and with EnableOpacSearchHistory on and off. I get the same results in both themes. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 12536] New: Incorrect number of irregularity issues
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12536 Bug ID: 12536 Summary: Incorrect number of irregularity issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: simith.doliveira(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com In Serials -> Planning tab, irregularity is always 1 issue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 12851] New: order tags are not removed on claiming serials/orders
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12851 Bug ID: 12851 Summary: order tags are not removed on claiming serials/orders Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org If you use a claimissue notice to claim serials, the generated letter will be <order>Title1, Author1</order> <order>Title2, Author2</order> ... <order>TitleN, AuthorN</order> We need to ged rid of these tags. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 12959] New: Check in forgets to remember arbitrary backdating of returns setting
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12959 Bug ID: 12959 Summary: Check in forgets to remember arbitrary backdating of returns setting Change sponsored?: --- Product: Koha Version: unspecified 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 Whenever a librarian is prompted with a form during the checking process ( hold to fill, transfer, etc ) the date to backdate returns to is forgotten! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 13157] New: improving facet definitions for unimarc
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13157 Bug ID: 13157 Summary: improving facet definitions for unimarc Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The new code for facets calculation could probably be more precise for unimarc (in biblio-koha-indexdefs.xml) - for series, 410 tag is probably better than 225 - the date and place subdivisions 6XX$y and 6XX$z could be indexed (in su-geo and su-chrono) - the subdivisionn $x is indexed for 606, but all 6XX$x could also be indexed (in su-to) - 5XX are not subjects, so I'm not sure that indexing them in su-ut is good (but we should check in ccl.properties how this index is defined). Anyway, I always found that indexing 5XX was a weird idea... and there is maybe a mistake for 995$b - holdingbranch (should be 995$c) M. Saby -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 10749] New: patron permissions typos
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10749 Bug ID: 10749 Summary: patron permissions typos Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In Home > Patrons > Set permissions for {staff member}, it says "edit_patronsPerform batch modifivation of patrons" which should be "edit_patronsPerform batch modification of patrons" It also says "budget_add_delAdd and delete budgets (but cant modify budgets)" which should be "budget_add_delAdd and delete budgets (but can't modify budgets)" -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 12407] New: phone label or data switched
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12407 Bug ID: 12407 Summary: phone label or data switched Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 28785 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=28785&action=edit enter data See attached image. You enter date in the secondary and other phone fields on the patron form and it shows next to the opposite label on the patron record. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 12924] New: Replay advance_notices.pl-cronjob in history
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12924 Bug ID: 12924 Summary: Replay advance_notices.pl-cronjob in history Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org If for some reason the advance_notices.pl script fails to run/crashes. It is very handy to be able to run it in a previous point in time. This feature improves the cronjob so we can run it any day in the past or future. This patch also introduces an exclusion feature to not run some day-differences. For ex. If the cronjob failed yesterday, and today the DUE-message is already generated, there is no point in generating PREDUE-messages from yesterday for those issues that expired and got notified today. If the cronjob failed many days ago playing with the exclusion days a bit trickier and requires careful testing, but it helps repair damage from unrealiable cronjobs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4