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

Price format in order by email
by Holger Meissner 24 Oct '18

24 Oct '18

Dear koha devs, when we send an order by email <<aqorders.listprice>> is formatted with decimal point and six decimal places, in spite of syspref CurrencyFormat set to EUR. Is anyone working on this? Is there some kind of workaround? koha version 17.11.10.000. Thanks, Holger

2 1

Koha 17.11.11 release
by Fridolin SOMERS 24 Oct '18

24 Oct '18

The Koha community is proud to announce the release of Koha 17.11.11. This is a maintenance release. The full release notes are available at https://koha-community.org/koha-17-11-11-release/ Debian packages will be upgraded in a few days. I've proposed to continue maitaining 17.11.x in Koha 19.05 roles. Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

1 0

Generic OpenIDConnect client
by David Cook 24 Oct '18

24 Oct '18

Hi all, About 4 years ago, I wrote a generic OpenIDConnect client, and kept telling myself that I would upstream it but I never did. until now: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21586. I wrote it for 1 specific client, so it exists heavily in a set of "Prosentient" namespaces and some of the code is legacy from 3.14 and could be replaced by modern code (I'm looking at you Koha::Prosentient::Borrowers), but maybe people can try it out and give me some feedback to make it worthy of a sign off, or people can adapt it and I can give feedback. (I already have some things I would like to change. I think I overuse base64url. but it is essential when working with JWTs. I think I just got carried away with a substitution command once.) I know we already have the GoogleOpenIdConnect. I actually wrote this code before that code existed, but I don't think my code would work for Google the way it is now. It would probably need some alterations. Anyway, I was sick of telling myself that I would upstream it one day, so I sat down and made a patch and now it's shared. Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

3 4

Koha 18.05.05 release
by Renvoize, Martin 23 Oct '18

23 Oct '18

The Koha community is proud to announce the release of Koha 18.05.05. This is a maintenance release containing 67 bugfixes The full release notes are available at https://koha-community.org/koha-18-05-05-release/ Debian packages will be updated within a few days Many thanks to everyone involved, *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

1 0

Questions about terminology
by Barton Chittenden 23 Oct '18

23 Oct '18

I've been looking at the Koha terminology page ( https://wiki.koha-community.org/wiki/Terminology) There are still a handful of occurrences of incorrect terminology throughout the '.tt' files. I'm starting with looking for instances of 'biblio', which should be 'Bibliographic record'. I'm wondering about instances of "Biblio number" in the text... I think that "Bibliographic number" is actually *less* clear... "Bibliographic Record Number" is better, but in most cases where Biblio number is used (e.g. the Marc Editor), Biblio number makes sense in its context. Cheers, --Barton

6 8

Bugs for 18.11
by Jonathan Druart 23 Oct '18

23 Oct '18

Hi devs, I have started using the 'rel_18_11_candidate' bugzilla keyword to keep track of the bugs we need to fix before the release. Here is the list: https://frama.link/koha_bz_rel_18_11_candidate They are either regressions or bug fixes for new features of 18.11. They should be considered as high priority (blocker for the release) for the next weeks. Cheers, Jonathan PS: You really should bookmark this link ;)

1 0

SQL queries showing data that will cause software errors.
by Barton Chittenden 19 Oct '18

19 Oct '18

When ByWater started upgrading our partners to 17.11 last spring, I noticed that we were getting a lot of errors of the form "can't call method * on an undefined value at ..." We're starting to see these errors because more and more of our code uses Koha objects, and these will fail if a method is called on an undefined object. I brought this up here: http://lists.koha-community.org/pipermail/koha-devel/2018-June/044613.html I think that there was also another thread about this, which I can't find at the moment... Jonathan's opinion on this is that we should start creating queries which find data that will fail. This thread is for those queries, since I have an example: Circulating or holdable items without item type SELECT biblionumber, itemnumber, barcode, title, notforloan FROM items INNER JOIN biblio USING (biblionumber) WHERE notforloan < 1 AND itype IS NULL Once we have a few of these at hand, I'll start a page on the Koha wiki.

2 2

Master broken by 20521 (sql modes)
by Jonathan Druart 18 Oct '18

18 Oct '18

Hi devs, I quick email to let you know that master and tests are (completely) broken because of the recent push of bug 20521. It turned on the "problematic SQL modes" for dev installs (I let you search for that in your emails if it did not ring you the bell). I am working on fixing the different test failures (the ones we introduced since bug 20144, 6 months ago). They are all regressions and there are a lot! This shows us that we absolutely need this change, to alert us when we are doing something wrong, that's why I would not recommend a revert. If you are stuck in something urgent/important you can revert commit aafd0476342ca9691fd8a7c2c754c425ae1cf61f Bug 20521: Enable problematic SQL modes for dev installs Or easier, remove the dev_install flag in your koha-conf (but do not forget to switch it back in a few days!). Cheers, Jonathan

3 4

Call for News: October 2018 Newsletter
by kohanews 17 Oct '18

17 Oct '18

I'm collecting news for the October 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

Invitation to join the core team
by Renvoize, Martin 12 Oct '18

12 Oct '18

Hi everyone, I just wanted to remind you all that the role proposals page for the upcoming 19.05 development cycle is available at https://wiki.koha-community.org/wiki/Roles_for_19.05 and we'd love to see some new names on the volunteers' list. The vote on roles will be held at the next irc general meeting. Roles to draw your attention to: * Bug Wranglers - We can always do with more bug wranglers! These people love to keep things tidy and Bugzilla is always in need of your help. We need people to help manage 'the list', identifying the duplicates, promoting bugs to specialists and finding people to do signoffs and testing. Everyone is invited to this party, we need you! * Documentation Team - The documentation team is a growing team that's made great inroads into bringing Koha's documentation up to date and ensuring we have a really well-documented piece of software. There's plenty more to do and they're always on the lookout for new contributors. * Wiki Curators - Koha's wiki is bursting at the seams with good information, but we need your help to bring order to the chaos and keep improving the content. If you've got an interest in maintaining an area of the Wiki, helping identify out of date information or categorizing data then this is a job for you. * Quality Assurance Team - This vitally important team is always looking for new recruits! If you've got an eye for detail, or you're a tester who likes rolling up their sleeves a little bit and looking at how a piece of code works, then we'd love to hear from you. Again, there's always support available from 'the usual suspects' so don't shy away, why not make this your first cycle on the QA team and see how much fun it can be working with this important team. * Quality Assurance Topic Expert - Do you know one particular area of koha better than the rest? Are you the 'go to' guy (or gal) for SIP2, EDI, Acquisitions or another area of Koha? We'd like to hear from you too. You don't have to know the whole codebase to be a great QA Specialist, you're an expert in what you know and we always need more experts. * Release Maintainer 18.05 - I've enjoyed being RMaint this last five months, and have offered to take up the mantle again for the next 'stable' (18.11) release. So, we need someone to take up my mantle and maintain 'oldstable' (18.05). As ever, the community is a great place and lots of support will be available to show you the ropes. See https://wiki.koha-community.org/wiki/Release_maintenance for a description of the day to day activities of this role. Those are just a few highlights, please see the wiki page above for the full list. *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

1 0