July 2015 - Koha-devel - lists.koha-community.org

Report in ISBD format
by Partha Mukhopadhyay 28 Jul '15

28 Jul '15

3 3

Automatic backup testing
by Mirko Tietgen 28 Jul '15

28 Jul '15

Hi there, I was wondering if some of you do automatic tests of Koha backups and would like to share their strategies. Cheers, Mirko

1 0

Bug 13906: the start of Auth/Web test rewritting of Olli-Antti Kivilahti
by Tajoli Zeno 27 Jul '15

27 Jul '15

Hi to all, I'm starting to see what to do for sign-off the work done by Olli-Antti Kivilahti about rewritting of Authentication and Test web interface of Koha. I see that first bug to test is bug 13906 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13906 The bug is 'In discussion'. I'm not sure od situation. What do you think about the proposal of Olli-Antti ? Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.tajoli(a)cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)

2 3

SIP Authentication broken when LDAP Auth Enabled
by Bernard Shiundu 27 Jul '15

27 Jul '15

We have been running KOHA with ldap authentication enabled and are now trying to get the SIP server going. I notice that when ldap auth is enabled I cannot authenticate a regular Koha Account via SIP. With ldap enabled, testing via telnet using 9300CNkohasipuserid|COkohasipuserpwd|CPmybranch| returns 941 but in the sip ogs I see: LDAP bind failed as kohauser kohasipuser: LDAP error #49: LDAP_INVALID_CREDENTIALS # The wrong password was supplied or the SASL credentials could not be processed When I disable ldap auth in koha-xml.conf everything works as advertised. I have also tried adding my kohasipuser to ldap. This makes the error go away in the logs but Koha users still cannot login via SIP. Any suggestions on how to overcome this? Bernard Shiundu Nairobi, Kenya -- -- Note: All emails sent from Strathmore University are subject to Strathmore’s Email Terms & Conditions. Please click here <http://www.strathmore.edu/aboutus.php?id=184> to read the policy. "Visit our Facebook <https://www.facebook.com/StrathmoreUniversity>Page and Twitter <https://twitter.com/StrathU>Account".

2 2

Koha::RecordProcessor question
by Mark Tompsett 25 Jul '15

25 Jul '15

Greetings, I am beginning my work on bug 11592 the filter version. I was curious if this patch makes sense: diff --git a/Koha/RecordProcessor.pm b/Koha/RecordProcessor.pm index 9bb1fc2..a345156 100644 --- a/Koha/RecordProcessor.pm +++ b/Koha/RecordProcessor.pm @@ -103,7 +103,7 @@ sub new { my $filter_module = $filter =~ m/:/ ? $filter : "Koha::Filter::${schema}::${filter}"; if (can_load( modules => { $filter_module => undef } )) { my $object = $filter_module->new(); - $filter_module->initialize($param); + $object->initialize($param); push @filters, $object; } } Because otherwise, how can I properly set some parameters? GPML, Mark Tompsett

2 2

Bug 7174 - Authentication rewriting and getting to REST API
by Kivilahti Olli-Antti 22 Jul '15

22 Jul '15

Hi there! Few weeks ago in an IRC meeting Kyle told me that the REST API should also allow authentication from the CGISESSID. I told it is easy peezy. Had I known in what a mess the C4::Auth is... I didn't want to make things worse by duplicating somebodys already duplicated code, so I decided to take the hard way. I did my best in trying to bring all the real world problems we tackle in C4::Auth into modular and reusable authentication components we can use to authenticate different types of requests. I have to say it was really really difficult, but I think I have a pretty decent solution. (with PageObject integration tests to cover for regression) For my sanity, and yours, I ask you to take a peek at Bug 7174 and Bug 14540 to find some structure to the Koha's authentication mechanisms. There is a nice picture and a lot of text... and code, and tests. Take Care! Olli-Antti Kivilahti Järjestelmäkeittäjä vaarakirjastot.fi +358 50 449 7763 --Powered by Kubuntu Linux!

