August 2012 - Koha-bugs - lists.koha-community.org

[Bug 8546] New: OPAC Advanced Search Publication date range guide text FAIL
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '12

28 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8546 Priority: P5 - low Change sponsored?: --- Bug ID: 8546 Assignee: oleonard(a)myacpl.org Summary: OPAC Advanced Search Publication date range guide text FAIL Severity: trivial Classification: Unclassified OS: All Reporter: m.kirjasto.hailuoto(a)gmail.com Hardware: All Status: NEW Version: unspecified Component: OPAC Product: Koha Guide text in the advanced search form is incorrect: "For example: 1999-2001. You could also use "-1987" for everything published before 1987 or "2008-" for everything published after 2008." is illogical. The logically and functionally correct way being: For example: 1999-2001. You could also use "-1987" for everything published before 1988 or "2008-" for everything published after 2007. Reproducing the bug: Search date range 2008- for "everything published _after_2008_" and you'll get also books published 2008, not only after 2008. @ http://catalog.farmingtonlibraries.org/cgi-bin/koha/opac-search.pl This text bug prevails in community's demo runs 3.8, 3.6, 3.2 and master, provided by Bywater, CALYX, Equinox, Libriotech, software.coop http://koha-community.org/demo/ The four TOF demo Opacs on the list. Also in Bywater sandbox OPAC http://catalog.bywatersolutions.com/ EVEN THOUGH text bug has been fixed in Bywater sandbox Intranet (ver.3.09.00.026, whatever that would mean) (login bywater - bywater reqrd): http://intranet.bywatersolutions.com/cgi-bin/koha/catalogue/search.pl Bug shows in live instances too, e.g. Farmington Koha, http://catalog.farmingtonlibraries.org/cgi-bin/koha/opac-search.pl Most likely in KOHA 3.10 too. FIX SUGEGSTION, that do not age along the years: like w Bywater format: yyyy-yyyy PS. All in all, when I "patron-eyed" Farmington Adv search, I started to miss guide text feature. The advSearch page is so long. It could be shortened. Esp. the Item type list should be made drop-down type and also divided into 2 or more categories: Item types and thematical types. Or newest item types? Now the list doesn't work for, well, anybody. Schratching here my head: some patrons could use this as an itemtype browsing feature. (Well but this is now off-topic already.) -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 8515] New: OPAC password change does not obey OpacPasswordChange
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '12

28 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8515 Priority: P5 - low Change sponsored?: --- Bug ID: 8515 Assignee: oleonard(a)myacpl.org Summary: OPAC password change does not obey OpacPasswordChange Severity: minor Classification: Unclassified OS: All Reporter: gmcharlt(a)gmail.com Hardware: All Status: NEW Version: master Component: OPAC Product: Koha Currently the OpacPasswordChange system preference only controls whether the user sees a link to the password change form. If the user can guess the URL of the password reset form, they would still be able to change their password contrary to the to the system preference setting. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 7805] New: Exposing the new list permissions in opac and staff
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '12

28 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7805 Priority: P5 - low Change sponsored?: --- Bug ID: 7805 Assignee: m.de.rooy(a)rijksmuseum.nl Summary: Exposing the new list permissions in opac and staff QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: m.de.rooy(a)rijksmuseum.nl Hardware: All Status: ASSIGNED Version: master Component: Virtual Shelves Product: Koha The next step after 7310: Exposing the new permissions to add and delete. Will submit the patch now, but give a more detailed test plan later (if needed). What should be tested here is: 1 Adding a list and checking various permission settings on opac and staff (edit again or look in the shelves table via sql). 2 Editing a list, changing perm settings and checking them again. 3 Try to add an item to a list without permissions to add (note: you should not be the owner). Try this via interface or even try to hack a URL. It should not be possible. 4 Try to delete an item that you added yourself to a list while delete_own is Do not allow. Even as owner you should not be able to. 5 Try to delete an item that another one added to a list while delete_other is Do not allow. Even as owner you should not be able to. 6 Try some things that you should be allowed to do so. Important note: The owner can always add, but needs perms to remove. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 8498] New: can't specify an hour when specifying due date
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '12

27 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8498 Priority: P5 - low Change sponsored?: --- Bug ID: 8498 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: can't specify an hour when specifying due date Severity: normal Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Circulation Product: Koha With hourly loans Koha can make items due specific hours, but if you have the specify due date box on the checkout screen you can't enter an hour in it ... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 7570] New: Item availability to cart list
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '12

27 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7570 Bug #: 7570 Summary: Item availability to cart list Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha.sekjal(a)gmail.com For items in the cart (opac-basket.pl), only location and call no. are displayed, change this page to display item availability status as well. -- 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 24

[Bug 7600] New: Have book cover image script return single-pixel gif data
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '12

27 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7600 Bug #: 7600 Summary: Have book cover image script return single-pixel gif data Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools AssignedTo: jcamins(a)cpbibliography.com ReportedBy: oleonard(a)myacpl.org QAContact: koha.sekjal(a)gmail.com When you request a book cover image from Amazon which doesn't exist, the response isn't a 404 but a single-pixel GIF. This page describes ways in which developers can use this to have display of Amazon covers gracefully degrade: http://www.oreillynet.com/pub/a/javascript/2003/10/21/amazonhacks.html We use the client-side technique in Koha. I wonder if we couldn't do the same thing with the local covers? The hex dump of a single-pixel gif is tiny: 4749 4638 3961 0100 0100 8000 00ff ffff 0000 0021 f904 0100 0000 002c 0000 0000 0100 0100 0002 0244 0100 3b Could that be converted to binary and returned in place of an error? For instance, line 103 of opac-image.pl, "warn "No image exists for $imagenumber" if $DEBUG;" I'm guessing this would speed up loading the page since the browser spends a lot of time looking for cover images which don't exist. -- 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 7

[Bug 7559] New: Edit links for patron attributes and messaging preferences are broken
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '12

27 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7559 Bug #: 7559 Summary: Edit links for patron attributes and messaging preferences are broken Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: /cgi-bin/koha/members/moremember.pl?borrowernumber=19 OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons AssignedTo: katrin.fischer(a)bsz-bw.de ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha.sekjal(a)gmail.com CC: gmcharlt(a)gmail.com Edit links below sections for patron attributes and enhanced messaging preferences are broken and the page is empty except for the heading. To test: 1) Verify all edit links on the page lead to the correct sections of the patron empty record. 2) Verify the edit link from the toolbar still works correctly. -- 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 8

[Bug 7496] New: Personally identifying information sent in opac user TITLE
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '12

27 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7496 Bug #: 7496 Summary: Personally identifying information sent in opac user TITLE Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: wizzyrea(a)gmail.com QAContact: koha.sekjal(a)gmail.com We show the name of the user in the OPAC in the TITLE of the user pages, so on public stations if the history is not cleared after every session, the next user would be able to see who had logged in last. The name also appears in "place hold for" pages. Is this reason for concern? Surely this runs afoul of privacy laws *somewhere*. -- 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 8

[Bug 6323] New: Attach/move items -- error handling cleanup
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '12

27 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6323 Bug #: 6323 Summary: Attach/move items -- error handling cleanup Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com When an item move fails, the current behavior is to send the user back to the MARC detail page only. I believe there should be an option to "try again with a different barcode." -- 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 37

[Bug 7580] New: duplicate budget should allow for description change
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '12

27 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7580 Bug #: 7580 Summary: duplicate budget should allow for description change Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha.sekjal(a)gmail.com Depends on: 6943 When duplicating a budget in addition to the start and end dates you should be able to assign a new description for the budget so that you don't end up with two budgets with the same name. -- 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 2