-- In a separate email, I've asked what I should be looking for in terms of QA. Or are we still at a stage of looking for feedback? Personally, I think that we might still be a bit too ERM focused with the Vue.js. Instead of http://localhost:8081/cgi-bin/koha/erm/erm.pl perhaps we should be going to http://localhost:8081/cgi-bin/koha/spa/erm. Note that "spa" is a placeholder here (in this case standing for single page application). Off the top of my head, I don't have a great base URL in mind. That way "Koha" is the Vue.js app, and "ERM" is a component provided to "Koha". We could centralize a number of methods in the root "Koha" app. Actually, me emailing is probably pointless. Maybe one night I can do some work in the evening, so that I can link up with folk and we can chat more. David Cook Senior 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 jonathan.druart at bugs.koha-community.org Wed Feb 22 07:43:04 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 22 Feb 2023 07:43:04 +0100 Subject: [Koha-devel] Vue improvements/refactorings In-Reply-To: <034c01d9467c$8f3933c0$adab9b40$@prosentient.com.au> References:

<034c01d9467c$8f3933c0$adab9b40$@prosentient.com.au> Message-ID: It's a lot of changes, that's why they are split into several bug reports and patches. Is it always either too big or too small? > I’m not sure what to be looking for from a QA perspective Does it look better after the patches than before? Is it still working? If so they should get in. > I’d probably do things a bit differently There are always different ways. Here it's mine, feel free to propose alternatives. > creating a design that maximizes reusability and eases maintenance That's *exactly* the goal of these patches. And more work is in the pipe so it cannot wait too long. Le mer. 22 févr. 2023 à 06:14, David Cook a écrit : > I think that the number of bug reports and commits is a bit intimidating. > Unless there is a compelling reason to the contrary, I think squashing a > lot of these commits would be a good idea. > > > > Also, I’m doing a diff on > https://gitlab.com/joubu/Koha/-/commits/bug_32991 and the stats are: 76 > files changed, 929 insertions(+), 1823 deletions(-). That’s a lot of > changes to review. > > > > Looking through the changed files… I’d say targeting changes that affect > non-ERM functionality should take highest priority – like Bug 32981 and Bug > 32923 – since more people have the skills to work on them. Then maybe all > the ERM changes can be tested at 1 time all together, although that’s a bit > messy in terms of attaching signed off patches… > > > > Looking at the Vue components… I’m not sure what to be looking for from a > QA perspective, since we don’t have any rules around Vue.js specifically. > For Javascript related things, things look OK in the couple of *.vue files > I’ve reviewed, but I’d need to double-check them to know for sure. > > > > Looking through Breadcrumb.vue and Main.vue, I’d probably do things a bit > differently for readability and generalizability/reusability. I don’t know > if that should be a blocker or not at this stage though… > > > > Personally, I don’t have any investment in the ERM work, but I’m very > interested in the Vue.js work. I’d love to make sure we’re creating a > design that maximizes reusability and eases maintenance. > > > > My koha-testing-docker is broken at the moment, so I’ll look at fixing > that up, and then I’ll try to look at this more. > > > > I am willing to help, although my schedule is fairly full too. I’m trying > to do more Vue.js on other projects, so hopefully I can bring that > experience back to Koha and help more… > > > > David Cook > > Senior 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 *Jonathan Druart > *Sent:* Wednesday, 22 February 2023 1:57 AM > *To:* koha-devel > *Subject:* Re: [Koha-devel] Vue improvements/refactorings > > > > A quick update. > > > > There are several bug reports, and the tree is at > https://gitlab.com/joubu/Koha/-/commits/bug_32991 > > It's ~40 commits on top of master, a lot of architecture changes in the > erm/vue files. > > It would be great to have them pushed ASAP, they are blocking other works. > > Most important is that people will read, learn and copy the code that is > in master, which will be obsolete (and generate conflicts) one this tree > will be pushed. > > > > How can we coordinate to make it move forward? Who is willing to help here? > > Cheers, > > Jonathan > > > > Le mer. 15 févr. 2023 à 14:09, Jonathan Druart < > jonathan.druart at bugs.koha-community.org> a écrit : > > Hi, > > > > Pedro and I have been working on improving the way we request the Koha > REST API from Vue components. > > We ended up with the implementation that is available on the following > remote branch: > > https://gitlab.com/joubu/Koha/-/commits/bug_32925 > > > > It contains the patches from the following bug reports: > > *Bug 32898* > - > Cypress tests are failing > > *Bug 32923* > - > x-koha-embed must a header of collectionFormat csv > > *Bug 32806* > - Some > Vue files need to be moved for better reusability > > *Bug 32939* > - Have > generic fetch functions in vue modules > > *Bug 32925* > - > Display loading info when a form is submitted > > > > First, make the tests pass (32898)! We forgot to include the cypress test > in the jenkins pipeline and we missed regressions! There have been > regressions on the REST API specs, that are fixed on 32923. > > We noticed that the code we provided for the ERM module was not flexible > enough and too ERM oriented. Some directories have been moved and code > split a bit to make it more reusable for other modules (32806). > > Finally there are 32939 that introduce generic fetch functions, to have > all the error handling (catch exceptions and display the error on the UI) > in a single place. On top of that we added a "loading" message when a form > (POST/PUT/DELETE) is submitted and, thanks to the previous moves, it's only > a couple of lines of code! > > > > All this must be considered a base for future Vue enhancements, and I > would like people interested in the Vue work to have a look at it. > > > > Cheers, > > Jonathan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.roussos at dataly.gr Wed Feb 22 07:45:47 2023 From: a.roussos at dataly.gr (Andreas Roussos) Date: Wed, 22 Feb 2023 08:45:47 +0200 Subject: [Koha-devel] ChatGPT and Koha In-Reply-To: <032a01d94658$19686a40$4c393ec0$@prosentient.com.au> References: <032a01d94658$19686a40$4c393ec0$@prosentient.com.au> Message-ID: <4f8809b7-6b79-ccea-0d01-a3d31a5cd127@dataly.gr> Hi David, FWIW, a couple of weeks ago I copied and pasted two snippets of Perl code from Koha because I couldn't understand what type of variable they were generating. ChatGPT came back with a pretty comprehensive answer about hash references. What impressed me (apart from the quality of its reply) was that I copied/pasted the code in a hurry including the line numbers preceding each line, however that did not seem to confuse ChatGPT at all! Kind regards, Andreas On 2023-02-22 02:53, David Cook wrote: > > Hi all, > > Like many around the world, I may have been bitten by the ChatGPT bug… > > Most of my ChatGPT questions have been more general in nature, but I > figured I’d ask it about Koha, as there is a lot of public > information, but it’s still a niche topic. > > I asked it to generate me a Koha plugin, and it refused for a while, > but eventually I was able to convince it to try. The result wouldn’t > even compile, but it got a lot of things right. In other > conversations, it’s made mistakes but always done a good job of fixing > its mistakes. > > Has anyone else played with ChatGPT and Koha or ChatGPT in general (on > IT topics)? > > David Cook > > Senior 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Wed Feb 22 07:53:04 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 22 Feb 2023 07:53:04 +0100 Subject: [Koha-devel] Testing ERM functionality In-Reply-To: <036301d94686$f5cdd690$e16983b0$@prosentient.com.au> References: <036301d94686$f5cdd690$e16983b0$@prosentient.com.au> Message-ID: About the warning I guess you are working on top of the "refactoring" branch, have a look at 32991 commit message and the discussion on the bug. Le mer. 22 févr. 2023 à 07:29, David Cook a écrit : > Hi Jonathan and folks, > > > > Is there a general test plan that can be used for testing ERM > functionality? Should/could koha-testing-docker come with some test data > for ERM to ease testing? > > > > Here’s my first look (in a very long time): > > 1. Go to > http://localhost:8081/cgi-bin/koha/admin/preferences.pl?tab=erm > 2. Change “ERMModule” to “Enable” > 3. Go to http://localhost:8081/cgi-bin/koha/erm/erm.pl > > > > I note the following warning in the console: > > > > runtime-core.esm-bundler.js:167 [Vue warn]: setup() return property > "_is_loading" should not start with "$" or "_" which are reserved prefixes > for Vue internals. > > at

