February 2009 - Koha-bugs - lists.koha-community.org

[Bug 2972] Include patron ID in bounce email alerts
by bugzilla-daemon＠pippin.metavore.com 20 Feb '09

20 Feb '09

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2972 ------- Comment #1 from oleonard(a)myacpl.org 2009-02-20 06:45 ------- Excellent point: My library has had problems with this as well, and in the past our solution was to create a custom search interface (in PHP) for searching by email. This also highlights the need for a patron advanced search to allow librarians to search for *any* specific piece of the patron record. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2972] New: Include patron ID in bounce email alerts
by bugzilla-daemon＠pippin.metavore.com 20 Feb '09

20 Feb '09

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2972 Summary: Include patron ID in bounce email alerts Product: Koha Version: rel_3_0 Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: System Administration AssignedTo: paul.poulain(a)free.fr ReportedBy: beverly.church(a)liblime.com QAContact: koha-bugs(a)lists.koha.org The bounce alert sent to libraries doesn't provide any ID info about the actual patron. The email address is often something completely unrelated to the patron's actual name. Currently the only way to find the patron record by their email address is to create a guided report using a SQL statement. Unfortunately, even a mid-sized library might receive dozens of email bounces due to bad or changed patron email addresses each day. Looking up each patron individually by an SQL guided report isn't feasible. If the bounce message contained a patron barcode in the subject line or body of the message this would solve the problem. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2341] items marked 'On Order' (notforloan == -1) don't interact correctly with opac-reserve.tmpl
by bugzilla-daemon＠pippin.metavore.com 20 Feb '09

20 Feb '09

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2341 beverly.church(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |beverly.church(a)liblime.com ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2540] Error exporting reports in Reports to both csv or tabbed format in 3.0
by bugzilla-daemon＠pippin.metavore.com 20 Feb '09

20 Feb '09

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2540 cookie.wolfrom(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cookie.wolfrom(a)liblime.com ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2655] Items waiting on the hold shelf display as "Available" in OPAC
by bugzilla-daemon＠pippin.metavore.com 20 Feb '09

20 Feb '09

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2655 cookie.wolfrom(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cookie.wolfrom(a)liblime.com ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2971] Shopping cart popup's dropshadow leaks memory
by bugzilla-daemon＠pippin.metavore.com 20 Feb '09

20 Feb '09

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2971 sedwards(a)alloycomputing.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Priority|P3 |PATCH-Sent Resolution| |FIXED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2971] Shopping cart popup's dropshadow leaks memory
by bugzilla-daemon＠pippin.metavore.com 20 Feb '09

20 Feb '09

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2971 ------- Comment #2 from sedwards(a)alloycomputing.com 2009-02-19 11:45 ------- Agreed in principle, but after reading the docs for Drop Shadow, it's probably a lot safer just to create it as needed, which shouldn't be very often anyway. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2971] Shopping cart popup's dropshadow leaks memory
by bugzilla-daemon＠pippin.metavore.com 19 Feb '09

19 Feb '09

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2971 ------- Comment #1 from joe.atzberger(a)liblime.com 2009-02-19 10:37 ------- Nice catch. Alternatively, check for a hidden shadow before creating a new one. If exists, unhide it. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2971] Shopping cart popup's dropshadow leaks memory
by bugzilla-daemon＠pippin.metavore.com 19 Feb '09

19 Feb '09

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2971 sedwards(a)alloycomputing.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2971] New: Shopping cart popup's dropshadow leaks memory
by bugzilla-daemon＠pippin.metavore.com 19 Feb '09

19 Feb '09

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2971 Summary: Shopping cart popup's dropshadow leaks memory Product: Koha Version: HEAD Platform: PC URL: koha-tmpl/opac-tmpl/prog/en/js/basket.js OS/Version: Linux - Debian Status: NEW Severity: minor Priority: P3 Component: OPAC AssignedTo: sedwards(a)alloycomputing.com ReportedBy: sedwards(a)alloycomputing.com QAContact: koha-bugs(a)lists.koha.org The javascript file basket.js contains several functions for displaying popup notifications for the user's shopping cart button. A jquery plug-in function, 'dropShadow' is used to create a shadow for the popup. When the popup is no longer needed, the shadow is removed with the 'hide' function. Every time the user hovers over the cart or otherwise causes the popup to display, this results in the creation of a new dropShadow object. The resulting DOM keeps growing. The correct way to dispose of the shadow is to call 'removeShadow'. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0