February 2018 - Koha-bugs - lists.koha-community.org

[Bug 19646] New: value_builder marc21_linking_section template is broken
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '18

05 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19646 Bug ID: 19646 Summary: value_builder marc21_linking_section template is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using marc21_linking_section cataloging plugin, you get the error : Template process failed: undef error - The method selected is not covered by tests! at /home/koha/src/C4/Templates.pm line 122. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 12446] Enable an adult to have a guarantor
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '18

01 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12446 Charles Farmer <charles.farmer(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #64828|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12446] Enable an adult to have a guarantor
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '18

01 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12446 Charles Farmer <charles.farmer(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #64794|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12446] Enable an adult to have a guarantor
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '18

01 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12446 --- Comment #58 from Roch D'Amour <roch.damour(a)inlibro.com> --- Created attachment 72295 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=72295&action=ed… Bug 12446 - Enable an adult to have a guarantor I have rebased the patch and corrected some bugs. It should work now :) Here's the test plan: 1) Apply the patch 2) Run updatedatabase.pl to add AdditionalGuarantorField to preferences and canbeguarantee to categories. 3) Go to patron category administration, edit a category and change the value of Can Be Guarantee to yes (for Child and Professional mostly to set it by default) 4) See below to test various scenarios - Enable an adult to have a guarantor: 0.0) Create or edit a patron category of type 'A'. 0.1) Set the "Can be guarantee" field to "Yes" and save. 1) Select an adult patron -> details tab; 2) Click edit button; 3) validate "guarantor information" fieldset; - Shows guarantees' fines in the guarantor's page: 4) Click Set to patron button and select a guarantor; 5) Generate a fine; 6) Select guarantor patron -> details tab; 7) Validate guarantee's fine information. - Transfer some guarantor's information to the guarantee while adding a guarantiee: 0) Select an adult patron; 1) Insert all information; 2) Click Add guarantiee bouton; 3) Validade Garantor information/Main address/Contact fieldsets filled; - Transfer some guarantor's information to the guarantee while creating a new patron 0) Select an adult patron; 1) Insert all information; 2) Add a new adult patron; 3) Click "Set to patron" button; 4) Select the adult patron from 0); 5) Validade Garantor information/Main address/Contact fieldsets filled; - Transfer some guarantor's information to the guarantee while adding a guarantiee: 0) Select an adult patron; 1) Insert all information; 2) Click Add guarantiee bouton; 3) Validade Garantor information/Main address/Contact fieldsets filled; - Transfer guarantor's alternate address/contact to the guarantee while creating a new patron: 0) Search AdditionalGuarantorField preference; 1) Insert some additional database columns from alternate address/contact to be transferred from guarantor; 2) Select an adult patron; 3) Insert all information; 4) Add a new adult patron; 5) Click "Set to patron" button; 6) Select the adult patron from 0); 7) Validade Garantor information/Main address/Contact fieldsets filled; 8) Validade Garantor additional alternate address/contact filled; - Transfer guarantor's alternate address/contact to the guarantee while adding a guarantiee: 0) Search AdditionalGuarantorField preference; 1) Insert some additional database columns from alternate address/contact to be transferred from guarantor; 3) Select an adult patron; 4) Insert all information; 5) Click Add guarantiee bouton; 6) Validade Garantor information/Main address/Contact fieldsets filled; 7) Validade Garantor additional alternate address/contact filled; Thanks for testing :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12446] Enable an adult to have a guarantor
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '18

01 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12446 Roch D'Amour <roch.damour(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 18849] New: HTML notice affecting display in notice viewer.
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '18

28 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18849 Bug ID: 18849 Summary: HTML notice affecting display in notice viewer. Change sponsored?: --- Product: Koha Version: 16.11 Hardware: Macintosh OS: Mac OS Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kafilini(a)mac.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 64558 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=64558&action=ed… Notice display after sending HTML notice. 1. Holds notice sent in HTML. Can no longer see the content of the notices in patron>notices when clicking on them, even ones that were sent beforehand. The search bar at the top of the page has also been altered, patron image and tabs have been moved down the page. 2. Removed HTML from notice, placed hold and sent notice. All appears normal, can view previous notices etc. Search bar and patron image are appearing normally. 3. HTML reinstated in Holds notice, hold placed and notice sent. Same problems as found in step 1; unable to see notice content, search bar altered, images and tabs moved down the page. Tested in both Chrome and Safari, bug appearing in both browsers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 15504] Track Patron's Last Activity
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '18

28 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 Maksim Sen <maksim.sen(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maksim.sen(a)inlibro.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 19280] New: CanBookBeIssued must take a Koha::Patron in parameter
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '18

28 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19280 Bug ID: 19280 Summary: CanBookBeIssued must take a Koha::Patron in parameter Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org We need to make subroutine from C4 use more Koha::Object objects Seeing bug 19276, starting here is a good start. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 9262] Patch complexity field user interface is awkward to use
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '18

28 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9262 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart(a)bugs.koha-c | |ommunity.org Severity|major |minor -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 7882] Add ability to move and reorder fields in MARC editor
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '18

28 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7882 David Bourgault <david.bourgault(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david.bourgault(a)inlibro.com Status|Failed QA |In Discussion --- Comment #44 from David Bourgault <david.bourgault(a)inlibro.com> --- >There's a more serious issue, however, which isn't caused by this patch but which would become more obvious with it -- if you open the record again in the editor, field order isn't maintained. For example, if you construct your record so that subject headings are in the following order: > >650 $aElizabethan theatre >600 $aShakespeare, William > >Then open it up again in the editor, the 600 will be displayed before the 650, even though the 650 field is stored first in the record. This has the potential to be seriously confusing to users, and I feel that a patch that allows sorting of the fields in a user-specified order needs to be accompanied by work that makes the editor display existing fields in the order that they appear in the record. This raises another question as to how to order the fields when loading a Marc record. Let [1,2,3,4] be the framework structure Let [1,4,2] be the saved record Currently we load on the framework structure order, giving us 1, 2, 3 (empty), 4 This does not respect the saved record order. But if we load according do the saved record order, where should the empty tag (3) go? Should we place it before the saved record's fields or after? Or do some weird half-sorted behavior? before : [3 (empty), 1, 4, 2] after : [1, 4, 2, 3 (empty)] weird : [1, 3 (empty), 4, 2] Let me know if my explanation isn't clear enough. -- You are receiving this mail because: You are watching all bug changes.

1 0