- Koha - lists.katipo.co.nz

Fwd: Re: [Koha-devel] Koha 3.22.21 release
by Bob Birchall 23 May '17

23 May '17

Whilst I know very well that its just a change of numbering, nonetheless I had a little twinge to read of the demise of Koha 3.x. Irma had just a handful of clients on Koha 2.9, which was pretty neat eh, but I remember the first time she showed me Koha 3.0. I couldn't believe the difference, and how smart it looked. And all those extra features. And then over the years it just got better and better. So congratulations and thank you to all the librarians, the developers, the translators, the writers of documentation, the Release Managers and the Release Maintainers who made Koha 3.x the best ILS around in its time. And particular congratulations to Julian who kept 3.22 going through 21 maintenance releases. Awesome! So now we have 16.11 and in a few days we'll have 17.05. What an incredible project. Congratulations to every contributor and every user wherever you are. Ma tini ma mano ka rapa te whai. Bob Calyx -------- Forwarded Message -------- Subject: Re: [Koha-devel] Koha 3.22.21 release Date: Mon, 22 May 2017 19:52:10 +0200 From: Julian Maurice <julian.maurice(a)biblibre.com> To: Tomas Cohen Arazi <tomascohen(a)gmail.com>, koha-devel(a)lists.koha-community.org <koha-devel(a)lists.koha-community.org> Glad to read that :-) Thanks Le 22/05/2017 à 19:04, Tomas Cohen Arazi a écrit : > Julian, 3.22 was pretty good :-D > Well done! > > El lun., 22 may. 2017 a las 13:17, Julian Maurice > (<julian.maurice(a)biblibre.com <mailto:julian.maurice@biblibre.com>>) > escribió: > > The Koha community is proud to announce the release of Koha 3.22.21. > > This is a maintenance release and contains several bugfixes. > > The full release notes are available at > https://koha-community.org/koha-3-22-21-release/ > > Please note that Koha version 3.22 won't be maintained anymore and this > is the last 3.22 release. If you are still using it, you should consider > upgrading to a more recent version. > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > -- > Tomás Cohen Arazi > Theke Solutions (https://theke.io <http://theke.io/>) > ✆ +54 9351 3513384 > GPG: B2F3C15F -- Julian Maurice <julian.maurice(a)biblibre.com> BibLibre

1 0

Items Not Being Cleared From Patron Account After Check-In
by Lennon Mazonde 23 May '17

23 May '17

