January 2014 - Koha-bugs - lists.koha-community.org

[Bug 8190] New: Koha does not have a logging module
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8190 Priority: P5 - low Change sponsored?: --- Bug ID: 8190 Assignee: gmcharlt(a)gmail.com Summary: Koha does not have a logging module Severity: enhancement Classification: Unclassified OS: All Reporter: jonathan.druart(a)biblibre.com Hardware: All Status: NEW Version: unspecified Component: Architecture, internals, and plumbing Product: Koha I would be great to specify a log level (to differentiate production and development environment for example). -- You are receiving this mail because: You are watching all bug changes.

1 144

[Bug 10998] New: code duplication introduced by Z39.50 authority search
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10998 Bug ID: 10998 Summary: code duplication introduced by Z39.50 authority search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 10096, which introduces a feature to import authority records via Z39.50, also introduces some code duplication. To summarize the differences: - z3950_search.pl and z3950_auth_search.pl differ only in the input search attributes they accept - C4::Breeding::ImportBreeding() and C4::Breeding::ImportAuth() do mostly the same thing - the actual search logic in C4::Breeding::Z3950SearchAuth() and C4::Breeding::Z3950Search() is the same; the two routines differ only in the specific Z39.50 attributes they handle and in some details of post-retrieval record processing. Also, Z3950SearchAuth() does not reflect the work that was done for bug 10462. Consequently, there is plenty of opportunity for code consolidation, as well as adding unit tests. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 8582] New: NULL issuedates with offline circ
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8582 Priority: P5 - low Change sponsored?: --- Bug ID: 8582 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: NULL issuedates with offline circ Severity: enhancement Classification: Unclassified OS: All Reporter: melia(a)bywatersolutions.com Hardware: All Status: NEW Version: rel_3_8 Component: Circulation Product: Koha We don't think offline circ works quite right with 3.8. It may be a date vs. datetime problem, perhaps? After processing offline circ files in 3.8, we have seen some NULL issues.issuedate. We discovered these after seeing the following error occur when going to the check-out screen. Software error: Can't call method "strftime" on an undefined value at /home/koha/kohaclone/Koha/DateUtils.pm line 117 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 11629] New: Add ability to update not for loan status on checkin
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11629 Bug ID: 11629 Summary: Add ability to update not for loan status on checkin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries would like to streamline the cataloging process my automatically updating notforloan values on checkin. For example, an item is set to notforloan of -1 ( ordered ). The item, is received, processed, and checked in for the first time before being shelved. The checkin automatically changes the nfl value from -1 to 0. The same workflow could be used for damaged items as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50

[Bug 7372] New: RoadTypes should be folded into Authorised Values
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7372 Bug #: 7372 Summary: RoadTypes should be folded into Authorised Values Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: jonathan.druart(a)biblibre.com The current data structure for Road Types is essentially the same as for Authorised Values, but it gets it's own admin page and database table. In an effort to simply both the Koha data structure, and the admin main page, I suggest moving this into Authorised Values. This development is marked as "(OUEST-PROVENCE)". Is there a reason for the separate table and admin page that I don't understand, (not being in a European library)? -- 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 29

[Bug 10866] New: Books entered in malayalam language cannot to search
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10866 Bug ID: 10866 Summary: Books entered in malayalam language cannot to search Change sponsored?: --- Product: Koha Version: 3.12 Hardware: PC OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: sameer(a)kvasu.ac.in QA Contact: testopia(a)bugs.koha-community.org Sir, Prior to install 3.12, i was using 3.2 and i could search the terms in malayalam language. Now in 3.12 I cannot search the titles in malayalam, but it is ok in English. is there any solution -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 11620] New: dissertation-information is only defined for UNIMARC
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '15

20 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11620 Bug ID: 11620 Summary: dissertation-information is only defined for UNIMARC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The dissertation-information index is added by bug 11202 for UNIMARC but does not exist for others marc formats. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 9006] New: autoload in C4::Context is a bad idea
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '15

20 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9006 Priority: P5 - low Change sponsored?: --- Bug ID: 9006 Assignee: gmcharlt(a)gmail.com Summary: autoload in C4::Context is a bad idea Severity: minor Classification: Unclassified OS: All Reporter: jcamins(a)cpbibliography.com Hardware: All Status: NEW Version: master Component: Architecture, internals, and plumbing Product: Koha The comment in C4/Context.pm pretty much sums it up: # AUTOLOAD # This implements C4::Config->foo, and simply returns # C4::Context->config("foo"), as described in the documentation for # &config, above. # FIXME - Perhaps this should be extended to check &config first, and # then &preference if that fails. OTOH, AUTOLOAD could lead to crappy # code, so it'd probably be best to delete it altogether so as not to # encourage people to use it. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 9164] New: Only allow kohaadmin login under special conditions
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '15

20 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9164 Bug ID: 9164 Summary: Only allow kohaadmin login under special conditions Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl Would it be an idea to separate the Koha password of kohaadmin [or whatever you name it during installation] from the database password (in terms of security)? Furthermore, is it necessary that kohaadmin can login via opac? And even, could we disable staff client login via kohaadmin under normal circumstances, only allowing login under special conditions (installer, maintenance mode, or so). We could define these conditions and provide a way for system administrators to "force these conditions" without compromising security again. Will ask for some ideas in this regard on the dev list. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 11623] New: Errors with upgrade from 3.00.00.070 to 3.14.02.000
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '15

20 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11623 Bug ID: 11623 Summary: Errors with upgrade from 3.00.00.070 to 3.14.02.000 Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: dswhite42(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are a number of database upgrade errors that take place when upgrading from 3.00.00.070 to 3.14.02.000 * A number of upgrades expect the tables to have foreign keys and be in InnoDB format. In 3.00.00.070, MyISAM (and no foreign keys) is the standard. With no testing to see if the keys exist, these commands fail with (errno: 152) Problem examples: ALTER TABLE issues DROP FOREIGN KEY `issues_ibfk_1` ALTER TABLE issues DROP FOREIGN KEY `issues_ibfk_2` ALTER TABLE `message_transports` DROP FOREIGN KEY `message_transports_ibfk_3` ALTER TABLE patronimage DROP FOREIGN KEY patronimage_fk1 * In updatedatabase.pl, in the section for DBVersion 3.00.00.091, there are references to the @sql_scripts "installer/data/mysql/en/optional/sample_notices_message_attributes.sql" and "installer/data/mysql/en/optional/sample_notices_message_transports.sql" . These should be "installer/data/mysql/en/mandatory/sample_notices_message_attributes.sql" and "installer/data/mysql/en/mandatory/sample_notices_message_transports.sql" * Even when that's corrected, the sample_notices_message_transports.sql script fails because it references foreign keys to the "letters" table that have not been created yet. The reserves/HOLD combo isn't created until the 3.01.00.05 section of the updatedatabase.pl script, and circulation/CHECKIN and circulation/CHECKOUT are not created until the 3.01.00.013 section. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4