April 2019 - Koha-bugs - lists.koha-community.org

[Bug 21774] New: Subfield clone fields dissapear when editing a record
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '20

13 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21774 Bug ID: 21774 Summary: Subfield clone fields dissapear when editing a record Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jesus(a)medios.es QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When editing an item record that has repetable subfields, these subfields dissapear on the editing screen in those records that have more than one value. - On the cataloging screen (basic screen), create a new record - Go to a field with repetable subfields and associated with authorised values CCODE - Select a value for the subfield 952$8) - Clone the subfield - select another value for the new subfield - Save the record - Edit the record to modify => the clone subfields have disappeared. Seems to be related to bug 17818 Verified happening on 17.11.04 and 18.05.05-1 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 20419] New: Current location not updated correctly on the return of a reserved item
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '20

13 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20419 Bug ID: 20419 Summary: Current location not updated correctly on the return of a reserved item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Circulation Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At present when a reserved item is returned to a library branch which is not the branch set as the pickup location for the reserve then after clicking the 'Confirm hold and transfer' button on the return modal box the items current location is set to the pickup location even though the item is actually in transit. The current location of the item should be set as the branch that the item was returned to whilst in transit and only change to the pickup location when it checked in at the pickup location branch. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 17483] New: Forgiving charge should apply to item's last fine.
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '20

11 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17483 Bug ID: 17483 Summary: Forgiving charge should apply to item's last fine. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When returning an item with a fine, if the Forgive checkbox is clicked, this forgives the first accountline associated to the item/user, not the current/latest as it should. Scenario (Real world): - A patron returns a book late, ensuring a 5$ fine. Does not pay it. - The patron borrows the book again 3 months later. Gets late again, and fined 2$. - Great timing: The library offers amnesty for a week. Bring back your book and we'll forget that they're late. - On checkin, the librarian clicks "Forgive overdue charges" and scan the book. - Koha cancels the 3-months-ago 5$ fine. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 22331] New: Lost items that are written off gives credit when returned
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '20

11 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22331 Bug ID: 22331 Summary: Lost items that are written off gives credit when returned Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bdaeuber(a)cityoffargo.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- When a lost item is written off by the library, but later returned, Koha gives a credit for that item. To recreate: 1. Ensure "Refund lost item fee" is set to "Yes" in Circulation and Fine Rules. 2. Check out an item to a patron. 3. Mark item as lost. Replacement price should be added to their account. 4. Write off the fee. 5. Return the item. A refund is generated. A write off should not generate a refund in this situation. Is it possible this is related to Bug 19919 ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 19634] New: Advanced editor - Rancor - error in display of macro editor in firefox
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '20

10 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19634 Bug ID: 19634 Summary: Advanced editor - Rancor - error in display of macro editor in firefox Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: 0 - Use firefox 1 - Open the advanced editor 2 - Click 'new macro' 3 - name it 4 - the editor window has only one line This js is a workaround for the moment: $(document).ready(function(){ $("#macro-editor").closest("div.row").css("height","100%"); }); -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 22064] New: Allow to change due date of an item without requiring checkin or renewal
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '20

08 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22064 Bug ID: 22064 Summary: Allow to change due date of an item without requiring checkin or renewal Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Sometimes it woudl be helpful if it was possible to change the due date of an item without generating an e-mail by renewing or checkin/checkout. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 18231] New: Add the missing id-column to koha.issuingrules-table for DBIC fixtures
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '20

08 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18231 Bug ID: 18231 Summary: Add the missing id-column to koha.issuingrules-table for DBIC fixtures 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Test::DBIx::Class fixtures won't work if the resultset doesn't support last_insert_id. This is only supported with a integer primary key. This patch adds one to issuingrules. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 17885] New: Koha::SearchEngine::Elasticsearch-> reset_elasticsearch_mappings throws DBD::mysql Duplicate entry exceptions
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17885 Bug ID: 17885 Summary: Koha::SearchEngine::Elasticsearch->reset_elasticsearch _mappings throws DBD::mysql Duplicate entry exceptions 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 20766] New: KohaPlugins.t does not clean up
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20766 Bug ID: 20766 Summary: KohaPlugins.t does not clean up Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 20181 The tests pass but the DB is altered if plugins exist: prove t/Koha_Template_Plugin_KohaPlugins.t 1 ↵ [12:36:11] t/Koha_Template_Plugin_KohaPlugins.t .. 1/10 DBD::mysql::db do failed: Table 'koha_plugin_com_bywatersolutions_kitchensink_mytable' already exists [for Statement " CREATE TABLE koha_plugin_com_bywatersolutions_kitchensink_mytable ( `borrowernumber` INT( 11 ) NOT NULL ) ENGINE = INNODB; "] at /var/lib/koha/kohadev/plugins/Koha/Plugin/Com/ByWaterSolutions/KitchenSink.pm line 303. Plugin Koha::Plugin::Com::ByWaterSolutions::KitchenSink failed during installation! at /home/vagrant/kohaclone/Koha/Plugins/Base.pm line 51. t/Koha_Template_Plugin_KohaPlugins.t .. 7/10 DBD::mysql::db do failed: Table 'koha_plugin_com_bywatersolutions_kitchensink_mytable' already exists [for Statement " CREATE TABLE koha_plugin_com_bywatersolutions_kitchensink_mytable ( `borrowernumber` INT( 11 ) NOT NULL ) ENGINE = INNODB; "] at /var/lib/koha/kohadev/plugins/Koha/Plugin/Com/ByWaterSolutions/KitchenSink.pm line 303. Plugin Koha::Plugin::Com::ByWaterSolutions::KitchenSink failed during installation! at /home/vagrant/kohaclone/Koha/Plugins/Base.pm line 51. t/Koha_Template_Plugin_KohaPlugins.t .. ok Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20181 [Bug 20181] Allow plugins to add CSS and Javascript to OPAC -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 20626] New: Fines are recalculated and removed on SIP checkin
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20626 Bug ID: 20626 Summary: Fines are recalculated and removed on SIP checkin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When a patron has an accruing fine (code FU) for an item, and that item is returned, there are some parts of the logic that causes unexpected consequences. All of the following assumes CalculateFinesOnReturn is not active. The following happens when the issuing rule fine value is set to 0. If the return is made via the staff interface, and no explicit return date is set, the item is returned, and the fine is changed to code F, but amount remains. If the return is made via the staff interface, with an explicit return date, the item is returned, and the fine is changed to code F, but the amount is cleared. This is documented in a comment in the code as the expected behaviour. If the return is made via the SIP2 protocol, it will always have an explicit return date, because the date is set from the SIP reply. Therefor the amount will be cleared. This is unexpected since the SIP checkins aren't backdated returns. When the issuing rule fine value is set to higher than 0, similar things happen, except it will change the fine instead of clearing it. Again, this is unexpected for SIP checkin. With no expected backdating, and CalculateFinesOnReturn disabled, I'd expect fine amounts to remain untouched. A very simple fix is of course to change C4/SIP/ILS/Transaction/Checkin.pm and simply not send $return_date to AddReturn(). I don't know if this is a proper solution or not. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3