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

[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 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 6778] New: Display suggestor's name in catalog detail page
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6778 Bug #: 6778 Summary: Display suggestor's name in catalog detail page Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha-bugs(a)lists.koha-community.org Display suggestor's name in catalogue detail page (both regular and XSLT views) -- 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 6341] New: Request for multiple calendar support option
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6341 Bug #: 6341 Summary: Request for multiple calendar support option Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Holidays AssignedTo: henridamien(a)koha-fr.org ReportedBy: indradg(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Koha provides only a single calendar option - the Gregorian calendar. However, in places like India, the *official* national calendar is not Gregorian, although it is used alongside. Plus in rural parts of country, many people still using the "old" non-Gregorian standard. See http://en.wikipedia.org/wiki/Indian_national_calendar It will be nice if Koha can support the option of choosing from multiple calendars. I believe support for Hejri (the Islamic calendar) may also be required for middle-East deployments. -- 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 1

[Bug 6563] New: Default OPAC language not set properly
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6563 Bug #: 6563 Summary: Default OPAC language not set properly Classification: Unclassified Change sponsored?: Sponsored Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: I18N/L10N AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org For libraries with multiple installed and enabled OPAC languages, the first enabled language in the list of activated languages is selected as default, not the primary language for the installation. To reproduce: 1. Install multiple OPAC languages 2. Active one that is 'higher' on the list than your native install language 3. Go to the OPAC, and see that that language, not your native language, displays Root of the problem: Line 57 of opac/opac-main.pl references "opac-main.tmpl", which no longer exists since the conversion to Template::Toolkit. Changing this to opac-main.tt fixes the issue. Patch forthcoming. -- 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 13

[Bug 6416] New: koha-remove fails when dropping user
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6416 Bug #: 6416 Summary: koha-remove fails when dropping user Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Packaging AssignedTo: robin(a)catalyst.net.nz ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org I have MySQL running on the same machine as Apache/Koha, and have created a new library with "sudo koha-create --create-db demo". When i do "sudo koha-remove demo" I get this: Removing Koha instance demo ERROR 1396 (HY000) at line 1: Operation DROP USER failed for 'koha_demo'@'%' When I log in to mysql as root and do this: DROP USER failed for 'koha_demo'@'%'; I get pretty much the same message. But when I replace % with localhost and do this: DROP USER failed for 'koha_demo'@'localhost'; it succeeds. -- 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 6798] New: Make koha-create send email with details of created site
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6798 Bug #: 6798 Summary: Make koha-create send email with details of created site Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: magnus(a)enger.priv.no ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org The packages are so awesome, it takes way longer to tell someone you set up an instance for them, than to create the actual instance. So why not make koha-create do even more of the work? I'm thinking of adding two more options: --emailto = Make koha-create send an email to the given address that contains the URLs for OPAC and intranet, username and password. This could be someone who is going to use the instance, or yourself, for future reference or forwarding to whoever needs it. --emailtemplate = point to a custom template for the email, instead of the default one. I'm thinking both of these could be set in the configfiles, as well as on the command line. If you have two different configfiles you might want to have different email templates for each of them. The one usecase I can think of for having the email in a configfile is if you want to send the details of created instances to yourself, either just as a reminder or for forwarding to whoever else needs the information. Sending the password in an email like this might be A Bad Thing, but the passwords are supposed to be temporary anyway, right? -- 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 1

[Bug 5851] New: SIP Slips printed in wrong circumstances -- Local hold and no hold items
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5851 Bug #: 5851 Summary: SIP Slips printed in wrong circumstances -- Local hold and no hold items Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: SIP2 AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Here is how we would like the check-in process to work in Koha on the SIP connection: 1) a WALKIN item type should never generate a hold slip (currently does) 2) a LOCALHOLD type should only generate a hold slip if there is an unfilled hold for a local patron (currently does for any hold) 3) If a hold slip is generated for any valid circumstances... a) the item processed should be tied to the patron on the slip b) the item should be in the proper status (hold should be confirmed and put in transit if necessary) In summary, when a hold slip is generated we should be able to place the slip in the item and put it in the courier or on our hold shelf. -- 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 6676] New: Acquisition basket access control trivially by-passable
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6676 Bug #: 6676 Summary: Acquisition basket access control trivially by-passable Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: ef(a)math.uni-bonn.de QAContact: koha-bugs(a)lists.koha-community.org Currently, while booksellers.pl tries to restrict a user's ability to view baskets, that's trivially circumvented by simply altering the basketno CGI parameter to, e.g. baket.pl. I can think of three ways to close this security hole: 1. Check permissions in every script that deals with baskets. This would probably require an extension to C4::Auth. 2. Randomise basket numbers. 3. Add a random key to each basket that must be given as a CGI parameter (in addition to basketno) in order for a script to allow access to that basket. -- 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 6