April 2016 - Koha-bugs - lists.koha-community.org

[Bug 16114] New: Regression: Bug 14828 broke display of localized item type descriptions
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '18

05 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16114 Bug ID: 16114 Summary: Regression: Bug 14828 broke display of localized item type descriptions Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/catalogue/itemsearch.pl OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration 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 If you have defined a translation for an item type (Administration -> Item types -> Edit -> Translate into other languages), the item type description is not displayed correctly in the item search form (catalogue/itemsearch.pl). Instead you see something like "Koha::Localization=HASH(0x849c980)" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 15730] New: 500 error on returns.pl if barcode doesn't exist
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '18

05 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15730 Bug ID: 15730 Summary: 500 error on returns.pl if barcode doesn't exist Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a librarian enters a barcode that does not match an item in the database, a 500 error will be displayed instead of the "No item with barcode" message. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 15879] New: Allow multiple plugin directories to be defined in koha-conf.xml
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '18

22 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15879 Bug ID: 15879 Summary: Allow multiple plugin directories to be defined in koha-conf.xml Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be very useful to be able to define multiple plugin directories in the Koha conf file. This would allow for ease of plugin development so that each plugin installed can live in its own git repository. For compatibility, the first plugindir instance defined should be the one used for uploading plugins via the web interface. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 16365] New: Selectively introduce GetMarcStructure() "unsafe" variant for better performance
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '18

13 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16365 Bug ID: 16365 Summary: Selectively introduce GetMarcStructure() "unsafe" variant for better performance Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org GetMarcStructure() currently uses Koha::Cache in the "safe" mode (returning deep copy of the result data structure by default), which causes numerous performance issues in many Koha scripts. Switching it to the "unsafe" mode globally (2nd patch from Bug 16140) resolves those issues, but ensuring that it is regression-free (and that it will stay that way in the future) is far from easy. This patch proposes a bit more manageable solution, it introduces a possibility to use "unsafe" variant selectively (only in those places in the code where GetMarcStructure() is called repetively). That way, amount of the code that needs to be audited for possible problems gets vastly reduced, without any performance trade-offs. -- You are receiving this mail because: You are watching all bug changes.

1 29

[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 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 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 15937] New: Batch checkout buggy behavior
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '18

09 Jan '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15937 Bug ID: 15937 Summary: Batch checkout buggy behavior 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: hector.hecaxmmx(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 1920 For damaged items the warning message is not displayed, and Koha let to checkout the item as shown in the image. <https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=48411> I notice about a buggy behavior in this functionallity, for example the program let to checkout the first item available without confirm the checkout message, for example, Maxwell's handbook was borrowed/renewed to this patron every time in which I repeat the process. When the process end, you will presented with this table (<https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=48412>), one items was checked-out and the others wasn't, but the message is not clear whether those items was checked out or not. Another thing that I could observe is: if circ policies only allow an specific number e.g. two checkouts and two renews of an item the module doesn't let to checkout if patron has one or more checkouts and the message displayed for the program is not clear; If MaxFine is set affect in the checkouts and don't let us checkout as show in the previous image, and as before, the message doesn't provide an adequate information. NOTE: The images presented in this bug, they are obtained by applying bug 15920. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1920 [Bug 1920] Total price not saving to order -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 16239] New: Upgrade Bootstrap in the staff client
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '17

04 Dec '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16239 Bug ID: 16239 Summary: Upgrade Bootstrap in the staff client 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 Depends on: 15883 Blocks: 14546 Now that we are on a path to getting a jQuery upgrade, it's time to start working on an upgrade to Bootstrap in the staff client. I propose that this upgrade be done as a precursor to (rather than simultaneously with) a full conversion of the staff client to a Bootstrap grid (Bug 14546). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14546 [Bug 14546] Make staff client templates responsive https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15883 [Bug 15883] Upgrade jQuery from v1.7.2 in the staff client -- You are receiving this mail because: You are watching all bug changes.

1 119

[Bug 16069] New: XSS issue in basket.pl page
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '17

28 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16069 Bug ID: 16069 Summary: XSS issue in basket.pl page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: amitddng135(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com XSS issue in basket.pl page -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6