July 2013 - Koha-bugs - lists.koha-community.org

[Bug 10426] New: Remove unused sub GetCcodes from C4::Koha
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '13

06 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10426 Bug ID: 10426 Summary: Remove unused sub GetCcodes from C4::Koha Classification: Unclassified 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: colin.campbell(a)ptfs-europe.com Only reference to routine is in a comment. Delete it Lets not waste time maintaining unused code (and I can see at least 3 things that could be fixed in it, if we were) -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 7898] New: Browse Results is easily confused
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '13

05 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7898 Priority: P5 - low Change sponsored?: Seeking cosponsors Bug ID: 7898 Assignee: oleonard(a)myacpl.org Summary: Browse Results is easily confused QA Contact: koha.sekjal(a)gmail.com Severity: normal Classification: Unclassified OS: All Reporter: mjr(a)software.coop URL: http://localnet/cgi-bin/koha/opac-detail.pl Hardware: All Status: NEW Version: master Component: OPAC Product: Koha To break the Browse Results box added in Bug 6483: 1. search for many pages of results common, like "a"; 2. open results page 2 in a new tab; 3. open any result detail from page 1; 4. enjoy the Browse Results box either: moving you around the wrong page; or having previous/next greyed out while Back to Results takes you to the wrong page. This is because the Browse Results links are stored in the session rather than encoded in the URLs. I think it needs more behind-the-scenes knowledge than even OPAC power users will have before you expect that behaviour, but power users open results pages in tabs. The obvious fix is to encode the session parameter busc in the URLs rather than the session. That would also make it rather easier to debug things like bug 7394 and bug 7894. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 10539] New: Remove unused unit tests in lib/KohaTest
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '13

05 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10539 Bug ID: 10539 Summary: Remove unused unit tests in lib/KohaTest Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Test Suite Assignee: m.de.rooy(a)rijksmuseum.nl Reporter: m.de.rooy(a)rijksmuseum.nl As discussed on the dev list, we can remove the unit tests in lib/KohaTest. Galen suggested: [I have no objection to a patch that removes them, but it would be a niceness to look over the individual tests and see which ones can be easily ported to the current DB-dependent test framework.] Since these unit tests are not used now, they only generate unnecessary maintenance; they are regularly updated for nothing. I propose to remove them rightaway. But with Galen's suggestion in mind, I will walk through them (placed outside the Koha codebase) in the next couple of months to see if we can still retrieve some additional tests and inject them in the active db_dependent unit tests. Anyone else who wants to join that activity is welcome; you can easily retrieve these files from git. Please let me know if you do. I will open a separate report for that purpose. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 10361] New: Add Option to cleanup_database.pl to purge search_history entries
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '13

04 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10361 Bug ID: 10361 Summary: Add Option to cleanup_database.pl to purge search_history entries Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: mirko(a)abunchofthings.net Reporter: mirko(a)abunchofthings.net Add an option to cleanup_database.pl to purge the search_history entries older than X days. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 10634] New: Use datatables for course details items table
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '13

04 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10634 Bug ID: 10634 Summary: Use datatables for course details items table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should make the course items table in the course details a datatable to enable searching or sorting. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 8605] New: cs-CZ: Filesystem sent error: No such file or directory
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '13

02 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8605 Priority: P1 - high Change sponsored?: --- Bug ID: 8605 CC: frederic(a)tamil.fr Assignee: koha-bugs(a)lists.koha-community.org Summary: cs-CZ: Filesystem sent error: No such file or directory Severity: blocker Classification: Unclassified OS: All Reporter: black23(a)gmail.com URL: http://translate.koha-community.org/cs/38/ Hardware: All Status: NEW Version: rel_3_8 Component: translate.koha-community.org Product: Koha If we can (download) upload files (from) into translation Project, we get error: Error accessing /home/koha/Pootle-2.1.6/po/38/cs, Filesystem sent error: No such file or directory -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 4823] New: Raw Socket interface failing to accept connections
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '13

02 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4823 Summary: Raw Socket interface failing to accept connections Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: SIP2 AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: colin.campbell(a)ptfs-europe.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 This has been reported on 3M self checkouts in both the US and UK. Sip working ok for days (weeks even) then suddenly the server refuses to accept connections. Restarting sip does not always rectify (immediately) the problem. Suggests the socket gets stuffed (technical term covering a number of possible error conditions). A rare occurence and not easily repeatable. May occur intermittently when the symptom is very poor response time (sip messages are not being responded to, are timing out then server responds on second or third retry) -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 2

[Bug 7420] New: Add max fines to circulation matrix
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '13

02 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7420 Bug #: 7420 Summary: Add max fines to circulation matrix Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: srdjan(a)catalyst.net.nz QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com Capped charge is applied per item. Work to be done: * Add a numeric overduefinescap field to the issuingrules table * Add "Overdue Fines Cap" section at the bottom of the Corculation Rules page, inputs: - item type - patron category - cap in $ or whatever currency * C4::Overdues::UpdateFine() - observe overduefinescap rule when updating overdue charges - leave the charge at overduefinescap if it goes over * create tests How to test: * Check that new field values stick when maintained on the circ rules matrix page * Check that the cap is applied. This is a tricky one. A quick test would be: - set the cap to a value less then the overdue charge - have an overdue item - run fines.pl cronjob - check that the capped charge is applied A more complex test would be to set the cap anywhere between one day charge and two day charges, and run fines.pl cronjob on two consecutive days, but I'm not sure how practical it is, or is it possible to have a testing facility that can push the date forward -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 42

[Bug 10490] New: Overdue fines cap (amount) in circulation rules rounds
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '13

02 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10490 Bug ID: 10490 Summary: Overdue fines cap (amount) in circulation rules rounds Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To test: 1) Add a new circulation rule, give 4.50 for overdue fines cap. > Verify the system saves it to be 5.00 2) Edit an existing circulation rule, give 3.40 for overdue fines cap. > Verify the system saves it to be 3.00 Obviously, that's not good and especially bad because most of our libraries have standardized on 4.50. Maybe there is a problem with the datatype definition in the kohastructure.sql? We have: overduefinescap decimal default NULL, -- the maximum amount of an overdue fine In opposite to: reservecharge decimal(28,6) default NULL, I couldn't test it, but the definition is the same for kohastructure and update database. So a bit worried that we might change the data here on update instead of copying it correctly from the system preference into issuingrules. The feature was added with bug 7420. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 10221] New: hold expiration doesn't show on patron's list of holds
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '13

02 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10221 Bug ID: 10221 Summary: hold expiration doesn't show on patron's list of holds Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All URL: /cgi-bin/koha/circ/circulation.pl?borrowernumber=51 OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com When looking at the patron details in the staff client you don't see the holds expiration date, but you do see all the other dates (placed, suspension) We should see the same here: /cgi-bin/koha/circ/circulation.pl?borrowernumber=51 that we see here: /cgi-bin/koha/reserve/request.pl?biblionumber=3174 When it relates to hold dates. -- You are receiving this mail because: You are watching all bug changes.

1 14