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

[Bug 25964] New: Data loss possible when items are modified
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '20

13 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25964 Bug ID: 25964 Summary: Data loss possible when items are modified Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 23463 Coming from: Bug 23463: Use new method Koha::Object->set_or_blank We have DB fields that are not mapped with MARC fields, for instance paidfor. They are not handled correctly. In ModItemFromMarc, we get a MARC record in parameter and update the item in DB. But we are loosing the fields that are not in the MARC record. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23463 [Bug 23463] Move C4::Items CRUD subroutines to Koha::Item -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 26042] New: Koha/ItemTypes.t is failing with latest MariaDB
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '20

13 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26042 Bug ID: 26042 Summary: Koha/ItemTypes.t is failing with latest MariaDB 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 Failing on Master_D9_MDB_Latest https://jenkins.koha-community.org/job/Koha_Master_D9_MDB_Latest/346/consol… But I recreate on D10 locally. The test is failing with: # Failed test 'item types should be sorted by translated description' # at t/db_dependent/Koha/ItemTypes.t line 137. # got: 'b translated itemtype desc' # expected: 'a translated itemtype desc' # Looks like you failed 1 test of 24. The generated query is (without the full field list): SELECT `me`.`itemtype`, COALESCE( `localization`.`translation`, `me`.`description` ) AS `translated_description` FROM `itemtypes` `me` LEFT JOIN (SELECT localization_id, code, lang, translation FROM localization WHERE entity='itemtypes') `localization` ON ( `localization`.`lang` = 'en' AND `me`.`itemtype` = `localization`.`code` ) ORDER BY `translated_description`; I have removed the transaction and run the query in the MariaDB CLI: *************************** 1. row *************************** itemtype: type1 translated_description: b translated itemtype desc *************************** 2. row *************************** itemtype: type2 translated_description: a translated itemtype desc *************************** 3. row *************************** itemtype: type3 translated_description: description *************************** 4. row *************************** itemtype: woR9bd5 translated_description: nlHDyp MariaDB version is: 10.5.4-MariaDB-1:10.5.4+maria~focal -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 24474] New: Lost items that are checked out are always returned
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '20

10 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24474 Bug ID: 24474 Summary: Lost items that are checked out are always returned 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This was a bug introduced by Bug 22982. "Hey all, this patch is causing problems for some of our libraries because it's been assumed that lost items with no attached charge should automatically be returned. This is not always the desired behaviour - we have one case where the library wants to keep lost items on a patron's record, and another case where a checked out lost item will be renewed, but the amount outstanding is zero, so the item gets returned. These are edge cases, but the assumptions in this patch do not consider them, and are causing problems. Is there a workaround? Or perhaps a better way of doing this patch that can allow for the cases of 'renewing a lost item' or 'wanting to keep a lost item on the checkouts record'? A solution that avoids doing circulation actions in the accounts modules as this patch does would be ideal." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 99

[Bug 23423] New: Online resource links which are OPAC retrieve file references are not correctly formatted in the OPAC detail view
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '20

10 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23423 Bug ID: 23423 Summary: Online resource links which are OPAC retrieve file references are not correctly formatted in the OPAC detail view Change sponsored?: --- Product: Koha Version: 19.05 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: steve(a)softwaremage.co.nz QA Contact: testopia(a)bugs.koha-community.org Created attachment 91946 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=91946&action=ed… Example markup Symptom: Online resources: <a property="url" href="http:///cgi-bin/koha/opac-retrieve-file.pl?id=f445180b2247beac068a3bdef750856b" target="_blank">PDF Views of Acca, Haifa, Mt. Carmel and Other Places</a> | <a property="url" href="http:///cgi-bin/koha/opac-retrieve-file.pl?id=343848fcfdc5123bedf606f5b98110d6" target="_blank">PDF Views of Acca, Haifa, Mt. Carmel and Other Places (Annotated Version)</a> href is malformed: http:///cgi-bin/koha Cause ?? Looks like problem in XSLT (fragment from MARC21slim2OPACDetail.xsl) <xsl:if test="not(contains(marc:subfield[@code='u'],'://'))"> <xsl:choose> <xsl:when test="@ind1=7"> <xsl:value-of select="marc:subfield[@code='2']"/><xsl:text>://</xsl:text> </xsl:when> <xsl:when test="@ind1=1"> <xsl:text>ftp://</xsl:text> </xsl:when> <xsl:otherwise> <xsl:text>http://</xsl:text> </xsl:otherwise> </xsl:choose> Note these same resource links are correct in the opac search view. Online access: <a target="_blank" href="/cgi-bin/koha/opac-retrieve-file.pl?id=f445180b2247beac068a3bdef750856b">PDF Views of Acca, Haifa, Mt. Carmel and Other Places</a> | <a target="_blank" href="/cgi-bin/koha/opac-retrieve-file.pl?id=343848fcfdc5123bedf606f5b98110d6">PDF Views of Acca, Haifa, Mt. Carmel and Other Places (Annotated Version)</a> If one explicitly adds the full path to the 856u URI these are correctly referenced in the resulting markup. Relative paths are not. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 24742] New: Can't save news item in strict mode without value in number field
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '20