1 0

Call for Updates on Kohacon 2016 proposals
by Mirko Tietgen 20 Jul '15

20 Jul '15

Voting on the location for Kohacon 2016 is scheduled for September. We have two bids so far: - Aristotle University of Thessaloniki, Greece - National Library of the Philippines Both bids lack a link to a more detailed proposal so far. If you are involved in one of these bids, please let us know as much as possible about your plans soon. :) Anyone else interested in hosting Kohacon 2016, please add your proposal now so people have time to make up their minds. All available information can be found in/ should be added to the Koha wiki at http://wiki.koha-community.org/wiki/KohaCon16_Proposals Thanks a lot to everyone working on the bids. -- Mirko -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

1 0

patronimage.pl allows user image to be accessed without user session
by Indranil Das Gupta 20 Jul '15

20 Jul '15

Hi all, I ran across this and have filed http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14566 One question, is there any design decision I should be aware of before moving in on this? thanks -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org

2 1

Integration testing (WebDriver), Permission system rewrite and getting to Koha REST API!
by Kivilahti Olli-Antti 17 Jul '15

17 Jul '15

(Zeno hinted that I should post this message to the koha-devel mailinglist instead of koha mailinglist) Hi there! I have been working to get the new REST API working with Koha. Big issues are authenticating the REST API and doing browser-based automated testing. However there are some pretty fundamental issues in Koha that make working with those topics very difficult. PERMISSIONS: First of all the permissions system is very hard to manipulate outside of the user space. There is no internal Koha API for granting/revoking specific permissions. This is a huge issue with integration testing where we need to easily set up test context with proper permissions. Also there is no way currently to conveniently operate permissions using a REST API. So we would need to rewrite the permission back-end anyway. Bug 14540<http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14540> - Move member-flags.pl to PermissionsManager to better manage permissions for testing. deals with this issue and rewrites the internal permission mechanism, while preserving the end-user experience as it was. This enables us as testers to easily setUp and tearDown permissions for automated browser testing sessions. I recommend you take a look, as the rewrite is well tested and covered with WebDriver-tests. INTEGRATION TESTING: I have implemented a integration testing framework using the PageObject-pattern to create clear and robust browser tests. These browser tests don't need any additional servers to install, but rely on system packages (apt-get install phantomjs) to make the integration tests. These tests instantiate a real browser with javascript execution capability, and make real HTTP requests to the configured host and port, simulating real user interactions as accurately as possible. There are also two debugging interfaces for the automated test agent to make it more easy to script the user session. Take a look at: Bug 14495<http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14495> - WebDriver/WebTester Factory for easy generation of Web testing UserAgents. Bug 14536<http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14536> - PageObject-pattern base implementation DEALING WITH EXCEPTIONS: In Koha we currently don't have any established mechanism of propagating errors from business/database-layer to the end-user, and conveniently catching them and presenting them. Currently we return $error-variables from subroutines, which makes programming more challenging, and tedious, especially if we need to propagate the same errors through multipe subroutine calls to the end-user. I have implemented to Koha an Exception-system very similar from other programming languages. Quite frankly this is an industry standard nowadays and a best-practice for dealing with things-going-wrong. It helps a lot in programming defensively. Take a look at: Bug 13995<http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13995> - Proper Exception handling I am 100% convinced that these improvements will push Koha testing and development to the next level. The best overview of the new features can be seen from the test scripts in Bug 14540<http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14540> Looking forward to your sign offs! -- Olli-Antti Kivilahti Järjestelmäkeittäjä vaarakirjastot.fi +358 50 449 7763 --Powered by Kubuntu Linux!

1 0

It's that time again, string freeze for 3.20.2
by Chris Cormack 15 Jul '15

15 Jul '15

Hi All Time to get those translating hats on Chris

1 0