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

[Bug 2280] authorized value for indicators in UNIMARC Framework at field level
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '12

02 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2280 --- Comment #2 from Zeno Tajoli <tajoli(a)cilea.it> --- In Unimarc indicator can be specified in a list. But often a specific list for every field. Also for me this is and ENH. But in fact the column 'authorized values' is present and doesn't work. -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 2712] Invalid 3rd party content ( eg Amazon ) can break page layout
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '12

02 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2712 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |katrin.fischer(a)bsz-bw.de Depends on| |5568 Resolution|--- |WONTFIX --- Comment #1 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I am closing this bug as WONTFIX (see related bug 5568). -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 2619] Turning on XSLTResultsDisplay preference turns off item detail display
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '12

02 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2619 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de Version|rel_3_0 |master --- Comment #1 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- The system preference OPACItemsResultsDisplay still exists in current master. I am not sure if it's implemented for XSLT. I did a quick test and could see no change in my result display after switching the preference OFF/ON. I suggest the description of the system preference to be changed to reflect that this will not work with XSLT display (or fix XSLT to obey the system prefernece). -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2399] All status fields in the item edit interface offer two blank/null entries per dropdown instead of one
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '12

02 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2399 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|rel_3_2 |master --- Comment #3 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Updating version to master, 5 and 7 still have 2 empty lines theres For 3.6 it's 4,5 and 7. I think the problem is caused by the sample data for authorized values. Perhaps the line for 0 without description should be removed from all the sample data? But I am not sure if it's safe to do this? -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 2370] MARC21 non-public note is mapped to items.paidfor
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '12

02 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2370 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I did a quick check and items.paidfor is still mapped to internal note 952$x in current frameworks. But I disagree with the original bug reporter on the way to fix this. I think we need a new column in items and deleteditems for internal notes as proposed in bug 4222. This bug is currently stuck in "Failed QA" because of issues with the update process for existing installations. In order to move discussion there I am marking this bug as WONTFIX. Please reopen if I missed something. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 2280] authorized value for indicators in UNIMARC Framework at field level
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '12

02 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2280 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de --- Comment #1 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- For MARC21 it's not possible to specify a value list for indicators - I am not sure if UNIMARC is different here? Should this perhaps be an enhancement request instead? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2271] tmpl_process3.pl warns on a semmingly valid construct
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '12

02 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2271 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I have retested this and our unit tests catch both cases: <p [% IF ( loggedinusername ) %]class="something"[% END %] />Test</p> <p [% IF ( loggedinusername ) %]class="something"[% END %]/>Test</p> 1..1 not ok 1 - TT syntax: not using TT directive within HTML tag # Failed test 'TT syntax: not using TT directive within HTML tag' # at xt/tt_valid.t line 55. # Files list: # opac-tmpl/prog/en/modules/opac-main.tt: 39, 42 # Looks like you failed 1 test of 1. The test succeeds on current master and we will catch new instances. Even with those constructs updating and installing German templates generates no visible errrors for me: perl translate update de-DE perl translate instal de-DE The translated templates are ok in this case, but I believe there were problems with other similar constructs causing translation issues. I am marking this resolved fixed. Please reopen if I missed something. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 6907] New: remove unused 'borrowers.checkhist' column
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '12

01 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6907 Bug #: 6907 Summary: remove unused 'borrowers.checkhist' column Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Database AssignedTo: gmcharlt(a)gmail.com ReportedBy: mtj(a)kohaaloha.com QAContact: koha-bugs(a)lists.koha-community.org remove unused 'borrowers.checkhist' column, in files... ./koha-tmpl/intranet-tmpl/prog/en/columns.def ./koha-tmpl/intranet-tmpl/prog/fr-FR/columns.def -- 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 5889] New: Allow message names to be translatable
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '12

01 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5889 Bug #: 5889 Summary: Allow message names to be translatable Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: I18N/L10N AssignedTo: frederic(a)tamil.fr ReportedBy: julian.maurice(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Actually, message names are not translatable. Will submit a patch that makes it possible. -- 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