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

[Bug 17207] New: Cannot access the website from China
by bugzilla-daemon＠bugs.koha-community.org 14 Jan '20

14 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17207 Bug ID: 17207 Summary: Cannot access the website from China Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: thadickal.mapleleaf(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Recently, many schools in China, specifically in Shanghai and surrounding area have not been able to access the Koha website. Can you please advise us how we can restore our connection to your service. Thanks -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 17093] New: JavaScript error on patron entry page if toolbar is not displayed
by bugzilla-daemon＠bugs.koha-community.org 14 Jan '20

14 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17093 Bug ID: 17093 Summary: JavaScript error on patron entry page if toolbar is not displayed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons 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 Under some circumstances the patron entry form and toolbar are not displayed by memberentrygen.tt. For instance, if there are no libraries or patron categories defined. If this happens a JavaScript error is triggered because a check for #toolbar's position returns null. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 16766] New: Merging two records with title level holds for the same patron creates two holds on one record
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16766 Bug ID: 16766 Summary: Merging two records with title level holds for the same patron creates two holds on one record 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1 - Place a title level hold for a patron on a record 2 - Do it again on another record 3 - Merge these recrods 4 - See they now have two holds on one record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 16413] New: Prototype for GetLatestAutoRenewDate and GetSoonestRenewDate should be changed
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16413 Bug ID: 16413 Summary: Prototype for GetLatestAutoRenewDate and GetSoonestRenewDate should be changed 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: 16344 Currently the 2 GetLatestAutoRenewDate and GetSoonestRenewDate subroutines takes $borrowernumber and $itemnumber in parameter. They refetch the patron, item and issue information but they already are available from where they are called. It would make sense to change the prototype of these 2 subroutines to accept the patron, item and issue information directly to avoid unnecessary refetches. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16344 [Bug 16344] Add a circ rule to limit the auto renewals given a specific date -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 16140] New: Only clear L1 cache when needed
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16140 Bug ID: 16140 Summary: Only clear L1 cache when needed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P2 Component: Architecture, internals, and plumbing Assignee: jweaver(a)bywatersolutions.com Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 16044 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16044 [Bug 16044] Define a L1 cache for all objects set in cache -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 17542] New: Altering an invoice throws error unless shipment date and billing date both defined or both undefined
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '20

12 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17542 Bug ID: 17542 Summary: Altering an invoice throws error unless shipment date and billing date both defined or both undefined Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When creating an invoice you can create it without a billing or shipment date You can then alter the shipment cost, however, trying to define a billing date without first defining a shipment date causes: invoice.pl: Odd number of elements in hash assignment at /home/vagrant/kohaclone/C4/Acquisition.pm line 2700., referer: http://localhost:8081/cgi-bin/koha/acqui/invoice.pl Define only a shipment date and the change will go through, but then attempting to change the shipment cost will fail until a billing date is also defined -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 17230] New: borrowers table should be better normalized
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '20

12 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17230 Bug ID: 17230 Summary: borrowers table should be better normalized 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I've always been bothered by the fact that we have 3 separate sets of contact information in the borrowers table: streetnumber streettype address address2 city state zipcode country email phone B_streetnumber B_streettype B_address B_address2 B_city B_state B_zipcode B_country B_email B_phone altstreetnumber altstreettype altaddress altaddress2 altcity altstate altzipcode altcountry altemail altphone These should be moved to a contacts table, which contains a 'contact_type' field corresponding to 'primary', 'B_' or 'alt' (although these also desperately need to be renamed), as well as a link to the borrower and a timestamp. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 17662] New: Patron can have more than one hold when records are merged
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17662 Bug ID: 17662 Summary: Patron can have more than one hold when records are merged Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We had a patron that placed a hold on two different records, one was an item level hold, and the other was a first available hold. These records were merged, and the system held on to both holds! I am not sure how you would go about preventing this from happening, except maybe check if any kind of hold exists on both records with the same borrower number and stop the merge so the staff member could go and remove one. Or perhaps it could show both holds and the staff member choses to delete either or both holds. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17632] New: Branch facets in opac do not respect OPAC_SEARCH_LIMIT.
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17632 Bug ID: 17632 Summary: Branch facets in opac do not respect OPAC_SEARCH_LIMIT. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I think this is similar to Bug 12848 : Hotlinked searches from detailed record does not respect OPAC_SEARCH_LIMIT. Here's an excerpt from the apache config for each opac URL: ACLL: ServerName acll.bywatersolutions.com SetEnv OPAC_SEARCH_LIMIT branch:ACLL RequestHeader add X-Koha-SetEnv "OPAC_SEARCH_LIMIT branch:ACLL" CCCLL: ServerName catalog.cccpllib.org ServerAlias ccll.acll.bywatersolutions.com SetEnv OPAC_SEARCH_LIMIT branch:CCCLL RequestHeader add X-Koha-SetEnv "OPAC_SEARCH_LIMIT branch:CCCLL" And here are the branch groups: select branchcode, branchname, branchrelations.categorycode from branches inner join branchrelations using (branchcode) order by categorycode, branchcode; +------------+------------------------------------------------+--------------+ | branchcode | branchname | categorycode | +------------+------------------------------------------------+--------------+ | Computer | Computer Use Only - Alameda County Law Library | ACLL | | DUB | Dublin Satellite Location | ACLL | | Hay | Hayward Branch | ACLL | | Oak | Oakland | ACLL | | MAR | Martinez | CCCLL | | PIT | Pittsburg Branch | CCCLL | | RICH | Richmond Branch | CCCLL | +------------+------------------------------------------------+--------------+ The following search is from the acll.bywatersolutions.com domain, i.e. it should only be returning search results for the branches 'Computer', 'DUB', 'Hay' and 'Oak', but the branch 'Martinez' (i.e MAR) is showing in the "Holding libraries" facet. http://acll.bywatersolutions.com/cgi-bin/koha/opac-search.pl?idx=su%2Cphr&a… -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 17623] New: Two different fine amount for same record
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17623 Bug ID: 17623 Summary: Two different fine amount for same record Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: vimal0212(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Dear Friends, Our Koha version 3.22.11. Two different fine amount show on two occassion for same book issued. e.g. Rs. 18 at circulation page and Rs. 20 at Fine payment section. Please see the screen shots attached. https://s13.postimg.org/u4vhngr07/FINE_ERROR1.png https://s14.postimg.org/lrmptbjdd/FINE_ERROR2.png https://s11.postimg.org/6bapri2er/FINE_ERROR3.png Regards, -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4