December 2017 - Koha-bugs - lists.koha-community.org

[Bug 16333] New: Google Calendar integration don't work
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '19

07 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16333 Bug ID: 16333 Summary: Google Calendar integration don't work Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: wosch(a)freebsd.org On the page https://koha-community.org/calendar/ is a link 'g+ Add to Google'. I tried it out and google calendar reports an error message: "This email address isn't associated with an active Google Calendar account: https://koha-community.org/?plugin=all-in-one-event-calendar&controller…. Please check the email address and try again." -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16347] New: many news articles are tagged excessively or not tagged at all
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '19

07 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16347 Bug ID: 16347 Summary: many news articles are tagged excessively or not tagged at all Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: mirko(a)abunchofthings.net The usage of categories in news posts is weird. The Koha newsletter seems to be using every category available, while 3.22 is not tagged at all. https://koha-community.org/category/release/ has mostly 3.20. Where is 3.22? Why are all the community newsletters showing up there? https://koha-community.org/category/release/3-22/ has newsletters almost exclusively. 3.22.1 is the last one listed. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 16840] New: URLs for old releases are broken with every new release
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '19

07 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16840 Bug ID: 16840 Summary: URLs for old releases are broken with every new release Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: jsn.sherman(a)gmail.com I'm working up a nice CentOS 7 ansible role that builds Koha from the tarball release. The way you shuffle tarball upon release makes automating koha builds more difficult than it has to be, and is user hostile. When you move tarballs under old releases, you don't offer a redirect to the new location, instead you return a 404. When you publish content to the web, you should treat that URL as valid for as long as you have the associated content. In this case, you still have the content, and you know exactly where it is. Ideally, you would offer clients a 301 redirect to the new location. You should only return a 404 when you deleted content or honestly have no idea what the client is asking for. This is a general website stewardship issue, and it may not seem like the most critical thing when you are trying to get a release out the door, so I would be happy to contribute my expertise and/or time to improve this aspect of release management for Koha. Thanks! -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 19818] New: Add id into tag html from moremember.tt
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '19

06 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19818 Bug ID: 19818 Summary: Add id into tag html from moremember.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: stephane.delaye(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In this screen /cgi-bin/koha/members/moremember.pl? I have several li tags html without id. So when I want custom the labels with the preference system 'intranetuserjs', i can't... from the record patron (memberentry.pl)...it is possible .... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 16743] New: Datatables error when checking overdues in chrome
by bugzilla-daemon＠bugs.koha-community.org 05 Feb '19

05 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16743 Bug ID: 16743 Summary: Datatables error when checking overdues in chrome Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: james.elian(a)britishschool.ro QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 52410 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=52410&action=ed… Screenshot of error This error does not occur in Firefox or Internet Explorer, only in Chrome. On going to a patron page when the patron has overdue items, no items show in the checkout table. If "Always show checkouts immediately" is checked, an error message appears. A screenshot is here as an attachment, and the text is: "DataTables warning: table id=issues-table - Cannot reinitialise DataTable. For more information about this error, please see http://datatables.net/tn/3" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 19045] New: Circulation rules seem not to work correctly with single library systems
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '19

04 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19045 Bug ID: 19045 Summary: Circulation rules seem not to work correctly with single library systems 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: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Online help and manual for "Circulation and Fines Rules" say: "If you are a single library system choose your branch name before creating rules (sometimes having only rules for the 'all libraries' option can cause issues with holds)" Such issues should be considered as bug and need investigation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 15807] New: library branch sorting on guarantor_search.pl is incorrect
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '19

04 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15807 Bug ID: 15807 Summary: library branch sorting on guarantor_search.pl is incorrect Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The library branch sorting on guarantor_search.pl is incorrect. It's displaying as Leavenworth... Carbondale... Prairie Hills... Lyndon... and so on. The sorting behavior is the same as what was reported and fixed on this bug, https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13950, if that helps resolve this one more quickly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 18323] New: Create option to retain accountlines data when a borrower is deleted
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '19

04 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18323 Bug ID: 18323 Summary: Create option to retain accountlines data when a borrower is deleted Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cmurdock(a)ccfls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In order to retain accurate long-term fines income statistics it would be useful if there were an option to allow libraries to retain a borrower's data from the accountlines table when the borrower is deleted, something like the biblio/deletedbiblio data retention. Our library system has been using Koha for almost 10 years now, so I'm surprised our staff hasn't noticed this until now! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 16919] New: Problems with cart
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '19

04 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16919 Bug ID: 16919 Summary: Problems with cart 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The cart deletion does not seem to always delete the cart. Users have reported that after adding items to a cart, clearing the cart (from the results screen) and then adding an item from the results all previous items reappear. I have recreated this, but not with steps I can recreate. Basically if you add and remove items enough from cart you start to see oddities. Try various combintations of adding/removing and going forward/backward in browser and new results. I also noted in testing I ended up with two cookies, one pointing to the base URL and one pointing to baseurl/cgi-bin/opac-main.pl -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 19002] New: Invoice filters "Shipment date (From):" and " Billing date (From):" don't start with date selected
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '19

04 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19002 Bug ID: 19002 Summary: Invoice filters "Shipment date (From):" and "Billing date (From):" don't start with date selected Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: jsterben(a)umich.edu QA Contact: testopia(a)bugs.koha-community.org When filtering invoices using "Search filters" on left side of screen, setting the "From:" shipment date does not include results from that date, effectively functioning as a "greater than" limiter instead of a "greater than or equal to" limiter. I (and, I expect, most users) would expect "greater than or equal to" functionality. This condition was confirmed true both when only "shipment dates" were used to limit as well as when another criterion (I chose "vendor") was selected. URL parameters show correct passing of date value in "shipmentdatefrom". The same conditions and results are true with "Billing date (From):" and its parameters. Maybe a simple wording change is the fix, ("From" to "After"), though typical usage of date limiters includes, not excludes, the date selected in results sets. It is unknown if this condition existed in earlier releases. VERIFY (using Shipment Date): 1) Using any means at your disposal, learn of any valid shipmentdate value in aqinvoices 2) GO TO: Home > Acquisitions > Invoices 3) Set a limiter for "Shipment date (From:)" using that valid shipmentdate 4) Observe that no results from that date appear in the results OTHER DETAILS: Koha 17.05.01.000 on Ubuntu 14.04 with MySQL 5.5.55, installed and updated via packages. Observed in Chrome 59.0.* and Firefox 53.0.* -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1