We want to know which requests to protect (ie. Requiring a csrf token):
those having a op starting with cud-
Otherwise you could GET something that should be POSTed.
I've tried to describe this change as best as I could on the wiki, please
adjust if it's not clear enough.
Hi Paul,
I've adjusted the description of the event.
Cheers,
Jonathan
Le lun. 4 mars 2024 à 15:26, Paul Poulain via Koha-devel
a écrit :
>
> Hello all,
>
> I don't know who to ask, so asking widely, sorry.
> The hackfest announcement on https://koha-community.org/calendar/ is correct.
>
Seen it for the first time right now.
It is inside "cas_ticket" and it contains the columns for Koha::Patrons
Seems related to bug 34893
Le mar. 13 févr. 2024 à 01:36, David Cook via Koha-devel <
koha-devel@lists.koha-community.org> a écrit :
> Hi all,
>
>
>
> The last two days I’ve noticed that
Hi Emmi,
Search for "No job found" in the worker logs. Do you have jobs (in DB
table background_jobs) stuck in "new" (with
type="update_elastic_index")?
If so, search in the data column for your biblionumbers.
See also bug 35819.
Regards,
Jonathan
Le lun. 29 janv. 2024 à 13:32, Emmi Takkinen
The problem should be fixed for live packages.
Le mer. 24 janv. 2024 à 06:59, David Cook via Koha-devel
a écrit :
>
> I help out a few libraries running 22.11 straight from the community, and two
> libraries lately have had Koha go down during automatic upgrades to
> 22.11.12-1.
>
>
>
>
Please report it.
There is another one, related:
https://gitlab.com/koha-community/koha-l10n/-/issues/1
Yours should be reported on bugzilla I'd say.
Le mer. 24 janv. 2024 à 06:59, David Cook via Koha-devel
a écrit :
>
> I help out a few libraries running 22.11 straight from the community, and
Hello,
The translation server has been migrated from Pootle to Weblate.
It's a whole new server with a complete new workflow.
The goal was to have it ready to translate 23.11, but everything is not set
up yet (downtimes may appear).
You can login with your Pootle credentials, and you should have
t; El mar, 7 nov 2023 a las 17:22, Jonathan Druart via Koha-devel (<
koha-devel@lists.koha-community.org>) escribió:
>>
>> Hi,
>> I am suggesting removing the tarball from our release process. I don't
think anybody is using it anyway.
>> It's extra work for RMaints,
You missed the original request, Victor. The .po files will be missing from
the src and so the git extract won't be enough.
I think we better need to have a job triggered on tags pushed that will
build and push the .tar.gz files.
Le ven. 10 nov. 2023 à 04:52, Victor Grousset/tuxayo via
Hi,
I am suggesting removing the tarball from our release process. I don't
think anybody is using it anyway.
It's extra work for RMaints, and it does not seem necessary.
I am going to suggest removing the po files from the Koha src code starting
from November releases, and that will require yet
About ktd you need to include one of the ES/OS compose files (
docker-compose.es* docker-compose.os*), there are bin/ktd switches.
You also need KOHA_ELASTICSEARCH set to "yes" in the .env file.
Le mar. 7 nov. 2023 à 03:55, David Cook via Koha-devel <
koha-devel@lists.koha-community.org> a écrit
:D
>
>
>
> 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
Because of 26170, I left a comment there.
Le ven. 3 nov. 2023 à 13:49, Tomas Cohen Arazi via Koha-devel
a écrit :
>
> Hi all, this is master's latest failures:
>
> https://jenkins.koha-community.org/job/Koha_Master/lastCompletedBuild/testReport/
>
> The selenium failure has been there for a
David, if you don't know Jenkins and you are part of the QA team, I guess
you are not alone to be lost with our CI structure and it means we have a
big problem. Either motivation, or tools or communication.
I am not answering you now but maybe we need to document a bit better how
it works for the
Some ideas:
1. You could hack the worker to process all queues, then you could have
only one worker (?)
2. Stop the worker, modify Koha::BackgroundJob->enqueue to call ->process
(not with $self, you will need to refetch the job)
3. You can remove the "use" statements from plack.psgi to reduce
It's enabled, so the problem is not coming from there.
Le lun. 23 oct. 2023 à 04:59, David Cook via Koha-devel <
koha-devel@lists.koha-community.org> a écrit :
> Hi all,
>
>
>
> It looks like my “bugmail has been disabled” for the last 10 days on
> Bugzilla, so if I haven’t responded to a
tSet=HASH(0x55b81f9d6b68),
> 12) called at /kohadevbox/koha/Koha/Objects.pm line 96
>
> Koha::Objects::find("Koha::BackgroundJobs", 12) called at
> /kohadevbox/koha/misc/background_jobs_worker.pl line 132
>
>
>
> David Cook
>
> Senior Software Engine
this case probably an alias should be created for ‘docker
> volume rm koha_db-data’ to easily delete the volume if necessary…
>
>
>
> Wouldn’t it be a possibility?
>
>
>
> Best greetings,
>
>
>
> Janusz
>
>
>
> *From:* Jonathan Druart
> *Sent:* Mon
Is this only broken on the sandboxes? What about ktd?
I've tried the plugin (for the first time, in ktd), and the configuration
page is full of JS errors. Also I don't manage to create a carousel (it's
always saying "No carrousels have been configured").
It seems that you are not using
If you have trouble with yarn/node/cypress, always start with deleting your
local node_modules (ie. the one in $SYNC_REPO)
Le ven. 8 sept. 2023 à 15:17, Nick Clemens a
écrit :
> A ktd pull didn't resolve issues for me, I followed Martin's suggestion
> and cleared out my node_modules directory
Use the non-translated interface or update the French templates (from the
admin of the sandboxes, under the actions menu)
Le jeudi 31 août 2023, Philippe Blouin a
écrit :
> Hi!
>
> Any suggestion onto why our plugin doesn't seem to work on (bywater's)
Devboxes while being perfectly fine in
JS manuals and see if I can do something to extend the code (JS isn't my
> favourite language and I've probably not written any for about 15 years).
>
> Is my supposition about where it would go in the MARC record correct?
>
> Thanks
>
> Nigel
>
> On 21/07/2023 12:29, Jo
Looks like it's only using the ISBN. The code is in
koha-tmpl/opac-tmpl/bootstrap/js/openlibrary.js
https://gitlab.com/koha-community/Koha/-/blob/master/koha-tmpl/opac-tmpl/bootstrap/js/openlibrary.js#L19
and opac-results:
899 [% IF OpenLibraryCovers
How did you modify .env?
Keep those as it:
KOHA_INSTANCE=kohadev
KOHA_CONF=/etc/koha/sites/kohadev/koha-conf.xml
Le jeu. 20 juil. 2023 à 07:19, Waylon Robertson
a écrit :
>
> after doing ktd up, after configuring the database info etc in .env, I am
> getting
> koha-koha-1 | Running
>
Have a look at bug 25548 maybe?
It has been backported but maybe your apache config is not correct (see the
RewriteRule)?
Le jeu. 8 juin 2023 à 18:03, Philippe Blouin
a écrit :
> Hi David,
>
> Yes, connection being the login page. Any call to it with =&
> will get see its empty variable get
Hi Kyle,
It should work if you mount it in /intranet/metrics and access it using
/cgi-bin/koha/metrics
Cheers,
Jonathan
Le mar. 30 mai 2023 à 18:36, Kyle Hall a écrit :
> Hey yinz, I’m trying to add some Prometheus metrics to Koha. This looks
> like it has what we want:
>
Hello,
An info that you should spread to your Koha friends: koha-howto has
been embedded into koha-testing-docker. Which means that it is
available at http://localhost:8081/cgi-bin/koha/how-to.pl when your
Koha container is started.
Koha-howto [1] is a friendly tool for newcomers, it asks them
Hi David,
I have not investigated how we could split and reuse Vue components
from Koha plugins.
But Paul Derscheid told me webpack is legacy and we should move to
Vite or Turbopack instead.
Cheers,
Jonathan
Le mar. 21 mars 2023 à 05:03, David Cook a écrit :
>
> Hey Jonathan,
>
>
>
> Do you
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
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
>
ent 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
but I thought you might find that interesting.
>
>
>
> David Cook
>
> Senior Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 80
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.
02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> *From:* Koha-devel *On
> Behalf Of *Jonathan Druart
> *Sent:* Thursday, 16 February 2023 12:10 AM
> *To:* koha-devel
> *Subject:* [Koha-devel] Vue improvements/refactorings
>
>
>
> Hi,
>
>
>
> Pedro and
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:
Hi,
We have a pre-commit hook in the wiki but people forget to install it. And
it was not easy to update and propagate the changes. We decided to embed it
in koha-testing-docker and install it automatically.
So if you see a message telling you your commit is missing something, don't
ignore it ;)
las 6:08, Jonathan Druart (<
> jonathan.dru...@bugs.koha-community.org>) escribió:
>
>> See https://codeberg.org/forgejo/forgejo and
>> https://forgejo.org/2022-12-15-hello-forgejo/
>> "To this end we are very proud that Codeberg e.V. has decided to become
>&
See https://codeberg.org/forgejo/forgejo and
https://forgejo.org/2022-12-15-hello-forgejo/
"To this end we are very proud that Codeberg e.V. has decided to become our
project’s custodian."
Le mer. 1 févr. 2023 à 09:44, Marc Véron a écrit :
> Hi everybody
> Why not https://codeberg.org/ ?
>
Some updates: https://forgejo.org/2023-01-31-monthly-update/
I think Victor's email is missing questions: what do we do?
If we decide to migrate to forgejo, when?
Le mer. 25 janv. 2023 à 03:45, Victor Grousset/tuxayo a
écrit :
> Hi :)
>
> Thanks David Nind for sharing this info on the last dev
> to assign the superlibrarian permission to a service account "just to get it
> working"
Looks like the equivalent of `sudo chmod -R 777 *` ;)
Le mer. 4 janv. 2023 à 16:11, Galen Charlton a écrit :
>
> Hi,
>
> On Tue, Jan 3, 2023 at 7:58 PM David Cook wrote:
> > It seems to me that we
We are not giving up, we never really tried.
It could stay a long term goal, waiting for someone to work on it.
I don't think we should start again adding MySQLisms.
Le mar. 6 déc. 2022 à 02:49, David Cook a écrit :
> Hi all,
>
>
>
> Should we formally give up on trying to provide PostgreSQL
nk no one wants to be the person that refuse a patch because a
> comment is misaligned, so if that kind of thing is not automated, "not
> good enough code" will continue to be pushed.
>
>
> Le 05/12/2022 à 14:55, Jonathan Druart a écrit :
> > I don't think we
dy pushed into our codebase
> somehow ?
>
> -Original Message-
> From: Koha-devel On Behalf Of
> Jonathan Druart
> Sent: Monday, December 5, 2022 2:56 PM
> To: koha-devel
> Subject: Re: [Koha-devel] Good enough?
>
> Existing hooks can be found at
> http
Existing hooks can be found at
https://wiki.koha-community.org/wiki/Tips_and_tricks#Hooks
Le lun. 5 déc. 2022 à 11:34, Marcel de Rooy a écrit :
>
> Could you provide more info on those git hooks? A wiki URL?
>
> Marcel
>
> -Original Message-
> From: Koha-devel On
roke something. It also makes writing new tests more difficult
> than it should.
>
> If I wanted to improve Koha developer experience, I would start with that.
>
> My 2 cents.
>
> Le 02/12/2022 à 15:42, Jonathan Druart a écrit :
> > Hi devs,
> >
> > I was wonder
Hi devs,
I was wondering... How good is your "good enough"?
It's a question I often ask myself, when writing patches or QAing
yours: is it good enough to be into Koha? It does not have to be
perfect or it may never reach master, but it must meet certain
standards.
When I was RM I tried to put
[resending, my previous reply didn't reach the list]
release_tools is the place I guess.
https://gitlab.com/koha-community/release-tools
But, I run it on master:
sed: -e expression #1, char 1: unknown command: `-'
sed: -e expression #1, char 1: unknown command: `-'
% more translate-errors
t; We might not have remorse in trying to scam a publicly traded company
> but we should be aware among ourselves that's the plan.
>
>
> On 22-05-26 12:39, Jonathan Druart wrote:
> > There is a checkbox on the form
> > That's the only reason I haven't filled in the form already,
Hi devs,
[I sent this on Aug 26th 2021 but it never reached the list!]
You may have seen the following warning when signing off on patches
using the git alias
"""
WARNING: git-filter-branch has a glut of gotchas generating mangled
history
rewrites. Hit Ctrl-C before proceeding to
r 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: Thursday, 26 May 2022 8:33 AM
> To: Tomas Cohen
I had a look at it a couple of months ago but at some point you have to
"certify that project maintainer are not seeking profit from this project
by, for example, selling services"...
Le mer. 25 mai 2022 à 17:51, Tomas Cohen Arazi a
écrit :
> Hi, we need to take a look at the upcoming changes
Yes, good idea. Write the patch! :D
Le lun. 9 mai 2022 à 04:18, a écrit :
>
> Hi all,
>
>
>
> A librarian pointed out to me that the table in the OPAC cart is not
> responsive (ie the table flows off the edge of the screen).
>
>
>
> I took a little look online and it looks like DataTables does
Hi devs,
Could we vote at the next dev meeting that the ERM module will be
written in Vue3 and that it will not be a problem for its integration
into Koha?
This module will contain a lot of CRUD operations and simple forms.
And so all the necessary REST API routes will be provided from the
Try /var/log/koha/$KOHA_INSTANCE/plack-error.log
Or, watch them all with /var/log/koha/$KOHA_INSTANCE/*.log
Le jeu. 24 mars 2022 à 09:21, Londhe Amar a écrit :
>
> Hello,
>
> Thanks for quick response.
>
> I have tried all sorts of ways to identify the problem.
>
> 1) Tried to clear browser
> Nice to hear that. How was coding UI tests compared to Selenium?
It's easier to write and easier to debug (given the screenshot and the
ability to inspect the DOM after each test).
> And the API tests compared to the current way?
Please have a look at the patch, or at least the very succinct
ior 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
> Jonathan Druart
> Sent: Thursday,
Hi devs,
Following my previous email here, I have started to work on the ERM
project and wanted to try Vue in a more complex example.
You can find the whole tree at https://gitlab.com/joubu/Koha/-/commits/erm
It contains CRUD operations for ERM's agreement (can link users and
periods), all
'Authorization': 'Bearer' +access_token
Add a space after "Bearer"
'Authorization': 'Bearer ' +access_token
Le mar. 15 mars 2022 à 17:10, Esharat Mia a écrit :
>
>
> Dear All,
>
> Here is my python code for testing REST API -
>
> import requests
> import json
> data = {
> "client_id":
Hi devs,
I wanted to let you know that I played a bit with React the last couple of
days and I published my work on
Bug 30160 - Rewrite cities admin view in React
If you have some experience with React I would like to get your opinion on
this code.
Feel free to test the patch and catch bugs if
Hi devs,
If you are using koha-testing-docker and you write patches, you certainly
also use the koha-qa.pl script (alias `qa`).
That may cause you permission problems.
There is a workaround I explained on
https://gitlab.com/koha-community/qa-test-tools/-/issues/57
Cheers,
Jonathan
Can we make propositions or submit ideas? I'd like a dark theme :-)
Le mer. 19 janv. 2022 à 18:52, Owen Leonard a écrit :
> As Paul announced in December
> (
> https://lists.koha-community.org/pipermail/koha-devel/2021-December/046841.html
> )
> Biblibre is sponsoring a refresh of the staff
use C4::Output qw( output_with_http_headers )
will fix it. See also the "Other" section of the tech release note from
21.11 (related to bug 17600)
https://koha-community.org/koha-21-11-released/
Le mer. 12 janv. 2022 à 17:17, Michael Kuhn a écrit :
> Hi
>
> Our library uses a non-Koha Perl
>
> 1. misc4dev, I don't really have a boat in the race here.. I don't
> personally use it directly in any way and I'm not close enough to it to
> know what knock on effects it would have to help my workflows.
>
It's used by koha-testing-docker, so you are using misc4dev daily. For
instance the
Hello everybody,
I have been listing some tasks I would like to work on during the next
development cycle.
I suggest a give and take approach. Help me on one or more of those
topics and I will help you as I can on whichever topic(s) you decide.
1. Add more sample data to misc4dev
It can be
Are you seeing this in koha-testing-docker?
Le mar. 16 nov. 2021 à 14:11, Marcel de Rooy a écrit :
>
> Hi all,
>
> Nobody seeing things like this?
>
> mkdir: cannot create directory ‘/var/run/rabbitmq’: Permission denied
> Failed to create directory: /var/run/rabbitmq
>
Hi,
I've started to list the technical stuffs to highlight in the release
notes of 21.11
https://annuel.framapad.org/p/koha_21.11_tech_release_notes
Feel free to add descriptions when needed or add your own topics there.
Cheers,
Jonathan
___
Hey, the Koha deveppers core team is willing to show and explain anything
you want.
Don't you have some specific needs or questions? :)
Le ven. 15 oct. 2021 à 09:01, Renvoize, Martin <
martin.renvo...@ptfs-europe.com> a écrit :
> Hi all,
>
> We're looking to organise another Koha advent
print "NO lost card\n";
> }
>
> Stephen
>
> -----Original Message-
> From: Stephen Graham
> Sent: 18 October 2021 14:04
> To: Jonathan Druart
> Cc: koha-devel
> Subject: RE: [Koha-devel] Changing the lost card value
>
> Thanks Jonathan. I understa
Hi Stephen,
You can use
Koha::Patrons->find(42)->lost(0)->store;
to set borrowers.lost to 0 for patron with borrowernumber=42.
Cheers,
Jonathan
Le lun. 18 oct. 2021 à 12:47, Stephen Graham a écrit :
>
> Sorry if this is a basic question. I’ve searched through the Koha::Patron and
>
Thanks for your reply, Kyle!
(And sorry for my delayed answer, your message hit the spam folder!?)
Inline replies below.
Le jeu. 7 oct. 2021 à 13:15, Kyle Hall a écrit :
>>
>> 1. LTS
>> I think it's time to have a Long Term Support release. We noticed that
>> some people are still using very
The election of the 22.05 team will take place during the next general
IRC meeting, on Wednesday October 20th 2021, 14:00 UTC.
https://wiki.koha-community.org/wiki/General_IRC_meeting_20_October_2021
There is still plenty of room available!
Le mer. 29 sept. 2021 à 17:12, Jonathan Druart
Hello devs,
As you must know we had two hard months, several very bad bugs hit us.
The release team had to coordinate and it was not an easy task.
We noticed some flaws in the workflow and I would like to suggest some
improvements to discuss.
The main problematic issue is to backport patch
Hi Victor,
Yes, assign a class or id to the element.
This is done several times in basic_workflow.t
Cheers,
Jonathan
Le jeu. 30 sept. 2021 à 00:25, Victor Grousset/tuxayo
a écrit :
>
> Hi :)
>
> I'm writing an UI test for creating a club to later use it for holds.
> In the page
Hello everybody,
The roles for the 22.05 release cycle are now opened.
The vote will take place during one of the dev meetings in October.
https://wiki.koha-community.org/wiki/Roles_for_22.05
The description of the roles can be found at this wiki page
Hello everybody,
I am announcing, on behalf of the whole Koha release team,
synchronised releases for the four release versions we are currently
supporting.
The release notes are available below:
21.05.04 -
https://koha-community.org/koha-21-05-04-released-%e2%9a%a0-security-release/
20.11.10 -
Hello everybody,
Don't ignore this email!
Last week a critical security bug was reported on our bug tracker. We
fixed it and built debian packages for the four stable releases we
currently support.
The security flaw can cause a privilege escalation from OPAC users. It
can be highly damaging,
admin/cities.pl and /api/v1/cities ?
Same for branches/libraries
Le ven. 3 sept. 2021 à 08:26, a écrit :
> Hi all,
>
>
>
> Do we have any examples of using the Mojolicious REST API to provide data
> for DataTables in Koha?
>
>
>
> I think the answer is probably no since the DataTables calls
Keep it simple, why not the following?
my $canbe = CanItemBeReserved( $patron->borrowernumber, $itemnumber );
is_deeply(
[$canbe->{status}, $canbe->{limit}]
['tooManyReservesToday', 0],
'Patron cannot reserve if holds_per_day is 0 (i.e. 0 is 0)'
);
Le sam. 28 août 2021 à 09:38,
Indeed, it's coming from
commit 8ea80995c590dad86c43df636456640d3aa84bab
Increment version for 21.05.03 release
-$VERSION = "21.05.02.002";
+$VERSION = "21.05.02.003";
Le jeu. 26 août 2021 à 15:50, Michael Kuhn a écrit :
>
> Hi
>
> Yesterday/today I was installing the most current Koha:
>
Hi devs,
Bug 25078 was pushed yesterday and it modifies how we deal with our upgrade
process.
I adjusted the wiki page -
https://wiki.koha-community.org/wiki/Database_updates
The different things to know about it:
* The skeleton for atomic updates is modified [1]
* On push the atomic updates
It may break plugins using modules that were using EXPORT and now EXPORT_OK
Le mer. 11 août 2021 à 01:04, Fridolin SOMERS
a écrit :
> Hi,
>
> Do we need to impact Koha plugins ?
>
> Best regards,
>
> Le 15/07/2021 à 21:02, Jonathan Druart a écrit :
> > Hi,
> >
Hello Michael,
Can you try the `koha-translate --install de-DE` command with the
--verbose flag?
What's the output?
Is "/usr/share/koha/opac/htdocs/opac-tmpl/prog/en/" a directory? It's
missing "bootstrap", it must be
"/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/"
Le lun. 12 juil. 2021 à
Hi,
I've just pushed bug 17600, it's a massive patch (1311 files changed,
4077 insertions(+), 4362 deletions(-)) that will cause conflicts with
a lot of other patches in the queue.
I've described in the commit message what it is doing, please read it.
Most of the time the changes it brings are
Yes
Le ven. 25 juin 2021 à 17:34, Victor Grousset/tuxayo a
écrit :
> On 21-06-24 15:57, Jonathan Druart wrote:
> > I've just pushed bug 28489 that is adding a new "lib" directory.
>
> Isn't it this one instead ? Bug 28519 - Add a 2nd directory for Perl
>
I've answered on the bug report. It's a valid error.
Le lun. 21 juin 2021 à 15:37, Marcel de Rooy a écrit :
>
> Hi all,
>
> I am looking at bug 27944 and see the following qa warn:
>
> FAIL koha-tmpl/intranet-tmpl/prog/en/modules/circ/request-article.tt
>OK filters
>OK
(This is a message from last week that didn't reach the list)
Hi,
I've just pushed bug 28489 that is adding a new "lib" directory. It
needs to be added to the apache config, and new koha-testing-docker
images have been published.
The error:
couldn't load CGI::Session::Serialize::yamlxs: Can't
> Until now it worked fine, but after a koha upgrade in 20.11.x, it is stuck
> with the status disabled and it won't activate.
Just a guess: is the is_enable code correct?
https://github.com/DSI-Universite-Rennes2/koha-plugin-warehouse-request/blob/master/Koha/Plugin/Fr/UnivRennes2/WRM.pm#L310
Hi Thomas,
I've sent the following notes to the QA team, but maybe it needed to be public.
The history behind 28519 is not trivial :)
"""
To clarify and explain a bit more what we are doing here (to those
outside of the loop):
- We switched from YAML[::Syck] to YAML::XS (22824, 27673)
- We had
Hi devs,
I'd like to see us focus on those bugs, good candidates for early push:
Bug 17600 - Standardize the EXPORT
Bug 27526 - Remove Mod/AddItemFromMarc from additem.pl (first step,
more work needed in this area)
Bug 17427 - Replace CGI::Session with Data::Session
Bug 25078 - Update DB process
Hello Stefano,
This idea has been discussed on bug 16881.
It's also indirectly related to bug 27467.
Cheers,
Jonathan
Le mar. 8 juin 2021 à 14:21, Stefano Bargioni a écrit :
>
> Hi,
> imho, Columns settings in circ/circulation.pl (while checking out) doesn't
> save columns chosen by the
Le jeu. 3 juin 2021 à 20:59, Joonas Kylmälä
a écrit :
>
> Hi,
>
> On 03/06/2021 16:07, Jonathan Druart wrote:
> > Should we keep the historical mailing list or move to something
> > modern, like discourse or flarum?
> > Is it something:
> > - we reall
Hi devs,
Should we keep the historical mailing list or move to something
modern, like discourse or flarum?
Is it something:
- we really want/need
- we don't want/need
- neat we could have
Currently the lists are not maintained (messages are not reviewed/no
moderation), the mailman version is
://annuel.framapad.org/p/koha_21.11_roadmap
It would be great to see more names, and even new names, on this document.
Let me know if you have any questions.
Cheers,
Jonathan
Le mar. 11 mai 2021 à 12:30, Jonathan Druart
a écrit :
>
> Hi developers!
>
> Yes, I know, 21.05 is not there yet
I haven't followed up here but the tests have been fixed this "morning"
Le lun. 10 mai 2021 à 18:01, Jonathan Druart
a écrit :
>
> Hi,
>
> Some of the REST API tests are failing on master, if it's blocking for
> you you can revert bug 28272 from your local branc
Hi developers!
Yes, I know, 21.05 is not there yet, but we can start to think on
which different topics we want to work on during the next cycle!
It has been a bit abandoned during the end of the 21.05 cycle, but new
topics appeared.
I have started to list them on a new document -
Hi,
Some of the REST API tests are failing on master, if it's blocking for
you you can revert bug 28272 from your local branch.
Cheers,
Jonathan
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
You should grep "loop.count", not ".count"
Most of the count you have with your regex is coming from
koha_objects->count
Le ven. 7 mai 2021 à 09:17, Fridolin SOMERS
a écrit :
> Hi community,
>
> I've been on a mindblowing search on a template error :D
>
> I was thinking that "loop.count" was
The problem is fixed now, thanks Galen!
Le lun. 26 avr. 2021 à 15:35, Jonathan Druart
a écrit :
>
> Hi all,
>
> We are experiencing issues on bugzilla.
> It seems that it is not possible to comment and search.
> However you can search if you are logged out, and apply pa
Hi all,
We are experiencing issues on bugzilla.
It seems that it is not possible to comment and search.
However you can search if you are logged out, and apply patches using git-bz.
The issue will certainly not be fixed until tomorrow.
Cheers,
Jonathan
git checkout 9f03a9e974a930416e237b846fe78b8e0e5b3404 # 20.12.00.003
reset_all
git checkout master
updatedatabase
=> no errors for me
Le mar. 13 avr. 2021 à 02:33, a écrit :
>
> koha-testing-docker OK with master after I pulled new KTD images, but I
> wonder if updatedatabase.pl has a problem
1 - 100 of 596 matches
Mail list logo
