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

[Bug 2633] Notices when used with overdue_notices.pl
by bugzilla-daemon＠pippin.metavore.com 09 Oct '08

09 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2633 frederic(a)tamil.fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2630] ISBN cleanup fails for some ISBNs
by bugzilla-daemon＠pippin.metavore.com 09 Oct '08

09 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2630 frederic(a)tamil.fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2667] XSLT Subjects in OPAC
by bugzilla-daemon＠pippin.metavore.com 09 Oct '08

09 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2667 ------- Comment #1 from nicole.engard(a)liblime.com 2008-10-09 07:18 ------- Example: http://seu.kohalibrary.com/cgi-bin/koha/opac-search.pl?idx=su&q=jesus+christ Click the first result no subjects show - but they're in the MARC. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2667] New: XSLT Subjects in OPAC
by bugzilla-daemon＠pippin.metavore.com 09 Oct '08

09 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2667 Summary: XSLT Subjects in OPAC Product: Koha Version: HEAD Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nicole.engard(a)liblime.com QAContact: koha-bugs(a)lists.koha.org CC: jmf(a)liblime.com When XSLT is on only 650s appear - 610, 651, 600, 630 don't appear in the PAC or the staff (you can search by it but it will not show up in the record) ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2666] New: OPACDisplayItypes not in default database definition
by bugzilla-daemon＠pippin.metavore.com 09 Oct '08

09 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2666 Summary: OPACDisplayItypes not in default database definition Product: Koha Version: HEAD Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P3 Component: System Administration AssignedTo: paul.poulain(a)free.fr ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha.org 'OPACDisplayItypes' is a system pref for controlling whether itemtype images appear in the OPAC. It is missing from the default database definition. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2620] OPAC authority detail
by bugzilla-daemon＠pippin.metavore.com 09 Oct '08

09 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2620 ------- Comment #4 from henridamien(a)koha-fr.org 2008-10-09 01:33 ------- MMM... It would certainly be great. But, my question is if you have many fathers which are quite space consuming, will it be displayed correctly ? Maybe having it right hand side would be much more relevant, since it is not a view TYPE of data related to authority (like link to MARC view or link to ISBD view, for instance) detail page combines here 2 types of display : hierarchical AND record display (as if MARC AND ISBD would be on same page). Can you understand my point ? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2419] Adding a Vendor crashes Koha (error in updateseller.pl file)
by bugzilla-daemon＠pippin.metavore.com 09 Oct '08

09 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2419 marc.chantreux(a)biblibre.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rch(a)liblime.com |marc.chantreux(a)biblibre.com Status|ASSIGNED |NEW ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2419] Adding a Vendor crashes Koha (error in updateseller.pl file)
by bugzilla-daemon＠pippin.metavore.com 09 Oct '08

09 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2419 marc.chantreux(a)biblibre.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2665] New: opac-sendbasket fails on UTF-8
by bugzilla-daemon＠pippin.metavore.com 08 Oct '08

08 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2665 Summary: opac-sendbasket fails on UTF-8 Product: Koha Version: HEAD Platform: PC URL: /cgi-bin/koha/opac-sendbasket.pl OS/Version: All Status: NEW Severity: normal Priority: P3 Component: I18N/L10N AssignedTo: jmf(a)liblime.com ReportedBy: joe.atzberger(a)liblime.com QAContact: koha-bugs(a)lists.koha.org Characteristic error: Wide character in subroutine entry at /usr/share/koha/opac/cgi-bin/opac/opac-sendbasket.pl line 132. This is almost surely a problem with UTF-8 handling. The error line (132) is: my $isofile = encode_base64($iso2709); The encode_base64 function is form MIME::Base64. From perldoc MIME::Base64 regarding the error seen: "Wide character in subroutine entry: The string passed to encode_base64() contains characters with code above 255. The base64 encoding is only defined for single-byte characters. Use the Encode module to select the byte encoding you want.... Perl v5.8 and better allow extended Unicode characters in strings. Such strings cannot be encoded directly, as the base64 encoding is only defined for single-byte characters. The solution is to use the Encode module to select the byte encoding you want. For example:" use MIME::Base64 qw(encode_base64); use Encode qw(encode); $encoded = encode_base64(encode("UTF-8", "\x{FFFF}\n")); print $encoded;" I will send a patch for review that attempts to follow this methodology. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2660] Duplicate overdue notices generated when only one notice is defined.
by bugzilla-daemon＠pippin.metavore.com 08 Oct '08

08 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2660 rch(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |PATCH-Sent ------- Comment #2 from rch(a)liblime.com 2008-10-08 09:19 ------- This in fact is the case regardless of how many overdue rules are defined. Submitting a patch now to alter this behavior so that a notice is sent only if at least one item actually hits the trigger defined in overdue triggers. Marking 2661 (64k limit on notices) duplicate of this one, since it's highly unlikely to actually hit that limit if this patch is applied. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0