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

[Bug 15758] New: Move the C4::Branch related code to Koha::Libraries - part 4
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '21

23 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15758 Bug ID: 15758 Summary: Move the C4::Branch related code to Koha::Libraries - part 4 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 Depends on: 15629 Blocks: 15293 This fourth and last part will remove: - GetBranchName - GetBranchesLoop - GetBranches - GetBranch will move mybranch and onlymine to C4::Context and finally remove all occurrences of C4::Branch. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15293 [Bug 15293] Move the C4::Branch related code to Koha::Libraries https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15629 [Bug 15629] Move the C4::Branch related code to Koha::Libraries - part 3 -- You are receiving this mail because: You are watching all bug changes.

1 169

[Bug 16181] New: Limit number of tags loaded initially for tag cloud
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '21

09 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16181 Bug ID: 16181 Summary: Limit number of tags loaded initially for tag cloud 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a patron has an large number of tags (say 3,421) the tag cloud takes an inordinately long time to load. Maybe we could enforce a limit on initial load and then allow user to load more or paginate through all? -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 15683] New: Inconsistent population of lastreneweddate between AddRenewal and AddIssue
by bugzilla-daemon＠bugs.koha-community.org 12 May '21

12 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15683 Bug ID: 15683 Summary: Inconsistent population of lastreneweddate between AddRenewal and AddIssue Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When lastreneweddate is populated via C4::Circulation::AddRenewal, it is added as a date, whereas C4::Circulation::AddIssue stores it as DateTime, i.e. hours, minutes and seconds are populated. Because of hourly loans, I think that it only makes sense to store lastreneweddate as a full datetime. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 15729] New: SIP server allows checkin of reserved item
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '21

30 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15729 Bug ID: 15729 Summary: SIP server allows checkin of reserved item Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: bc(a)interleaf.ie QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com At present the SIP server will allow an item to be returned even if there is an outstanding hold on it. Some libraries do not see this as an issue and run reports for reserves before re-shelving. However, some prefer to have the item denied at the selfservice unit and force the borrower to return the item to the desk. With this in mind there should be a SIP systempreference which allows libraries to specify if a reserved item should be permitted to be checked in via the selfservice unit -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 15751] New: Koha offline circulation Firefox addon does not update last seen date for check-ins
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '21

22 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15751 Bug ID: 15751 Summary: Koha offline circulation Firefox addon does not update last seen date for check-ins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: contribs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: fridolin.somers(a)biblibre.com, koha-bugs(a)lists.koha-community.org, testopia(a)bugs.koha-community.org When I check in something using the KOCT the last seen date is not updated. It does update the last seen date upon checkout, for what it's worth. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. You are watching all bug changes.

1 22

[Bug 16149] New: Generate and send custom notices based on report output
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '21

16 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16149 Bug ID: 16149 Summary: Generate and send custom notices based on report output Change sponsored?: Seeking cosponsors Product: Koha Version: master Hardware: All URL: http://devs.bywatersolutions.com/projects/custom-notic es-based-report-output/ OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Work to be done: Write a cron script that will a) Accept parameters for 1) a report id 2) a notice code 3) a notice module 4a) a branchcode 4b) or database column from which to select the branchcode 5) a column from which to select the email address to send to ( if not set, Koha will use the first available email address for the patron ) 6a) A "from" email address 6b) A column from which to select the "from" email address b) The script will run the report and for each row of results will generate a notice and queue it for sending. All and only the columns from the report will be available to be used in the notice text. Looking for sponsors: http://devs.bywatersolutions.com/projects/custom-notices-based-report-outpu… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 53

[Bug 15933] New: Regarding publishercode
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '21

11 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15933 Bug ID: 15933 Summary: Regarding publishercode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: tejoskumar(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, As in the serials module there is an option to search for an existing vendor and add the vendor code while creating a new one, I could not find an option to search for a publishercode. If this is available the data entry part of the publishercode will be very uniform throughout the cataloging entries. I could not find this option any where hence posting it here. Regards Suresh Kumar -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 16067] New: Koha::Cache, fastmmap caching system is broken
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16067 Bug ID: 16067 Summary: Koha::Cache, fastmmap caching system is broken 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 After Bug 11998, fastmmap caching system implementation in Koha::Cache ceased to work properly. If fastmmap is enabled (= environment variable CACHING_SYSTEM is set to 'fastmmap'), any CGI script call causes the following error: Use of uninitialized value $db_name in concatenation (.) or string at /home/koha/devkohaclone/Koha/Database.pm line 73. Use of uninitialized value $db_host in concatenation (.) or string at /home/koha/devkohaclone/Koha/Database.pm line 73. DBI connect('database=;host=;port=','',...) failed: Access denied for user 'koha'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1249 DBIx::Class::Storage::DBI::dbh(): DBI Connection failed: Access denied for user 'koha'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1253. at /home/koha/devkohaclone/Koha/Database.pm line 90 To reproduce on command line: 0) ensure that you have fastmmap perl module installed (libcache-fastmmap-perl in debian) 1) export CACHING_SYSTEM=fastmmap 2) export GATEWAY_INTERFACE=1 3) try to run this simple script: #!/usr/bin/perl use Modern::Perl; use C4::Biblio; GetMarcStructure(); -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 15791] New: Don't delete a fund if existing orders are linked to it
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '20

04 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15791 Bug ID: 15791 Summary: Don't delete a fund if existing orders are linked to it Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/admin/aqbudgets.pl?op=delete_confirm OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org When you go to delete a fund Koha displays this message in the confirmation dialog: "If you delete this fund, all orders linked to this fund will be deleted!" The error appears even if there are no orders linked to the fund. In order to be consistent we ought to warn the user only if existing orders will be deleted. Should it even be possible to delete a fund if there are orders linked to it? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 15956] New: Rearranging some SIP unit tests (test without SIP server)
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '20

02 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15956 Bug ID: 15956 Summary: Rearranging some SIP unit tests (test without SIP server) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: gmcharlt(a)gmail.com This report is a follow-up for bug 13871 and bug 15947. The two tests SIP_ILS.t and SIPILS.t (what's in a name) will be broken into a few more specific tests. Will add tests for handling Patron Status request and Patron Info request too. -- You are receiving this mail because: You are watching all bug changes.

1 29