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

[Bug 7802] New: A MySQLism is used to get the current date.
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '15

16 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7802 Priority: P5 - low Change sponsored?: --- Bug ID: 7802 Assignee: gmcharlt(a)gmail.com Summary: A MySQLism is used to get the current date. QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: marc(a)msys.ch Hardware: All Status: NEW Version: unspecified Component: Database Product: Koha To get todays date, the MySQL only function CURDATE() or CURRENT_DATE() is being used in many places. Neither CURDATE() nor CURRENT_DATE() must be used, but instead the standard form CAST(now() AS date). -- You are receiving this mail because: You are watching all bug changes.

1 49

[Bug 7172] New: Data Persistency
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '15

16 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7172 Bug #: 7172 Summary: Data Persistency Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: major Priority: P1 - high Component: Architecture, internals, and plumbing AssignedTo: paul.poulain(a)biblibre.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: ian.walls(a)bywatersolutions.com Blocks: 7119 We need to fix up the code throughout the system to be able to handle data faster-than-CGI processors like Plack, FastCGI or mod_perl. At this time, most of Koha can run okay, but when errors happen, they crash HARD. Some issues than need attention: nested subroutines: mod_perl, and I think other systems, turn each script into a subroutine. If you have subroutines in subroutines (as we do in C4 and some of the scripts), and an inner subroutine modifies a variable declared outside in the outer subroutine, you will get an error "variable will not stay shared". This can sometimes (always?) be fixed by using "our" instead of "my". Or using better coding practices :) memory leaks: some memory may not be released, so a persistent engine could bloat over time. other issues may come up, 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 48

[Bug 4888] New: pre-set of field indicators value
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '15

15 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4888 Summary: pre-set of field indicators value Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: s.bolelli(a)libercoop.it QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 Building a MARC Framework now is not possible to set default values for the field indicators. It would be very useful to set default values for indicators because in many cases they change very rarely -- 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 4948] New: canceling a hold missing steps for existing holds
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '15

13 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4948 Summary: canceling a hold missing steps for existing holds Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: cgi-bin/koha/circ/waitingreserves.pl OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Hold requests AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 on holds waiting report you click cancel and it tells you that there is a hold for someone else the button below that says submit query which isn't helpful and it doesn't present you with the option to confirm or cancel the hold or a way to print a slip -- all things that are needed in this scenario -- 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 7840] New: Koha as a CMS
by bugzilla-daemon＠bugs.koha-community.org 12 Oct '15

12 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7840 Priority: P5 - low Change sponsored?: --- Bug ID: 7840 Assignee: nengard(a)gmail.com Summary: Koha as a CMS QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: magnus(a)enger.priv.no Hardware: All Status: NEW Version: master Component: Documentation Product: Koha * magnuse has a library asking about "Using Koha as a Content Management System" <magnuse> http://manual.koha-community.org/3.6/en/kohacms.html <magnuse> http://wiki.koha-community.org/wiki/Koha_as_a_CMS <magnuse> no plan on implementing that hack - feels like it should either be part of koha or removed from the manual? <kf> magnuse: I guess perhaps implementing the hack as a real featurew would be nice <kf> I have had some problems with editing localuse prefernces :( there is a bug <kf> on bugzilla for that <kf> magnuse: perhaps it could be an enhancement to work similar to the news? <slef> we've used koha as a CMS before. Not sure if it was that hack or an earlier one. Basically: don't. Use a CMS. <kf> slef: I agree, but an option to add a few pages is nice <kf> slef: not full cms functionality, but perhaps things like a help page <slef> anyone like to open a bug suggesting dropping Appendix E from the manual, or integrate it properly, using extending news instead of using sysprefs? So what do we want to do? 1. Remove appendix E from the manual? 2. Implement limited CMS-functionality properly? -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 7899] New: Remove C4::Dates from C4::Circulation
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '15