> > > > -- > > > > In a separate email, I’ve asked what I should be looking for in terms of > QA. Or are we still at a stage of looking for feedback? > > > > Personally, I think that we might still be a bit too ERM focused with the > Vue.js. > > > > Instead of http://localhost:8081/cgi-bin/koha/erm/erm.pl perhaps we > should be going to http://localhost:8081/cgi-bin/koha/spa/erm. Note that > “spa” is a placeholder here (in this case standing for single page > application). Off the top of my head, I don’t have a great base URL in > mind. > > > > That way “Koha” is the Vue.js app, and “ERM” is a component provided to > “Koha”. We could centralize a number of methods in the root “Koha” app. > > > > Actually, me emailing is probably pointless. Maybe one night I can do some > work in the evening, so that I can link up with folk and we can chat more… > > > > David Cook > > Senior 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 uwe.dierolf at kit.edu Wed Feb 22 08:31:17 2023 From: uwe.dierolf at kit.edu (Uwe Dierolf) Date: Wed, 22 Feb 2023 08:31:17 +0100 Subject: [Koha-devel] ChatGPT and Koha In-Reply-To: <4f8809b7-6b79-ccea-0d01-a3d31a5cd127@dataly.gr> References: <032a01d94658$19686a40$4c393ec0$@prosentient.com.au> <4f8809b7-6b79-ccea-0d01-a3d31a5cd127@dataly.gr> Message-ID: Hi all, yes, ChatGPT is awesome. I asked ChatGPT to write a Koha plugin that places some javascript code into pages of the staff frontend. The code was as expected as far as I can say this, cause I never developed a Koha plugin but it was pretty similar to the code which you can find in the KitchenSink plugin. Then I asked the Bot to activate the javascript only on specific pages having a specific page id. Looked also very convincing. Last but not least I wanted to know how to create the kpz file and got an answer too. Perhaps ChatGPT can produce the code for the vue.js based frontend. Or perhaps copilot already can do this ;-) Best regards, Uwe -------------------------------------------------------------------------- Uwe Dierolf Karlsruher Institut für Technologie (KIT) KIT-Bibliothek -------------------------------------------------------------------------- Am Wed, Feb 22, 2023 at 08:45:47AM +0200 schrieb Andreas Roussos: > Hi David, > > FWIW, a couple of weeks ago I copied and pasted two snippets of Perl code from Koha because I couldn't understand what type of variable they were generating. ChatGPT came back with a pretty comprehensive answer about hash references. > > What impressed me (apart from the quality of its reply) was that I copied/pasted the code in a hurry including the line numbers preceding each line, however that did not seem to confuse ChatGPT at all! > > Kind regards, > > Andreas > > On 2023-02-22 02:53, David Cook wrote: > > > Hi all, > > > > Like many around the world, I may have been bitten by the ChatGPT bug… > > > > Most of my ChatGPT questions have been more general in nature, but I figured I’d ask it about Koha, as there is a lot of public information, but it’s still a niche topic. > > > > I asked it to generate me a Koha plugin, and it refused for a while, but eventually I was able to convince it to try. The result wouldn’t even compile, but it got a lot of things right. In other conversations, it’s made mistakes but always done a good job of fixing its mistakes. > > > > Has anyone else played with ChatGPT and Koha or ChatGPT in general (on IT topics)? > > > > David Cook > > Senior 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/ > > _______________________________________________ > 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 Wed Feb 22 09:25:14 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 22 Feb 2023 09:25:14 +0100 Subject: [Koha-devel] ChatGPT and Koha In-Reply-To: <032a01d94658$19686a40$4c393ec0$@prosentient.com.au> References: <032a01d94658$19686a40$4c393ec0$@prosentient.com.au> Message-ID: For Koha core developers I am not sure it is relevant. Hasn't ChatGPT been fed with 2 years old data? With data we actually wrote ourselves. So basically if I ask it something I am requesting what my 2 year-ago self knew? I have certainly forgotten some stuff, but I also know that what was true 2 years ago is no longer 100% correct. By the way, what would be the license for such generated code? Certainly GPLv3 for Koha, but what about Vue.js code for instance? Le mer. 22 févr. 2023 à 01:53, David Cook a écrit : > Hi all, > > > > Like many around the world, I may have been bitten by the ChatGPT bug… > > > > Most of my ChatGPT questions have been more general in nature, but I > figured I’d ask it about Koha, as there is a lot of public information, but > it’s still a niche topic. > > > > I asked it to generate me a Koha plugin, and it refused for a while, but > eventually I was able to convince it to try. The result wouldn’t even > compile, but it got a lot of things right. In other conversations, it’s > made mistakes but always done a good job of fixing its mistakes. > > > > Has anyone else played with ChatGPT and Koha or ChatGPT in general (on IT > topics)? > > > > David Cook > > Senior 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at davidschmidt.at Wed Feb 22 10:51:01 2023 From: mail at davidschmidt.at (David Schmidt) Date: Wed, 22 Feb 2023 10:51:01 +0100 Subject: [Koha-devel] koha-testing-docker startup gotcha... In-Reply-To: <035601d94682$7ddabbc0$79903340$@prosentient.com.au> References: <035601d94682$7ddabbc0$79903340$@prosentient.com.au> Message-ID: <300ea59e-ba65-4434-82d7-6f2e5abc2483@app.fastmail.com> what I like to do to always have matching UIDs ########## ########## # Dockerfile ARG CONTAINER_UID=1000 RUN useradd --create-home --home-dir /home/hks3 \ --uid $CONTAINER_UID --user-group --shell /bin/bash hks3 # building container docker-compose build --build-arg CONTAINER_UID=`id -u` ########## ########## now the ids always match. cheers david (HKS3 / koha-support.eu) On Wed, 22 Feb 2023, at 6:57 AM, David Cook wrote: > Hi all, > > With the latest version of koha-testing-docker, you might have problems getting it to start up if your “koha” git directory is not owned by UID 1000. > > I use koha-testing-docker on Windows, so I use a named volume to mount my “koha” git directory. It also means that I cloned that git repo and do my checkouts with the “root” user in koha-testing-docker (not as my normal user on a Docker host like you would do if you were using Linux as your workstation). So “root” owns my “koha” git directory, which causes koha-testing-docker to fail to startup. > > I’ve worked around that by chowning my “koha” git repo to be owned by UID 1000, and that’s got it starting up, but it could have future issues where permissions aren’t quite right. > > Anyway, just something to be aware of… > > David Cook > Senior 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Wed Feb 22 15:07:38 2023 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 22 Feb 2023 11:07:38 -0300 Subject: [Koha-devel] Pull newer images today :-D Message-ID: Hi, we've just pushed a change to Koha, moving away from node-sass to dart-sass, and older docker images will fail as all assets are automatically built on startup and it will fail otherwise. Best regards -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From victor at tuxayo.net Wed Feb 22 23:25:07 2023 From: victor at tuxayo.net (tuxayo) Date: Wed, 22 Feb 2023 23:25:07 +0100 Subject: [Koha-devel] Volunteer needed to open the bidding for KohaCon24 & need confirmation of task list Message-ID: <8d2adb4d-b487-f887-46eb-98cfe8b374e5@tuxayo.net> Hi :) The things to do are: - making the wikipage using the template - make an announcement email using past ones - send reminders - @all: anything else? The aim is to start the bid in the next weeks so proposals that start early 2024 have time to plan. And let the bid run until the next general meeting in april I can help with proofreading and finding past resources. (wikipage template, emails) Cheers, -- tuxayo From dcook at prosentient.com.au Thu Feb 23 00:56:45 2023 From: dcook at prosentient.com.au (David Cook) Date: Thu, 23 Feb 2023 10:56:45 +1100 Subject: [Koha-devel] ChatGPT and Koha In-Reply-To: References: <032a01d94658$19686a40$4c393ec0$@prosentient.com.au> Message-ID: <046201d94719$5a023970$0e06ac50$@prosentient.com.au> I understand what you’re saying because it says its knowledge after 2021 is limited, but it also has a greater breadth of knowledge than your 2 year-ago self. It claimed that some of its Vue.js answers were due to the conventions used by the Vue.js community, which was fascinating. It differed from some examples I found online in Vue.js documentation, so it would be interesting to know if the AI was out of date or if the documentation was out of date. Considering the explanation it gave for its answer, I think the documentation was probably out of date, as it gave a better answer than the documentation. (I found ChatGPT was able to answer my Vue.js questions much better than the official Vue.js documentation and most of the examples I could find online.) I asked it to explain some general best practices for processing background tasks and distributed computing and it gave some excellent answers (and follow-up answers to follow-up questions). It certainly offers a better understanding of those topics than any Koha community developer has. I told it that its not particularly skilled at very specific tasks (like writing a Koha plugin), but it’s very good with fundamentals, and it mentioned that explaining fundamentals is one of its primary goals. It’s not there to write your code for you, but to offer advice/guidance to help you write code better. That said, it’s not always 100% correct either. You do have to consider its answers critically, and sometimes it’s just plain wrong, although usually its wrong in terms of minor details, and if you point out its mistake, it gets the correct answer. I was quizzing it on the use of some Perl POE modules from CPAN and there were times it tried to pass options that just didn’t exist (and have never existed). But its corrections were accurate and followed the concurrent programming designs I used myself years ago with those modules. On the other hand, I had it design a recursive algorithm in PHP for filtering data, and while its first attempts were close, the more I tried to get it to fix it, the worse it got until it was absolutely unusable. Perhaps the problem was the AI or perhaps the problem was with my instructions. I just asked it to do an algorithm for converting ISBN-13 to ISBN-10 in Javascript. I already wrote one myself a few days ago, and it’s interesting to compare. Its algorithm is probably 98% correct, and it wrote it more concisely than I did (although we know I love verbosity). Licensing is certainly a tough topic (consider the licensing problems with GitHub Copilot). According to a post online, it claims not to have a licence on its code, but advises checking with legal professionals to be on the safe side. However, I don’t think a person would really be using the code generated by ChatGPT. The code it generates tends to be example code. The kind of thing you’d find in documentation, tutorials, Stackoverflow, etc. It’s good for illustrating concepts, but you wouldn’t necessarily want to copy/paste it, and just use it. It probably wouldn’t help a person to write “Koha code”, but it could help a person to better understand a concept they need to know while writing “Koha code”. Another example… I just asked “could you generate a functional operating system from scratch?” It said that it could not, but outlined what a person would need to do in order to write one, and gives some good warnings about why it’s probably not a good idea to try to do it solo haha. I know this email is too long, but I suppose I’d just emphasize that it’s a very interesting “helper”. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Jonathan Druart Sent: Wednesday, 22 February 2023 7:24 PM To: David Cook Cc: koha-devel Subject: Re: [Koha-devel] ChatGPT and Koha For Koha core developers I am not sure it is relevant. Hasn't ChatGPT been fed with 2 years old data? With data we actually wrote ourselves. So basically if I ask it something I am requesting what my 2 year-ago self knew? I have certainly forgotten some stuff, but I also know that what was true 2 years ago is no longer 100% correct. By the way, what would be the license for such generated code? Certainly GPLv3 for Koha, but what about Vue.js code for instance? Le mer. 22 févr. 2023 à 01:53, David Cook > a écrit : Hi all, Like many around the world, I may have been bitten by the ChatGPT bug… Most of my ChatGPT questions have been more general in nature, but I figured I’d ask it about Koha, as there is a lot of public information, but it’s still a niche topic. I asked it to generate me a Koha plugin, and it refused for a while, but eventually I was able to convince it to try. The result wouldn’t even compile, but it got a lot of things right. In other conversations, it’s made mistakes but always done a good job of fixing its mistakes. Has anyone else played with ChatGPT and Koha or ChatGPT in general (on IT topics)? David Cook Senior 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Thu Feb 23 14:15:36 2023 From: julian.maurice at biblibre.com (Julian Maurice) Date: Thu, 23 Feb 2023 14:15:36 +0100 Subject: [Koha-devel] Random data in CGI Vars Message-ID: Hello, I've been encountering strange bugs on two different Koha instances (both 21.11). When cataloguing new records, instead of the record being saved, users are being redirected to an empty cataloguing form (like if they clicked on "New record"). They have to use "Back" and submit the form again until it works. I suspected something going wrong in how the form data was being sent to Koha so I added the following line in cataloguing/addbiblio.pl warn Data::Dumper->Dump([{ $input->Vars }], ['Vars']) . "\n"; right after CGI->new And indeed there is something going wrong. Some of the variables are replaced by random data. Here's an example: 'tag_041_subfield_a_452653_624274' => '', '' => "Ly[\x{1cf}^KJ{)Z\x{fffd}(-D<\x{fffd}\x{fffd}\x{fffd}BN", 'tag_856_code_x_883542_376496' => 'x', Sometimes the 'op' parameter is replaced by random data, and that's why we see this strange behaviour. Have you ever experienced something like this ? Do you know where it could come from ? -- Julian Maurice BibLibre From martin.renvoize at ptfs-europe.com Thu Feb 23 19:02:52 2023 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Thu, 23 Feb 2023 18:02:52 +0000 Subject: [Koha-devel] Koha 22.11.03 release Message-ID: Hello, Bonjour, Ola, Kia ora, 今日は, The Koha community is pleased to announce the release of version 22.11.03. This release is a bugfix/maintenance release with a small number of minor architectural enhancements to aid in the continued maintenance of this version. It includes 40 enhancements and 87 bugfixes. For full release notes, please visit https://koha-community.org/koha-22-11-03-released/ Thanks for anybody involved! 🚀 Martin Renvoize, MPhys (Hons) Head of Development and Community Engagement E: martin.renvoize at ptfs-europe.com P: +44 (0) 1483 378728 M: +44 (0) 7725 985636 www.ptfs-europe.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From trmurakami at gmail.com Fri Feb 24 02:39:16 2023 From: trmurakami at gmail.com (Tiago Murakami) Date: Thu, 23 Feb 2023 22:39:16 -0300 Subject: [Koha-devel] Permissions on Pootle In-Reply-To: <48d83df8-ff3d-7603-033d-425335994b9b@web.de> References: <48d83df8-ff3d-7603-033d-425335994b9b@web.de> Message-ID: Hi Katrin and Koha-Devel community, I've translated many strings in the last few days, but when I download the files, they don't have the newly translated strings. Please let me know how often Pootle export files are generated. Thank you in advance, Tiago Murakami On Mon, Feb 13, 2023 at 4:24 PM Katrin Fischer wrote: > Hi Tiago, > > we had a change/correction to the permission system a while ago. I have > made you part of the pt-BR translation team now. You should be able to > submit translations. > > Katrin > On 13.02.23 19:24, Tiago Murakami wrote: > > Hi, > > I´m a librarian in Brazil. I had Pootle permissions for translation, but, > I only have them for suggestions. What is the best way to ask for > permission to translate Pootle in pt-BR? > > Thanks in advance, > > -- > Tiago Murakami > > _______________________________________________ > Koha-devel mailing listKoha-devel at lists.koha-community.orghttps://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/ > -- Tiago Murakami -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohanews at gmail.com Mon Feb 27 18:59:59 2023 From: kohanews at gmail.com (Koha Newsletter) Date: Mon, 27 Feb 2023 18:59:59 +0100 Subject: [Koha-devel] Koha Community Newsletter: February 2023 Message-ID: The Koha Community Newsletter for February 2023 is here: https://koha-community.org/koha-community-newsletter-february-2023/ Many thanks to everyone who submitted articles and news to this 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: