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

[Bug 8337] New: System preferences for longoverdue cron
by bugzilla-daemon＠bugs.koha-community.org 15 Jan '15

15 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8337 Priority: P5 - low Change sponsored?: --- Bug ID: 8337 Assignee: gmcharlt(a)gmail.com Summary: System preferences for longoverdue cron Severity: enhancement Classification: Unclassified OS: All Reporter: pelletiermaxime(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: Command-line Utilities Product: Koha Patch to follow that adds 3 new system preferences to control the parameters for the longoverdue script. New prefs are DefaultLongOverdueChargeValue, DefaultLongOverdueLostValue and DefaultLongOverdueDays. These preferences are used when you call the longoverdue.pl script without their parameters. -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 7556] New: Use "preventDoubleFormSubmit()" more in the OPAC and Intranet to prevent duplicate data
by bugzilla-daemon＠bugs.koha-community.org 14 Jan '15

14 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7556 Bug #: 7556 Summary: Use "preventDoubleFormSubmit()" more in the OPAC and Intranet to prevent duplicate data Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: wizzyrea(a)gmail.com QAContact: koha.sekjal(a)gmail.com Depends on: 6496 When 6496 is pushed, we will have a new jquery function: preventDoubleFormSubmit(). When used thusly: $('#form-id').preventDoubleFormSubmit(); It will prevent a submitted form from being submitted a second (or third, or fourth, or fifth) time. We should probably use this on most submission forms in the OPAC. As Paul states on 6496 - "we can teach librarians not to double click, but not patrons." The function exists in both the OPAC and Intranet, and so it can be used anywhere a double (or rapid) click would resubmit a form. I think we should try to use it more. -- 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 6

[Bug 6832] New: Validation of total > budget in neworderempty
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '15

13 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6832 Bug #: 6832 Summary: Validation of total > budget in neworderempty Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: pelletiermaxime(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 5264 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=5264 [PATCH] Fix multiple bugs and refactor the code to fix the alert of the total exceeding the budget in neworderempty The javascript function totalExceedsBudget never returns anything. Refactored it to use jQuery for the ajax stuff and to make it work. Only 1 line changed in a tmpl, so should be easy to adapt for 3.4. Steps to reproduce : Create a new order in a basket. Set a total higher than the total of the selected budget. You will see an ajax request, but no error. This patch fixes the return, make it work for ie6 by using jQuery and prints correctly the total of the budget in the error. -- 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 23

[Bug 9822] New: No alert appears on adding an order to a basket if the budget has exceeded
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '15

13 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9822 Bug ID: 9822 Summary: No alert appears on adding an order to a basket if the budget has exceeded Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 9810] New: Search limit 'available' does not hide damaged or withdrawn items
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '15

12 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9810 Bug ID: 9810 Summary: Search limit 'available' does not hide damaged or withdrawn items Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 5592] New: circ rule cloning can be dangerous
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '15

08 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5592 Summary: circ rule cloning can be dangerous Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: gmcharlt(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 The clone circ rules widget on the circ rules page unconditionally deletes the target library's existing rules and replaces them with copies of the rules from the source library. Consequently, if the clone rule button is accidentally clicked, a lot of configuration work can be destroyed in an instant. To avoid this: * there should *always* be a required confirmation step, whether the clone-rules.pl script is accessed directly or via the smart-rules.pl page * even better, a backup copy of the previous version of the target library's rules could be made The library who ran into this bug had tried cloning the rules form a different library because they thought that would be a way to copy over that library's rules and add them to the rules that the target library had previously entered -- that kind of cloning-via-merge feature also seems like a good idea, in fact. -- 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 4

[Bug 7817] New: Items Permanent location (shelving location) is set to NULL when item is edited
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '15

08 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7817 Priority: P5 - low Change sponsored?: --- Bug ID: 7817 Assignee: gmcharlt(a)gmail.com Summary: Items Permanent location (shelving location) is set to NULL when item is edited QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: joy(a)bywatersolutions.com Hardware: All Status: NEW Version: rel_3_6 Component: Cataloging Product: Koha When an item is edited, the field items.permanent_location is set to NULL. This causes significant problems when a library is utilizing the CART and PROC system preferences to assign CART and PROC shelving locations. If items.permanent_location is NULL then there is no way to restore the original shelving location for these items. This results in significant data loss for libraries. -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 6780] New: Log duplicate card issuance
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6780 Bug #: 6780 Summary: Log duplicate card issuance Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com If patron related logging is turned on, log duplicate card issuance -- 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 3

[Bug 6760] New: Generate new card number on renewals and duplicate card issuance
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6760 Bug #: 6760 Summary: Generate new card number on renewals and duplicate card issuance Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Some libraries need a new card to be generated on membership renewal and duplicate card issuance. A new sys pref will be created for this purpose. -- 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 8601] New: Allow more pictures on Patron Cards
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8601 Priority: P5 - low Change sponsored?: --- Bug ID: 8601 Assignee: cnighswonger(a)foundations.edu Summary: Allow more pictures on Patron Cards Severity: enhancement Classification: Unclassified OS: All Reporter: derrynj(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: Label printing Product: Koha Currently there is only 2 pictures allowed on patron card. This is acceptable, however it would be nice to be able to add more with an "add another image" button or something along those lines. At the very least, could we free up a custom image by making the patron image a separate component? I've tried adding extra images to the XML code in the database, and it seems to work just by incrementing the image number value. -- You are receiving this mail because: You are watching all bug changes.

1 3