From dcook at prosentient.com.au Mon Feb 1 05:08:28 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 1 Feb 2021 15:08:28 +1100 Subject: [Koha-devel] Cross-browser automated testing in Javascript (Puppeteer/Playwright) Message-ID: <005b01d6f84f$e5505400$aff0fc00$@prosentient.com.au> Hi all, What do people think about doing our cross-browser automated testing in Javascript rather than Perl? We're already using Node.js for generating Koha's CSS: https://wiki.koha-community.org/wiki/Working_with_SCSS_in_the_OPAC_and_staff _interface. I've been playing with Puppeteer and Playwright lately for non-test related browser automation, and they're pretty easy to work with. Playwright is based on Puppeteer, and their basic APIs are the same, so fairly interchangeable. (We'd need to use another library like Jest or Playwright-test to do the test evaluation.) It looks like we only have 6 files that use Selenium, so it wouldn't be a big drama to replace them. There is a Perl library https://metacpan.org/pod/Playwright but it's just a wrapper around Playwright anyway and it's so new that I'd be a bit wary of using it. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Mon Feb 1 11:33:36 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Mon, 1 Feb 2021 11:33:36 +0100 Subject: [Koha-devel] Zebra ICU / phrases-icu.xml / Bug 27299 In-Reply-To: <084001d6e7e1$8f54b740$adfe25c0$@prosentient.com.au> References: <084001d6e7e1$8f54b740$adfe25c0$@prosentient.com.au> Message-ID: <1fea76f7-bfd9-61c8-fa00-0d188ce6aa7c@biblibre.com> Hi, thanks a lot for your amazing work in the depth of obscure code ;) Le 11/01/2021 à 07:18, dcook at prosentient.com.au a écrit : > Hi all, > > Indexdata have confirmed that the default phrases-icu.xml shipped with > Zebra (and Koha) is misconfigured. They’re updating the default one in > Zebra and I have a patch to update Koha at Bug 27299: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27299 > > > It’s an easy enough change to make, and I’ll be updating it for all my > ICU libraries. > > I encourage all you Zebra ICU users out there to update your > phrases-icu.xml as I’ve suggested on Bugzilla. I think that you’ll find > it makes a world of difference. > > Cheers, > > David Cook > > Software Engineer > > Prosentient Systems > > Suite 7.03 > > 6a Glen St > > Milsons Point NSW 2061 > > Australia > > Office: 02 9212 0899 > > Online: 02 8005 0595 > -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From dcook at prosentient.com.au Mon Feb 1 23:44:51 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 2 Feb 2021 09:44:51 +1100 Subject: [Koha-devel] Zebra ICU / phrases-icu.xml / Bug 27299 In-Reply-To: <1fea76f7-bfd9-61c8-fa00-0d188ce6aa7c@biblibre.com> References: <084001d6e7e1$8f54b740$adfe25c0$@prosentient.com.au> <1fea76f7-bfd9-61c8-fa00-0d188ce6aa7c@biblibre.com> Message-ID: <011701d6f8eb$da6910d0$8f3b3270$@prosentient.com.au> Thanks, Fridolin! That's kind of you to say ^_^. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Fridolin SOMERS Sent: Monday, 1 February 2021 9:34 PM To: dcook at prosentient.com.au; 'koha-devel' Subject: Re: Zebra ICU / phrases-icu.xml / Bug 27299 Hi, thanks a lot for your amazing work in the depth of obscure code ;) Le 11/01/2021 à 07:18, dcook at prosentient.com.au a écrit : > Hi all, > > Indexdata have confirmed that the default phrases-icu.xml shipped with > Zebra (and Koha) is misconfigured. They’re updating the default one in > Zebra and I have a patch to update Koha at Bug 27299: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27299 > > > It’s an easy enough change to make, and I’ll be updating it for all my > ICU libraries. > > I encourage all you Zebra ICU users out there to update your > phrases-icu.xml as I’ve suggested on Bugzilla. I think that you’ll > find it makes a world of difference. > > Cheers, > > David Cook > > Software Engineer > > Prosentient Systems > > Suite 7.03 > > 6a Glen St > > Milsons Point NSW 2061 > > Australia > > Office: 02 9212 0899 > > Online: 02 8005 0595 > -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From fridolin.somers at biblibre.com Wed Feb 3 11:14:59 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 3 Feb 2021 11:14:59 +0100 Subject: [Koha-devel] Display Koha version in staff interface Message-ID: Hi, There is a discussion in : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27497 I propose that the community makes a vote : Would you like to see more prominently Koha version in staff interface ? Where ? - In lower right corner - In Header - Bellow "About Koha" big link - Other ... I'm OK if we change nothing in the end. I made a plugin that can be adapted : https://github.com/biblibre/koha-plugin-intranet-version-in-header Best regards -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From victor at tuxayo.net Thu Feb 4 21:28:47 2021 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Thu, 4 Feb 2021 21:28:47 +0100 Subject: [Koha-devel] Cross-browser automated testing in Javascript (Puppeteer/Playwright) In-Reply-To: <005b01d6f84f$e5505400$aff0fc00$@prosentient.com.au> References: <005b01d6f84f$e5505400$aff0fc00$@prosentient.com.au> Message-ID: Hi :) On 21-02-01 05:08, dcook at prosentient.com.au wrote: > What do people think about doing our cross-browser automated testing in > Javascript rather than Perl? We’re already using Node.js for generating > Koha’s CSS: > https://wiki.koha-community.org/wiki/Working_with_SCSS_in_the_OPAC_and_staff_interface > . > > > I’ve been playing with Puppeteer and Playwright lately for non-test > related browser automation, and they’re pretty easy to work with. > Playwright is based on Puppeteer, and their basic APIs are the same, so > fairly interchangeable. (We’d need to use another library like Jest or > Playwright-test to do the test evaluation.) > > It looks like we only have 6 files that use Selenium, so it wouldn’t be > a big drama to replace them. Thanks for you exploration work :D I don't think I can help much in setting up the test stack **but** I can rewrite all the tests in whatever the community see fit. Though I don't really know what would be the gains in practice of switching to Playwright compared to staying with Selenium via Perl. Or switching to Selenium via JavaScript if our Perl lib gives troubles. No opinion for now. About our Selenium Perl lib, it's still being maintained with good work in progress to support the upcoming Selenium 4 https://github.com/teodesian/Selenium-Remote-Driver/issues/452#issuecomment-760415316 Is Puppeteer needed in a stack using Playwright? Because it's centered on Chromium, it's already a good surprise that Google worked to bring experimental Firefox support. But it's hard to bet that it will get stable and still be maintained for years. https://github.com/puppeteer/puppeteer/#q-what-is-the-status-of-cross-browser-support > There is a Perl library https://metacpan.org/pod/Playwright > but it’s just a wrapper around > Playwright anyway and it’s so new that I’d be a bit wary of using it. If the tests are to be rewritten to use Playwright, +1 to do that in JS rather than Perl to avoid depending on an unofficial lib. -- Victor Grousset/tuxayo From dcook at prosentient.com.au Thu Feb 4 23:21:48 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 5 Feb 2021 09:21:48 +1100 Subject: [Koha-devel] Cross-browser automated testing in Javascript (Puppeteer/Playwright) In-Reply-To: References: <005b01d6f84f$e5505400$aff0fc00$@prosentient.com.au> Message-ID: <038901d6fb44$210e1fd0$632a5f70$@prosentient.com.au> Based on https://github.com/teodesian/Selenium-Remote-Driver/issues/452#issuecomment- 760415316, there's only 1 person maintaining that library, and he's even saying there's a lot of work to do on it. It would either be Puppeteer *or* Playwright. I'd be more inclined to go with Playwright as it supports Chromium, Firefox, and WebKit. That said, I've only used it with Chromium. Selenium seems a lot more heavy-weight and has a diminishing reputation. With Selenium, you need a Java-based server (we're using a Docker container for that), whereas with Puppeteer/Playwright, all you need is Node.js installed and then you just need to install the puppeteer/playwright Node module and it installs everything you need into a disposable node_modules directory. (Actually, Playwright has a few options for where to install the browser binaries, but not relevant here.) I have a fair bit on my plate at the moment, but I know code speaks louder than words too, so maybe at some point I could put something together... David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Victor Grousset/tuxayo Sent: Friday, 5 February 2021 7:29 AM To: dcook at prosentient.com.au; 'koha-devel' Cc: 'Tomas Cohen Arazi' Subject: Re: Cross-browser automated testing in Javascript (Puppeteer/Playwright) Hi :) On 21-02-01 05:08, dcook at prosentient.com.au wrote: > What do people think about doing our cross-browser automated testing > in Javascript rather than Perl? We're already using Node.js for > generating Koha's CSS: > https://wiki.koha-community.org/wiki/Working_with_SCSS_in_the_OPAC_and > _staff_interface > . > > > I've been playing with Puppeteer and Playwright lately for non-test > related browser automation, and they're pretty easy to work with. > Playwright is based on Puppeteer, and their basic APIs are the same, > so fairly interchangeable. (We'd need to use another library like Jest > or Playwright-test to do the test evaluation.) > > It looks like we only have 6 files that use Selenium, so it wouldn't > be a big drama to replace them. Thanks for you exploration work :D I don't think I can help much in setting up the test stack **but** I can rewrite all the tests in whatever the community see fit. Though I don't really know what would be the gains in practice of switching to Playwright compared to staying with Selenium via Perl. Or switching to Selenium via JavaScript if our Perl lib gives troubles. No opinion for now. About our Selenium Perl lib, it's still being maintained with good work in progress to support the upcoming Selenium 4 https://github.com/teodesian/Selenium-Remote-Driver/issues/452#issuecomment- 760415316 Is Puppeteer needed in a stack using Playwright? Because it's centered on Chromium, it's already a good surprise that Google worked to bring experimental Firefox support. But it's hard to bet that it will get stable and still be maintained for years. https://github.com/puppeteer/puppeteer/#q-what-is-the-status-of-cross-browse r-support > There is a Perl library https://metacpan.org/pod/Playwright > but it's just a wrapper around > Playwright anyway and it's so new that I'd be a bit wary of using it. If the tests are to be rewritten to use Playwright, +1 to do that in JS rather than Perl to avoid depending on an unofficial lib. -- Victor Grousset/tuxayo From lari.taskula at hypernova.fi Fri Feb 5 19:37:10 2021 From: lari.taskula at hypernova.fi (Lari Taskula) Date: Fri, 5 Feb 2021 20:37:10 +0200 Subject: [Koha-devel] TestBuilder float and decimal format differs from the values returned by database Message-ID: Hi devs, While working on patron data export ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20028 ), I was trying to generate a bunch of test data with TestBuilder, and then compare them to what was returned by DBIx's search(). Unfortunately I couldn't do this, because most decimals from DBI/DBIx are returned in a different formatting to what TestBuilder has. Running an is_deeply() to compare the objects fails with: # Structures begin differing at: # $got->[0]{amount} = '90203.710000' (value returned by DBIx) # $expected->[0]{amount} = '90203.71' (value in HASHref generated by TestBuilder) This is because TestBuilder's _gen_real() forces the formatting to 2 decimal places. But there's more - My original idea to solve this issue was by using "column_info" provided by DBIx, and formatting the value to maximum decimal places allowed. But even if you follow the column's size definition, you will notice that there is a different behavior between data types "float"/"double" and "decimal". If it's a decimal, it stays in "stringified" format with all those trailing zeroes, but if it's a float, all the insignificant zeroes are dropped from the end. At some layer lower than DBIx (perhaps DBD::mysql?) there appears to be some formatting magic. A concrete example of this is when you have a FLOAT(10,4) and DECIMAL(10,4) columns and store "10.1000" in both columns, in the end the float becomes 10.1 and the decimal "10.1000". It's the same result with both DBI and DBIx. However, for example mariadb-client chooses to format both values as "10.1000". My other solution was to reload the row generated by DBIx in TestBuilder::_storeColumnValues() with discard_changes/get_from_storage method, but that 1. doesn't work for tables that do not have primary key (e.g. statistics), see DBIx::Class::ResultSource::_pri_cols_or_die(): Operation requires a primary key to be declared on 'Statistic' via set_primary_key at /home/koha/Koha/t/lib/TestBuilder.pm line 362 2. adds some overhead, although only into tests I would appreciate some ideas or improvements. I've created a Bug for this issue, see https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27630 . There is a test to demonstrate the issue, and the previously mentioned attempts to solve this issue. P.S. Somewhat related bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20621 -- Lari Taskula CEO, Hypernova Oy PL 16 80101 Joensuu, Finland -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Mon Feb 8 12:32:19 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 8 Feb 2021 12:32:19 +0100 Subject: [Koha-devel] TestBuilder float and decimal format differs from the values returned by database In-Reply-To: References: Message-ID: Hi Lari, Your patch makes sense to me. However we might increase the test suite execution time significantly [ref needed]. I would suggest to refresh (discard_changes) the object from your .t file ($built would be built using build_object, then call ->discard_changes->unblessed). The "Statistic" FIXME would be moved there as well (or depend on a bug that will add the PK!). It's definitely less clean as I am suggesting to move code out of (test covered) .pm, but it feels better in this specific situation. Cheers, Jonathan Le ven. 5 févr. 2021 à 19:37, Lari Taskula a écrit : > > Hi devs, > > While working on patron data export ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20028 ), I was trying to generate a bunch of test data with TestBuilder, and then compare them to what was returned by DBIx's search(). > > Unfortunately I couldn't do this, because most decimals from DBI/DBIx are returned in a different formatting to what TestBuilder has. Running an is_deeply() to compare the objects fails with: > > # Structures begin differing at: > # $got->[0]{amount} = '90203.710000' (value returned by DBIx) > # $expected->[0]{amount} = '90203.71' (value in HASHref generated by TestBuilder) > > This is because TestBuilder's _gen_real() forces the formatting to 2 decimal places. > > But there's more - My original idea to solve this issue was by using "column_info" provided by DBIx, and formatting the value to maximum decimal places allowed. But even if you follow the column's size definition, you will notice that there is a different behavior between data types "float"/"double" and "decimal". If it's a decimal, it stays in "stringified" format with all those trailing zeroes, but if it's a float, all the insignificant zeroes are dropped from the end. > > At some layer lower than DBIx (perhaps DBD::mysql?) there appears to be some formatting magic. A concrete example of this is when you have a FLOAT(10,4) and DECIMAL(10,4) columns and store "10.1000" in both columns, in the end the float becomes 10.1 and the decimal "10.1000". It's the same result with both DBI and DBIx. However, for example mariadb-client chooses to format both values as "10.1000". > > My other solution was to reload the row generated by DBIx in TestBuilder::_storeColumnValues() with discard_changes/get_from_storage method, but that > 1. doesn't work for tables that do not have primary key (e.g. statistics), see > DBIx::Class::ResultSource::_pri_cols_or_die(): Operation requires a primary key to be declared on 'Statistic' via set_primary_key at /home/koha/Koha/t/lib/TestBuilder.pm line 362 > 2. adds some overhead, although only into tests > > I would appreciate some ideas or improvements. I've created a Bug for this issue, see https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27630 . There is a test to demonstrate the issue, and the previously mentioned attempts to solve this issue. > > P.S. Somewhat related bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20621 > > -- > Lari Taskula > CEO, Hypernova Oy > PL 16 > 80101 Joensuu, Finland > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ From lari.taskula at hypernova.fi Mon Feb 8 18:57:38 2021 From: lari.taskula at hypernova.fi (Lari Taskula) Date: Mon, 8 Feb 2021 19:57:38 +0200 Subject: [Koha-devel] TestBuilder float and decimal format differs from the values returned by database In-Reply-To: References: Message-ID: <7ff0d634-9687-cf50-3b91-f2d6fe501bab@hypernova.fi> Thanks for the idea. It seems build_object refreshes the build()ed object by searching the row via Koha-objects. This alone is enough to solve my original problem in the patron data export Bug, because all the tables that are related to patrons by a foreign key, and have float or decimal columns, do seem to have a Koha-object, making the use of build_object possible. In fact I found only two DBIx schema files that have decimal fields with higher number of allowed decimal places than two, and no corresponding Koha::Object. These are AqbudgetsPlanning and PendingOfflineOperation. So there are very few cases where build_object would not be sufficient to solve the decimal formatting issues. Lari Taskula CEO, Hypernova Oy PL 16 80101 Joensuu, Finland On 8.2.2021 13.32, Jonathan Druart wrote: > Hi Lari, > > Your patch makes sense to me. However we might increase the test suite > execution time significantly [ref needed]. > I would suggest to refresh (discard_changes) the object from your .t > file ($built would be built using build_object, then call > ->discard_changes->unblessed). > The "Statistic" FIXME would be moved there as well (or depend on a bug > that will add the PK!). > > It's definitely less clean as I am suggesting to move code out of > (test covered) .pm, but it feels better in this specific situation. > > Cheers, > Jonathan > > Le ven. 5 févr. 2021 à 19:37, Lari Taskula a écrit : >> Hi devs, >> >> While working on patron data export ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20028 ), I was trying to generate a bunch of test data with TestBuilder, and then compare them to what was returned by DBIx's search(). >> >> Unfortunately I couldn't do this, because most decimals from DBI/DBIx are returned in a different formatting to what TestBuilder has. Running an is_deeply() to compare the objects fails with: >> >> # Structures begin differing at: >> # $got->[0]{amount} = '90203.710000' (value returned by DBIx) >> # $expected->[0]{amount} = '90203.71' (value in HASHref generated by TestBuilder) >> >> This is because TestBuilder's _gen_real() forces the formatting to 2 decimal places. >> >> But there's more - My original idea to solve this issue was by using "column_info" provided by DBIx, and formatting the value to maximum decimal places allowed. But even if you follow the column's size definition, you will notice that there is a different behavior between data types "float"/"double" and "decimal". If it's a decimal, it stays in "stringified" format with all those trailing zeroes, but if it's a float, all the insignificant zeroes are dropped from the end. >> >> At some layer lower than DBIx (perhaps DBD::mysql?) there appears to be some formatting magic. A concrete example of this is when you have a FLOAT(10,4) and DECIMAL(10,4) columns and store "10.1000" in both columns, in the end the float becomes 10.1 and the decimal "10.1000". It's the same result with both DBI and DBIx. However, for example mariadb-client chooses to format both values as "10.1000". >> >> My other solution was to reload the row generated by DBIx in TestBuilder::_storeColumnValues() with discard_changes/get_from_storage method, but that >> 1. doesn't work for tables that do not have primary key (e.g. statistics), see >> DBIx::Class::ResultSource::_pri_cols_or_die(): Operation requires a primary key to be declared on 'Statistic' via set_primary_key at /home/koha/Koha/t/lib/TestBuilder.pm line 362 >> 2. adds some overhead, although only into tests >> >> I would appreciate some ideas or improvements. I've created a Bug for this issue, see https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27630 . There is a test to demonstrate the issue, and the previously mentioned attempts to solve this issue. >> >> P.S. Somewhat related bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20621 >> >> -- >> Lari Taskula >> CEO, Hypernova Oy >> PL 16 >> 80101 Joensuu, Finland >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : https://www.koha-community.org/ >> git : https://git.koha-community.org/ >> bugs : https://bugs.koha-community.org/ From martin.renvoize at ptfs-europe.com Wed Feb 10 22:54:50 2021 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Wed, 10 Feb 2021 21:54:50 +0000 Subject: [Koha-devel] How to make self-referential URLs in Koha In-Reply-To: <048901d62e47$9d8f53a0$d8adfae0$@prosentient.com.au> References: <02f601d62d83$c9eb8730$5dc29590$@prosentient.com.au> <048901d62e47$9d8f53a0$d8adfae0$@prosentient.com.au> Message-ID: Did this ever become a bug? Looks like an interesting improvement and would be nice to see a start made? On Wed, 20 May 2020, 2:40 am , wrote: > So happy to see responses to this ^_^ > > > > Owen: It looks like we’d need to do a search and replace in the templates > and the code. So I think it could involve a lot of kicking of tires. That > said, we could do it incrementally. We could work through it all module by > module, and then remove the “/cgi-bin/koha” once we’re sure it’s not > referenced anywhere. > > > > Kyle: I’m glad you like the idea. I’d like to use the same paths in Apache > and Plack (for the sake of the self-referential URLs), so I was thinking > “/opac/opac-detail.pl” and “/intranet/circ” (or “/intranet/circulation”). > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Online: 02 8005 0595 > > > > *From:* Koha-devel *On > Behalf Of *Kyle Hall > *Sent:* Tuesday, 19 May 2020 11:20 PM > *To:* Owen Leonard > *Cc:* koha-devel > *Subject:* Re: [Koha-devel] How to make self-referential URLs in Koha > > > > I think that would also me a great cosmetic enhancement. > > > > At the risk of scope creep, we could go a step further by mapping the perl > scripts to paths as well, so /cgi-bin/koha/circ/circulation-home.pl could > become /circulation/home ( or even just /circulation ) for example. > > > > Kyle > > > > --- > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > On Tue, May 19, 2020 at 9:08 AM Owen Leonard wrote: > > > In the past, I have wondered if we could get rid of “/cgi-bin/koha” as a > path prefix all together > > No idea what that would involve (other than search-and-replace in the > templates), but from the user's point of view I think it would be a > nice improvement. > > -- Owen > > -- > Web Developer > Athens County Public Libraries > (740) 737-6006 > https://www.myacpl.org > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://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/ > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Wed Feb 10 23:14:22 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 11 Feb 2021 09:14:22 +1100 Subject: [Koha-devel] How to make self-referential URLs in Koha In-Reply-To: References: <02f601d62d83$c9eb8730$5dc29590$@prosentient.com.au> <048901d62e47$9d8f53a0$d8adfae0$@prosentient.com.au> Message-ID: <012001d6fffa$1611f1f0$4235d5d0$@prosentient.com.au> Nah, I don’t think that I ever created a Bugzilla issue for it. There’s pretty much 0 chance that I would work on it anyway. I just don’t have the time to devote to it. Sometimes I wonder how long it will take me to finish #26791 (which uses an /intranet/staff mount point in plack.psgi) since it’s a 100% personal project and I almost never code at home at the moment. Maybe I will when winter comes to the southern hemisphere heh. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Renvoize, Martin Sent: Thursday, 11 February 2021 8:55 AM To: David Cook Cc: koha-devel Subject: Re: [Koha-devel] How to make self-referential URLs in Koha Did this ever become a bug? Looks like an interesting improvement and would be nice to see a start made? On Wed, 20 May 2020, 2:40 am , > wrote: So happy to see responses to this ^_^ Owen: It looks like we’d need to do a search and replace in the templates and the code. So I think it could involve a lot of kicking of tires. That said, we could do it incrementally. We could work through it all module by module, and then remove the “/cgi-bin/koha” once we’re sure it’s not referenced anywhere. Kyle: I’m glad you like the idea. I’d like to use the same paths in Apache and Plack (for the sake of the self-referential URLs), so I was thinking “/opac/opac-detail.pl ” and “/intranet/circ” (or “/intranet/circulation”). David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel > On Behalf Of Kyle Hall Sent: Tuesday, 19 May 2020 11:20 PM To: Owen Leonard > Cc: koha-devel > Subject: Re: [Koha-devel] How to make self-referential URLs in Koha I think that would also me a great cosmetic enhancement. At the risk of scope creep, we could go a step further by mapping the perl scripts to paths as well, so /cgi-bin/koha/circ/circulation-home.pl could become /circulation/home ( or even just /circulation ) for example. Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, May 19, 2020 at 9:08 AM Owen Leonard > wrote: > In the past, I have wondered if we could get rid of “/cgi-bin/koha” as a path prefix all together No idea what that would involve (other than search-and-replace in the templates), but from the user's point of view I think it would be a nice improvement. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://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/ _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Thu Feb 11 11:43:40 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Thu, 11 Feb 2021 11:43:40 +0100 Subject: [Koha-devel] [Koha] Display Koha version in staff interface In-Reply-To: References: Message-ID: <687a69e4-5829-9072-ddc1-ce6bcc0efd00@biblibre.com> Hi, The discussion leads to having version in lower right corner. See : https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=116704 Please sign patch ;) Le 03/02/2021 à 11:14, Fridolin SOMERS a écrit : > Hi, > > There is a discussion in : > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27497 > > I propose that the community makes a vote : > > Would you like to see more prominently Koha version in staff interface ? > Where ? >  - In lower right corner >  - In Header >  - Bellow "About Koha" big link >  - Other ... > > I'm OK if we change nothing in the end. > I made a plugin that can be adapted : > https://github.com/biblibre/koha-plugin-intranet-version-in-header > > Best regards > -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From fridolin.somers at biblibre.com Thu Feb 11 16:51:57 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Thu, 11 Feb 2021 16:51:57 +0100 Subject: [Koha-devel] How to make self-referential URLs in Koha In-Reply-To: References: <02f601d62d83$c9eb8730$5dc29590$@prosentient.com.au> <048901d62e47$9d8f53a0$d8adfae0$@prosentient.com.au> Message-ID: <66173030-22c7-8f7d-95c8-ca8b34c53edf@biblibre.com> In this case in webserver config we base dynamic pages on the ".pl" extension. This is the case for example on the php projects I know. But then we must rename files in "svc" dirs with .pl. I'd be happy to test ;) Le 10/02/2021 à 22:54, Renvoize, Martin a écrit : > Did this ever become a bug?  Looks like an interesting improvement and > would be nice to see a start made? > > On Wed, 20 May 2020, 2:40 am , > wrote: > > So happy to see responses to this ^_^____ > > __ __ > > Owen: It looks like we’d need to do a search and replace in the > templates and the code. So I think it could involve a lot of kicking > of tires. That said, we could do it incrementally. We could work > through it all module by module, and then remove the “/cgi-bin/koha” > once we’re sure it’s not referenced anywhere.____ > > __ __ > > Kyle: I’m glad you like the idea. I’d like to use the same paths in > Apache and Plack (for the sake of the self-referential URLs), so I > was thinking “/opac/opac-detail.pl ” and > “/intranet/circ” (or “/intranet/circulation”). ____ > > __ __ > > David Cook____ > > Systems Librarian____ > > Prosentient Systems____ > > 72/330 Wattle St____ > > Ultimo, NSW 2007____ > > Australia____ > > __ __ > > Office: 02 9212 0899____ > > Online: 02 8005 0595____ > > __ __ > > *From:*Koha-devel > *On Behalf Of > *Kyle Hall > *Sent:* Tuesday, 19 May 2020 11:20 PM > *To:* Owen Leonard > > *Cc:* koha-devel > > *Subject:* Re: [Koha-devel] How to make self-referential URLs in > Koha____ > > __ __ > > I think that would also me a great cosmetic enhancement.____ > > __ __ > > At the risk of scope creep, we could go a step further by mapping > the perl scripts to paths as well, so > /cgi-bin/koha/circ/circulation-home.pl > could become /circulation/home ( or even just /circulation ) for > example.____ > > __ __ > > Kyle____ > > __ __ > > ---____ > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com > ) > Meadville Public Library ( http://www.meadvillelibrary.org > ) > Crawford County Federated Library System ( http://www.ccfls.org > )____ > > __ __ > > __ __ > > On Tue, May 19, 2020 at 9:08 AM Owen Leonard > wrote:____ > > > In the past, I have wondered if we could get rid of > “/cgi-bin/koha” as a path prefix all together > > No idea what that would involve (other than search-and-replace > in the > templates), but from the user's point of view I think it would be a > nice improvement. > >  -- Owen > > -- > Web Developer > Athens County Public Libraries > (740) 737-6006 > https://www.myacpl.org > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > https://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/ > ____ > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > https://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/ > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ > -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From andrew at bywatersolutions.com Thu Feb 11 18:03:35 2021 From: andrew at bywatersolutions.com (Andrew Fuerste-Henry) Date: Thu, 11 Feb 2021 11:03:35 -0600 Subject: [Koha-devel] Testing Docker Issue Message-ID: Hi folks! A couple of us within ByWater have run into testing docker issues recently. When trying to start up testing docker on master, one gets a bunch of SQL errors before the koha process just dies. It seems to be ok with starting up on a different branch and then switching to master after the fact. Has anyone else seen this? -- Andrew Fuerste-Henry Educator (he/him/his) ByWater Solutions bywatersolutions.com Phone:(888)900-8944 <(888)%20900-8944> What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Thu Feb 11 19:31:30 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 11 Feb 2021 19:31:30 +0100 Subject: [Koha-devel] Testing Docker Issue In-Reply-To: References: Message-ID: Which errors do you get? Le jeu. 11 févr. 2021 à 18:03, Andrew Fuerste-Henry < andrew at bywatersolutions.com> a écrit : > Hi folks! > A couple of us within ByWater have run into testing docker issues > recently. When trying to start up testing docker on master, one gets a > bunch of SQL errors before the koha process just dies. It seems to be ok > with starting up on a different branch and then switching to master after > the fact. > Has anyone else seen this? > > -- > Andrew Fuerste-Henry > Educator > (he/him/his) > ByWater Solutions > bywatersolutions.com > Phone:(888)900-8944 <(888)%20900-8944> > > What is Koha? > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Thu Feb 11 20:42:45 2021 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 11 Feb 2021 16:42:45 -0300 Subject: [Koha-devel] Testing Docker Issue In-Reply-To: References: Message-ID: I had issues with reset_all as well. It is some latest changes on the db El jue., 11 feb. 2021 15:32, Jonathan Druart < jonathan.druart at bugs.koha-community.org> escribió: > Which errors do you get? > > Le jeu. 11 févr. 2021 à 18:03, Andrew Fuerste-Henry < > andrew at bywatersolutions.com> a écrit : > >> Hi folks! >> A couple of us within ByWater have run into testing docker issues >> recently. When trying to start up testing docker on master, one gets a >> bunch of SQL errors before the koha process just dies. It seems to be ok >> with starting up on a different branch and then switching to master after >> the fact. >> Has anyone else seen this? >> >> -- >> Andrew Fuerste-Henry >> Educator >> (he/him/his) >> ByWater Solutions >> bywatersolutions.com >> Phone:(888)900-8944 <(888)%20900-8944> >> >> What is Koha? >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : https://www.koha-community.org/ >> git : https://git.koha-community.org/ >> bugs : https://bugs.koha-community.org/ >> > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew at bywatersolutions.com Thu Feb 11 20:51:58 2021 From: andrew at bywatersolutions.com (Andrew Fuerste-Henry) Date: Thu, 11 Feb 2021 13:51:58 -0600 Subject: [Koha-devel] Testing Docker Issue In-Reply-To: References: Message-ID: Digging through the terminal, the errors I was getting were related to some new tables created in a bug I was testing. They somehow persisted after a git reset --hard and a reset_all. On Thu, Feb 11, 2021 at 1:42 PM Tomas Cohen Arazi wrote: > I had issues with reset_all as well. It is some latest changes on the db > > El jue., 11 feb. 2021 15:32, Jonathan Druart < > jonathan.druart at bugs.koha-community.org> escribió: > >> Which errors do you get? >> >> Le jeu. 11 févr. 2021 à 18:03, Andrew Fuerste-Henry < >> andrew at bywatersolutions.com> a écrit : >> >>> Hi folks! >>> A couple of us within ByWater have run into testing docker issues >>> recently. When trying to start up testing docker on master, one gets a >>> bunch of SQL errors before the koha process just dies. It seems to be ok >>> with starting up on a different branch and then switching to master after >>> the fact. >>> Has anyone else seen this? >>> >>> -- >>> Andrew Fuerste-Henry >>> Educator >>> (he/him/his) >>> ByWater Solutions >>> bywatersolutions.com >>> Phone:(888)900-8944 <(888)%20900-8944> >>> >>> What is Koha? >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : https://www.koha-community.org/ >>> git : https://git.koha-community.org/ >>> bugs : https://bugs.koha-community.org/ >>> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : https://www.koha-community.org/ >> git : https://git.koha-community.org/ >> bugs : https://bugs.koha-community.org/ >> > -- Andrew Fuerste-Henry Educator (he/him/his) ByWater Solutions bywatersolutions.com Phone:(888)900-8944 <(888)%20900-8944> What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Fri Feb 12 00:35:03 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 12 Feb 2021 10:35:03 +1100 Subject: [Koha-devel] How to make self-referential URLs in Koha In-Reply-To: <66173030-22c7-8f7d-95c8-ca8b34c53edf@biblibre.com> References: <02f601d62d83$c9eb8730$5dc29590$@prosentient.com.au> <048901d62e47$9d8f53a0$d8adfae0$@prosentient.com.au> <66173030-22c7-8f7d-95c8-ca8b34c53edf@biblibre.com> Message-ID: <021401d700ce$85a9ce00$90fd6a00$@prosentient.com.au> Hi Frido, That's an interesting point. I was thinking that we'd just replace "/cgi-bin/koha" with a different base path (like "/opac" and "/intranet"). If we didn't do that (after all "/opac" and "/intranet" are still ugly), then I suppose we would need some other mechanism (like file extension) to enable CGI execution. Even with Plack... if we wanted the reverse proxy to serve the static assets, we'd need some way of knowing which requests to proxy to Starman... But you could turn on proxy/CGI for everything *except* requests to "intranet-tmpl" and "opac-tmpl" using Location or LocationMatch directives for instance. The static assets already have that base path, so that provides a nice hook. I've just finished restructuring an old PHP project, so I do have URL paths and file locations on my mind. I'm not using Laravel, but with Laravel you put your index.php and static assets into the "/public" directory and use that as your web app root. Then you tell it to use index.php as a FastCGI app. Hmm... here's an interesting snippet from the internet for Apache (looking for equivalents of Nginx's try_files): RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ balancer://app_cluster%{REQUEST_URI} [P,QSA,L] Anyway, there are certainly options. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Koha-devel On Behalf Of Fridolin SOMERS Sent: Friday, 12 February 2021 2:52 AM To: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] How to make self-referential URLs in Koha In this case in webserver config we base dynamic pages on the ".pl" extension. This is the case for example on the php projects I know. But then we must rename files in "svc" dirs with .pl. I'd be happy to test ;) Le 10/02/2021 à 22:54, Renvoize, Martin a écrit : > Did this ever become a bug? Looks like an interesting improvement and > would be nice to see a start made? > > On Wed, 20 May 2020, 2:40 am , > wrote: > > So happy to see responses to this ^_^____ > > __ __ > > Owen: It looks like we’d need to do a search and replace in the > templates and the code. So I think it could involve a lot of kicking > of tires. That said, we could do it incrementally. We could work > through it all module by module, and then remove the “/cgi-bin/koha” > once we’re sure it’s not referenced anywhere.____ > > __ __ > > Kyle: I’m glad you like the idea. I’d like to use the same paths in > Apache and Plack (for the sake of the self-referential URLs), so I > was thinking “/opac/opac-detail.pl ” and > “/intranet/circ” (or “/intranet/circulation”). ____ > > __ __ > > David Cook____ > > Systems Librarian____ > > Prosentient Systems____ > > 72/330 Wattle St____ > > Ultimo, NSW 2007____ > > Australia____ > > __ __ > > Office: 02 9212 0899____ > > Online: 02 8005 0595____ > > __ __ > > *From:*Koha-devel > *On Behalf Of > *Kyle Hall > *Sent:* Tuesday, 19 May 2020 11:20 PM > *To:* Owen Leonard > > *Cc:* koha-devel > > *Subject:* Re: [Koha-devel] How to make self-referential URLs in > Koha____ > > __ __ > > I think that would also me a great cosmetic enhancement.____ > > __ __ > > At the risk of scope creep, we could go a step further by mapping > the perl scripts to paths as well, so > /cgi-bin/koha/circ/circulation-home.pl > could become /circulation/home ( or even just /circulation ) for > example.____ > > __ __ > > Kyle____ > > __ __ > > ---____ > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com > ) > Meadville Public Library ( http://www.meadvillelibrary.org > ) > Crawford County Federated Library System ( http://www.ccfls.org > )____ > > __ __ > > __ __ > > On Tue, May 19, 2020 at 9:08 AM Owen Leonard > wrote:____ > > > In the past, I have wondered if we could get rid of > “/cgi-bin/koha” as a path prefix all together > > No idea what that would involve (other than search-and-replace > in the > templates), but from the user's point of view I think it would be a > nice improvement. > > -- Owen > > -- > Web Developer > Athens County Public Libraries > (740) 737-6006 > https://www.myacpl.org > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > https://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/ > ____ > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > https://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/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ git : > https://git.koha-community.org/ bugs : > https://bugs.koha-community.org/ > -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/ From jonathan.druart at bugs.koha-community.org Fri Feb 12 10:00:47 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 12 Feb 2021 10:00:47 +0100 Subject: [Koha-devel] Testing Docker Issue In-Reply-To: References: Message-ID: I pushed bug 25026 (RaiseError must be set for the UI) a couple of days ago, and a related misc4dev's merge request has also been merged at the same time (https://gitlab.com/koha-community/koha-misc4dev/-/issues/52). Can you make sure you "docker-compose pull" before and that /kohadevbox/misc4dev HEAD is b300d83 (Issue #52 - Prevent SQL errors to stop the reset_all process)? Le jeu. 11 févr. 2021 à 18:03, Andrew Fuerste-Henry a écrit : > > Hi folks! > A couple of us within ByWater have run into testing docker issues recently. When trying to start up testing docker on master, one gets a bunch of SQL errors before the koha process just dies. It seems to be ok with starting up on a different branch and then switching to master after the fact. > Has anyone else seen this? > > -- > Andrew Fuerste-Henry > Educator > (he/him/his) > ByWater Solutions > bywatersolutions.com > Phone:(888)900-8944 > > What is Koha? > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ From agustinmoyano at theke.io Fri Feb 12 16:35:56 2021 From: agustinmoyano at theke.io (Agustin Moyano) Date: Fri, 12 Feb 2021 12:35:56 -0300 Subject: [Koha-devel] Testing Docker Issue In-Reply-To: References: Message-ID: Hi Andrew, if database persists after restarting ktd, you can do: docker system prune -f and docker volumes prune -f The first command will remove any container that's not actually running, and the second will remove any persistent volume that's not attached to a running container. Cheers. On Fri, Feb 12, 2021 at 6:01 AM Jonathan Druart < jonathan.druart at bugs.koha-community.org> wrote: > I pushed bug 25026 (RaiseError must be set for the UI) a couple of > days ago, and a related misc4dev's merge request has also been merged > at the same time > (https://gitlab.com/koha-community/koha-misc4dev/-/issues/52). > > Can you make sure you "docker-compose pull" before and that > /kohadevbox/misc4dev HEAD is b300d83 (Issue #52 - Prevent SQL errors > to stop the reset_all process)? > > > Le jeu. 11 févr. 2021 à 18:03, Andrew Fuerste-Henry > a écrit : > > > > Hi folks! > > A couple of us within ByWater have run into testing docker issues > recently. When trying to start up testing docker on master, one gets a > bunch of SQL errors before the koha process just dies. It seems to be ok > with starting up on a different branch and then switching to master after > the fact. > > Has anyone else seen this? > > > > -- > > Andrew Fuerste-Henry > > Educator > > (he/him/his) > > ByWater Solutions > > bywatersolutions.com > > Phone:(888)900-8944 > > > > What is Koha? > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : https://www.koha-community.org/ > > git : https://git.koha-community.org/ > > bugs : https://bugs.koha-community.org/ > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohanews at gmail.com Sat Feb 13 10:17:00 2021 From: kohanews at gmail.com (Koha Newsletter) Date: Sat, 13 Feb 2021 10:17:00 +0100 Subject: [Koha-devel] Call for news - Newsletter February 2021 Message-ID: I'm collecting news for this month's newsletter. Send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: -------------- * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. 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 to be announced are fine, e. g. Kohacon. * For past events, one month back is the cut-off. 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! Michael Kuhn Editor, Koha Community Newsletter -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Sun Feb 14 23:04:44 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 15 Feb 2021 09:04:44 +1100 Subject: [Koha-devel] Testing Docker Issue In-Reply-To: References: Message-ID: <005301d7031d$67a301f0$36e905d0$@prosentient.com.au> I would be careful using “docker volumes prune -f” as that’s a nuclear option. Easy to lose volumes that you don’t want to lose, if you use Docker for anything other than KTD, when using that command. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel On Behalf Of Agustin Moyano Sent: Saturday, 13 February 2021 2:36 AM To: Jonathan Druart Cc: koha-devel Subject: Re: [Koha-devel] Testing Docker Issue Hi Andrew, if database persists after restarting ktd, you can do: docker system prune -f and docker volumes prune -f The first command will remove any container that's not actually running, and the second will remove any persistent volume that's not attached to a running container. Cheers. On Fri, Feb 12, 2021 at 6:01 AM Jonathan Druart > wrote: I pushed bug 25026 (RaiseError must be set for the UI) a couple of days ago, and a related misc4dev's merge request has also been merged at the same time (https://gitlab.com/koha-community/koha-misc4dev/-/issues/52). Can you make sure you "docker-compose pull" before and that /kohadevbox/misc4dev HEAD is b300d83 (Issue #52 - Prevent SQL errors to stop the reset_all process)? Le jeu. 11 févr. 2021 à 18:03, Andrew Fuerste-Henry > a écrit : > > Hi folks! > A couple of us within ByWater have run into testing docker issues recently. When trying to start up testing docker on master, one gets a bunch of SQL errors before the koha process just dies. It seems to be ok with starting up on a different branch and then switching to master after the fact. > Has anyone else seen this? > > -- > Andrew Fuerste-Henry > Educator > (he/him/his) > ByWater Solutions > bywatersolutions.com > Phone:(888)900-8944 > > What is Koha? > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From victor at tuxayo.net Tue Feb 16 19:16:45 2021 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Tue, 16 Feb 2021 19:16:45 +0100 Subject: [Koha-devel] Time to translate: string freeze to prepare Koha 19.11.15 has begun Message-ID: Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 19.11.x maintenance branch. The release is scheduled for the 22th. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 19.11, then you must also copy it to 20.05 and 20.11. Otherwise your work will be lost for future versions. Happy translating, -- Victor Grousset/tuxayo From dcook at prosentient.com.au Wed Feb 17 03:56:50 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Wed, 17 Feb 2021 13:56:50 +1100 Subject: [Koha-devel] Occasional problems with koha-dump (LOCK TABLES) Message-ID: <009001d704d8$89e59310$9db0b930$@prosentient.com.au> Hi all, I was testing koha-dump on a new Ubuntu 18.04 server I put together, and I noticed that 2 out of 3 instances were failing to dump. Here are the errors: mysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces mysqldump: Got error: 1045: Access denied for user 'koha_'@'localhost' (using password: YES) when using LOCK TABLES The first isn't really relevant. The key one is the second one. You can workaround it by adding "--single-transaction" to mysqldump in koha-dump, but I'm still intrigued why it only happened to 2 out of 3 instances on that server. I haven't seen this issue on other 18.04 servers either. All the permissions and what not were the same across the instances, the database connections were sleeping, etc. Nothing made sense. mysql> show grants for 'koha_'@'localhost'; +--------------------------------------------------------------------------+ | Grants for koha_@localhost | +--------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO 'koha_'@'localhost' | | GRANT ALL PRIVILEGES ON `koha_`.* TO 'koha_'@'localhost' | +--------------------------------------------------------------------------+ Has anyone else had this problem? David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Wed Feb 17 04:35:25 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Wed, 17 Feb 2021 14:35:25 +1100 Subject: [Koha-devel] Announcing an alternate indexing daemon for Zebra which is more memory efficient In-Reply-To: <3d1c7fb2-baf4-8acb-8f7d-38f8c32d8e42@biblibre.com> References: <061f01d6e3db$f4a90970$ddfb1c50$@prosentient.com.au> <6fe76a28-c6d6-146e-0037-345f9fe39e0d@biblibre.com> <06b401d6e483$52541860$f6fc4920$@prosentient.com.au> <3d1c7fb2-baf4-8acb-8f7d-38f8c32d8e42@biblibre.com> Message-ID: <00a301d704dd$ee3652a0$caa2f7e0$@prosentient.com.au> How are people going with this? I've been running it for about 1.5 months now with 0 complaints. As I just noted on 27267, I just implemented it on a small cloud server with only 4GB RAM and I was able to save 500MB switching to the alternative indexer. Quite a big win in a resource constrained environment! David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Fridolin SOMERS Sent: Thursday, 7 January 2021 7:08 PM To: dcook at prosentient.com.au; koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Announcing an alternate indexing daemon for Zebra which is more memory efficient Ah of course, rebuild_zebra.pl itself has lock system. It ends if you dont use --wait-for-lock. Thanks ;) Le 07/01/2021 à 00:26, dcook at prosentient.com.au a écrit : > There's no need for a couple reasons. > > First, all child process operations for my "zebra_indexer.pl" (ie checking for records to index and the actual indexing) cause the parent indexing daemon to block (by using waitpid($pid,0)) so there should be no overlapping runs. > > Second, even if multiple rebuild_zebra.pl processes were launched magically, the built-in locking in rebuild_zebra.pl would prevent any but the 1st process from running. > > So it's all good 😃 > > David Cook > Software Engineer > Prosentient Systems > Suite 7.03 > 6a Glen St > Milsons Point NSW 2061 > Australia > > Office: 02 9212 0899 > Online: 02 8005 0595 > > -----Original Message----- > From: Koha-devel On > Behalf Of Fridolin SOMERS > Sent: Thursday, 7 January 2021 4:01 AM > To: koha-devel at lists.koha-community.org > Subject: Re: [Koha-devel] Announcing an alternate indexing daemon for > Zebra which is more memory efficient > > Oooh nice. > > Is there a protection against several launch ? Like in actual daemon --wait-for-lock ? > Or is there no need ? > > Regards, > > Le 06/01/2021 à 08:50, Josef Moravec a écrit : >> Hello David, >> >> thanks for sharing, it looks great! We are going to test it on one of >> our servers. We'll report how things are going probably in few days... >> >> >> Josef >> >> On Wed, Jan 6, 2021 at 4:28 AM > > wrote: >> >> Hi all,____ >> >> __ __ >> >> I’ve written a new indexing daemon for Zebra which you can find at >> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27267 >> . >> It’s dead easy to use. Once the daemon is installed, you just need >> to update /etc/default/koha-common and you’ll be using it.____ >> >> __ __ >> >> It only uses 6MB of RAM (instead of the 170-180MB I’ve seen >> rebuild_zebra.pl use in daemon mode), so >> it scales well on servers that host many instances of Koha. (For >> example, if you have 50 Koha instances on a server, you’ll use 300MB >> instead of 9GB for idle Zebra indexing daemons.) That said, this >> indexing daemon does launch rebuild_zebra.pl >> in non-daemon mode when necessary, so you >> still need to have memory available to do actual work. Making >> rebuild_zebra.pl more memory efficient is >> another task in itself and not a pressing issue atm.____ >> >> __ __ >> >> I’m planning to use it shortly myself, but I figured that I would >> share it with everyone else, so that everyone else could benefit >> from it too. ____ >> >> __ __ >> >> Hope others enjoy it as much as I do.____ >> >> __ __ >> >> David Cook____ >> >> Software Engineer____ >> >> Prosentient Systems____ >> >> Suite 7.03____ >> >> 6a Glen St____ >> >> Milsons Point NSW 2061____ >> >> Australia____ >> >> __ __ >> >> Office: 02 9212 0899____ >> >> Online: 02 8005 0595____ >> >> __ __ >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> >> website : https://www.koha-community.org/ >> >> git : https://git.koha-community.org/ >> bugs : https://bugs.koha-community.org/ >> >> >> >> >> -- >> Josef Moravec >> josef.moravec at gmail.com >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : https://www.koha-community.org/ git : >> https://git.koha-community.org/ bugs : >> https://bugs.koha-community.org/ >> > > -- > Fridolin SOMERS Software and system > maintainer 🦄 > BibLibre, France > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ git : > https://git.koha-community.org/ bugs : > https://bugs.koha-community.org/ > > -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From ztajoli at gmail.com Wed Feb 17 09:06:14 2021 From: ztajoli at gmail.com (Zeno Tajoli) Date: Wed, 17 Feb 2021 09:06:14 +0100 Subject: [Koha-devel] Build slection of Jquery-UI Message-ID: Hi to all, last days I'm starting to use JQuery-UI much more. I find that in Koha there aren't all sections of JQuery-UI but only a selection. In opac: widget.js, position.js, data.js, keycode.js, scroll-parent.js, unique-id.js, widgets/sortable.js, widgets/autocomplete.js, widgets/datepicker.js, widgets/menu.js, widgets/mouse.js, widgets/slider.js, widgets/tabs.js, widgets/tooltip.js with version 1.12.1 In staff the list is: core.js, widget.js, mouse.js, position.js, draggable.js, droppable.js, sortable.js, accordion.js, autocomplete.js, button.js, datepicker.js, menu.js, progressbar.js, slider.js, tabs.js, effect.js, effect-highlight.js with version 1.11.4 There are specific motivation behind those different lists ? What do you think if I propose to add the dialog widget ( https://api.jqueryui.com/dialog/) to opac and staff ? Cheers Zeno Tajoli -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Wed Feb 17 10:35:05 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 17 Feb 2021 10:35:05 +0100 Subject: [Koha-devel] Build slection of Jquery-UI In-Reply-To: References: Message-ID: Hi Zeno, It Looks like you could use the Bootstrap's modals instead of dialog's jQuery UI. It's what we are using already in different places of the code. Cheers, Jonathan Le mer. 17 févr. 2021 à 09:06, Zeno Tajoli a écrit : > > Hi to all, > last days I'm starting to use JQuery-UI much more. > I find that in Koha there aren't all sections of JQuery-UI but only a selection. > In opac: widget.js, position.js, data.js, keycode.js, scroll-parent.js, > unique-id.js, widgets/sortable.js, widgets/autocomplete.js, > widgets/datepicker.js, widgets/menu.js, widgets/mouse.js, > widgets/slider.js, widgets/tabs.js, widgets/tooltip.js with version 1.12.1 > > In staff the list is: core.js, widget.js, mouse.js, position.js, draggable.js, droppable.js, > sortable.js, accordion.js, autocomplete.js, button.js, datepicker.js, menu.js, > progressbar.js, slider.js, tabs.js, effect.js, effect-highlight.js with version 1.11.4 > > There are specific motivation behind those different lists ? > What do you think if I propose to add the dialog widget (https://api.jqueryui.com/dialog/) to opac and staff ? > > Cheers > Zeno Tajoli > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ From ere.maijala at helsinki.fi Wed Feb 17 11:20:35 2021 From: ere.maijala at helsinki.fi (Ere Maijala) Date: Wed, 17 Feb 2021 12:20:35 +0200 Subject: [Koha-devel] Build slection of Jquery-UI In-Reply-To: References: Message-ID: <490723c4-bdc9-8959-14dc-a7437ad51edd@helsinki.fi> Hi, Just a side note: jQuery UI hasn't seen much development lately. I wouldn't build new functionality on top of it. --Ere Zeno Tajoli kirjoitti 17.2.2021 klo 10.06: > Hi to all, > last days I'm starting to use JQuery-UI much more. > I find that in Koha there aren't all sections of JQuery-UI but only a > selection. > In opac: widget.js, position.js, data.js, keycode.js, scroll-parent.js, >  unique-id.js, widgets/sortable.js, widgets/autocomplete.js, >  widgets/datepicker.js, widgets/menu.js, widgets/mouse.js, >  widgets/slider.js, widgets/tabs.js, widgets/tooltip.js with version 1.12.1 > > In staff the list is: core.js, widget.js, mouse.js, position.js, > draggable.js, droppable.js, > sortable.js, accordion.js, autocomplete.js, button.js, datepicker.js, > menu.js, > progressbar.js, slider.js, tabs.js, effect.js, effect-highlight.js with > version 1.11.4 > > There are specific motivation behind those different lists ? > What do you think if I propose to add the dialog widget > (https://api.jqueryui.com/dialog/ ) to > opac and staff ? > > Cheers > Zeno Tajoli > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ > -- Ere Maijala Kansalliskirjasto / The National Library of Finland From oleonard at myacpl.org Wed Feb 17 12:04:14 2021 From: oleonard at myacpl.org (Owen Leonard) Date: Wed, 17 Feb 2021 06:04:14 -0500 Subject: [Koha-devel] Build slection of Jquery-UI In-Reply-To: <490723c4-bdc9-8959-14dc-a7437ad51edd@helsinki.fi> References: <490723c4-bdc9-8959-14dc-a7437ad51edd@helsinki.fi> Message-ID: > Just a side note: jQuery UI hasn't seen much development lately. I > wouldn't build new functionality on top of it. I agree 100%. Although it continues to work well for us, I'm concerned about its long-term health. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org From andrew at bywatersolutions.com Wed Feb 17 13:57:22 2021 From: andrew at bywatersolutions.com (Andrew Fuerste-Henry) Date: Wed, 17 Feb 2021 06:57:22 -0600 Subject: [Koha-devel] Testing Docker Issue In-Reply-To: <005301d7031d$67a301f0$36e905d0$@prosentient.com.au> References: <005301d7031d$67a301f0$36e905d0$@prosentient.com.au> Message-ID: Thanks for the feedback, all. Docker commands are definitely something I could stand to learn more about! Andrew On Sun, Feb 14, 2021 at 4:05 PM wrote: > I would be careful using “docker volumes prune -f” as that’s a nuclear > option. Easy to lose volumes that you don’t want to lose, if you use Docker > for anything other than KTD, when using that command. > > > > David Cook > > Software Engineer > > Prosentient Systems > > Suite 7.03 > > 6a Glen St > > Milsons Point NSW 2061 > > Australia > > > > Office: 02 9212 0899 > > Online: 02 8005 0595 > > > > *From:* Koha-devel *On > Behalf Of *Agustin Moyano > *Sent:* Saturday, 13 February 2021 2:36 AM > *To:* Jonathan Druart > *Cc:* koha-devel > *Subject:* Re: [Koha-devel] Testing Docker Issue > > > > Hi Andrew, if database persists after restarting ktd, you can do: > > > > docker system prune -f > > > > and > > > > docker volumes prune -f > > > > The first command will remove any container that's not actually running, > and the second will remove any persistent volume that's not attached to a > running container. > > > > Cheers. > > > > On Fri, Feb 12, 2021 at 6:01 AM Jonathan Druart < > jonathan.druart at bugs.koha-community.org> wrote: > > I pushed bug 25026 (RaiseError must be set for the UI) a couple of > days ago, and a related misc4dev's merge request has also been merged > at the same time > (https://gitlab.com/koha-community/koha-misc4dev/-/issues/52). > > Can you make sure you "docker-compose pull" before and that > /kohadevbox/misc4dev HEAD is b300d83 (Issue #52 - Prevent SQL errors > to stop the reset_all process)? > > > Le jeu. 11 févr. 2021 à 18:03, Andrew Fuerste-Henry > a écrit : > > > > Hi folks! > > A couple of us within ByWater have run into testing docker issues > recently. When trying to start up testing docker on master, one gets a > bunch of SQL errors before the koha process just dies. It seems to be ok > with starting up on a different branch and then switching to master after > the fact. > > Has anyone else seen this? > > > > -- > > Andrew Fuerste-Henry > > Educator > > (he/him/his) > > ByWater Solutions > > bywatersolutions.com > > Phone:(888)900-8944 > > > > What is Koha? > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : https://www.koha-community.org/ > > git : https://git.koha-community.org/ > > bugs : https://bugs.koha-community.org/ > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ > -- Andrew Fuerste-Henry Educator (he/him/his) ByWater Solutions bywatersolutions.com Phone:(888)900-8944 <(888)%20900-8944> What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From bargioni at pusc.it Wed Feb 17 17:51:20 2021 From: bargioni at pusc.it (Stefano Bargioni) Date: Wed, 17 Feb 2021 17:51:20 +0100 Subject: [Koha-devel] Build slection of Jquery-UI In-Reply-To: <490723c4-bdc9-8959-14dc-a7437ad51edd@helsinki.fi> References: <490723c4-bdc9-8959-14dc-a7437ad51edd@helsinki.fi> Message-ID: You are right, Ere, thx. But Zeno asked for me: I have to migrate some old code - step 1, let's say in a hurry. Step 2: I'll study how to convert old dialogues to Bootstrap. Ciao. Stefano > On 17 Feb 2021, at 11:20, Ere Maijala wrote: > > Hi, > > Just a side note: jQuery UI hasn't seen much development lately. I wouldn't build new functionality on top of it. > > --Ere > > Zeno Tajoli kirjoitti 17.2.2021 klo 10.06: >> Hi to all, >> last days I'm starting to use JQuery-UI much more. >> I find that in Koha there aren't all sections of JQuery-UI but only a selection. >> In opac: widget.js, position.js, data.js, keycode.js, scroll-parent.js, >> unique-id.js, widgets/sortable.js, widgets/autocomplete.js, >> widgets/datepicker.js, widgets/menu.js, widgets/mouse.js, >> widgets/slider.js, widgets/tabs.js, widgets/tooltip.js with version 1.12.1 >> In staff the list is: core.js, widget.js, mouse.js, position.js, draggable.js, droppable.js, >> sortable.js, accordion.js, autocomplete.js, button.js, datepicker.js, menu.js, >> progressbar.js, slider.js, tabs.js, effect.js, effect-highlight.js with version 1.11.4 >> There are specific motivation behind those different lists ? >> What do you think if I propose to add the dialog widget (https://api.jqueryui.com/dialog/ ) to opac and staff ? >> Cheers >> Zeno Tajoli >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : https://www.koha-community.org/ >> git : https://git.koha-community.org/ >> bugs : https://bugs.koha-community.org/ > > -- > Ere Maijala > Kansalliskirjasto / The National Library of Finland > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ From fridolin.somers at biblibre.com Thu Feb 18 12:03:42 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Thu, 18 Feb 2021 12:03:42 +0100 Subject: [Koha-devel] Time to translate: string freeze to prepare February release Message-ID: <9892d0d4-cdda-4f27-323e-4efcd8de7ae5@biblibre.com> Hi, String freeze is into effect today for the 20.11.x maintenance branch for 20.11.03 release. The release is scheduled for around the 23rd. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Happy translating 🌎🌍🌏 -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From philippe.blouin at inlibro.com Thu Feb 18 18:55:17 2021 From: philippe.blouin at inlibro.com (Philippe Blouin) Date: Thu, 18 Feb 2021 12:55:17 -0500 Subject: [Koha-devel] Known issues with plack on Debian 10 ? Message-ID: Hello all, As we are slowly upgrading our servers to D10, along with clients to Koha 20.05.08 from 19.05, I just realized plack was not working. Starman is up, the logs in plack-error.log are filling with normal stuff, I see no error in /var/log/daemon.log, or any log for that matter...  But absolutely no performance improvement. Zero, nada... Does anyone has a hint on what I should be looking for?  I've never dug the plumbing of that magic, and admit I'm clueless right now.  These are Dev (git) installs. Great thanks, -- Philippe Blouin, Directeur de la technologie Tél.  : (833) 465-4276, poste 230 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.blouin at inlibro.com Thu Feb 18 19:07:50 2021 From: philippe.blouin at inlibro.com (Philippe Blouin) Date: Thu, 18 Feb 2021 13:07:50 -0500 Subject: [Koha-devel] Known issues with plack on Debian 10 ? In-Reply-To: References: Message-ID: <6d7fd17f-9ca7-727c-6da0-e65a76b751cb@inlibro.com> NOTE: I've added the --user and --group to start-stop-daemon, which was preventing the stop and status. Philippe Blouin, Directeur de la technologie Tél.  : (833) 465-4276, poste 230 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com On 2021-02-18 12:55 p.m., Philippe Blouin wrote: > > Hello all, > > As we are slowly upgrading our servers to D10, along with clients to > Koha 20.05.08 from 19.05, I just realized plack was not working. > > Starman is up, the logs in plack-error.log are filling with normal > stuff, I see no error in /var/log/daemon.log, or any log for that > matter...  But absolutely no performance improvement. Zero, nada... > > Does anyone has a hint on what I should be looking for?  I've never > dug the plumbing of that magic, and admit I'm clueless right now.  > These are Dev (git) installs. > > Great thanks, > > -- > Philippe Blouin, > Directeur de la technologie > > Tél.  : (833) 465-4276, poste 230 > philippe.blouin at inLibro.com > > inLibro | pour esprit libre | www.inLibro.com > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Fri Feb 19 08:07:53 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 19 Feb 2021 08:07:53 +0100 Subject: [Koha-devel] Known issues with plack on Debian 10 ? In-Reply-To: References: Message-ID: Hi Philippe, No performance improvement compared to what? What is "no perf improvement"? How much time per request? Did you search for warnings/errors on the about page? Cheers, Jonathan Le jeu. 18 févr. 2021 à 18:55, Philippe Blouin a écrit : > > Hello all, > > As we are slowly upgrading our servers to D10, along with clients to Koha 20.05.08 from 19.05, I just realized plack was not working. > > Starman is up, the logs in plack-error.log are filling with normal stuff, I see no error in /var/log/daemon.log, or any log for that matter... But absolutely no performance improvement. Zero, nada... > > Does anyone has a hint on what I should be looking for? I've never dug the plumbing of that magic, and admit I'm clueless right now. These are Dev (git) installs. > > Great thanks, > > -- > Philippe Blouin, > Directeur de la technologie > > Tél. : (833) 465-4276, poste 230 > philippe.blouin at inLibro.com > > inLibro | pour esprit libre | www.inLibro.com > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ From philippe.blouin at inlibro.com Fri Feb 19 13:56:23 2021 From: philippe.blouin at inlibro.com (Philippe Blouin) Date: Fri, 19 Feb 2021 07:56:23 -0500 Subject: [Koha-devel] Known issues with plack on Debian 10 ? In-Reply-To: References: Message-ID: Oh, the about page.  Completely forgot about that one, thanks! That would have helped me with the libraries. Yes, I meant searches, mainly, but it all started with the display of acqui-home.pl.  I had big hopes that moving to a new server would help for a client with 3000+ budgets to display, and it did... until I turned on plack which made NO difference.  I then realized the problem was generalized. Seems I have "fixed" it, by reinstalling the libraries, manually editing all the daemon files, etc (I honestly can't remember). Reading bz 26893 a few times might have helped too. Still plack wouldn't log the "Can't locate REST/Client.pm in @INC", I had to drop it to see the message, but that probably a config issue with that installation, again. All in all, it works now, but I'll try to think of about.pl in the future before rampaging. Cheers, Philippe Blouin, Directeur de la technologie Tél.  : (833) 465-4276, poste 230 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com On 2021-02-19 2:07 a.m., Jonathan Druart wrote: > Hi Philippe, > > No performance improvement compared to what? What is "no perf > improvement"? How much time per request? > Did you search for warnings/errors on the about page? > > Cheers, > Jonathan > > Le jeu. 18 févr. 2021 à 18:55, Philippe Blouin > a écrit : >> Hello all, >> >> As we are slowly upgrading our servers to D10, along with clients to Koha 20.05.08 from 19.05, I just realized plack was not working. >> >> Starman is up, the logs in plack-error.log are filling with normal stuff, I see no error in /var/log/daemon.log, or any log for that matter... But absolutely no performance improvement. Zero, nada... >> >> Does anyone has a hint on what I should be looking for? I've never dug the plumbing of that magic, and admit I'm clueless right now. These are Dev (git) installs. >> >> Great thanks, >> >> -- >> Philippe Blouin, >> Directeur de la technologie >> >> Tél. : (833) 465-4276, poste 230 >> philippe.blouin at inLibro.com >> >> inLibro | pour esprit libre | www.inLibro.com >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : https://www.koha-community.org/ >> git : https://git.koha-community.org/ >> bugs : https://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Tue Feb 23 16:51:05 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Tue, 23 Feb 2021 16:51:05 +0100 Subject: [Koha-devel] Release of Koha 20.11.03 Message-ID: <4f609bb7-8144-631e-b7b4-824e176b49a0@biblibre.com> Hello everyone 🤗 The Koha community is proud to announce the release of Koha 20.11.03. It is a maintenance release including 2 new features, 22 enhancements, 74 bugfixes, 1 security fix. So consider upgrading quickly 🤖 The full release notes are available here: https://koha-community.org/koha-20-11-03-released/ Debian packages should be available in a few days. Best regards 🤓 -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From andrew at bywatersolutions.com Tue Feb 23 21:57:15 2021 From: andrew at bywatersolutions.com (Andrew Fuerste-Henry) Date: Tue, 23 Feb 2021 14:57:15 -0600 Subject: [Koha-devel] Release of Koha 20.05.09 Message-ID: Hi folks! The Koha community is pleased to announce the release of Koha 20.05.09. This is a bugfix/maintenance release that includes 2 security fixes, 1 new features, 13 enhancements, 63 bugfixes. Due to those security bugs, a speedy upgrade is encouraged! Full release notes are available here: https://koha-community.org/koha-20-05-09-released/ Thanks! Andrew Fuerste-Henry Educator (he/him/his) ByWater Solutions bywatersolutions.com Phone:(888)900-8944 <(888)%20900-8944> What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From victor at tuxayo.net Wed Feb 24 00:05:57 2021 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Wed, 24 Feb 2021 00:05:57 +0100 Subject: [Koha-devel] =?utf-8?q?Koha_19=2E11=2E15_released=2C_security_re?= =?utf-8?b?bGVhc2Ug4pqg?= Message-ID: Hello! The Koha Community is happy to announce the release of Koha 19.11.15 The full release notes can be found at: https://koha-community.org/koha-19-11-15-released/ Debian packages will be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo From mtj at kohaaloha.com Wed Feb 24 04:02:07 2021 From: mtj at kohaaloha.com (Mason James) Date: Wed, 24 Feb 2021 16:02:07 +1300 Subject: [Koha-devel] =?utf-8?q?Koha_packages_are_available_=F0=9F=8E=81?= In-Reply-To: <4f609bb7-8144-631e-b7b4-824e176b49a0@biblibre.com> References: <4f609bb7-8144-631e-b7b4-824e176b49a0@biblibre.com> Message-ID: hi Folks the latest Koha packages are available cheers, Mason On 24/02/21 4:51 am, Fridolin SOMERS wrote: > Hello everyone 🤗 > > The Koha community is proud to announce the release of Koha 20.11.03. > > It is a maintenance release including 2 new features, 22 enhancements, 74 bugfixes, 1 security fix. > So consider upgrading quickly 🤖 > > The full release notes are available here: > https://koha-community.org/koha-20-11-03-released/ > > Debian packages should be available in a few days. > > Best regards 🤓 > From fridolin.somers at biblibre.com Wed Feb 24 08:14:53 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 24 Feb 2021 08:14:53 +0100 Subject: [Koha-devel] Release of Koha 20.11.03 In-Reply-To: <4f609bb7-8144-631e-b7b4-824e176b49a0@biblibre.com> References: <4f609bb7-8144-631e-b7b4-824e176b49a0@biblibre.com> Message-ID: Oups I fergot to add that there are 2 bug fixes: Bug 27604 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27604 Le 23/02/2021 à 16:51, Fridolin SOMERS a écrit : > Hello everyone 🤗 > > The Koha community is proud to announce the release of Koha 20.11.03. > > It is a maintenance release including 2 new features, 22 enhancements, > 74 bugfixes, 1 security fix. > So consider upgrading quickly 🤖 > > The full release notes are available here: > https://koha-community.org/koha-20-11-03-released/ > > Debian packages should be available in a few days. > > Best regards 🤓 > -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From tomascohen at gmail.com Wed Feb 24 19:30:33 2021 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 24 Feb 2021 15:30:33 -0300 Subject: [Koha-devel] Help with bug 25674 Message-ID: Hi all, we have introduced the use of the message broker (RabbitMQ) but surprisingly the bug that actually makes that configurable for regular installs hasn't been moved even a tiny bit [1] Can some of you please take a look? It is really easy to test (just play with the koha-create option switches and see the resulting koha-conf.xml entries) and a valuable addition. Thanks in advance [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25674 -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohanews at gmail.com Sun Feb 28 18:47:05 2021 From: kohanews at gmail.com (Koha Newsletter) Date: Sun, 28 Feb 2021 18:47:05 +0100 Subject: [Koha-devel] Koha Community Newsletter: February 2021 Message-ID: The Koha Community Newsletter for February 2021 is here: https://koha-community.org/koha-community-newsletter-february-2021/ Many thanks to everyone who submitted articles and news to last month's newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.nind at gmail.com Sun Feb 28 20:24:23 2021 From: david.nind at gmail.com (David Nind) Date: Mon, 1 Mar 2021 08:24:23 +1300 Subject: [Koha-devel] Koha Community Newsletter: February 2021 In-Reply-To: References: Message-ID: Thanks Michael for another great edition! David Nind On Mon, 1 Mar 2021 at 06:47, Koha Newsletter wrote: > The Koha Community Newsletter for February 2021 is here: > https://koha-community.org/koha-community-newsletter-february-2021/ > > Many thanks to everyone who submitted articles and news to last month's > newsletter! > > Please feel free to email me with any corrections or suggestions. > -- > Michael Kuhn > Editor, Koha Community Newsletter > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: