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

[Bug 8089] New: Use Koha::Cache everywhere
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '15

17 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8089 Priority: P5 - low Change sponsored?: --- Bug ID: 8089 Assignee: gmcharlt(a)gmail.com Summary: Use Koha::Cache everywhere Severity: enhancement Classification: Unclassified OS: All Reporter: jcamins(a)cpbibliography.com Hardware: All Status: NEW Version: master Component: Architecture, internals, and plumbing Depends on: 7248 Product: Koha -- You are receiving this mail because: You are watching all bug changes.

1 65

[Bug 9434] New: Static variables used for caches are not Plack-friendly
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '15

17 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9434 Bug ID: 9434 Summary: Static variables used for caches are not Plack-friendly Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: jcamins(a)cpbibliography.com At the moment we cache numerous pieces of information in module-level variables which then do not get updated in other threads/processes when they are changed by the user. This is a serious usability issue. Examples of this include the way we treat sysprefs (there is now a method to disable the syspref cache, but by default it is enabled), notices, frameworks, field mappings, and koha-conf.xml, at least. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 5515] New: Leading 'and' in search never returns a result
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '15

14 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5515 Summary: Leading 'and' in search never returns a result Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: bob-ewart(a)bobsown.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Searching on "and the band played on" returns no results. There are 3 biblios for that title, a book, a DVD and a video. The error log shows: [Thu Dec 16 17:18:27 2010] [error] [client 127.0.0.2] [Thu Dec 16 17:18:27 2010] search.pl: WARNING: query problem with kw,wrdl,rtrn=and band played ZOOM error 10014 "CCL parsing error" (addinfo: "Search word expected") from diag-set 'ZOOM' at /usr/share/koha/lib/C4/Search.pm line 346., referer: http://127.0.0.2:8080/cgi-bin/koha/mainpage.pl This happens with Koha 3.02.01 on openSUSE 11.3 (32-bit and 64-bit) and on Debian squeeze/sid (64-bit) with zebra. Searching on 'the band played on' gets all three records. -- 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 10

[Bug 8697] New: slips not using custom lists on all pages
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '15

14 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8697 Priority: P5 - low Change sponsored?: --- Bug ID: 8697 Assignee: koha-bugs(a)lists.koha-community.org Summary: slips not using custom lists on all pages Severity: major Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Notices Product: Koha When on the patron record on the Details or Fines tab if you choose to print slip or quick slip it chooses the 'all libraries' slip. Other tabs - like the checkout tab use the custom slip for that branch. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 6976] New: User hold limit can be avoided by users in OPAC
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '15

14 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6976 Bug #: 6976 Summary: User hold limit can be avoided by users in OPAC Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: colin.campbell(a)ptfs-europe.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Problem as reported: borrowers are only allowed 5 holds. If holds are done individually, it is obeying that law i.e. X has held 5 separate books – when I tried to do a 6th book it told me that I could not place a hold. However, if a borrower checks the catalogue, gets the intial list up and clicks items on the “results” box and then clicks “place hold” they can hold more than 5 items – I have been able to hold 8 (and I suspect could do more) Looks like the logic is a bit flawed when placing multiple holds as the variable canreserve is not reset for each iteration of the loop. Testing fix on site patch to follow -- 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 7830] New: return policy error in hold policy by item type after upgrade
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '15

14 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7830 Priority: P5 - low Change sponsored?: --- Bug ID: 7830 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: return policy error in hold policy by item type after upgrade QA Contact: koha.sekjal(a)gmail.com Severity: major Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Circulation Depends on: 7144 Product: Koha Created attachment 8633 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8633&action=edit error message After upgrading to master (as of this morning) I see the attached on my circ and fine rules. Shouldn't this have a default value set on upgrade so that there isn't an error? I think this comes from the Floating Collections dev - but I'm not sure. Adding a 'depends on' for that bug report. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 9730] New: The sub 'AnonymiseIssueHistory' fails quietly if 'AnonymousPatron' is not a valid entry
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '15

14 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9730 Bug ID: 9730 Summary: The sub 'AnonymiseIssueHistory' fails quietly if 'AnonymousPatron' is not a valid entry Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: christophe.croullebois(a)biblibre.com it fails also if 'AnonymousPatron' = 0 With the patch in this case the borrowernumber becomes NULL -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 8411] New: merging allows for creation of duplicate fields where not allowed
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '15

13 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8411 Priority: P5 - low Change sponsored?: --- Bug ID: 8411 CC: m.de.rooy(a)rijksmuseum.nl Assignee: gmcharlt(a)gmail.com Summary: merging allows for creation of duplicate fields where not allowed Severity: critical Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Cataloging Product: Koha See here : http://manual.koha-community.org/3.8/en/stafflists.html#mergebibrecs the merging bib records tool used to stop you from adding fields if they were not repeatable, but I was just able to add the two 001 fields to my destination record but the framework says it's not repeatable. For the 999 it didn't add it but didn't give me an error either. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 7571] New: Maintain exchange rate history
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '15

13 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7571 Bug #: 7571 Summary: Maintain exchange rate history Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha.sekjal(a)gmail.com Indian libraries need to maintain exchange rates across time. When items are invocied, sometime invoice date can be in the past, the actual cost needs to be calculated using the exchange rate as it stood on the inovice date. With this change Koha will store exchange rates for each currency along with "last update date". Invoicing and receiving pages will be changed to calculate actual cost based on exchange rates as on on invoice dates. -- 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 19

[Bug 5711] New: Distinction between authors/additional authors in opac normal view (MARC21/XSLT)
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '15

13 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5711 Summary: Distinction between authors/additional authors in opac normal view (MARC21/XSLT) Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The patch for bug 5701 put the additional authors with their relator codes on their own line in the staff client and we should do the same in the OPAC. I suggest a further break out that looks like this: Author: Editor: Illustrator: Translator: Additional Authors: Otherwise the editor or translator will appear as an author and that's confusing I think to the patrons. Relator Codes here: http://www.loc.gov/marc/relators/relaterm.html -- 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 7