10 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24742 Bug ID: 24742 Summary: Can't save news item in strict mode without value in number field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org If strict mode is enabled, you can't save a news item without putting a number in the "Appears in position" field. The operation fails silently and this error appears in the log: DBD::mysql::st execute failed: Incorrect integer value: '' for column 'number' at row 1 [for Statement "UPDATE opac_news SET number = ?,expirationdate = ?,lang = ?,timestamp = ?,title = ?,branchcode = ?,content = ? WHERE idnew = ?;" with ParamValues: 0="", ... ] at /kohadevbox/koha/C4/NewsChannels.pm line 106. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 26072] New: Add ability to *not* force holds to be placed via the REST API even if AllowHoldPolicyOverride is enabled
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '20

07 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26072 Bug ID: 26072 Summary: Add ability to *not* force holds to be placed via the REST API even if AllowHoldPolicyOverride is enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com There are use cases where we need to be able to place holds via the API, but not place holds that are in violation of the current holds policy. If AllowHoldPolicyOverride is enabled, holds placed via the API will succeed regardless of violations of the current hold rules. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 16935] New: launch export_records.pl with deleted_barcodes param fails
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '20

07 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16935 Bug ID: 16935 Summary: launch export_records.pl with deleted_barcodes param fails Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: stephane.delaune(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz when I launch /home/koha/src/misc/export_records.pl with this command line : ~/src/misc/export_records.pl --date=`date +%d/%m/%Y` --deleted_barcodes --filename=/home/koha/test I've got this error message : DBD::mysql::db selectall_arrayref failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 4 [for Statement " ( SELECT DISTINCT barcode FROM deleteditems WHERE deleteditems.biblionumber = ? "] at /home/koha/src/misc/export_records.pl line 189. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 24820] New: The cashup workflow should use the static 'date' field rather than the transient 'timestamp' field in accountlines
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '20

07 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24820 Bug ID: 24820 Summary: The cashup workflow should use the static 'date' field rather than the transient 'timestamp' field in accountlines Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: martin.renvoize(a)ptfs-europe.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The 'cashup' process introduced in bug 23355 assumes that once set, the timestamp of an accountline is fixed. This assumption is incorrect as the timestamp is a 'last updated' time and as such is transient. We should be using the 'date' field for comparisons instead as this field is a fixed 'created on' record. -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 21268] New: Can’t add to basket from staged file if base-level allocated is zero
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '20

07 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21268 Bug ID: 21268 Summary: Can’t add to basket from staged file if base-level allocated is zero Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org We recently carried out fiscal period close, and as we are not permitted to move remaining unspent funds we ended up with negative amounts in Total Available (due to open orders rolling forward into the new fiscal period, of course). We did not get around to adding any amounts so all Base-level allocated amounts remained zero. Since the fiscal period close we have been able to add to baskets using options OTHER than from a staged file. Selecting this option sees the Fund dropdown box (in the Default Accounting Details tab) not effective. We cannot see any of the funds. Once base-level allocated amounts are increased from zero this problem vanishes- funds are visible and selectable in the Fund pull-down. This is not a major problem, but it is a puzzle that this problem only appears with the stage file option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 23727] New: Editing course reserve items is broken
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '20

07 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23727 Bug ID: 23727 Summary: Editing course reserve items is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Adding an item to course reserves and trying to edit any values in a second step does not work. Values are not saved and the table shows all values as "Unchanged". To test: - Create a new course - Find an item, make sure it has a location set - Add the item to the course, leave all values unchanged - Edit the course item - Change all the values - Verify the table still says "Unchanged" - Verify the table doesn't show the location - Edit the item again - Verify the changed values don't show -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 81