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

[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 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

[Bug 20283] New: Editing a course item for an inactive course affects the item fields directly
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '20

07 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20283 Bug ID: 20283 Summary: Editing a course item for an inactive course affects the item fields directly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When adding an item to course reserves the values in the items and course_items tables are swapped e.g. items.holdingbranch becomes course_items.holdingbranch and vice versa. When a course is marked inactive, the values are swapped back. When editing an inactive course we modify item values directly. This seems to be because we don't check if the course is active or not. When a course is active ti is correct to modify the items, but if inactive we should only modify course_items To recreate: 1 - Find/create an item with existing values for: item type collection code shelving location holding library staff/public note 2 - Add this item to an active course in course reserves, change all the values 3 - Make the course inactive 4 - Edit the course item, changing all the values 5 - Save and note the changes did not populate to the course reserve 6 - View the item, note the item was changed 7 - Edit the course again, note the dropdowns show the course item values, not the new item values I think we have two options: 1 - Check if a course it active when modifiying a course reserve and adjust the correct table 2 - Don't allow editing of items for inactive courses -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 22087] New: It would be helpful to have City and State visible in member.pl
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22087 Bug ID: 22087 Summary: It would be helpful to have City and State visible in member.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- When a staff member searches for a patron via the search patron box or filters a search through the patron module, they get results on members-home.pl or member.pl. The column for name includes firstname, surname, address and email. It would be beneficial to also see the city and state. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 63

[Bug 24910] New: Make it possible to choose see also-authorities in authority finder
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24910 Bug ID: 24910 Summary: Make it possible to choose see also-authorities in authority finder 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When searching for authorities, sometimes you may see the result you want to select in a see also, but it is not possible to *choose* that one. You have to do another search to get it into the results list of auth finder. Wouldnt it be nice if we could somehow add a link to choose them too? The current link allows you to open them, but this seems less useful at least in our case. Would a preference be useful to switch between choosing or opening ? Or should we add a small link? How could we address that best in terms of styling etc? Your feedback is appreciated ! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 23885] New: Move staff client search results JavaScript into separate file
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23885 Bug ID: 23885 Summary: Move staff client search results JavaScript into separate file Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Coding guideline JS1 (https://wiki.koha-community.org/wiki/Coding_Guidelines#JS1:_Embedding_JavaS…) says "Whenever possible JavaScript should be placed in a separate file." I propose to move most of the JS embedded in results.tt to a separate file. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 25361] New: Support X-Forwarded-* headers
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25361 Bug ID: 25361 Summary: Support X-Forwarded-* headers Change sponsored?: --- Product: Koha Version: master 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Thanks to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23068 we are able to use X-Forwarded-For to pass the client IP via a reverse proxy. Now it would be useful to use other X-Forwarded-* headers like X-Forwarded-Proto in the same way. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8