March 2017 - Koha-bugs - lists.koha-community.org

[Bug 17706] New: MARC staging fails with "Upload status: Denied" when memcached is enabled
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17706 Bug ID: 17706 Summary: MARC staging fails with "Upload status: Denied" when memcached is enabled Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org In 16.11.00 with memcached enabled, staging MARC records fails with "Upload status: Denied". It works after disabling memcached. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 17694] New: Add human friendly REST documentation
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17694 Bug ID: 17694 Summary: Add human friendly REST documentation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: benjamin.rokseth(a)kul.oslo.kommune.no, brendan(a)bywatersolutions.com, jonathan.druart(a)bugs.koha-community.org, koha-bugs(a)lists.koha-community.org, lari.taskula(a)jns.fi, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 16212, 17432 With Bug #17432 we allowed the output of a computer friendly json representation of the swagger specification. We should now add a human friendly 'pretty' form too. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16212 [Bug 16212] Swagger specification separation and minification https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17432 [Bug 17432] Remove requirement to minify swagger.json -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 17581] New: Have possibility to edit due date to avoid to do a renewal
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17581 Bug ID: 17581 Summary: Have possibility to edit due date to avoid to do a renewal 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: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, It would be fine to have possibility to edit due date for a loan in progress to avoid to do a renewal. Only for staff. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 17514] New: Record details page uses incorrect class "results_summary "
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17514 Bug ID: 17514 Summary: Record details page uses incorrect class "results_summary" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The record details page re-uses the class results_summary which is semantically incorrect and causes unwanted interactions with the styling of the actual results page which also uses the results_summary class. We should change the instances of the results_summary class to details_summary on this page. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 17474] New: Make possible to create fee after hold is filled and checked out to patron
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17474 Bug ID: 17474 Summary: Make possible to create fee after hold is filled and checked out to patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 17463] New: Wrong recipient for suggestion' s notice in branch specific
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17463 Bug ID: 17463 Summary: Wrong recipient for suggestion's notice in branch specific 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: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org Hi, There is test plan to understand the problem: Branch A with borrower A and librarian A, Branch B with librarian B Notice ACCEPTED, ORDERED, AVAILABLE set to each branch - borrower A done a suggestion A - librarian from branch A accepted suggestion A - email for suggestion ACCEPTED sent to borrower A - librarian from branch A ordered suggestion A, a biblio is created (biblio A) - email for suggestion ORDERED sent to borrower A - librarian from branch B ordered an other copy from the same biblio A (not from suggestion A, really from biblio A) - Order from librarian B is also related to suggestion A : this is the problem. - librarian B received his item before librarian A - email for suggestion AVAILABLE sent to borrower A while item for branch A is not arrived yet. Do you understand me? Order from an other branch for the same biblio should not be related to the initial suggestion. Regards, Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 17440] New: Checkout notes ignores OPAC description in OPAC
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17440 Bug ID: 17440 Summary: Checkout notes ignores OPAC description in OPAC Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 56416 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=56416&action=ed… Screenshot of how message displays in OPAC If a user sets up a BOR_NOTES authorised value with a staff and OPAC description, and then uses the Add messages option in the /cgi-bin/koha/circ/circulation.pl screen, when the message is viewed in the OPAC only the staff description displays. If a message in the messages database table is given a message_type of B, then the OPAC description should display. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 17371] New: REST API: add CRUD for biblios
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17371 Bug ID: 17371 Summary: REST API: add CRUD for biblios Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: benjamin.rokseth(a)kul.oslo.kommune.no QA Contact: testopia(a)bugs.koha-community.org This bug proposes to add full CRUD for biblios to the REST API, meaning a basic endpoint for managing records outside of Koha staff. It will make use of Koha Objects and largely replicate the /svc/biblios functionality, but from a RESTful perspective. Proposed routes : GET /api/v1/biblios/{biblionumber} Get a simple record GET /api/v1/biblios/{biblionumber}/items Get a record with items GET /api/v1/biblios/{biblionumber}/expanded Get a record with items and item statuses POST /api/v1/biblios/{biblionumber}/{frameworkcode} Create a record with items (and optional framework) PUT /api/v1/biblios/{biblionumber}/{frameworkcode} Update a record without touching items (and optional framework) DELETE /api/v1/biblios/{biblionumber} Delete a record with items POST and PUT will take marcxml as input -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[Bug 17354] New: Group By/Order By SQL mismatch in issues_stats.pl
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17354 Bug ID: 17354 Summary: Group By/Order By SQL mismatch in issues_stats.pl Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: jcoehoorn(a)york.edu QA Contact: testopia(a)bugs.koha-community.org I'm looking in intranet/cgi-bin/reports/issues_stats.pl. I'm not sure of the exact line number, since I may have changed some white space earlier in the file on my system while tracking this down, but near line 350 in that file you'll see this: $colorder = ($colfield =~ /dayname/) ? "weekday($column)" : ($colfield =~ /^month/ ) ? " month($column)" : $colfield; The $colorder value will be used in the ORDER BY clause for the final SQL statement for the report. Contrast that with this code from earlier in the file, which will be used for the GROUP BY and SELECT clauses: $colfield = ($dsp == 1) ? " dayname($column)" : ($dsp == 2) ? "monthname($column)" : There's a clear mismatch here. The earlier snippet should be using "monthname()" instead of "month()", to match the GROUP BY syntax. I found this while playing with Ubunutu 16.04/MySql 5.7. I have turned strict mode off in MySql 5.7, but even with strict mode off the Circulation Report listed under "Statistics Wizards" was broken when I tried to group by month. I suspect grouping by day will be broken as well. The report works as expected for grouping by month after changing to use the monthname() function. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 17133] New: DE Startseite
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17133 Bug ID: 17133 Summary: DE Startseite Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: mirko(a)abunchofthings.net Übersetzung der Startseite -- You are receiving this mail because: You are watching all bug changes.

1 5