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

selenium
by David Cook 25 Sep '17

25 Sep '17

Hi all, Does anyone use the "selenium" directory in Koha? I think that I recall Jonathan mentioning selenium scripts years ago, but maybe I'm just imagining that. It looks like Henri-Damien Laurent added the directory back in August 2009. If it's not being used, I figure we should probably remove it. While I'm intrigued by Selenium, I think we already use Test::WWW::Mechanize to achieve that functionality. No point holding on to something that isn't being used. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 1

KohaDevBox + Master
by Tomas Cohen Arazi 22 Sep '17

22 Sep '17

Hi everyone, the recent push of bug 18137 [1] replaced Swagger2 for Mojolicious::Plugin::OpenAPI as dependencies in master. Fortunately, all deps are already packaged in the community repo (thanks Mirko!). The only missing bit is koha-perldeps pulling libmojolicious-plugin-openapi-perl. Until that gets fixed in the unstable koha-* packages, we have added a manual install step to kohadevbox provisioning scripts. So, if you are having issues with your dev environment (the UI not responding, plack looping in errors, etc), please re-provision your kohadevbox (or install this new dep if you are using a custom dev environment). In kohadevbox this would be done like this: # Pull the latest changes in kohadevbox $ git pull # Provision $ vagrant provision If you created the dev box with Elasticsearch, do this: $ KOHA_ELASTICSEARCH=1 vagrant provision to take advantage of the addition of the analysis-icu plugin for Elasticsearch, that is needed to test bug 18318, and is harmless without the patches [2]. Please answer this email or contact us on IRC if you have any issues. Have a nice weekend! Shanah tovah umetukah! [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18137 [2] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18318 -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

koha-reset-passwd still uses MD5 instead of Bcrypt
by David Cook 15 Sep '17

15 Sep '17

Hi all, I was just pondering how one might move the scripts out of debian/scripts and into a non-Debian directory where they could be used on any kind of Koha install, when I noticed that debian/scripts/koha-reset-passwd is still using MD5 instead of Bcrypt. I've opened a report at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19321, but I don't use Koha Debian packages typically, so I have no plans to work on this. Figured I'd mention it here so that one of you Debian users could take it over instead. Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

Call for News: September 2017 Newsletter
by kohanews 15 Sep '17

15 Sep '17

I'm collecting news for the September newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Proposal for ES6 development on the staff client
by Jesse 13 Sep '17

13 Sep '17

As part of my work on bug 15522 <https://bugs.koha-community. org/bugzilla3/show_bug.cgi?id=15522>, I've been working with Preact (a React clone with a friendlier license). We've established that this needs ES6[1] in previous discussions on the mailing list and in IRC. From there, we found IE's many limitations meant we needed a transpiler[2] to to make use of these features. Owen and I have been thinking about the easiest way to do this, and this is the lowest-friction process we've come up with to transpile ES6: $ sudo apt-get install nodejs npm $ sudo npm install -g yarn $ yarn install $ yarn build Yarn is a somewhat faster version of npm, the de-facto JavaScript package manager. Normally, this would be a pointless addition, but the npm in the Debian repositories is 3 major versions out of date, and therefore not a great option. Many npm packages simply fail to install. This is a constant problem with the JS packages in the Debian repos; most if not all of the tools that one might want either are completely unpackaged or woefully out of date. Packaging them ourselves means working our way through a number of dependencies (see [3] for an example). Any frontend build process worth our time cannot solely use packages from the upstream repos. That aside, this build process will use Gulp, Browserify and Babel to take any files in koha-tmpl/intranet-tmpl/prog/js/src, and compile them into a matching file in koha-tmpl/intranet-tmpl/prog/js/built . This means that any new files will not have to be manually whitelisted. You can see a working example at https://github.com/pianohacker/koha, branch bz15522. I'm currently committing the built versions of the files, but this is purely for convenience of prototyping. The page in question is admin/policy.pl, and the relevant code is at .../prog/js/src/admin/policy.js . [1] ECMAScript 6, a semi-recent version of JavaScript with a large number of new features, including a nice class syntax, arrow functions, and destructuring assignment. [2] A tool that transforms ES6 syntax (and the JSX syntax extension used by (P)react) into something that can be run by older browsers, including IE. [3] https://wiki.debian.org/Javascript/Nodejs/Tasks/gulp -- Jesse Weaver

4 7

Fw: [Bug 19214] Patron clubs: Template process failed: undef error - Cannot use "->find" in list context
by Mark Tompsett 13 Sep '17

13 Sep '17

Greetings, While I would tend to agree, the change is consistent with the tendency to just throw “scalar” at it. I figure I’d forward this to devel list to potentially get other folks’ opinions and feedback on the matter. GPML, Mark Tompsett From: bugzilla-daemon(a)bugs.koha-community.org Sent: Tuesday, September 12, 2017 11:08 AM To: mtompset(a)hotmail.com Subject: [Bug 19214] Patron clubs: Template process failed: undef error - Cannot use "->find" in list context Comment # 8<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19214#c8> on bug 19214<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19214> from Fridolin SOMERS In my opinion it would have been better to set a var $ret and return $ret. Better for debugging for example. ________________________________ You are receiving this mail because: * You are on the CC list for the bug.

1 0

On-site checkouts
by Rodrigo Santellan 11 Sep '17

11 Sep '17

Hi, I have some items on the library that are only for using on the library. The difference with those items is that you can place a hold on them to use them during the day and also you can place a hold on them and checkout for using on the weekends and during the night (you check it out at last hour of the day and have to return it on first hour of next day). For what I can figure out is that I should create a new item type with different circulation rules, but I don't have a way to warn the librarian that the item is of restricted type. Is there a way to achieve it? Regards and thanks for all the help in advance!!

2 3

TestBuilder usage, recommendation
by Tomas Cohen Arazi 11 Sep '17

11 Sep '17

Hi everyone, on my QA-related tasks I've found many of us use TestBuilder to generate random data for our tests (YAY!). I just wanted to remind you that TestBuilder can now return Koha::Object-derived objects instead of just unblessed hashes now, through a new method: my $builder = t::lib::TestBuilder->new(); my $patron = $builder->build_object({ class => 'Koha::Patrons' }); It was introduced to avoid this pattern we see very often on the tests: my $builder = t::lib::TestBuilder->new(); my $patron_id = $builder->build({ source => 'Borrower' })->{'borrowernumber'}; my $patron = Koha::Patrons->find( $patron_id ); (or just to make use of object accessors without all the symbols handling hashrefs add, like in $patron->{'borrowernumber'} At some point we could make ->build_object() replace ->build() for simplicity. Regards -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Next meetings
by Jonathan Druart 06 Sep '17

06 Sep '17

Hi all, There is a collision about dev and general meetings tonight. Next general meeting will be tonight/today at 22UTC: https://wiki.koha-community.org/wiki/General_IRC_meeting_6_September_2017 And the next development meeting will be next week: https://wiki.koha-community.org/wiki/Development_IRC_meeting_13_September_2… Hope to see you there! Cheers, Jonathan

2 1

[Important] Update your MySQL|MariaDB configuration to avoid data loss
by Jonathan Druart 01 Sep '17

01 Sep '17

Hello everybody, This is an important email and you should not ignore it. If you are a librarian and have no technical skills you should forward this email to the administrator of your Koha installation. We have been dealing with circulation history loss in the last versions of Koha, and we ended up with a solution. You should read the following wiki page attentively and set up the proposed solution: https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix Cheers, Jonathan

3 5