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

[Bug 7770] New: usage of OPACBaseURL
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7770 Priority: P5 - low Change sponsored?: --- Bug ID: 7770 CC: gmcharlt(a)gmail.com Assignee: paul.poulain(a)biblibre.com Summary: usage of OPACBaseURL QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: laurence.lefaucheur(a)biblibre.com Hardware: All Status: NEW Version: rel_3_8 Component: System Administration Product: Koha System preferences OPACBaseURL is used at different places in koha, for instance : - CAS authentication (7745) - OAI - file upload (6874) Description of the syspref indicates that http:// will automatically be added. We tested that for oai biblio url and for CAS, it is not the case, and we have to fill http:// in the syspref. The usage of this syspref in Koha and how it should be really filled should be precised so that it is consistent everywhere -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 10654] New: Add featute: export basket in CSV, list of custom formats for various vendors
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10654 Bug ID: 10654 Summary: Add featute: export basket in CSV, list of custom formats for various vendors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P3 Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 19977 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=19977&action=edit screenshot of menu Hello, in Koha we can set custom format of CSV for basket export from OPAC. I think that very useful feature can be same option for export from basket in module acquisition. Our vendors accept import of orders in CSV in their e-shops but formats are various. Is possible to add into button "Export this basket as CSV" some pull-down list of vendors and export order in specific CSV format? Thank You. Mike -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 9120] New: Typing the ENTER key when submitting a tag from search results reloads the page
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9120 Bug ID: 9120 Summary: Typing the ENTER key when submitting a tag from search results reloads the page Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org If you have TagsInputOnList enabled and you are entering tags from the OPAC search results page, typing ENTER instead of clicking the "Add" button reloads the page without submitting the tag. The tag submission operation should be triggered without affecting the page state. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 11120] New: The date option for the overdue_notices cronjob is broken
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11120 Bug ID: 11120 Summary: The date option for the overdue_notices cronjob is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 7447 introduces the --date option for overdue notices. This option has never worked: the code is waiting for a value but the option is defined as a boolean. The date should be defined as --date:s and the script should correctly manage this option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 9227] New: items in transit can be checked out without warning
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9227 Bug ID: 9227 Summary: items in transit can be checked out without warning Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.8 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you try to check out items with different statuses (on hold for example) you get a warning, but if you try to check out an item that's in transit you don't get that warning and should. See here: http://screencast.com/t/wu3iJMdU -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 10606] New: query in GetUpcomingDueIssues
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '15

30 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10606 Bug ID: 10606 Summary: query in GetUpcomingDueIssues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The patch for bug 9362 (which I did accept into master) introduces a MySQLism: Using HAVING without GROUP BY is a MySQLism, so at some point the query will have to become: SELECT issues.*, items.itype as itemtype, items.homebranch, TO_DAYS( date_due )-TO_DAYS( NOW() ) as days_until_due, branches.branchemail FROM issues LEFT JOIN items USING (itemnumber) LEFT OUTER JOIN branches USING (branchcode) WHERE returndate is NULL AND (TO_DAYS( date_due )-TO_DAYS( NOW() )) > 0 AND (TO_DAYS( date_due )-TO_DAYS( NOW() )) < ?; This is a pity, as it would be nice to be able to use "days_until_due" as an alias to make the query more readable, but it simply isn't portable. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 10263] New: Add ability to limit which branch can edit a bibliographic record
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '15

30 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10263 Bug ID: 10263 Summary: Add ability to limit which branch can edit a bibliographic record Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: kyle.m.hall(a)gmail.com CC: m.de.rooy(a)rijksmuseum.nl Right now, it's possible to limit who can edit items by using IndependantBranches. However, Koha has no method of limiting who can edit bibliographic records, as they have no defined owner. -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 7650] New: total not always right on checkout summary
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '15

30 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7650 Priority: P5 - low Change sponsored?: --- Bug ID: 7650 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: total not always right on checkout summary QA Contact: koha.sekjal(a)gmail.com Severity: normal Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Circulation Product: Koha Created attachment 8024 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8024&action=edit total not matching the sum of above lines See attached. Every once in a while I'm noticing that the total shown does not add up the items above it - but I can't figure out what's making it not work or where the extra money is coming from. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 6505] New: purchase order not populating all fields
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '15

27 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6505 Bug #: 6505 Summary: purchase order not populating all fields Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org The purchase order PDF is not pulling info from the libraries. There are labels for Phone number Fax Billing address Email But they're not printing that info. Also, the library name is coming from the system preference for libraryname and not from the libraries admin area - all the info on the purchase order should comes from the data you enter in admin > libraries -- 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 6579] New: getalert SQL invalid for KOHA_USER
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '15

27 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6579 Bug #: 6579 Summary: getalert SQL invalid for KOHA_USER Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: ohiocore(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org The code for getalert in C4::Letters fails to account for one important case. While the POD says "all parameters NON mandatory", the result of NO arguments produces invalid SQL. The errors in the log look like: [error] [client 71.64.0.171] [Mon Jul 11 19:54:12 2011] opac-user.pl: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 at /usr/share/koha/lib/C4/Letters.pm line 197, <DATA> line 522., referer: https://my.koha.edu/cgi-bin/koha/opac-user.pl [error] [client 71.64.0.171] [Mon Jul 11 19:54:12 2011] opac-user.pl: DBD::mysql::st fetchall_arrayref failed: fetch() without execute() at /usr/share/koha/lib/C4/Letters.pm line 198, <DATA> line 522., referer: https://my.koha.edu/cgi-bin/koha/opac-user.pl If you look at the logic, you'll agree that "SELECT * FROM alert WHERE" is not a valid SQL query. Code should assemble bind name/value pairs in a hash instead of appending to the query and pushing onto an array. Then build the WHERE clause at the end only when hash is populated. -- 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