Hi Everyone, I'm running Koha 16.11.07, installed via packages, on Ubuntu 14.04. Recently, one of my clients started having circulation problems with their Koha system. Items that have been checked in are still appearing in the patron's account. This has been happening randomly to different patrons at different times using different items. There is no consistent traceable pattern, and there are no errors showing client-side. When i checked the Koha intranet logs, the following errors came up: [Mon May 22 07:04:15.958812 2017] [cgi:error] [pid 6424] [client 154.120.230.62:27062] AH01215: [Mon May 22 07:04:15 2017] returns.pl: DBD::mysql::db do failed: Duplicate entry '14846' for key 'PRIMARY' [for Statement "UPDATE issues SET issue_id = ? WHERE issue_id = ?"] at /usr/share/koha/lib/C4/Circulation.pm line 2179., referer: http://aby.com/cgi-bin/koha/circ/returns.pl [Mon May 22 07:08:57.501919 2017] [cgi:error] [pid 6879] [client 154.120.230.62:31881] AH01215: [Mon May 22 07:08:57 2017] returns.pl: DBD::mysql::db do failed: Duplicate entry '14847' for key 'PRIMARY' [for Statement "UPDATE issues SET issue_id = ? WHERE issue_id = ?"] at /usr/share/koha/lib/C4/Circulation.pm line 2179., referer: http://aby.com/cgi-bin/koha/circ/circulation.pl [Mon May 22 08:56:10.808209 2017] [cgi:error] [pid 20939] [client 154.120.230.62:43475] AH01215: [Mon May 22 08:56:10 2017] returns.pl: DBD::mysql::db do failed: Duplicate entry '14848' for key 'PRIMARY' [for Statement "UPDATE issues SET issue_id = ? WHERE issue_id = ?"] at /usr/share/koha/lib/C4/Circulation.pm line 2179., referer: http://aby.com/cgi-bin/koha/circ/returns.pl [Mon May 22 08:56:17.116111 2017] [cgi:error] [pid 20939] [client 154.120.230.62:43475] AH01215: [Mon May 22 08:56:17 2017] returns.pl: DBD::mysql::db do failed: Duplicate entry '14849' for key 'PRIMARY' [for Statement "UPDATE issues SET issue_id = ? WHERE issue_id = ?"] at /usr/share/koha/lib/C4/Circulation.pm line 2179., referer: http://aby.com/cgi-bin/koha/circ/returns.pl [Mon May 22 08:56:22.893948 2017] [cgi:error] [pid 20939] [client 154.120.230.62:43475] AH01215: [Mon May 22 08:56:22 2017] returns.pl: DBD::mysql::db do failed: Duplicate entry '14850' for key 'PRIMARY' [for Statement "UPDATE issues SET issue_id = ? WHERE issue_id = ?"] at /usr/share/koha/lib/C4/Circulation.pm line 2179., referer: http://aby.com/cgi-bin/koha/circ/returns.pl [Mon May 22 08:59:21.098733 2017] [cgi:error] [pid 21279] [client 154.120.230.62:44454] AH01215: [Mon May 22 08:59:21 2017] circulation.pl: DBD::mysql::db do failed: Duplicate entry '14851' for key 'PRIMARY' [for Statement "UPDATE issues SET issue_id = ? WHERE issue_id = ?"] at /usr/share/koha/lib/C4/Circulation.pm line 2179., referer: http://aby.com/cgi-bin/koha/circ/circulation.pl [Mon May 22 09:08:18.138124 2017] [cgi:error] [pid 22448] [client 154.120.230.62:48991] AH01215: [Mon May 22 09:08:18 2017] circulation.pl: DBIx::Class::Storage::DBI::select_single(): Query returned more than one row. SQL that returns multiple rows is DEPRECATED for ->find and ->single at /usr/share/koha/lib/Koha/Objects.pm line 83, referer: http://aby.com/cgi-bin/koha/circ/circulation.pl From the little that i understand, the duplicate entry is occurring because that table has reached the upper limit of the auto-increment field (see the first comment in this thread). Therefore, when a new record is inserted into the table, instead of generating a unique value, it is producing a duplicate key entry. What i think this then does on the client side is that when an item is checked in, instead of a new unique value being created for that particular transaction in the issue/old_issue fields, a duplicate value is generated and assigned to that check-in. The system then thinks that the item has already been checked in, since the supposedly unique value has been generated. The item will then continue showing in the patron's account, even though it's been checked in. Am i correct in my assessment of what is happening? I opened the module that was generating that error sudo nano -Bu +2179 /usr/share/koha/lib/C4/Circulation.pm The lines of code in the section around line 2179 deal with two tables in particular, issues and old_issues; # FIXME Improve the return value and handle it from callers $schema->txn_do(sub { $dbh->do( $query, undef, @bind ); my $id_already_exists = $dbh->selectrow_array( q|SELECT COUNT(*) FROM old_issues WHERE issue_id = ?|, undef, $issue_id ); if ( $id_already_exists ) { my $new_issue_id = $dbh->selectrow_array(q|SELECT MAX(issue_id)+1 FROM old_issues|); $dbh->do( q|UPDATE issues SET issue_id = ? WHERE issue_id = ?|, undef, $new_issue_id, $issue_id ); $issue_id = $new_issue_id; } $dbh->do(q|INSERT INTO old_issues SELECT * FROM issues WHERE issue_id = ?|, undef, $issue_id); I assumed the problems with the duplicate keys are emanating from these two tables. I tried increasing the index field of the column "issue_id" in both the old_issues and issues tables from INT to BIGINT (in the hopes of increasing the maximum limit of unique keys being generated) by doing the following in MySQL: mysql> use koha; mysql> describe old_issues; mysql> ALTER TABLE old_issues MODIFY issue_id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT; mysql> describe issues; mysql> ALTER TABLE issues MODIFY issue_id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT; However, the problem is still occurring. Can anyone help with an explanation of what is happening and why, and how i can fix it? For now, i'm just going to reinstall my client's database, but i don't think that's going to be a permanent fix since the problem is likely to recur. Regards, Lennon Mazonde

4 8

Koha 3.22.21 release
by Julian Maurice 22 May '17

22 May '17