09 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7899 Priority: P5 - low Change sponsored?: --- Bug ID: 7899 Assignee: tdavis(a)uttyler.edu Summary: Remove C4::Dates from C4::Circulation QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: koha.sekjal(a)gmail.com Hardware: All Status: NEW Version: master Component: Architecture, internals, and plumbing Product: Koha Now that we have Koha::Calendar and DateTime, we no longer need C4::Dates in C4::Circulation There are currently 6 usages of the module left: 2 'use' calls to this... both will be removed. 2 calls to format_date in CanBookBeIssued (needsconfirmation message). Will need to replace with KohaDates plugin on all template pages using this subroutine "if (C4::Context->preference('globalDueDate') && (C4::Context->preference('globalDueDate') =~ C4::Dates->regexp('syspref')" is never true since that syspref was removed, so it can be removed entirely sub TransferSlip creates a new $pulldate variable, but never uses it before the subroutine exits. Can be removed The rest of the usage here is in the POD, which needs to be updated to reflect the new type of objects we're using now with Hourly Loans. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 4858] New: Ability to Charge for Print Notices
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '15

09 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4858 Summary: Ability to Charge for Print Notices Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 With budgets being cut left and right, it would be great if libraries had the ability to choose to charge patrons who insisted on receiving notices (overdue and hold waiting) via snail mail. -- 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 8137] New: Checkout limit by patron category for all libraries
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '15

07 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 Priority: P5 - low Change sponsored?: --- Bug ID: 8137 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: Checkout limit by patron category for all libraries Severity: enhancement Classification: Unclassified OS: All Reporter: kyle.m.hall(a)gmail.com Hardware: All Status: NEW Version: master Component: Circulation Product: Koha We have a patron category Temporary Adult WTMP. Under "Checkout limit by patron category for all libraries" the limit is set to 5. This limit is not working. I was able to check out 7 items to Robert Harper (24388200094358)in the WTMP category Here is what is going on. We have the system preference CircControl set to "Use the checkout and fines rules of *the library where the item is from*". we also have this limit set to 5. So what Koha is doing, is comparing the limit to the number of checkouts of items the borrower has *from the same home library as that item*. If the item's home library is LibA, and the borrower has 4 items checked out whose home library is LibA, than the item will be checked out ( regardless of how many items are checked out ). If the borrower has 5 items checked out whose home library is LibA, Koha will indeed warn of too many checkouts. This does not seem intuitive. Is there any way to globally limit the number if checkouts a borrower can have by patron category? -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 8127] New: Most Circulated Items not working right
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '15

06 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127 Priority: P5 - low Change sponsored?: --- Bug ID: 8127 Assignee: gmcharlt(a)gmail.com Summary: Most Circulated Items not working right Severity: normal Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Reports Product: Koha I got this from a library: I'm trying to get the "Most Circulated Items" report to give me something and I am not having success. I chose a date range of 4 months, then I chose a library, then I chose a single item type (DVD1week) then I chose 20 for the limit, then I chose "library" for the "By" part of the limit and go an empty list. So I went back and changed "library" to "Itemtype." Now the system just hangs up spinning away without ever giving results. I wrote this to help for now - but the canned report should work: SELECT count(s.datetime) AS circs, b.title, b.author, i.ccode FROM statistics s JOIN items i USING (itemnumber) LEFT JOIN biblio b USING (biblionumber) WHERE DATE(s.datetime) > DATE_SUB(CURRENT_DATE(),INTERVAL 4 MONTH) AND DATE(s.datetime)<=CURRENT_DATE() AND s.itemnumber IS NOT NULL AND i.itype=<<Item type|itemtypes>> AND i.hombranch=<<Home branch|branches>> GROUP BY b.biblionumber ORDER BY circs DESC LIMIT 20 -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 6379] New: Remove link from unapproved and rejected tags in the OPAC's "My tags" table
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '15

05 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6379 Bug #: 6379 Summary: Remove link from unapproved and rejected tags in the OPAC's "My tags" table Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: /cgi-bin/koha/opac-tags.pl OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org You can't perform a search of the catalog using unapproved or rejected tags, so the table of the user's tags should not have clickable links for them. There should probably be additional visual feedback to indicate why the term isn't clickable. -- 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 26