July 2013 - Koha-bugs - lists.koha-community.org

[Bug 9988] New: Unneeded timeouts when saving authorities (Can we merge smarter?)
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '15

15 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9988 Bug ID: 9988 Summary: Unneeded timeouts when saving authorities (Can we merge smarter?) Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl When saving an authority used in many biblios, Koha may have a timeout due to updating all those bib records. But in case I just update e.g. a 551 tag for the auth record, there is no need at all to update all those bib records. We should have a smarter merge function in C4/AuthoritiesMarc.pm. Note that you could use the pref to move updating all biblios to a cron job. Wouldn't it be nicer if we could do something in between? If we really need to update a handful of records, do it rightaway. If we really (!!) need to update 2000 records (in my example Koha is updating 2000 records for nothing), we could perhaps leave that to a cron job. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 10169] New: Software error if one of multiple titles selected for hold in the OPAC has no items
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '15

15 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10169 Bug ID: 10169 Summary: Software error if one of multiple titles selected for hold in the OPAC has no items Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org CC: gmcharlt(a)gmail.com If you select multiple titles to place on hold in the OPAC and at least one of them has no items you will get a nasty error: Can't call method "field" on an undefined value at C4/Items.pm line 1398. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 10234] New: MySQL error when adding entry to z39.50servers
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10234 Bug ID: 10234 Summary: MySQL error when adding entry to z39.50servers Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au Recently, someone reported getting an error when trying to add an entry into z39.50servers (http://irc.koha-community.org/koha/2013-05-09#i_1250075) Here is a snippet of their log: log: "z3950servers.pl: DBD::mysql::st execute failed: Field 'description' doesn't have a default value at /usr/share/koha/intranet/cgi-bin/admin/z3950servers.pl line 133" I believe the problem is the result of using a strict SQL mode: Strict mode controls how MySQL handles input values that are invalid or missing. A value can be invalid for several reasons. For example, it might have the wrong data type for the column, or it might be out of range. A value is missing when a new row to be inserted does not contain a value for a non-NULL column that has no explicit DEFAULT clause in its definition. (For a NULL column, NULL is inserted if the value is missing.) (http://dev.mysql.com/doc/refman/5.5/en/server-sql-mode.html [You can check different versions, they all seem to have the same behaviour from what I can tell.]) * In this case, the field 'description' has no default value but is also NOT NULL field. If your SQL mode isn't strict, you'll get a warning but the insert will succeed (using a blank value rather than a null value). However, it if it strict, you'll get an error and a rolled back/failed insert. * If we observe other fields in kohastructure.sql that are NOT NULL and don't have a "real" default value, we typically use a default of ''. This will stop the warnings and the errors. Admittedly, the field "description" is documented as not being used, so perhaps the best thing to do is remove the field or perhaps make it NULL, but...using a default of '', will be the least potentially hazardous as it won't really change anything. It'll just enforce what we know as a default behaviour of using '' when the default value is missing. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 10252] New: File Print of Checkout History Truncates Results
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10252 Bug ID: 10252 Summary: File Print of Checkout History Truncates Results Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: thatcher.rea(a)bywatersolutions.com We're observing that printing of the checkout history is truncating some of the results. To replicate: Find a patron with more than 8 checkouts. Do a File-> Print of the page, and spool to PDF. The printout will drop results after 8 items. This seems to be affected in both 3.10.5 as well as master. Printing to hard copy is also affected. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 10161] New: rebuild_zebra.pl should (at least) exit 1 on error
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10161 Bug ID: 10161 Summary: rebuild_zebra.pl should (at least) exit 1 on error Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 10098] New: Inactive Funds are still showing in Acquisitions Order screen in Internet Explorer
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10098 Bug ID: 10098 Summary: Inactive Funds are still showing in Acquisitions Order screen in Internet Explorer Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au Currently, browsers like Chrome (and probably Firefox) allow you to use a "Show all" check box to show all funds or just the active funds. Unfortunately, in Internet Explorer, function using the JQuery .remove() method doesn't seem to be working. When the page loads, it shows both active and inactive funds. Using the "Show all" toggle does nothing. -- I haven't investigated this very far but I didn't see any mention of the method not working in IE on the JQuery site. I've seen a JSFiddle that uses a remove() method, so I'm thinking it must be how we're using it which causes the problem in IE... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 9993] New: On editing basket group delivery place resets to logged in branch
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9993 Bug ID: 9993 Summary: On editing basket group delivery place resets to logged in branch Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de When editing a basket group the selected options for delivery address don't match what's saved in the database. To reproduce: 1) Create a new basket group, set delivery place to "-" 2) Add a delivery address in the text box. 3) Save. 4) Edit basket group - delivery place is set to my current branch instead of "-" Comment from Fridolyn on this behaviour (bug 7996): Creating a new basketgroup and editing one uses the same page and operation : acqui/basketgroup.pl?op=add&booksellerid=x&basketgroupid=x So when you edit an existing basketgroup, selected branches are librarian branch. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 7607] New: Advanced search: Index and search term don't match when leaving fields empty
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7607 Bug #: 7607 Summary: Advanced search: Index and search term don't match when leaving fields empty Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 - low Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha.sekjal(a)gmail.com On advanced search in OPAC or staff: - leave the first pulldown on keyword and the search term empty - select author or title from the second pull down and enter a search term What will happen is, that Koha performs a keyword search with the search term from the second pull down. This means: Keyword: empty Title: <search term> Keyword: empty is equal to Keyword: <search term> Keyword: empty Keyword: empty but not the same as: Title : <search term> Keyword: empty Keyword: empty I wonder if this is related to bug 3264? But not sure how to fix it. -- 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 6

[Bug 7170] New: Remove use of XML::Simple
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7170 Bug #: 7170 Summary: Remove use of XML::Simple Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Architecture, internals, and plumbing AssignedTo: paul.poulain(a)biblibre.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: ian.walls(a)bywatersolutions.com Blocks: 7119 XML::Simple is known to be very slow compared to other XML parsers. It's used to parse the koha-conf.xml, which is loaded on every page, taking ~600ms on my localhost, so this is a performance hit. These files currently use or reference XML::Simple: ./about.pl ./C4/Auth_with_ldap.pm ./C4/Context.pm ./C4/External/Amazon.pm ./C4/External/BakerTaylor.pm ./C4/External/Syndetics.pm ./C4/ILSDI/Services.pm ./C4/Installer/PerlDependencies.pm ./C4/Reports/Guided.pm ./C4/Search/PazPar2.pm ./C4/Search.pm ./C4/SIP/Sip/Configuration.pm ./C4/SIP/xmlparse.pl ./C4/XISBN.pm ./labels/label-create-xml.pl ./misc/bin/zebraqueue_daemon.pl ./misc/cronjobs/zebraqueue_start.pl ./opac/ilsdi.pl ./patroncards/create-pdf.pl ./patroncards/edit-layout.pl ./svc/authentication ./svc/bib ./svc/bib_profile ./svc/new_bib -- 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 20

[Bug 5627] New: lock symbol even on not locked fields
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5627 Summary: lock symbol even on not locked fields Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: Mac OS Status: NEW Severity: normal Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When cataloging the authority controlled fields always show the lock symbol even if the field can be typed in - this is confusing to users and should only show locked if you can't type in the field. If it matters I'm on Mac and FF. -- 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 5