September 2018 - Koha-bugs - lists.koha-community.org

[Bug 19019] New: Patron clubs feature needs documentation
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '18

22 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19019 Bug ID: 19019 Summary: Patron clubs feature needs documentation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 12461 This bug is a good argument for a "no docs no pushie" rule. We should have documentation in place for any feature in a stable release. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12461 [Bug 12461] Add patron clubs feature -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 19087] New: Creating a serial with a seasonal pattern only starts with Spring
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19087 Bug ID: 19087 Summary: Creating a serial with a seasonal pattern only starts with Spring Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com The seasonal pattern for a 2x a year frequency does not work as expected. When using a serial that is a Summer & Winter frequency. If starting the serial with the Summer Issue, setting the last value and inner counter will only default to a Spring start in the test pattern. Setting the last value as any season, will still default to a spring start to the test pattern. The test pattern will adjust after the first two issues- Spring Fall, Summer, Winter, Summer, Winter, etc - but Koha insists on starting this pattern with Spring. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 13228] Documentation of 'restrictions' tab does not show "OVERDUE" restriction
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13228 Caroline Cyr La Rose <caroline.cyr-la-rose(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #5 from Caroline Cyr La Rose <caroline.cyr-la-rose(a)inlibro.com> --- I don't know what was wrong before. I retested and everything works perfectly. https://gitlab.com/koha-community/koha-manual/merge_requests/164 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10419] There is no cronjob script for deleting patrons
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10419 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |20915 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20915 [Bug 20915] Use date --iso-8601 instead of date +%Y-%m-%d to be more readable and crontab friendly -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 20631] New: C4::Acounts claims to use ReturnLostItem but doesn't
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20631 Bug ID: 20631 Summary: C4::Acounts claims to use ReturnLostItem but doesn't Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org use C4::Circulation qw(ReturnLostItem); When looking for ReturnLostItem I noticed it's listed in C4::Accounts, but appears not to be used there. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 12460] Search history: Combine to start a new search
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12460 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA CC| |jonathan.druart(a)bugs.koha-c | |ommunity.org --- Comment #34 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- Hi Julian, 1. minor: FAIL koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/search-history.tt FAIL forbidden patterns forbidden pattern: Do not use line breaks inside template tags (bug 18675) (line 104) forbidden pattern: Do not use line breaks inside template tags (bug 18675) (line 114) FAIL koha-tmpl/opac-tmpl/bootstrap/en/modules/opac-search-history.tt FAIL forbidden patterns forbidden pattern: Do not use line breaks inside template tags (bug 18675) (line 133) forbidden pattern: Do not use line breaks inside template tags (bug 18675) (line 144) 2. Bad news but... this will not work with Elastic, right? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15494] Block renewals by arbitrary item values
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

1 0

[Bug 15494] Block renewals by arbitrary item values
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15494 --- Comment #50 from Nick Clemens <nick(a)bywatersolutions.com> --- (In reply to Jonathan Druart from comment #39) > 1. In tests, prefer > Koha::IssuingRules->search->update($what_you_need_to_be_set); > instead of the DELETE then INSERT. It makes the changes more readable in my > opinion. I generally agree, but circ rules are messy and this file has the same code existing. Should be refactored as a whole > 2. What about "NULL" string values? :) I think we expect a certain level of input from the user and are fairly thorough here > 3. Should not we have the same code for > OpacHiddenItems and ItemsDeniedRenewal (and UpdateNotForLoanStatusOnCheckin?) > There is also UpdateItemLocationOnCheckin (bug 14576) > > The minimum would be a new get_rules_from_prefs sub Moved to its own sub/module - changes for other prefs should be on their own reports > Ah! Not sure the reason is available in the template tho. The reasons are stored in the issues table, they should be available to templates -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15494] Block renewals by arbitrary item values
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15494 --- Comment #49 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 79254 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=79254&action=ed… Bug 15494: Move yaml syspref code to its own sub To test: 1 - prove -v t/db_dependent/Koha/Util/SystemPreferences.t -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15494] Block renewals by arbitrary item values
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15494 --- Comment #48 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 79253 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=79253&action=ed… Bug 15494: (QA follow-up) Additional polishing [1] Fix two typos in Circulation.t. Although the test does not fail, line 2127 contains two typos. Changing INVISILE to INVISIBLE :) And type should be itype. [2] Remove $yaml as leftover from older code. [3] Add a next when the split on /:/ does not give two results. This will prevent uninit warnings (although still disabled now in Circulation). [4] For the same reason we should switch the lines for NULL and empty string. The undefs you insert should trigger a warn. [5] The line for empty string should not insert undef, but empty string. For the same reason adding the condition defined($_) ... And proving it by adding two tests for the opposite values of callnumber and itemnotes. [6] Adding a strip spaces around the fieldname. User friendly.. Signed-off-by: Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.

1 0