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

[Bug 20497] New: LibraryThing access should using https instead of http
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '18

02 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20497 Bug ID: 20497 Summary: LibraryThing access should using https instead of http 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: kyle(a)bywatersolutions.com QA Contact: 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 20494] New: Remove unused code in neworderempty.pl and addbiblio.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '18

02 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20494 Bug ID: 20494 Summary: Remove unused code in neworderempty.pl and addbiblio.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org z3950authortemplate is referenced in some comments and there are a few other lines commented out that seem to be cruft -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 20392] New: Multiple biblio holding does not work when patron is not set
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '18

02 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20392 Bug ID: 20392 Summary: Multiple biblio holding does not work when patron is not set Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 To recreate: 1) Set the system preference DisplayMultiPlaceHold to enable 2) Search in staff client catalogue 3) On results page check more then one result and click on Place hold button at the top of the page 4) Search for patron, but don't be to specific, you need to have more then one result 5) Click on one of the found patron 6) Now you are going to confirm a hold, but only for one record! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 20506] New: How do I get drop menu help for classification in koha?
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '18

02 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20506 Bug ID: 20506 Summary: How do I get drop menu help for classification in koha? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: manjunath(a)tapmi.edu.in QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl we have installed koha s/w in our library. we are not able to make the s/w auto appenadable field for books, journal issues, project reports separately. we ahave separate Accno/barcode for each item type. similarly, how do we get DDC classno & subject help from current pool of classnos and subject headings in the collection?. we have table of classnos and subejct headings in the book collection. we need the selection help to avoid typo errors. can KOHA community help us? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 2797] Add Summary records to represent summary holdings
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '18

01 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2797 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |DUPLICATE CC| |katrin.fischer(a)bsz-bw.de --- Comment #2 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- *** This bug has been marked as a duplicate of bug 20447 *** -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '18

01 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen(a)gmail.com --- Comment #67 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi David, thx for submitting. Peeking at the code I am not quite sure how it works, but notice it adds a lot of code to C4. Would probably need quite a bit of work. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14224] patron notes about item shown at check in
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '18

01 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14224 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|19772 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19772 [Bug 19772] Wrong success message if CHECKOUT_NOTE is not defined -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9634] Allow for parameters re-use on SQL reports
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '18

01 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9634 --- Comment #12 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- What I think is: Don't make the option, because the chance of messing up existing reports is very very slim. They will remain working as they work now if parameters are named differently. If there exist parameters who already are named the exactly same, the patch will take effect, but then we can also assume that this is indeed the wanted behaviour. Of course we should add a nice note to the release notes to highlight the new feature! -- You are receiving this mail because: You are watching all bug changes.

1 0