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

[Bug 5017] New: can enter multiple funds with the same code
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '12

15 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5017 Summary: can enter multiple funds with the same code Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2375 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2375 codes Code is not unique when adding funds - you can enter multiples with the same code - so why have a code? -- 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 5018] New: amount encumbered not showing on budgets
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '12

15 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5018 Summary: amount encumbered not showing on budgets Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 fund (cgi-bin/koha/admin/aqbudgets.pl?budget_period_id=3) not showing what is encumbered only what was spent - so it’s misleading to what is left in the budget - but it does show it on this page: cgi-bin/koha/acqui/acqui-home.pl -- 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 5798] New: SubscriptionHistory default not applied
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '12

15 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5798 Bug #: 5798 Summary: SubscriptionHistory default not applied Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org On a new install SubscriptionHistory is set to full history, but the default display is not full. To get it to show full you have to set it to 'a summary' and then save and then set it back to 'full' -- 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 5647] New: Enhanced Notices are using name and not id
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '12

14 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5647 Summary: Enhanced Notices are using name and not id Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal 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 According to bug 5646 the messaging preferences can't be translated because the code queries the name and not the id. I am opening a new bug here because that bug has been "resolved" with a work around. Instead I think the code should be updated to check for the primary key (id) instead of the name. This is necessary for translations and so that we can make changes to those labels. >From Bug 5646 (reported by Katrin) If you tranlate the message names in the installer sql files your messages will stop working, because the code relies on those have a specific value. - advance_notices.pl - C4/Members/Messaging.pm - C4/Form/MessagingPreferences.pm ... In C4/Members/Messaging.pm I found following lines: 47 my $preferences = C4::Members::Messaging::GetMessagingPreferences( { borrowernumber => $borrower->{'borrowernumber'}, 48 message_name => 'DUE' } ); 50 my $preferences = C4::Members::Messaging::GetMessagingPreferences( { categorycode => 'LIBRARY', 51 message_name => 'DUE' } ); We don't have DUE as a message name in the en file. Bug? -- 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 5793] New: parameters in guided reports are lost when changing result page
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '12

14 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5793 Bug #: 5793 Summary: parameters in guided reports are lost when changing result page Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Reports AssignedTo: gmcharlt(a)gmail.com ReportedBy: jmlongo(a)uncu.edu.ar QAContact: koha-bugs(a)lists.koha-community.org When a guided report that needs a run time parameter is executed it works fine, but if the results are presented in more than one page, clicking either a page number or the 'next page' link (>) executes the report as if it was the first time. It asks for the run time parameter again and presents the first page of results. Tests show that this is fixed adding 'sql_param=[runtime parameter here]' to the link to the other results pages. -- 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 5005] New: Branch transfer limits page doesn't show current branch in select menu
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '12

07 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5005 Summary: Branch transfer limits page doesn't show current branch in select menu Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: /cgi-bin/koha/admin/branch_transfer_limits.pl?branchco de=XXX OS/Version: All Status: NEW Severity: minor Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 The "Select a library" menu should automatically preselect the currently chosen branch in order to give visual feedback about branch being modified. -- 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 4947] New: patron restricted message unclear
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '12

07 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4947 Summary: patron restricted message unclear Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 In the patron management and overdue notice settings you can 'debar' a patron, but when you do that the patron record says they're 'restricted' - we should use the same language so that it's clear that this is why the patron cannot check out I also recommend a change to bar instead of debar which seems to mean the opposite of what it does. -- 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 5361] New: Internal note on each order line
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '12

06 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5361 Summary: Internal note on each order line Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/Internal_note_orde r_line_acq_RFC OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Deadline: 2011-05-01 A field will be added on each order line : internal note. It will be only for the library. In case of the move of an order, the internal note will be automatically filled with some information specified by the librarian -- 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

[Bug 5568] New: Upgrade Amazon module to support Product Advertising API
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '12

02 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5568 Summary: Upgrade Amazon module to support Product Advertising API Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: jeremy(a)bicha.net QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Amazon reviews no longer display in OPAC because Amazon has changed the API again. More information can be found in the documentation: http://aws.amazon.com/archives/Product%20Advertising%20API === Dear Developer, On November 8, 2010 the Reviews response group of the Product Advertising API will no longer return customer reviews content and instead will return a link to customer reviews content hosted on Amazon.com. You will be able to display customer reviews on your site using that link. Please refer to the Product Advertising API Developer guide found here for more details. The Reviews response group will continue to function as before until November 8 and the new link to customer reviews is available to you now through the Product Advertising API as well. We are introducing efficiency guidelines for high volume users related to API usage. These guidelines are designed to promote efficient use of the API while providing the most effective advertising functionality and feature-set for application developers like you. Starting October 15 all usage will be subject to the efficiency guidelines. In addition, due to low usage, we plan to deprecate a subset of API operations and response groups. Please refer to the "Efficiency Guidelines" and "API Changes" sections below for details on the efficiency guidelines and API operations/response groups slated for deprecation. The efficiency guidelines will be phased in over a period of three months, starting July 15, and by October 15 all usage will be subject to these guidelines. The Product Advertising API Team. Efficiency Guidelines The purpose of the Product Advertising API is to advertise Amazon Products and thereby enable Associates to make money by creating Amazon advertisements and sending traffic back to Amazon. A small number of users are requesting very large amounts of product data while generating a very small amount of product sales. The Product Advertising API efficiency guidelines are designed to promote efficient use of the API. Each account used to access the Product Advertising API will be allowed an initial usage limit of 2,000 requests per hour. Each account will receive an additional 500 requests per hour (up to a maximum of 25,000 requests per hour) for every $1 of shipped item revenue driven per hour in a trailing 30-day period. Usage thresholds are recalculated daily based on revenue performance. To ensure that each account qualifies for the additional threshold increase, the URLs served by the Product Advertising API must be used when linking back to Amazon and the Associate tags used must belong to the account owner. API Changes Due to low usage, the Product Advertising API operations and response groups listed below will not be supported after October 15, 2010: Operations: CustomerContentLookup, CustomerContentSearch, Help, ListLookup, ListSearch, TagLookup, TransactionLookup, VehiclePartLookup, VehiclePartSearch, VehicleSearch. Response Group: ListmaniaLists, MerchantItemAttributes, PromotionDetails, Subjects, Tags, TagsSummary, VariationMinimum Additionally, due to low usage, we will be discontinuing Multiple Operation Requests and the TextStream search parameter. === -- 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 5

[Bug 5646] New: translated message names on sql level break messaging
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '12

01 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5646 Summary: translated message names on sql level break messaging Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: I18N/L10N AssignedTo: frederic(a)tamil.fr ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 If you tranlate the message names in the installer sql files your messages will stop working, because the code relies on those have a specific value. - advance_notices.pl - C4/Members/Messaging.pm - C4/Form/MessagingPreferences.pm ... In C4/Members/Messaging.pm I found following lines: 47 my $preferences = C4::Members::Messaging::GetMessagingPreferences( { borrowernumber => $borrower->{'borrowernumber'}, 48 message_name => 'DUE' } ); 50 my $preferences = C4::Members::Messaging::GetMessagingPreferences( { categorycode => 'LIBRARY', 51 message_name => 'DUE' } ); We don't have DUE as a message name in the en file. Bug? Patch will undo my translation and other people's translations of those values. This means message names in borrower category and borrower account are not translatable at the moment. I think we need to change the templates to make them translatable? -- 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 16