April 2012 - Koha-bugs - lists.koha-community.org

[Bug 7581] New: Holds not working in OPAC in singlebranchmode
by bugzilla-daemon＠bugs.koha-community.org 09 May '12

09 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7581 Bug #: 7581 Summary: Holds not working in OPAC in singlebranchmode Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: pelletiermaxime(a)gmail.com QAContact: koha.sekjal(a)gmail.com When singlebranchmode is actived users can't place holds. Looks a lot like #3164 which was supposed to be resolved. Simple patch to follow. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 13

[Bug 7482] New: overdues report downloads without names
by bugzilla-daemon＠bugs.koha-community.org 09 May '12

09 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7482 Bug #: 7482 Summary: overdues report downloads without names Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: cgi-bin/koha/circ/overdue.pl OS/Version: All Status: NEW Severity: major Priority: P5 - low Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha.sekjal(a)gmail.com CC: gmcharlt(a)gmail.com When you click to download the overdues report it doesn't include the names but the report does print names to the screen. Names should be in the downloaded file. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 10

[Bug 7893] New: Missing build-dependency on libdatetime-format-dateparse-perl and libreadonly-perl
by bugzilla-daemon＠bugs.koha-community.org 09 May '12

09 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7893 Priority: P1 - high Change sponsored?: Sponsored Bug ID: 7893 Assignee: mjr(a)software.coop Summary: Missing build-dependency on libdatetime-format-dateparse-perl and libreadonly-perl QA Contact: koha.sekjal(a)gmail.com Severity: critical Classification: Unclassified OS: All Reporter: mjr(a)software.coop Hardware: All Status: ASSIGNED Version: unspecified Component: Packaging Product: Koha Created attachment 8826 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8826&action=edit add libdatetime-format-dateparse-perl to debian/control debian/build-git-snapshot fails because it cannot find DateTime::Format:DateParse or Readonly. A patch to update debian/control is attached. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 7597] New: fines not recording the right info in the stats table
by bugzilla-daemon＠bugs.koha-community.org 09 May '12

09 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7597 Bug #: 7597 Summary: fines not recording the right info in the stats table Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 - low Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha.sekjal(a)gmail.com CC: gmcharlt(a)gmail.com I did some testing today of paying fines and watched my DB only to find that the data being recorded when writing off a fine is wrong. http://screencast.com/t/XuhUtQRMccr When you write off a fine it's using the wrong branch code and it seems to be writing off the wrong amount altogether. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 26

[Bug 7485] New: Cannot edit barcode on Fast Add
by bugzilla-daemon＠bugs.koha-community.org 09 May '12

09 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7485 Bug #: 7485 Summary: Cannot edit barcode on Fast Add Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha.sekjal(a)gmail.com When new records use the fast add/ill framework, after initially adding an item record, including its barcode, when you go back to edit the item record, the barcode field is not editable -- in fact, nothing displays in the barcode field! (see attached) I replicated this behavior using both the Fast Cataloging link under Circulation, and by starting a new record from the Cataloging module using the Fast Add framework. I was able to temporarily resolve this for one of our libraries by having her switch the record framework to default. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 10

[Bug 7903] New: add an ordernumber column in orders history table
by bugzilla-daemon＠bugs.koha-community.org 08 May '12

08 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7903 Priority: P5 - low Change sponsored?: --- Bug ID: 7903 Assignee: koha(a)univ-lyon3.fr Summary: add an ordernumber column in orders history table QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: koha(a)univ-lyon3.fr Hardware: All Status: NEW Version: rel_3_6 Component: Acquisitions Product: Koha Created attachment 8918 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8918&action=edit Add ordernumber column in order's history table Add an ordernumber column in the search results table of orders. it would be an appreciate help as far as order tracking is concerned. to test : Go to Acquisition homepage : Click on Orders Search Button Type a title or a supplier Submit -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 6372] New: Batch progress bar does not check for 0 size jobs; should be in separate js too
by bugzilla-daemon＠bugs.koha-community.org 08 May '12

08 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6372 Bug #: 6372 Summary: Batch progress bar does not check for 0 size jobs; should be in separate js too Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: srdjan(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Batch progress bar does not check for 0 size jobs, and divides by 0, with unpredictable effects. Also, putting progress bar javascript inline makes it impossible to debug. It is possible that this change will improve situation with some bugs reported against background jobs that use progress bar. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 15

[Bug 7588] New: adding reserve restrictions after cataloging items can cause non-holdable items to be picked for holds
by bugzilla-daemon＠bugs.koha-community.org 07 May '12

07 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7588 Bug #: 7588 Summary: adding reserve restrictions after cataloging items can cause non-holdable items to be picked for holds Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests AssignedTo: koha.sekjal(a)gmail.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha.sekjal(a)gmail.com CC: gmcharlt(a)gmail.com When items are originally cataloged with an unrestricted item type and subsequently edited to a restricted item type with a restriction of 'home library' or 'No Holds,' Koha treats the item as unrestricted and allows those items to fill holds even after they are changed to a restricted i-type...because they were unrestricted at the time the hold was placed. The work around for this is to 1. make sure that your holdability rules are defined before you catalog items and allow patrons to place holds. 2. catalog restricted item types as restricted from the very start. I'm not sure how we can actually *fix* this bug, but I wanted to document the workaround. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 1

[Bug 7528] New: amount subtracting 1 cent
by bugzilla-daemon＠bugs.koha-community.org 04 May '12

04 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7528 Bug #: 7528 Summary: amount subtracting 1 cent Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 - low Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha.sekjal(a)gmail.com When adding an order if you enter an amount and hit tab it puts the amount minus 1 cent in the next couple fields - see here: http://screencast.com/t/SbVVtte8zHvk It's crazy - and critical that it be fixed. Nicole -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 9

[Bug 7816] New: use encoding(UTF-8) not utf-8 for output streams
by bugzilla-daemon＠bugs.koha-community.org 04 May '12

04 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7816 Priority: P5 - low Change sponsored?: --- Bug ID: 7816 Assignee: gmcharlt(a)gmail.com Summary: use encoding(UTF-8) not utf-8 for output streams QA Contact: koha.sekjal(a)gmail.com Severity: minor Classification: Unclassified OS: All Reporter: colin.campbell(a)ptfs-europe.com Hardware: All Status: NEW Version: master Component: Architecture, internals, and plumbing Product: Koha Setting :utf-8 on output streams flags the stream as unicode but does not ensure output is encoded as such using ':encoding(UTF-8) is the correct call. Fixed already in most files authorities/ysearch.pl reintroduces a case of not using encoding and causes make test to fail if TEST_QA is set -- You are receiving this mail because: You are watching all bug changes.

1 7