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

[Bug 14389] New: Editing a syspref in a textarea does not ednable the Save button
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '15

02 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14389 Bug ID: 14389 Summary: Editing a syspref in a textarea does not ednable the Save button Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com At least sometimes, editing a syspref in a textarea (like e.g. opaccredits) will not make the "Save" button active. I have observed this on 3.18.7. Others have possibly sighted it on master too. Workaround: Add and remove one char from a text input to activate the button. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 14626] New: can't save preferences without clicking 'out'
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '15

02 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14626 Bug ID: 14626 Summary: can't save preferences without clicking 'out' Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In Koha 3.18.8 when you edit system preferences you can't save the edits without first clicking out of the preference. It wasn't like this before and is causing great confusion - plus it's an extra click which is always annoying. I think it might be related to http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11464 -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 7947] New: 440/490 Koha Mapping
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '15

02 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7947 Priority: P5 - low Change sponsored?: --- Bug ID: 7947 Assignee: gmcharlt(a)gmail.com Summary: 440/490 Koha Mapping QA Contact: koha.sekjal(a)gmail.com Severity: major Classification: Unclassified OS: All Reporter: nengard(a)gmail.com URL: cgi-bin/koha/admin/koha2marclinks.pl Hardware: All Status: NEW Version: master Component: Cataloging Product: Koha The new Marc standard is that the 490a is the series title, but it's still mapped to 440a here: cgi-bin/koha/admin/koha2marclinks.pl We should probably change the default mapping. Nicole -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 14623] New: Specify due date and offline circulation, overdue fines is not synchronizing.
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '15

01 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14623 Bug ID: 14623 Summary: Specify due date and offline circulation, overdue fines is not synchronizing. Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: os.jerwynfernandez(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Greetings! I have this dilemma using koha version 3.20. The scenario is something like this: For some reasons librarian forgot to check-out a overnight book to his patron, lets say the date is 7/29/2015 the overdue of the book is on 7/30/2015. After a day which is 7/30/2015 the librarian recalled that he forgot to check-out the book to his patron. By using the tool Specify due date he can change the due date back to 7/29/2015. Assuming the overdue fines for this item type is 10.00 per day. Supposedly once the patron returned the book on that same day, koha would automatically synchronize the amount of how much is his overdue fines which is 10.00. However when the librarian check-in the book it did not calculated the fines, the fines is still 0.00. We also tried doing this using koha offline circulation by changing the date to 7/29/2015, and has the same result with 0.00 fines. Note we did it test to koha version 3.18 and it works perfectly specify due date and uploading offline circulation synchronized the overdue fines to 10.00. Thank you and best regards! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 13960] New: Patroncards: Code needs some cleanup / enhancement
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '15

01 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13960 Bug ID: 13960 Summary: Patroncards: Code needs some cleanup / enhancement Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org Parts of the patron card code needs some clean-up, including - if possible get rid of ImageMagick module - enhanced display options (e.g. background image / rotating images) - more options in UI Some background information can be found in comments to Bug 13954 -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 9480] New: Set barcode width and height configurable with system preferences in patron card creator
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '15

01 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9480 Bug ID: 9480 Summary: Set barcode width and height configurable with system preferences in patron card creator Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: vfernandes(a)keep.pt Problem: - barcode width scale is always set to 0.8 of the total width - barcode height scale is always set to 0.01 of total height - happens in 3.8.X, 3.10.X and master code Solution: - create a system preference to control width scale name BarcodeWidthScale (default: 0.8) - create a system preference to control height scale name BarcodeHeightScale (default: 0.01) - change Patroncard.pm to use the variables instead of the default values (if the sysprefs are empty uses the default values). -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 11140] New: Centralize all sending of email to one subroutine
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '15

31 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11140 Bug ID: 11140 Summary: Centralize all sending of email to one subroutine 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To reduce the chances of introducing bugs related to sending emails, and to follow the DRY principle, we should consolidate all calls to sendmail into a single subroutine such that any system preferences or other logic that alters how we send emails can be centralized. For example, bug 8000 and bug 8753, if both pushed, would introduce a bug into Koha if nobody noticed, since there would be no merge conflicts or unit test failures. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 10192] New: Add {ISBN13} as new parameter to OPACSearchForTitleIn
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '15

31 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10192 Bug ID: 10192 Summary: Add {ISBN13} as new parameter to OPACSearchForTitleIn Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de The {ISBN} will only provide you with a ISBN10, never with a ISBN13, even if one is present in the record. This is because we actually force ISBN10 in GetNormalizedISBN. Some newer services need ISBN13 to work correctly, so we should also make that available in the templates and OPACSearchForTitleIn. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 9296] New: overduerules table needs restructuring to allow future extension
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '15

31 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9296 Bug ID: 9296 Summary: overduerules table needs restructuring to allow future extension Classification: Unclassified Change sponsored?: Sponsored Product: Koha Version: master Hardware: All URL: http://intranet/cgi-bin/koha/tools/overduerules.pl OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: mjr(a)software.coop Reporter: mjr(a)software.coop The overduerules table almost hard-wired to three standard notices, with fields like delay1, delay2, delay3. I want to expand it in the future, so I plan to change it to the following: CREATE TABLE `overduerules` ( -- overdue notice status and triggers `overduerules_id` mediumint NOT NULL AUTO_INCREMENT, `branchcode` varchar(10) NOT NULL default '', -- foreign key from the branches table to define which branch this rule is for (if blank it's all libraries) `categorycode` varchar(10) NOT NULL default '', -- foreign key from the categories table to define which patron category this rule is for `delay` int(4) default NULL, -- number of days after the item is overdue that this notice is sent `letter` varchar(20) default NULL, -- foreign key from the letter table to define which notice should be sent `debarred` varchar(1) default 0, -- is the patron restricted when this notice is sent (1 for yes, 0 for no) `typecode` varchar(10) NOT NULL default '1', -- 1 2 3 for first second third, may be extended later PRIMARY KEY (`overduerules_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; I think the existing user interface and cronjob can be made to work with this structure pretty easily. Patch to follow. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 12771] New: Enhancement to manage more than 3 levels of overdue notice
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '15

31 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12771 Bug ID: 12771 Summary: Enhancement to manage more than 3 levels of overdue notice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: francois.charbonnier(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Sponsored by Halland County Library RFC : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement#Enhancement_… Description : A new system preference will be added : "MaxNumberReminders". It will set the maximum number of notifications the system can send. This preference will affect the number of tabs in the « Overdue notice/status triggers » tool. Note : if the librarian changes the settings and reduce the number of reminders, the current trigger settings will be disabled and hidden but not deleted. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11