Re: [Koha-devel] Suggestion: create a deprecated() function in Koha.

Hi Barton, I usually follow the same pattern for the commit messages when I remove a subroutine from C4. We could list them (something like `git log|grep "Move (.*) to Koha::*"`) for each release then provide a script to catch removed subroutine. However it will not help to know in advance (versio

Re: [Koha-devel] Suggestion: create a deprecated() function in Koha.

I've seen this sort of thing in a few projects and it works reasonably nicely.. though I'm not sure how it would work in Koha as we seem to replace all calls to a function and remove the function at the same time. If we did switch to this approach I'd suggest adding code to allow it to report to H

[Koha-devel] Koha 17.11.07 release

The Koha community is proud to announce the release of Koha 17.11.07. This is a maintenance release. The full release notes are available at https://koha-community.org/koha-17-11-07-release/ 17.11.x is my baby now ;) Regards, -- Fridolin SOMERS BibLibre, France - software and system mainta

Re: [Koha-devel] [Koha] Koha 18.05.01 released

The link to the release notes: https://koha-community.org/koha-18-05-01-release/ On Mon, 25 Jun 2018 at 10:10 Renvoize, Martin < martin.renvo...@ptfs-europe.com> wrote: > The Koha community is proud to announce the release of 18.05.01. > > This is a maintenance release and contains many bugfixes

[Koha-devel] Koha 18.05.01 released

The Koha community is proud to announce the release of 18.05.01. This is a maintenance release and contains many bugfixes and enhancements. As always you can download the release now and the packages will follow shortly: http://download.koha-community.org This is my first release as the 18.05

Re: [Koha-devel] Centralize and move to gitlab

Well spotted Mark, would be good to get those moved too :) *Martin Renvoize* Development Manager *T:* +44 (0) 1483 378728 *F:* +44 (0) 800 756 6384 *E:* martin.renvo...@ptfs-europe.com www.ptfs-europe.com Registered in the United Kingdom No. 06416372 V

Re: [Koha-devel] Staff/OPAC ISBD views and subfield visibility

Hi Andreas,   the restriction is in a general routine that is used in a lot of places to prevent Koha from leaking information you don't want to appear in the OPAC or exports. As such, I think it's implemented correctly. But please note, just because you mark it as visible, doesn't mean it will

Re: [Koha-devel] Add "cc" and "bcc" fields to message_queue

Hi Katrin, Thanks for your message. I know about those ones already, but they don’t really help for the multi-branch instances, although it looks like NoticeBcc could actually contain a string of multiple emails, so in theory a person could put a few branch emails in there and then branches

Re: [Koha-devel] Staff/OPAC ISBD views and subfield visibility

Hi Katrin, As far as our library is concerned we would not want the users to see in marc view an internal numerical code, which could be puzzling and confusing, especially if they are looking at personal name entries, who are usually followed by a role code in unimarc, e.g. 070 for author. Furthe