May 2011 - Koha-bugs - lists.koha-community.org

[Bug 5229] New: OPACItemsResultsDisplay preference does not work with XSLT results
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '14

14 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5229 Summary: OPACItemsResultsDisplay preference does not work with XSLT results Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: /cgi-bin/koha/opac-search.pl?q=foo OS/Version: All Status: NEW Severity: normal Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The description for the preference says "show/don't show an item's branch, location and call number in OPAC search results." The preference works with normal results, the alternatives being: Availability: Copies available: Athens (1) ("don't show") and Availability: Copies available: Athens [AF Needle] (1) ("show") In the OPAC's XSLT results display the latter version appears no matter what the preference is set to. -- 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 3

[Bug 4833] New: show all fields when ordering from suggestion
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '14

12 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4833 Summary: show all fields when ordering from suggestion Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: cgi-bin/koha/acqui/newordersuggestion.pl?booksellerid= 1&basketno=1 OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When you are adding a suggestion to the basket you see only some of the info from the suggestion. At the very least it should show the budget that the item should be ordered from since this is acquisitions and the budget is a field on the suggestion. -- 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 3

[Bug 5757] New: Checking in a waiting item again does not trigger hold prompt.
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '14

10 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5757 Summary: Checking in a waiting item again does not trigger hold prompt. Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Hold requests AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 If an item has already been made "waiting" (reserves.found = 'F'), checking in that item again will not trigger the hold prompt. It should trigger the prompt headed "Hold Found (item is already waiting)." -- 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 1

[Bug 5552] New: circ dates in the past
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '14

10 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5552 Summary: circ dates in the past Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: /cgi-bin/koha/circ/circulation.pl OS/Version: All Status: NEW Severity: major Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Created attachment 2918 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2918 error box with due date When you choose a due date in the past a box appears asking you to confirm the date. This box should have a calendar icon and a date format tip like all other date boxes in Koha to prevent big mistakes. -- 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 4

[Bug 5847] New: Manage Staged MARC Records stuck at 0% if isbn matching rule selected.
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '14

10 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5847 Bug #: 5847 Summary: Manage Staged MARC Records stuck at 0% if isbn matching rule selected. Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P1 Component: MARC Bibliographic record staging/import AssignedTo: gmcharlt(a)gmail.com ReportedBy: kmkale(a)anantcorp.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com If we try to use ISBN match rule while importing a staged batch, the Manage Staged MARC Records gets stuck at 0%. I can see a www-data owned background job running but the browser is stuck at 0% and no entries in the db. Tried leaving it overnight with no progress. Tried with firefox and chrome. Same MARC file is imported fine without using the ISBN match rule. The same marc records file imports fine with bulkmarcimport.pl utility even with the -isbn option. Sadly the bulkmarcimport.pl lacks the option to still add items even while ignoring a biblio if a isbn match is found. See attached screenshot for rules used during this import. -- 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 4

[Bug 5179] New: GetMember and GetMemberDetails should be combined
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '14

25 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5179 Summary: GetMember and GetMemberDetails should be combined Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 In Members.pm, GetMember and GetMemberDetails do almost the same thing. This common behaviour should be combined so that changes to this kind of thing don't have to happen in multiple places. Aiming for 3.4. -- 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 2

[Bug 6374] New: Use "size" as names/hash keys leads to an unexpected results when using Template::Toolkit (name of a virtual method there)
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '14

19 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6374 Bug #: 6374 Summary: Use "size" as names/hash keys leads to an unexpected results when using Template::Toolkit (name of a virtual method there) Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: januszop(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org In many places the name "size" is used as hash key when the hash is passed to the template system for display. So, for example, since "size" is used as a name of a column of bibioitems table, it appears (or not, depending on if it was defined or not) in elements of SEARCH_RESULTS (in catalogue/search.pl or opac-search.pl) and is passed to the template results.tt/opac-results.tt. Then, in [opac-]results.tt a test is being done: [% IF ( SEARCH_RESULT.size ) %] Now: if "size" was defined, everything is OK and the size will be displayed (e.g. 21 cm), BUT if it was not defined, then a "random" number appears. This is because "size" is one of the virtual methods defined in Template::Toolkit for every data type (cf. http://search.cpan.org/~abw/Template-Toolkit-2.22/lib/Template/Manual/VMeth…) So, if "size" was defined by Koha, it will overload the method, but if it was not, then 1) XXX.size exists anyway, 2) the virtual method size() is called -- and it returns the number of elements in the hash or loop etc., depending on what is referred. The number of suspicious similar spots is ca. 20: git grep "IF.*\.size" called in koha-tmpl The issue does not seem to me to be straightforward to resolve, so I am not proposing any patch at the time. Since it seems that in most of the cases it rooted in biblioitems.size column, maybe it would be the simplest to rename that column to 'format' (and make appropriate changes in the code)? Any other ideas? -- 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 27

[Bug 6070] New: On a new order defined from suggestion some fields were missing.
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '14

05 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6070 Bug #: 6070 Summary: On a new order defined from suggestion some fields were missing. Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org (MT #4937) The missing fields : publicationyear, place, collectiontitle. More the layout has been modified. -- 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 54

[Bug 5789] New: Fines don't work when items have null homebranch
by bugzilla-daemon＠bugs.koha-community.org 28 May '14

28 May '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5789 Bug #: 5789 Summary: Fines don't work when items have null homebranch Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: jcamins(a)cpbibliography.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com It seems that the fines cron job cannot handle databases that include items where homebranch, and possibly holdingbranch, are NULL. -- 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 4

[Bug 5421] New: More fields to Fast Add Framework
by bugzilla-daemon＠bugs.koha-community.org 17 May '14

17 May '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5421 Summary: More fields to Fast Add Framework Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: vimal0212(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 Consider following MARC fields in "Fast Add Framework", 020 a- INTERNATIONAL STANDARD BOOK NUMBER 082 - DEWEY DECIMAL CLASSIFICATION NUMBER a Classification number b Item number 100 - MAIN ENTRY--PERSONAL NAME a Personal name 245 - TITLE STATEMENT a Title b Remainder of title − 250 - EDITION STATEMENT − a Edition statement − 260 - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) a Place of publication, distribution, etc b Name of publisher, distributor, etc c Date of publication, distribution, etc 300 - PHYSICAL DESCRIPTION a Extent 490 - SERIES STATEMENT a Series statement 520 - SUMMARY, ETC. a Summary, etc − 650 - SUBJECT ADDED ENTRY--TOPICAL TERM a Topical term 700 - ADDED ENTRY--PERSONAL NAME a Personal name ... − 942 - ADDED ENTRY ELEMENTS (KOHA) c Koha [default] item typ Trim subfields in 952 952 -LOCATION AND ITEM INFORMATION 4 Damaged status 9 Koha itemnumber (autogenerated) a Permanent location b Current location c Shelving location d Date acquired g Cost, normal purchase price o Full call number p Barcode -- 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 4