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

[Bug 2605] New: bookcount thows strings at date handling
by bugzilla-daemon＠pippin.metavore.com 12 Sep '08

12 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2605 Summary: bookcount thows strings at date handling Product: Koha Version: HEAD Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Circulation AssignedTo: galen.charlton(a)liblime.com ReportedBy: joe.atzberger(a)liblime.com QAContact: koha-bugs(a)lists.koha.org bookcount.pl tries to embed English language user feedback that later gets passed to format_date as a date. In addition to being untranslatable, this results in errors like: [Fri Sep 12 11:11:09 2008] [error] [client 65.186.223.180] [Fri Sep 12 12:11:09 2008] bookcount.pl: Illegal Date 'Item has no branch transfers record' does not match 'iso' format: yyyy-mm-dd at /home/atz/koha/production/intranet/cgi-bin/circ/bookcount.pl line 85, referer: http://staff-atz.dev.kohalibrary.com/cgi-bin/koha/catalogue/moredetail.pl?b… In particular the 3 subs lastmove, lastseenat and slashdate should be reimplemented on a clean C4::Dates basis and all user feedback strings moved into the templates. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2604] Appending "\" character to a search in OPAC causes an unhelpful error screen to be displayed
by bugzilla-daemon＠pippin.metavore.com 12 Sep '08

12 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2604 ------- Comment #1 from chris(a)bigballofwax.co.nz 2008-09-11 19:54 ------- Confirming the bug exists http://public.demo.kohalibrary.com/cgi-bin/koha/opac-search.pl?q=fish\ Although, http://opac.koha.workbuffer.org/cgi-bin/koha/opac-search.pl?q=\ Which is running from git appears to be fine, so it may have been fixed and not ported to the stable branch. It also seems fine in earlier versions of koha http://opac.wlpl.org/cgi-bin/koha/opac-search.pl?op=do_search&type=opac&mar… Gets no error ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2604] New: Appending "\" character to a search in OPAC causes an unhelpful error screen to be displayed
by bugzilla-daemon＠pippin.metavore.com 12 Sep '08

12 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2604 Summary: Appending "\" character to a search in OPAC causes an unhelpful error screen to be displayed Product: Koha Version: unspecified Platform: PC URL: http://thebookpile.wordpress.com/2008/09/10/input- validation-in-koha-and-evergreen-one-simple-test-with- screenshots/ OS/Version: Linux - Debian Status: NEW Severity: normal Priority: P3 Component: OPAC AssignedTo: jmf(a)liblime.com ReportedBy: warren.layton(a)googlemail.com QAContact: koha-bugs(a)lists.koha.org I was playing the Athens, OH, OPAC and accidentally entered "orwell\" instead of "orwell", which gave me an error indicating an "Internal Server Error". It seems that the "\" is being inserted into the regular expression used for the search and isn't stripped out. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2602] Cloning for patrons
by bugzilla-daemon＠pippin.metavore.com 11 Sep '08

11 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2602 ------- Comment #2 from nicole.engard(a)liblime.com 2008-09-11 15:24 ------- It's something that a customer mentioned as handy because they don't have distinctions between children and adult patrons and so when they add a new family that has arrived in town it would save them a lot of time if they could just duplicate a patron like we duplicate catalog records. Seems pretty easy to implement it's just a matter of pulling the record out of the database and using it to fill in the add patron fields. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2602] Cloning for patrons
by bugzilla-daemon＠pippin.metavore.com 11 Sep '08

11 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2602 ------- Comment #1 from henridamien(a)koha-fr.org 2008-09-11 15:20 ------- Not much keen on that. I had rather add features for better relationship management and multiple relationship than duplicating borrowers. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2603] New: updateitem.pl : item statuses can be changed irrespective of Independent branches setting.
by bugzilla-daemon＠pippin.metavore.com 11 Sep '08

11 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2603 Summary: updateitem.pl : item statuses can be changed irrespective of Independent branches setting. Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: Cataloging AssignedTo: galen.charlton(a)liblime.com ReportedBy: rch(a)liblime.com QAContact: koha-bugs(a)lists.koha.org the template for moredetail.pl does not use the nomod template variable to disable submission of item status updates to updateitem.pl, nor does updateitem.pl check independantbranches against the logged-in user's branch. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2598] Pay Fines allows payment against accruing fine.
by bugzilla-daemon＠pippin.metavore.com 11 Sep '08

11 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2598 ------- Comment #2 from rch(a)liblime.com 2008-09-11 12:16 ------- Agreed there -- I have initial reports that paying against an accruing fine results in incorrect behavior, namely the account essentially being credited double the amount of the payment. A quick glance at the code suggests that it should be allowed, but some further testing is needed. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2602] New: Cloning for patrons
by bugzilla-daemon＠pippin.metavore.com 11 Sep '08

11 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2602 Summary: Cloning for patrons Product: Koha Version: HEAD Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: Patrons AssignedTo: galen.charlton(a)liblime.com ReportedBy: nicole.engard(a)liblime.com QAContact: koha-bugs(a)lists.koha.org CC: joe.atzberger(a)liblime.com It would be nice to be able to clone patrons. This is the same as 'Edit as new duplicate' for cataloging. Example: you have a family applying for cards they all have the same address so you just want to enter the diff names and then just the address once ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2601] Order fines by date and time
by bugzilla-daemon＠pippin.metavore.com 11 Sep '08

11 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2601 ------- Comment #1 from nicole.engard(a)liblime.com 2008-09-11 11:01 ------- Created an attachment (id=445) --> (http://bugs.koha.org/cgi-bin/bugzilla/attachment.cgi?id=445&action=view) fines ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2601] New: Order fines by date and time
by bugzilla-daemon＠pippin.metavore.com 11 Sep '08

11 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2601 Summary: Order fines by date and time Product: Koha Version: HEAD Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: Circulation AssignedTo: galen.charlton(a)liblime.com ReportedBy: nicole.engard(a)liblime.com QAContact: koha-bugs(a)lists.koha.org CC: oleonard(a)myacpl.org When handling fines can they be ordered by date and time? right now it's only by date - but the fine is appearing before the payment on the same day. See attachment where the payment appears before the fine. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0