The Koha community is proud to announce the release of Koha 3.22.21. This is a maintenance release and contains several bugfixes. The full release notes are available at https://koha-community.org/koha-3-22-21-release/ Please note that Koha version 3.22 won't be maintained anymore and this is the last 3.22 release. If you are still using it, you should consider upgrading to a more recent version.

2 1

Enquiry
by mohammed abdelgadir 22 May '17

22 May '17

hello guys have a nice day could you please guide me KOHA in my laptop log out in every step and ask me to sign in again what's the problem. thanks in advance

2 1

Koha 16.11.08 released
by Katrin 22 May '17

22 May '17

The Koha community is proud to announce the release of Koha 16.11.08. This is a maintenance release of 16.11 and includes 5 enhancements and 50 bugfixes. The full release notes are available at https://koha-community.org/koha-16-11-08-release/ Packages will be available soon.

2 1

Process to file bug
by vinod mishra 21 May '17

21 May '17

Dear all, While working on koha i found 3/4 bugs in already available options i.e. it was not working properly hence i immediately posted on bug to make aware the developers and users too. Unfortunately i have been told by one of the good developer that i am spaming ! So could you please let me know what to do if a user found many bugs? I feel every person is having limitation of time and technical capacity. Testing koha functionality and making it popular is another good contribution which can be done by library professionals easily.

2 1

Re: [Koha] [Koha-devel] What's on in koha-devel #11
by Jonathan Druart 18 May '17

18 May '17

Hello Wendy, (Answering to the list) I would say you should try both and see where you fit best :) The topics for the meetings are very different, you can find the topics in advanced on the wiki (and can add yours!) Regards, Jonathan On Wed, 5 Apr 2017 at 13:23 Wendy Sharkey <catalog(a)bfli.org> wrote: > Of the two meetings you mention, which one would best fit a librarian user > and abuser? > > Wendy Sharkey > Bennington, Vermont > > > ------------------------------ > *From:* Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> > *To:* "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz>; " > koha-devel(a)lists.koha-community.org" <koha-devel(a)lists.koha-community.org> > > *Sent:* Tuesday, April 4, 2017 9:55 AM > *Subject:* [Koha-devel] What's on in koha-devel #11 > > Hello librarians and developers, > > Not much has happened this month in terms of development. Things are going > very slowly at the moment, despite the hackfest in Marseille. > > We see a lot of new people on the mailing list and the IRC channel asking > for questions, but we need more people to be involved in the discussions > and the signoff process. There are hundreds of people on this list, you > need to know that the Koha community needs you to make the project moving > forward. I know that nobody has enough time, but you know one hour per > week of even per month can help a lot. It is very easy, fun and interesting > :) > > = How to get involved? = > > The first action would be to join us on the #koha IRC channel and the > koha-devel mailing list. Start by presenting yourself, where do you come > from, what do you do? For how long have you been using Koha? How do you > think you can help? > > Attend meetings! > We have two kinds of monthly meeting. There is a general one to talk about > koha-related stuffs, and the development meeting to talk about technical > stuffs. It is important for the community to have a place to be all > together and try to make things move. If you are a librarian, we need you > to tell developers the directions they need to go. > > Open bug reports > It is important to know that everybody can open new bug reports on our bug > tracker (https://bugs.koha-community.org) It is useful for the > development team to know the new bugs. And it is also important for you to > search for known bugs. A lot of bugs are known from developers but we do > not know how to fix them because we are waiting for feedbacks from users. > The dashboard (http://dashboard.koha-community.org) is very helpful to > know the "hot" bugs that need to be fixed/tested/QAed. The "Overall bug > traker health status" section displays the number of new bugs that are > important to follow, make moving. > If a developer submits a patch for the bug you opened, try and test it! > > Test bugs > Here is how you can really makes things move for the community. You become > involved in the development process and make the Koha project better. > Sandboxes (https://wiki.koha-community.org/wiki/Sandboxes) are available > to test patch easily. You do not need to install anything on your computer > and do not need any technical skills. If you are a Koha user, you can test > patches! > > Write patches > If you are a developer or have a minimum of technical skills you can write > your own patches and fixes bugs or develop new feature. > Our dedicated wiki page (wiki.koha-community.org/wiki/Submitting_A_Patch) > will guide you over the different steps. > It is very easy to get a development environment using KohaDevBox ( > https://github.com/digibib/kohadevbox) > Start with small patches :) > > = Refactoring = > If you have read my previous "what's on in koha-devel" emails, you may > have noticed I talked a lot of "refactoring" bugs. > And maybe you do not know what it is and what it brings. > The Koha codebase is aged/old, and has grown very quickly since 2006. > Since the last few years the development team decided to make the code more > robust and slow the integration of patches, getting a stronger integration > process. That's why we need to have at least one tester validating the > patches, then one QAer to review the patch technically and finally the > Release Manager to push it. That's mean 4 independent persons for a single > patch. That made our codebase stronger and less regression prone. > Some part of the code now needs to be rewritten, and it is why I have > focussed on the "refactoring" work over the last year. The goal is to > rewrite modules of Koha, step by step. It cleans the code, makes it more > readable, reduces the number of lines, centralise the responsibilities, > homogenise the code, fixes bugs, adds test coverage, etc. > On the mid-long term it means a modern application, easy to maintain, > robust, flexible. The bugs will be easier to fix, the enhancements will be > quicker to develop and so less expensive. > Do you start to understand how it is useful? > So yes, it's boring to test because it does not bring anything new to the > interface, but the project needs it. > > If you have been using Koha for months or years, it made you save money, > it makes you happy to use it and you love it. If you already got answer > from people on the mailing lists or the IRC channel, it's time to say thank > you, by getting involved! > > If you have any specific questions on how to get involved, you can join me > on the IRC channel or by email. I can help and guide you if necessary. > > A developer that loves Koha but needs help, > > Jonathan > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > >

