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

[Bug 14826] Resurrect account offsets table
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '17

23 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14826 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #65642|0 |1 is obsolete| | --- Comment #80 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- Created attachment 66387 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=66387&action=ed… Bug 14826 - Update database Signed-off-by: Josef Moravec <josef.moravec(a)gmail.com> Signed-off-by: Tomas Cohen Arazi <tomascohen(a)theke.io> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15032] [Plack] Scripts that fork (like stage-marc-import.pl) don' t work as expected
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '17

23 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032 John Sterbenz <jsterben(a)umich.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsterben(a)umich.edu -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15239] Add multiple items fail on barcode
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '17

23 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15239 Ruben Norori <kachomanic(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #11 from Ruben Norori <kachomanic(a)gmail.com> --- Hi Tomás. Thank for your suggestion, try the long way because I didn't know another solution, but I will try your recomendation. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11897] Stock Rotation for Koha
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '17

23 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11897 --- Comment #152 from Alex Sassmannshausen <alex.sassmannshausen(a)ptfs-europe.com> --- Hi Tomás, (In reply to Tomás Cohen Arazi from comment #150) > Hi guys, I've been looking at this patchset without trying it yet. > Everything looks as expected :-D > The only thing I would like to mention is that the auth chain added a check > for maintenance mode (usually on upgrades) that requires some more error > codes to be added to the spec. Can you please take a look at (say) > patrons.json from bug 18137? It's pretty straightforward. I believe I have added a patch now that implements what you requested. Feel free to let me know if you think I missed something! Alex -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11897] Stock Rotation for Koha
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '17

23 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11897 --- Comment #151 from Alex Sassmannshausen <alex.sassmannshausen(a)ptfs-europe.com> --- Created attachment 66381 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=66381&action=ed… Bug 11897: Follow up: Add more error conditions. * api/v1/swagger/paths/rotas.json: Add 401, 500 & 503 error conditions. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11897] Stock Rotation for Koha
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '17

23 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11897 Alex Sassmannshausen <alex.sassmannshausen(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15239] Add multiple items fail on barcode
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '17

23 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15239 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen(a)gmail.com --- Comment #10 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- Hi Ruben, (In reply to Ruben Norori from comment #9) > I have the definitive solution: > First we must add two new procedures, functions, methods, which consult in > the database the registry homebranch. I didn't go deep into the problem you're trying to solve, but I suggest you don't introduce new subs, but use the current api instead. We have a (sort of) DAO class called Koha::Items that exposes a ->search method, which returns Koha::Item objects. So you can simply do something like this: use Koha::Items; my $item = Koha::Items->find( $barcode ); ->find gets an id column to find the row and create the object. 'barcode' is a unique key, so this works. Now you have a Koha::Item object, representing the item with the passed barcode. You can then use it like: my $homebranch = $item->homebranch; Hope it clarifies! This conversations are easier on the koha-devel list or on the IRC channel. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6979] LDAP authentication fails during password comparison
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '17

23 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6979 Mason James <mtj(a)kohaaloha.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=18947 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15562] Make Koha more suitable for shared hosting with plack
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '17

23 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15562 --- Comment #66 from Srdjan Jankovic <srdjan(a)catalyst.net.nz> --- > but then we're also keeping all the data for all the > different sites accessible in memory by the same process which could allow > things to leak across if we're not careful (booo). That was exactly my point with Context. There should be no references to *anything* external (db, cache etc handles) outside Context. Now because we are still in this CGI frame of mind, we have all this horrible singletons. Once we are able to instantiate contexts and keep them in app containers, and pass them to request handlers we will be safe. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15562] Make Koha more suitable for shared hosting with plack
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '17

23 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15562 --- Comment #65 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Srdjan Jankovic from comment #64) > Well did not think of that... It should be limited by resources available, > not the application itself. It should... > I suppose I was just thinking in terms of any leaks, but hopefully it won't leak anywhere! > I'm quite sure this will never see the light of day (although I did get it > going), just too hard. However, I want to keep it alive for various reasons. > The main one is: the fact that this *is* too hard tells that we are doing > some things fundamentally wrong. Workarounds devised here (and most of it is > exactly that - workarounds) should help understanding the problems better. > Koha is being heavily optimised for the container per site scenario, but > "abstractly thinking" I don't see why we should not be able to share the > code. In a real world scenario you could imagine a cluster of small poor > schools benefiting from that. > Well, I was thinking about that from a security perspective. At the moment, we're already sharing the code, but since it's CGI it loads it up in separate processes on the fly. If we're using multiple sites with Plack managed by a single process, then we're loading the code into memory once (yay for efficiency!) but then we're also keeping all the data for all the different sites accessible in memory by the same process which could allow things to leak across if we're not careful (booo). It would be too bad if this didn't see the light of day since I imagine there would be lots of people wanting to host multiple Koha instances with the same Plack instance, but I do wonder a bit how feasible it would be, although surely people do it with other apps or URLMap wouldn't exist, yeah? Actually, I've been thinking about Tomcat a bit lately as well. I reckon it would work similarly to Plack. You define a number of URL routes and then specify the code that you want to run for each route. So you can have lots of Java apps running under the same single Tomcat instance. I don't know how it separates them so that they don't overlap of course. I suppose Tomcat might do it by virtue of Java apps being written to be run on Tomcat whereas we've been shoehorning Koha to work with Plack. > One day we will get rid of C4 and re-engineer Context, no CGI .pl... Maybe > even move to static pages and API... Then this will become obsolete. But > good to have it as a reference, until that happens. > > And thanks for your wishes :) Public transport is useful even when it's > horrible. I've been thinking for a while how nice it would be to separate the staff client and the OPAC. If I'm not mistaken, there are far fewer OPAC scripts than Staff Client scripts, so in theory writing a new OPAC would be easier than writing a new staff client. So we could build a new OPAC from the ground up that works with Plack natively. I figure library patrons should probably be the ones that demand the best performance, so why not start there, yeah? (Alternatively, if a separate OPAC is possible, it wouldn't even necessarily have to be written in Perl. Also, if we used APIs, we could use static pages with Javascript or people could access the APIs from their own websites and then we don't even have to worry about providing an OPAC - just maintaining the API.) Then maybe once the OPAC is separated out, we could work on overhauling the staff client bit by bit. That's my pie in the sky dream ;). Alas, I have too much other work to do, but it's a dream I have nonetheless... -- You are receiving this mail because: You are watching all bug changes.

1 0