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

[Bug 4994] New: ldap mapping inconsistancy: Net::LDAP returns lowercase names
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '11

14 Jul '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4994 Summary: ldap mapping inconsistancy: Net::LDAP returns lowercase names Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Authentication AssignedTo: gmcharlt(a)gmail.com ReportedBy: dpavlin(a)rot13.org QAContact: koha-bugs(a)lists.koha-community.org CC: dpavlin(a)rot13.org Estimated Hours: 0.0 This requires us to specify all LDAP mappings in koha-conf.xml in lowercase, instead of original case used withing LDAP. Compare readability of <userid is="hrEduPersonUniqueID" ></userid> (which doesn't work) with required (and non-intuitive) <userid is="hredupersonuniqueid" ></userid> -- 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 8

[Bug 5548] New: Hard Due Dates Circ Rule
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '11

14 Jul '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5548 Summary: Hard Due Dates Circ Rule Change sponsored?: Sponsored Product: Koha Version: HEAD Platform: All OS/Version: All Status: ASSIGNED Severity: enhancement Priority: P5 Component: Circulation AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 This development shall enable libraries to specify global and/or ceiling due dates for specific combinations of branchcode, item type and patron category. Full RFC: http://wiki.koha-community.org/wiki/Hard_Due_Dates_Circ_Rule_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 5268] New: Language Issue: Debarred
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '11

14 Jul '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5268 Summary: Language Issue: Debarred Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Patrons 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 For those using US English, would it make more sense to change debar and debarred to 'restricted' or 'barred'? I have to admit that I have yet to train a library where they didn't ask what 'debarred' meant and why it wasn't just 'barred' -- 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 6

[Bug 5307] New: language searching fields
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '11

14 Jul '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5307 Summary: language searching fields Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The language values from the 008 and 041 fields are what's used to determine the language for the item. It does not differentiate between 041$a (the current language) and 041$h (original language). I think it should only search the 041$a because that's the language of the record you're searching for. -- 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 6

[Bug 5449] New: JSON malformed in Koha - Blocker with jQuery 1.4.x
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '11

14 Jul '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5449 Summary: JSON malformed in Koha - Blocker with jQuery 1.4.x Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: brice.sanchez(a)sys-tech.net QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2789 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2789 Patch for JSON bug [EN] After updating jQuery in version 1.4.3, I could not import MARC records with the tools "Stage MARC records for import". Indeed, JSON was malformed, the JSON script did not respect the standard. So I changed all JSON scripts created on Koha. Please note, this problem is a blocker with jQuery 1.4.x but not with 1.3.x as the old version was more permissive. Attached patch. [FR] Après avoir mis à jour jQuery en version 1.4.3, je ne pouvais plus importer de notices MARC avec l'outils "Stage MARC records for import". En effet, les JSON étaient mal formés, ils ne respectaient pas la norme. J'ai donc modifié tous les script créant des JSON sur Koha. Attention, ce problème est bloquant avec jQuery 1.4.x mais pas 1.3.x car l'ancienne version était plus permissive. Ci-joint, le correctif -- 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 4993] New: ldap search always anonymous when using auth_by_bind
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '11

14 Jul '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4993 Summary: ldap search always anonymous when using auth_by_bind Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Authentication AssignedTo: gmcharlt(a)gmail.com ReportedBy: dpavlin(a)rot13.org QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When using auth_by_bind, search was always done as anonymous user. This is a problem if we want to fetch LDAP values which have ACL permissions only for users. -- 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 5714] New: Unescaped ampersands in OPAC facets
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '11

14 Jul '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5714 Summary: Unescaped ampersands in OPAC facets Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: minor 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 Unescaped ampersands are being sent to the template in the query_cgi variable. -- 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 17

[Bug 6343] New: Label Creator not working , Current Branch: NULL
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '11

14 Jul '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6343 Bug #: 6343 Summary: Label Creator not working , Current Branch: NULL Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: Linux Status: NEW Severity: critical Priority: P5 Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: ata.rehman(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Lable Creator not working as mentioned: 1- http://lists.katipo.co.nz/pipermail/koha/2011-May/028983.html 2- http://lists.katipo.co.nz/pipermail/koha/2011-May/029032.html Can not add barcodes in new batch or manage batch -- 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 18

[Bug 5653] New: default new label layout and sample data have broken call number placeholder
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '11

13 Jul '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5653 Summary: default new label layout and sample data have broken call number placeholder Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: gmcharlt(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The sample label layout data and the hardcoded default values for a new spine label layout refer to 'callnumber' instead of 'itemcallnumber'. Consequently, labels based on these layouts will not include the call number unless the user manually updates the layout to use itemcallnumber. -- 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 12

[Bug 6133] New: Authorised values administration, warn for modifs
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '11

12 Jul '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6133 Bug #: 6133 Summary: Authorised values administration, warn for modifs Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: alex.arnaud(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com When a librarian modifies auth values, he sometimes think that the modifs he does will be done on records that use the authvalue. It's not the case. This patch just add a warning about that on main & modif pages. -- 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 9