6 23

Error uploading cover images
by Sebastian Krieg 18 May '17

18 May '17

Hello Koha, I'm getting an error in /var/log/koha/koha-error.log while uploading cover images. The upload failes. This is the error message: ... [Wed May 17 21:42:11.840699 2017] [cgi:error] [pid 2900] [client 192.168.0.110:54342] AH01215: [Wed May 17 21:42:11 2017] upload-file.pl: DBD::mysql::db do failed: MySQL server has gone away [for Statement "INSERT INTO sessions (id, a_session) VALUES(?, ?) ON DUPLICATE KEY UPDATE a_session = ?"] at /usr/share/perl5/vendor_perl/CGI/Session/Driver/mysql.pm line 50.: /var/www/koha/intranet/cgi-bin/tools/upload-file.pl, referer: http://192.168.0.200:8081/cgi-bin/koha/tools/upload-cover-image.pl ... My system: - Koha 16.11.06 - Fedora 25 Server - MariaDB 10.1.21.3 - Perl 5.24.1 - DBD::mysql::db 4.042 Has someone an idea what's happend and is there a solution? Thanks Sebastian - _______________ mailto: sebastian.krieg(a)tuz-eisenach.de

2 1

smtp: Failed: Server does not advertise any supported authentication methods
by Vimal Kumar V. 18 May '17

18 May '17

Dear Friends, I was trying to configure nullmailer with gmail using following document, http://blog.janjonas.net/2011-04-22/configure-nullmailer-smtp-authenticatio… Here is the format of login credentials in /etc/nullmailer/remotes smtp.gmail.com smtp --port=587 --user=xyz --pass=xyz Message did not sent, following is the error log of nullmailer, May 18 14:33:54 koha nullmailer[13567]: smtp: Failed: Server does not advertise any supported authentication methods May 18 14:33:54 koha nullmailer[13409]: Sending failed: Temporary error in sending the message Any clue regarding this error? My Koha version is 16.11.7 Regards, -- Vimal Kumar V. Librarian School of Indian Legal Thought Mahatma Gandhi University Kottayam, Kerala Web: http://www.vimalkumar.info Blogs: http://linuxhalwa.blogspot.com http://kohageek.blogspot.in http://dspacegeek.blogspot.in http://moovandan.blogspot.in <http://moovandan.blogspot.in> --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

1 0

UDC number not shown in the holding area on the OPAC
by Davian Cooper 18 May '17

18 May '17

I switched from DDC (082 tag) to UDC(080 tag) and reimported the records. When it was DDC I could edit the record item, click in the item call number and the call number would appear. Now when i edit the record it doesn't appear nor is it shown in the holdings area on the OPAC. Is there a way to get it in the table (call number section) so that the user can browse the shelf? Davian Cooper

2 1