March 2015 - Koha-bugs - lists.koha-community.org

[Bug 12020] New: label-edit-batch has hardcoded error messages
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '15

06 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12020 Bug ID: 12020 Summary: label-edit-batch has hardcoded error messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr $ grep errstr labels/label-edit-batch.pl koha-tmpl/intranet-tmpl/prog/en/modules/labels/* labels/label-edit-batch.pl:my $errstr = undef; labels/label-edit-batch.pl: $errstr = "item(s) not removed from batch $batch_id." if $err; labels/label-edit-batch.pl: $errstr = "batch $batch_id was not deleted." if $err; labels/label-edit-batch.pl: $errstr = "item(s) not added to batch $batch_id." if $err; labels/label-edit-batch.pl: $errstr = "items(s) not added, the error was: Branch is not set, you please set your branch before adding items to a batch"; labels/label-edit-batch.pl: $errstr = "batch $batch_id not fully de-duplicated." if $duplicate_count == -1; labels/label-edit-batch.pl: errstr => $errstr, koha-tmpl/intranet-tmpl/prog/en/modules/labels/label-edit-batch.tt: <strong>WARNING:</strong> An error was encountered and [% errstr %] Please have your system administrator check the error log for details. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 8754] New: Cardnumber/accession number range when creating print batches in tools
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '15

06 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8754 Priority: P5 - low Change sponsored?: --- Bug ID: 8754 Assignee: gmcharlt(a)gmail.com Summary: Cardnumber/accession number range when creating print batches in tools Severity: enhancement Classification: Unclassified OS: All Reporter: amit.gupta(a)osslabs.biz Hardware: All Status: NEW Version: rel_3_10 Component: Tools Product: Koha Give ability to generate print batches on the basis of barcode range. for example barcode range: 100001-100099 -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 10895] New: Tests for C4::Items GetHiddenItems
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '15

04 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10895 Bug ID: 10895 Summary: Tests for C4::Items GetHiddenItems Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: gmcharlt(a)gmail.com Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org There were no tests for GetHiddenItems, and given that I have been working on tweaking this function (bug 10589, bug 10872), I thought some test modules might be in order. t/db_dependent/GetHiddenItems.t - Generic toggling of OpacHiddenItems system preference to test if NULL, blank, whitespace, and a rule all work. t/db_dependent/GetHiddenItems_PatronCategory.t - Setting of OpacHiddenItems, and then toggling a dummy patron's category code to see if visibility is correct. -- You are receiving this mail because: You are watching all bug changes.

1 48

[Bug 13707] New: Adding a new column datereceived for items and biblioitems
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '15

04 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13707 Bug ID: 13707 Summary: Adding a new column datereceived for items and biblioitems Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org This column tells when the Item or Biblio has been received for the first time into a library. Date-of-acquisition (dateaccessioned) answers, when the Item has been ordered. Date-of-receival (datereceived) answers, when the Item has arrived to the library or when the first Item for the Biblio has for the first time arrived to the library. This is very useful regarding statistics of acquisitions if they are based on the date received instead of the date acquired. Also other cool stuff can be built on top of it, like better searches for new material. This patch adds new DB columns items.datereceived, biblioitems.datereceived, deleteditems.datereceived, deletedbiblioitems.datereceived and populates those columns from the acorders.datereceived if the Item has been acquired using the acquisitions module, or from the items.dateaccessioned-column if no acquisitions module has been used. Biblioitems.datereceived is always the oldest timestamp from all the Items the Biblio has. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 8425] New: Duplicate barcodes generated when placing an Order in Acquisitions when AcqCreateItem = "placing an order" and Autobarcode is turned on
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '15

04 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8425 Priority: P5 - low Change sponsored?: --- Bug ID: 8425 Assignee: koha-bugs(a)lists.koha-community.org Summary: Duplicate barcodes generated when placing an Order in Acquisitions when AcqCreateItem = "placing an order" and Autobarcode is turned on Severity: normal Classification: Unclassified OS: All Reporter: dcook(a)prosentient.com.au Hardware: All Status: NEW Version: master Component: Acquisitions Product: Koha Duplicate barcodes are generated when placing an Order in Acquisitions when AcqCreateItem = "placing an order" and Autobarcode is turned on. The problem is that you can accidentally attach 3 items to an order, but only 1 will be saved to the database. When you go to receive your order, you can only receive 1 item as the other two were never made, since the barcode wasn't unique. In 3.8.0, a software error comes up which prevent any item creation, I believe, but master (3.9.x) doesn't throw any warnings or errors. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 9047] New: show hold info on self check out
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '15

04 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9047 Priority: P5 - low Change sponsored?: --- Bug ID: 9047 CC: gmcharlt(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: show hold info on self check out Severity: enhancement Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Hold requests Product: Koha In the self-check UI, it would be great if patrons could view holds and place in the queue (like they can when they log in to the opac). It would also be nice if it showed what holds were ready for pick up - like it does on the staff circ screen. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 13909] New: _debar_user_on_return doesn't honour finesCalendar
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '15

03 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13909 Bug ID: 13909 Summary: _debar_user_on_return doesn't honour finesCalendar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The routine should be using C4::Overdues::_get_chargeable_units instead of an ad-hoc calculation of the overdue days to use as basis for the calculatio here: my $calendar = Koha::Calendar->new( branchcode => $branchcode ); # $deltadays is a DateTime::Duration object my $deltadays = $calendar->days_between( $dt_due, $dt_today ); To reproduce: - Set finesCalendar = "directly" - Have a circulation rule stating: interval for calculating fines = 1 suspension days = 3 - Have the calendar set for sunday and saturday as holidays. - Checkout an item with a branch/itype/borrower category that matches the defined circ rule with a hand-writen due date to (say) last friday. - Check the item in => FAIL: Notice that the user is debarred using the calendar (skipping saturday and sunday). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 9601] New: ccsr opac no results found ugly
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '15

03 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9601 Bug ID: 9601 Summary: ccsr opac no results found ugly Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com Created attachment 15280 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=15280&action=edit no results In the CCSR template the no results page could use some work. See attached. The column on the left looks like it wants to appear and the text at the top is smooched together. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 12625] New: Delete component parts when deleting the parent from detailed-view
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '15

03 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12625 Bug ID: 12625 Summary: Delete component parts when deleting the parent from detailed-view Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl See Bug 11175 for explanation of component parts. This feature automatically deletes all linked component parts when the component parent is deleted using "catalogue/detail.pl -> Edit -> Delete record" Generalizing this to C4::Biblio::DelBiblio() is not a good idea because we don't wan't to delete all component parts when we are for example, merging records :) -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 12902] New: Cronjob monitoring script, nagios3 compatible
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '15

03 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12902 Bug ID: 12902 Summary: Cronjob monitoring script, nagios3 compatible Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: gmcharlt(a)gmail.com Created attachment 31509 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=31509&action=edit initial patch After having issues with cronjobs not always running or getting regression issues, I decided to give a try to create a cronjobs monitoring solution. This patch introduces a wrapper script to log and time cronjobs. The wrapper script's log output is used to analyze whther cronjobs ran and if there were any errors. Also cronjobs timings can be validated to prevent nasty errors with for. ex. expiring waiting holds one day too early/late. This check can also be integrated to nagios! Also provided is a scaffold to start introducing more nagios-checks, with example command and service configurations. This patch introduces a koha_cronjobs-script to read the /var/spool/cron/crontabs/koha and analysz its contents. Then one can validate whether the cronjob timings are right (this is not mentioned in the manual at all) and what is right is (currently) based on my honest feelings. Then each cronjobs frequency is determined and the cronjobs log output is checked based on the script parameters. Currently the cronjob frequencies are split to minutely, hourly, daily, etc. Koha_cronjobs-script is meant to be ran on those intervals to catch errors ASAP. I would also like to hear what kind of cronjob timings other libraries use? -- You are receiving this mail because: You are watching all bug changes.

1 5