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

[Bug 21115] New: Add multi_param call and add divider in cache key in svc/report and opac counterpart
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21115 Bug ID: 21115 Summary: Add multi_param call and add divider in cache key in svc/report and opac counterpart Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CGI::param called in list context from package CGI::Compile::ROOT::usr_share_koha_prodclone_opac_svc_report line 42, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 21291] New: request-article.pl doesn't show MARC, LabeledMARC and ISBD in sidebar
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21291 Bug ID: 21291 Summary: request-article.pl doesn't show MARC, LabeledMARC and ISBD in sidebar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When on a detailed record in the intranet, any click on the sidebar will lead you to another page with the same sidebar EXCEPT for "Article requests". When clicking on article requests, you get a new sidebar without MARC Labeled MARC ISBD -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 21113] New: Hint Messages are misleading at "Merge Selected Patrons" in Patron Lists
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21113 Bug ID: 21113 Summary: Hint Messages are misleading at "Merge Selected Patrons" in Patron Lists Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: ultron960x(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 77251 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=77251&action=ed… The message is suitable to display upon "Remove Selected" or "Remove Selected Patrons" buttons clicked but the "Merge Selected Patrons" ones. In patron lists, There are two functions for us to handle patrons: "Removed Selected Patrons" and "Merge Selected Patrons". However, even for "Merge Selected Patrons" both , the messages showed either "Are you sure you want to remove the selected patrons?" or "You must select one patron or more patrons to remove." given that one had clicked selected patrons beforehand. It seemed the original files of translations or phases didn't have separate message contents for them individually. (Please check the link as well as the attached image: http://translate.koha-community.org/en_GB/18.05/translate/en-GB-staff-prog.… ) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 21365] New: Advanced MARC Editor - Rancor - BiblioAddsAuthorities not working
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21365 Bug ID: 21365 Summary: Advanced MARC Editor - Rancor - BiblioAddsAuthorities not working Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: ere.maijala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 19687] New: Recent upgrade to 17.05.04.000 bulkmarcimport started to fail
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19687 Bug ID: 19687 Summary: Recent upgrade to 17.05.04.000 bulkmarcimport started to fail 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: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org After recent upgrade to 17.05.04.000 bulkmarcimport started to fail on all items attempted to be added. ERROR: Adding items to bib 1 failed: Undefined subroutine &C4::Items::TransformMarcToKoha called at /usr/share/koha/lib/C4/Items.pm line 382, <GEN46> line 1 So I manually added the prefix and the next error came up: ERROR: Adding items to bib 74925 failed: Undefined subroutine &C4::Items::GetMarcStructure called at /usr/share/koha/lib/C4/Items.pm line 2307, <GEN46> line 14. Manually adding the prefix to that line seems to have worked, but it does not feel like the right solution. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 21320] New: Holds to pull should honor syspref AllowHoldsOnDamagedItems
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21320 Bug ID: 21320 Summary: Holds to pull should honor syspref AllowHoldsOnDamagedItems 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: dpavlin(a)rot13.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 21426] New: setting USE_MEMCACHED to "no" in koha-sites.conf does not have any effect
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21426 Bug ID: 21426 Summary: setting USE_MEMCACHED to "no" in koha-sites.conf does not have any effect Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P3 Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: arouss1980(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I recently set up a new Koha 18.05 instance for testing and decided not to use memcached. So, in /etc/koha/koha-sites.conf I set the USE_MEMCACHED variable to "no" and ran `koha-create --create-db dev`. Oddly enough, once my instance was up and running I noticed that a memcached process had been started (Home > About Koha in the Staff interface also reported memcached as running). Apparently, setting USE_MEMCACHED to "no" does no longer have any effect because (as of Bug 18342) memcached is enabled by default for new installs. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 21389] New: Javascript error on article requests page bis
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21389 Bug ID: 21389 Summary: Javascript error on article requests page bis Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 21076 fixed a Javascript error on article requests page when patron is found. There is also an error when patron is not found, with message : Patron not found No patron with this name, please, try another -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 20941] New: Displaying requests does not display request material type
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20941 Bug ID: 20941 Summary: Displaying requests does not display request material type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com I'm not sure when this crept in. At some point we switched from storing material type in illrequests.medium to an arbitrary attribute in illrequestattributes. However, the display end of things wasn't updated accordingly. As such, material type doesn't display in any of the UIs, it should! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 65

[Bug 16420] New: Buttons inconsistent between "Hold found" and "Hold found (waiting)" dialogs in checkin
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16420 Bug ID: 16420 Summary: Buttons inconsistent between "Hold found" and "Hold found (waiting)" dialogs in checkin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com "Hold found": "Confirm hold", "Print slip and confirm" and "Ignore" "Hold found (item is already waiting)": "Confirm", "Cancel hold", "Print and confirm" We should settle on one ordering and wording; the current approach is both bad for translators and confusing for librarians. It's all too easy to reach for the middle button out of muscle memory and cancel a hold! I would argue that the wording and ordering of the "Hold found" dialog is more natural, so the waiting dialog should be changed to the following: "Confirm hold", "Print slip and confirm", "Cancel hold" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12