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

[Bug 17255] New: Upgrade Elastic Search code to work with version 2.4+
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '17

20 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17255 Bug ID: 17255 Summary: Upgrade Elastic Search code to work with version 2.4+ Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: chris(a)bigballofwax.co.nz QA Contact: testopia(a)bugs.koha-community.org Before building more things on Elastic (I have 3 things ready to go) We need to upgrade to work with the latest stable (2.4) This will involve getting a 2.4 cluster running, pointing Koha at it, and fixing any errors that occur. -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 17519] New: Item editor handles clearing dateaccessioned and replacementpricedate inconsistently
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '17

18 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17519 Bug ID: 17519 Summary: Item editor handles clearing dateaccessioned and replacementpricedate inconsistently Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 17366] New: create patron list, software error
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '17

15 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17366 Bug ID: 17366 Summary: create patron list, software error Change sponsored?: --- Product: Koha Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: arunet(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When we try to create patron lists the getting software error cgi-bin/koha/patron_lists/add-modify.pl getting software error Software error: Can't call method "patron_list_id" on an undefined value at /usr/share/koha/intranet/cgi-bin/patron_lists/add-modify.pl line 55. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 17533] New: Syncing private to public list or adding more specific permissions?
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '17

09 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17533 Bug ID: 17533 Summary: Syncing private to public list or adding more specific permissions? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I now have two lists: private list A (shared between some users), and public list B. A local custom cron job daily syncs changes from A to B. What I would like, is: Let this group of users that now share A, have permissions to add/delete entries from public list B (but no one else). The current permission strategy on public lists is all or nothing, but not just a group of selected users. What would be the best way to go to achieve this goal? What about giving staff users the right to add/delete entries from public lists? In my specific case the editors include a normal user ;) Redesign the whole permissions thing on lists? Aarg. Add a sync lists option? What do you think? -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 16961] New: Add the Koha::Objects->update method
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '17

08 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16961 Bug ID: 16961 Summary: Add the Koha::Objects->update method Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org In order to update several rows in a single query, we need this new method. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 17327] New: Item level holds no longer enforced
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '17

28 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17327 Bug ID: 17327 Summary: Item level holds no longer enforced Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Reported by Katrin: Example: - on shelf holds allowed - holds allowed 5 - holds on same record allowed 5 - FORCE item level holds On a record with only one item, you can only place a record level hold in OPAC now - which is against your circulation conditions. Another example: - record with 2 items - circulation rules as above, 1 hold allowed on the record - Item level holds: forced I can only place record level holds in OPAC and staff. At the moment, I am not able to place item level holds in any circumstances in my installation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 17782] New: Patron updated_on field should be set to current timestamp when borrower is deleted
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '17

23 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17782 Bug ID: 17782 Summary: Patron updated_on field should be set to current timestamp when borrower is deleted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently the timestamp is not udpated when a patron is deleted. This is because we insert the db value of updated_on from the patron when we move the borrower. Clearing the value beforehand should resolve this -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 17788] New: (MARC21) $9 fields not indexed in authority-linked fields
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '17

23 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17788 Bug ID: 17788 Summary: (MARC21) $9 fields not indexed in authority-linked fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org If you check the default framework shipped with Koha, you will notice several fields are linked to authority records (even though they might be hidden in the editor): MariaDB [koha_kohadev]> SELECT tagfield,tagsubfield,authtypecode FROM marc_subfield_structure WHERE authtypecode IS NOT NULL AND authtypecode<>'' AND frameworkcode='' GROUP BY tagfield,tagsubfield,authtypecode ; +----------+-------------+--------------+ | tagfield | tagsubfield | authtypecode | +----------+-------------+--------------+ | 100 | a | PERSO_NAME | | 110 | a | CORPO_NAME | | 111 | a | MEETI_NAME | | 130 | a | UNIF_TITLE | | 440 | a | UNIF_TITLE | | 600 | a | PERSO_NAME | | 610 | a | CORPO_NAME | | 611 | a | MEETI_NAME | | 630 | a | UNIF_TITLE | | 648 | a | CHRON_TERM | | 650 | a | TOPIC_TERM | | 651 | a | GEOGR_NAME | | 654 | a | TOPIC_TERM | | 655 | a | GENRE/FORM | | 656 | a | TOPIC_TERM | | 657 | a | TOPIC_TERM | | 658 | a | TOPIC_TERM | | 662 | a | GEOGR_NAME | | 690 | a | TOPIC_TERM | | 691 | a | GEOGR_NAME | | 696 | a | PERSO_NAME | | 697 | a | CORPO_NAME | | 698 | a | MEETI_NAME | | 699 | a | UNIF_TITLE | | 700 | a | PERSO_NAME | | 710 | a | CORPO_NAME | | 711 | a | MEETI_NAME | | 730 | a | UNIF_TITLE | | 796 | a | PERSO_NAME | | 797 | a | CORPO_NAME | | 798 | a | MEETI_NAME | | 799 | a | UNIF_TITLE | | 800 | a | PERSO_NAME | | 810 | a | CORPO_NAME | | 811 | a | MEETI_NAME | | 830 | a | UNIF_TITLE | | 896 | a | PERSO_NAME | | 897 | a | CORPO_NAME | | 898 | a | MEETI_NAME | | 899 | a | UNIF_TITLE | +----------+-------------+--------------+ But looking at etc/zebradb/marc_defs/marc21/biblio-koha-indexdefs.xml you will notice the $9 subfields is not correctly added to the Koha-Auth-Number:w index. This has the consequence of authority usage count not being precise if those fields are used and linked. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 16984] New: Acquisitions broken
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '17

23 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16984 Bug ID: 16984 Summary: Acquisitions broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In acquisitions, even if AcqCreateItem is set to create an item at the time of ordering, the item creation form does not display. Instead, this JavaScript error shows in the console: additem.js:176 Uncaught TypeError: window[events[i]] is not a function I believe this regression was introduced by bug 15531. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 16115] New: JavaScript error on item search form
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '17

23 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16115 Bug ID: 16115 Summary: JavaScript error on item search form Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/catalogue/itemsearch.pl OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org In the template for the item search page there is this at line 290: { 'type': 'select', 'values': [% notforloans.json %] }, [% notforloans.json %] appears to be undefined, whether the search form has been submitted or not. Viewing source shows this: { 'type': 'select', 'values': }, ...and the Firebug console reports this error: SyntaxError: expected expression, got '}' /cgi-bin/koha/catalogue/itemsearch.pl Line 240 -- You are receiving this mail because: You are watching all bug changes.

1 19