January 2017 - Koha-bugs - lists.koha-community.org

[Bug 17852] New: Multiple URLs (856) in list email are broken
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '17

15 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17852 Bug ID: 17852 Summary: Multiple URLs (856) in list email are broken 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Same bug as bug 14614, but for list emails send from staff and intranet. If there are multiple URLs (865 fields), the URLs get squashed together into 'one URL' in the email sent and are broken therefore. Same fix as for the other bugs should work nicely here. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 17865] New: If a subscription has no history end date, it shows as expired today in OPAC
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '17

15 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17865 Bug ID: 17865 Summary: If a subscription has no history end date, it shows as expired today in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com If there is no subscription histenddate (NULL) in subscriptionhistory, the subscription will show as expired today in the OPAC. I think this happens becasue of this bit in GetSubscriptionsFromBiblionumber: 451 if ( $subs->{enddate} eq '0000-00-00' ) { 452 $subs->{enddate} = ''; 453 } else { 454 $subs->{enddate} = output_pref( { dt => dt_from_string( $subs->{enddate}), dateonly => 1 } ); 455 } I am not sure why this appears to return the current date, but it seems a good candidate to start the search. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[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 17992] New: REST api: Cities controller should not use ->unblessed
by bugzilla-daemon＠bugs.koha-community.org 12 Mar '17

12 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17992 Bug ID: 17992 Summary: REST api: Cities controller should not use ->unblessed 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org As bug 17932 introduced the TO_JSON method there's no need to call ->unblessed anymore. As this is a reference implementation, I fix it to the new coding style. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 18000] New: Add --tablename option to misc/devel/ update_dbix_class_files.pl script
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '17

10 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18000 Bug ID: 18000 Summary: Add --tablename option to misc/devel/update_dbix_class_files.pl script Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Developers, Don't you think it's quite disturbing to see that all Koha schema files appear as modified in your git status when you ran update_dbix_class_files.pl script to get the one related to the table you've just created ? If yes, here is a patch that add the ability to specify a table name to this script, so test and sign. -- You are receiving this mail because: You are watching all bug changes.

1 13

[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 17988] New: Select2 prevents correct tag expand/ minimize functionality
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '17

25 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17988 Bug ID: 17988 Summary: Select2 prevents correct tag expand/minimize functionality Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: synapse.ova(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Overview: Select2 (Bug 13501) introduced divs and inputs that broke some assumptions about the expected HTML structure. Because of that, expanding fields to show all hidden subfields does not work properly. Steps to Reproduce: 1. Open some book in the editor or create new (cataloguing/addbiblio.pl) 2. Try to minimize or expand fields, that have among subfields the following: — Thesaurus driven subfield → subfield with Select2 — Hidden subfield. Actual Results: — some fields become hidden, some not, and vice versa — in the console, you'll see «Uncaught TypeError: Cannot read property 'match' of null» Expected Results: — all subfields should minimize/maximize completely Additional Information: This happens because Select2 adds some divs, that do not have ID property. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 17913] New: Merge three authority merge fixes
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '17

24 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17913 Bug ID: 17913 Summary: Merge three authority merge fixes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Best from 5572/11315/11700 comes here -- You are receiving this mail because: You are watching all bug changes.

1 104