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

[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 26060] New: Replace staff interface table sort icons with SVG
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26060 Bug ID: 26060 Summary: Replace staff interface table sort icons with SVG 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 DataTables in the staff interface have sorting icons added to the headers via a background PNG image in a data-url. I suggest we replace these with SVG images which will look better, especially on higher-resolution screens. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 26063] New: Use Koha::Plugins->call for circulation hooks
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26063 Bug ID: 26063 Summary: Use Koha::Plugins->call for circulation hooks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 24031 introduced the handy method and we should use it instead of using in-place helpers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[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

[Bug 21094] New: Syndetics: always use https instead of http
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '20

05 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21094 Bug ID: 21094 Summary: Syndetics: always use https instead of http Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: katrin.fischer(a)bsz-bw.de, kyle(a)bywatersolutions.com, testopia(a)bugs.koha-community.org Blocks: 17137 As per bug 17137, we should be using SSL for all external resources. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17137 [Bug 17137] Omnibus: Always use SSL when referencing external sources -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 20375] New: Add a new permission for managing invoices
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '20

05 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20375 Bug ID: 20375 Summary: Add a new permission for managing invoices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Invoices are currently accessible for patrons with any acquisition permission. We should clean this up and have a separate permission for managing invoices. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 22936] New: /patrons Showing Error
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '20

05 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22936 Bug ID: 22936 Summary: /patrons Showing Error Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: muneebkalathil(a)yahoo.com Target Milestone: --- I am getting The below error while using /patrons Route "errors": [ { "message": "Expected string - got null.", "path": "/1/updated_on" }, : : { "message": "Expected string - got null.", "path": "/1000/updated_on" }, It was working on 17.11 and I upgraded to 18.11, It is showing this error. When I try with a fresh Install(18.11), the route is working. /patrons/{patronid} is working though. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2