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

[Bug 5316] New: Limit 39.50 targets to specific users
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '13

13 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5316 Summary: Limit 39.50 targets to specific users Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: spalding(a)senylrc.org QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 Have several locations with different OCLC subscriptions. Would need a way to limit the z39.50 target to specific accounts. -- 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 5345] New: Table sorters in Koha
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '13

13 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5345 Summary: Table sorters in Koha Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/Table_sorters_RFC OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Templates AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 We will add table sorter & filters « everywhere » in Koha We will avoid adding sorters & filters where perf is a caveat (like circulation) -- 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 111

[Bug 5766] New: Add system preference for excluding articles from jQuery table sorter
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '13

13 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5766 Summary: Add system preference for excluding articles from jQuery table sorter Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: I18N/L10N AssignedTo: frederic(a)tamil.fr ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The jQuery table sorter can be configured with a custom parser for excluding articles from sorting. Many pages in Koha already include this, but for English only: $.tablesorter.addParser({ id: 'articles', is: function(s) {return false; }, format: function(s) { return s.toLowerCase().replace(/^(the|an|a) /,''); }, type: 'text' }); A system preference should be created to contain the pipe-delimited articles (or other text) for exclusion so that speakers of other languages can include their own. -- 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 13

[Bug 6124] New: In transferstoreceive.pl some biblios are empty.
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '13

12 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6124 Bug #: 6124 Summary: In transferstoreceive.pl some biblios are empty. Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: julian.maurice(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Due to the fact that it is possible to have some lines in branchtransfers with an itemnumber that does not exists in table items. With the coming patch in this case the line with no biblios will be omitted. -- 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 10

[Bug 6697] New: Empty Organisation(s) field for organisational patrons
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '13

12 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6697 Bug #: 6697 Summary: Empty Organisation(s) field for organisational patrons Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: /cgi-bin/koha/members/memberentry.pl?op=modify&borrowe rnumber=1159&category_type=I OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org Created attachment 4930 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=4930 screenshot When adding or modifying a patron with a patron category that is type 'organisation' an additioanl fieldset 'Organisation' with an empty field 'Organisation(s)' is displayed in the patron record. I see no way to make use of this. I linked a professional patron to my organisation, but the field stayed empty. I tried adding a second organisation, but the field still stayed empty. There is currently no way to link orgaisational patrons together in hierarchies - so why should we display a list of organisations there? Perhaps this is a leftover from an earlier feature. As it seems not to be working it should be removed. And if there is a trick to make it work it should be documented. -- 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 7

[Bug 7207] New: Cannot export label batches
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '13

12 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7207 Bug #: 7207 Summary: Cannot export label batches Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: wizzyrea(a)gmail.com QAContact: ian.walls(a)bywatersolutions.com http://screencast.com/t/hthSz0Uz5 We discussed this on IRC - this is just the formal bug report. See also Bug 6679, which should have the patch applied that will fix this error. -- 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 21

[Bug 6833] New: Notifications Rewrite
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '13

12 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6833 Bug #: 6833 Summary: Notifications Rewrite Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: tdavis(a)uttyler.edu QAContact: koha-bugs(a)lists.koha-community.org http://wiki.koha-community.org/wiki/Notifications_RFC -- 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 7

[Bug 7032] New: can select multiple layouts to edit
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '13

12 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7032 Bug #: 7032 Summary: can select multiple layouts to edit Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: cgi-bin/koha/labels/label-manage.pl?label_element=layo ut OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org I've noticed that I am allowed to check off more than one layout in the list of layouts. It's not a big deal, since the system tells me to choose only one layout to edit, but it seems like those check boxes should be exclusive (I can't come up with the right term for it) -- so if I check one box and then check another box, the initial check should go away when I check box #2 or they should be radio buttons instead. -- 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 13

[Bug 7075] New: Fine in days values are returned for patrons with past overdues when fine in days is set to 0
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '13

12 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7075 Bug #: 7075 Summary: Fine in days values are returned for patrons with past overdues when fine in days is set to 0 Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Circulation 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 When Members.pm checks to see whether a particular patron can check out, it checks for issuingrules.finedays "WHERE finedays IS NOT NULL." If the user has created a rule via Circulation and fines rules, finedays will always be 0 even if an empty value has been submitted. This causes Members::IsMemberBlocked to return a value when it should not. [09:57] <sekjal> IsMemberBlocked checks for finedays IS NOT NULL [09:58] <oleonard> ...and it's 0. [09:58] <sekjal> so, if you have finedays = 0 in any of your rules, it'll trigger [09:59] <sekjal> so, in that case, it'll just take the date difference between the returndate, and the current date [09:59] <sekjal> which means it would grow to 44 tomorrow [09:59] <sekjal> and so on [09:59] <sekjal> that's.... bad [09:59] <libsysguy> ^^ [09:59] <oleonard> And you can't set finedays to null when editing an issuing rule [10:00] <libsysguy> so we could change that check or null or 0 [10:00] <libsysguy> and it would fix your issue right [10:00] <sekjal> yes, that's the fix [10:00] <sekjal> one more line to the SQL [10:00] <sekjal> "AND finedays != 0" http://stats.workbuffer.org/irclog/koha/2011-10-21#i_795577 -- 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 11

[Bug 6604] New: without OPACXSLTResultsDisplay, some entries are "no items available" in opac-search
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '13

12 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6604 Bug #: 6604 Summary: without OPACXSLTResultsDisplay, some entries are "no items available" in opac-search Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: semarie-koha(a)latrappe.fr QAContact: koha-bugs(a)lists.koha-community.org Under some circumstances (seems to be zebra indexing), some entries in opac-search are marked with "No items available", whereas in opac-detail, the items are showed. This occurs only without OPACXSLTResultsDisplay preference (not using xsl for result display). The items not displayed seems to be correlated with zebra indexing state: only the latest items are "no items available". The incremental indexing not resolving this, but a full indexing yes (indexing with reset). In order to test: - unset the system preferences OPACXSLTResultsDisplay (not use xsl for result display) - in OPAC: search for your lasted created entries in search form (created after a full indexing) - check the availability displayed Additional question: zebra incremental indexing shouldn't process also items (not just notice) ? So I don't now if the problem is more a "display" error (information present in zebra, but not showed), or a zebra problem (the information isn't present so can't be showed) -- 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