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

[Bug 16246] New: Return all reserves columns in ILS-DI GetRecords response
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '18

06 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16246 Bug ID: 16246 Summary: Return all reserves columns in ILS-DI GetRecords response Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Web services Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The list of reserves fields returned in ILS-DI GetRecords response is arbitrary. Instead we should return all the fields available in reserves table -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 17091] New: Add AUTOLOAD to Koha::Objects
by bugzilla-daemon＠bugs.koha-community.org 05 Feb '18

05 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17091 Bug ID: 17091 Summary: Add AUTOLOAD to Koha::Objects Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement 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 Up to now if a Koha::Objects based object needs to call DBIx::Class methods, we have to create a new method for Koha::Objects, something like: sub method { my $self = shift; return $self->_resultset->method } To simplify and ease the call to DBIx::Class method, we could create an AUTOLOAD method. -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 16213] New: Allow to select hold's itemtype when using API
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '18

02 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16213 Bug ID: 16213 Summary: Allow to select hold's itemtype when using API 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: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 13903, 15533 Bug 15533 bring the capability to select an itemtype for a title-level hold in staff and OPAC. This should be possible through the API too. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13903 [Bug 13903] Add API routes to list, create, update, delete reserves https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15533 [Bug 15533] Allow patrons and librarians to select itemtype when placing hold -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 17682] New: Change URL for Google Scholar in OPACSearchForTitleIn
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '18

02 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17682 Bug ID: 17682 Summary: Change URL for Google Scholar in OPACSearchForTitleIn 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: felix.hemme(a)thulb.uni-jena.de QA Contact: testopia(a)bugs.koha-community.org Google Scholar is no longer accessible via <a href="http://www.scholar.google.com/scholar?q={TITLE}" target="_blank">Google Scholar</a>. It should be changed to the current url <a href="https://scholar.google.com/scholar?q={TITLE}" target="_blank">Google Scholar</a>. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 15876] New: Removing a course-reserved item with no initial shelving location does not revert items.location to NULL
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '18

01 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15876 Bug ID: 15876 Summary: Removing a course-reserved item with no initial shelving location does not revert items.location to NULL Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org (This happens only when one changes the shelving location while the item is on a course_reserve) Steps to replicate: 1) Find an item with NO shelving location info (ie one that has items.location=items.permanent_location=NULL in the DB and the OPAC/Intranet shows an empty string) 2) Add this item to a course reserve 3) Either when adding the item in the course reserve, or at a later stage CHANGE (from the course reserve screen!) the 'temporary' shelving location info that will be used by that course reserve, by selecting a value from the drop-down list. Let's say 'On Display' 4) Find the item in the OPAC or Intranet, the change is displayed (as expected) 5) REMOVE this specific item from the course reserve 6) Find the item again in the OPAC or Intranet. All the course-reserve related information is reverted back to the original values as expected, except the shelving location, which is NOT reverted back to 'empty'. The old value (in our example 'On Display') is still shown!. FYI, NULL is added from items.location to course_items.location in step 2 as expected However, that NULL value in NOT copied back to items.location or items.permanent_location in step 5 as expected, but instead the value from step 3 is retained. (I have verified this behavior both with 3.20 and 3.22) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 16603] New: When processing uploaded offline circulation file, "apply directly" option fails
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '18

31 Jan '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16603 Bug ID: 16603 Summary: When processing uploaded offline circulation file, "apply directly" option fails Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/offline_circ/process_koc.pl OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I have an offline circulation file which was generated by the Windows offline circulation program. If I upload this file and choose "Add to offline circulation queue" it works as expected. If I upload the same file and choose "Apply directly," the process never completes. Firebug shows a seemingly never-ending series of calls to /cgi-bin/koha/tools/background-job-progress.pl?jobID=8c20822320e5fbd7579aa1f61411ba00 but nothing happens. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 18312] New: Export is broken unless a file is supplied
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '18

30 Jan '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18312 Bug ID: 18312 Summary: Export is broken unless a file is supplied Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Tools Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Bug 18087 breaks export unless a file is supplied -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 18083] New: Don't show 'library' selection on popular titles page for single-branch libraries
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '18

23 Jan '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18083 Bug ID: 18083 Summary: Don't show 'library' selection on popular titles page for single-branch libraries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org On the 'popular titles' page in the OPAC there is a search filter labelled "From" that offers you to select a library branch. For a library with only one branch this makes no sense and it would be nice if it was automatically hidden for single-branch libraries. Note: Currently not possible to hide with CSS only either. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 18183] New: jQuery append error related to script tags in cloneItemBlock
by bugzilla-daemon＠bugs.koha-community.org 22 Jan '18

22 Jan '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18183 Bug ID: 18183 Summary: jQuery append error related to script tags in cloneItemBlock 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org This is a strange javascript error that I experienced on a 3.22 system and could not reproduce with the current (modified) framework in master. But since the code is essentially the same, it might still be possible. The js error is: TypeError: document.getElementById(...) is null The line in koha-tmpl/intranet-tmpl/prog/js/additem.js that causes this error is: $(clone).append(data); While running append, jQuery seems to call .domManip and .globalEval internally. The result on the interface is that you do not have an item block when receiving an order (AcqCreateItem=receiving). Note that data comes from services/itemrecorddisplay.pl and is a very long string containing all item fields and even script tags for plugins. Between the ACQ framework in 3.22 and in master (copied from Default), I noticed some smaller changes in the lines for plugins. Since the js variable "clone" contains a jQuery object for an element that is not yet added to the page, I could imagine a getElementById error. But it does not always occur, so some other condition must be triggered too. This condition appears to be connected to the script tags, since removing all plugins from the ACQ framework in 3.22 made the error disappear (no solution however). Some interesting comments on jQuery's handling of appending script tags are found in http://stackoverflow.com/questions/610995/cant-append-script-element Triggered by the getElementById error, I rearranged a few lines in cloneItemBlock so that I appended clone (the 'floating' div field for the new item) first to the outeritemblock div on the page and after that I appended the data string (item fields and script tags) to clone. This resolved the js error on 3.22 and did not affect master. Conclusion: We seem to stumble over a problem with our plugin script tags in jQuery's script evaluation when clone is not bound to the page yet. The proposed patch just adds this workaround touching three lines. If we would like to change (again) the way we handle script tags for plugins, we will need much more effort. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 18242] New: Remove primary key on old_issues.issue_id
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '18

18 Jan '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18242 Bug ID: 18242 Summary: Remove primary key on old_issues.issue_id 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 The table old_issues has a primary key defined on the issue_id column. This issue_id comes from the issues table when an item is checked in. In some case the value of issue_id already exists in the table Basically this happens when an item is returned and mysqld is restarted: The auto increment value for issues.issue_id will be reset to MAX(issue_id)+1 (which is the value of the last entry of old_issues). See also the description of bug 18003 for more informations. -- You are receiving this mail because: You are watching all bug changes.

1 49