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

[Bug 15545] Optionally make hold notes required when placing a hold ( via Koha::Plugin)
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15545 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|Signed Off |RESOLVED --- Comment #30 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- I'm kind of exhausted in finding new ways to get this simple change in Koha. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15545] Optionally make hold notes required when placing a hold ( via Koha::Plugin)
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15545 --- Comment #29 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Marcel de Rooy from comment #28) > (In reply to Jonathan Druart from comment #27) > > (In reply to Marcel de Rooy from comment #26) > > > (In reply to Jonathan Druart from comment #25) > > > > I don't think I am ready to QA this one. > > > > Julian has announced a new plugin system few weeks ago and this patch will > > > > adds a precedent for the existing plugin system. > > > > Do you have in mind other uses case? Did you plan to extend it to other > > > > behaviors? > > > > It would be great to ping koha-devel to get other dev opinions. > > > > > > Please follow the trace in the see also bug and see that it is already three > > > years under way. > > > > I do not understand, are you talking about bug 9743? How this bug report can > > answer my questions? > > It didn't ? :) > My point is: why block something that I am waiting for over three years > because something else was created a few months ago? The version of the patch on bug 9743 and the first version on this bug report did not introduced a new way to modify behaviors using plugings. If they get pushed, we will have a precedent and new patches/plugins will use it. That will add more stuffs to modify if we decide the switch our plugin system. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15397] Pay selected does not works as expected
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15397 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle(a)bywatersolutions.com Status|Passed QA |Pushed to Master --- Comment #12 from Kyle M Hall <kyle(a)bywatersolutions.com> --- Pushed to master for Koha 16.11! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 11360] Disable barcode field and submit button when a hold is found
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11360 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA --- Comment #60 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Kyle M Hall from comment #59) > (In reply to Jonathan Druart from comment #58) > > Created attachment 53686 [details] [review] [review] > > Bug 11360 [QA Followup] - Fix styles and button order > > > > Signed-off-by: Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> > > Jonathan did you intend to pass qa on this patch set, or did you just add an > additional sign-off? I wanted to let Katrin to have another look, but she told me it's ok if I PQA it. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15545] Optionally make hold notes required when placing a hold ( via Koha::Plugin)
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15545 --- Comment #28 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Jonathan Druart from comment #27) > (In reply to Marcel de Rooy from comment #26) > > (In reply to Jonathan Druart from comment #25) > > > I don't think I am ready to QA this one. > > > Julian has announced a new plugin system few weeks ago and this patch will > > > adds a precedent for the existing plugin system. > > > Do you have in mind other uses case? Did you plan to extend it to other > > > behaviors? > > > It would be great to ping koha-devel to get other dev opinions. > > > > Please follow the trace in the see also bug and see that it is already three > > years under way. > > I do not understand, are you talking about bug 9743? How this bug report can > answer my questions? It didn't ? :) My point is: why block something that I am waiting for over three years because something else was created a few months ago? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15006] Need to distinguish client timeout from login timeout
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15006 --- Comment #85 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Frédéric Demians from comment #84) > I'm about to push this patch on 16.05 branch (with 13807). But what about > 'client_timeout' SIPconfig.xml new parameter. Isn't it necessary to display > a warning to admin upgrading the stable branch, in order to advice him/her > to tweak its SIP configuration? It falls back to the service timeout if it is not present. If you do not have problems, there may be no direct need to add this parameter. But printing a line to notify a sysadmin about this option would be fine of course. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15545] Optionally make hold notes required when placing a hold ( via Koha::Plugin)
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15545 --- Comment #27 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Marcel de Rooy from comment #26) > (In reply to Jonathan Druart from comment #25) > > I don't think I am ready to QA this one. > > Julian has announced a new plugin system few weeks ago and this patch will > > adds a precedent for the existing plugin system. > > Do you have in mind other uses case? Did you plan to extend it to other > > behaviors? > > It would be great to ping koha-devel to get other dev opinions. > > Please follow the trace in the see also bug and see that it is already three > years under way. I do not understand, are you talking about bug 9743? How this bug report can answer my questions? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15006] Need to distinguish client timeout from login timeout
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15006 --- Comment #84 from Frédéric Demians <frederic(a)tamil.fr> --- I'm about to push this patch on 16.05 branch (with 13807). But what about 'client_timeout' SIPconfig.xml new parameter. Isn't it necessary to display a warning to admin upgrading the stable branch, in order to advice him/her to tweak its SIP configuration? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6934] New report Cash Register Statistics
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6934 --- Comment #102 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Francois Charbonnier from comment #96) > (In reply to Katrin Fischer from comment #59) > > > - What is the definition of an "Active transaction"? (was not clear to me, > > so asking :) ) > > The idea behind "Active transactions" is to help balance cash register > transactions. In other words, how much goes in or how much goes out the cash > register. The active transactions group what patrons paid or gave as credit > to the library, which means what went IN the register. > > The code works this way : it takes all transactions where account types are > NOT "F" (Fine), "FU" (Fine unpaid), "FOR" (Forgiven), "M" (Sundry), "L" > (Lost). Sorry, I still don't get it :( The list of excluded fine types looks a bit arbitrary to me - what about custom MANUAL_INV values? And what is left by excluding those? -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 7520] json script to return advanced search types
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7520 --- Comment #17 from M. Tompsett <mtompset(a)hotmail.com> --- Wasn't there some itype itemtype removal on something elsewhere recently? Is the permissions check correct still? Also, still stand by my question about the REST API. -- You are receiving this mail because: You are watching all bug changes.

1 0