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

[Bug 22835] New: Serve static files from plugins through the API
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '20

10 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22835 Bug ID: 22835 Summary: Serve static files from plugins through the API Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The last step to avoid having to tweak (or even depend on) Apache for plugins is having a way to serve static files through the OpenAPI spec. The plugins serving static files would supply a static_files_routes (or similar) method that should return the OpenAPI spec for a directory tree bundled with the plugin itself. This could be done manually, but a way to auto-generate this spec will be added to the KitchenSink plugin so it can be automated through the use of gulp. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[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 22982] New: Paying lost fee does not always remove lost item from checkouts
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22982 Bug ID: 22982 Summary: Paying lost fee does not always remove lost item from checkouts Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Depending on how a lost fee is paid, it may or may not be removed from the patrons current checkouts. The current expected behavior is for the lost item to be removed from the patrons checkouts when the lost fee is paid in full. This is due to the subroutine for handling of lost fees being included in the 'pay specific lines' code but not in the 'pay by amount' code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[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

[Bug 16972] New: ./misc/ sip_cli_emulator.pl should list mandatory vs. optional command line options in its usage section.
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16972 Bug ID: 16972 Summary: ./misc/sip_cli_emulator.pl should list mandatory vs. optional command line options in its usage section. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz As far as I can tell, the following options are mandatory: -a (address) -p (port) -su (sip user) -sp (sip password) -l (sip location/institution) The sip terminator (-t) is not mandatory, but getting it wrong hangs the script without warning. The usage would look like this, more or less: Usage: $0 -a <address> -p <port> -su <sip user> -sp <sip port> -l <location> [--patron <patron barcode>] [--password <patron password>] [-i <item barcode>] [-fa] [-m <message>] [-h] -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 18155] New: Add useful classes to the rows of checkouts table
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '20

04 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18155 Bug ID: 18155 Summary: Add useful classes to the rows of checkouts table 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: rbit(a)rbit.cz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Libraries sometimes ask to have different styling in checkouts table according to the item status such as awaiting reservation. Sometimes they need to highlight special document types. So I would propose to add another CSS classes to those already existing, something like: <tr class="odd group-item -group-item-strong.... itype-book hold-awaiting"> The itype class would be concatenated with an item type code. Maybe a class for item's location and overdue item would be useful as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2