[Koha] Can't Define or display libraries in staff client

[Abdulsalam Yousef]

Solved!

On Sun, 6 Feb 2022, 2:00 am , <koha-request at lists.katipo.co.nz> wrote:

> Send Koha mailing list submissions to
>         koha at lists.katipo.co.nz
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.katipo.co.nz/mailman/listinfo/koha
> or, via email, send a message with subject or body 'help' to
>         koha-request at lists.katipo.co.nz
>
> You can reach the person managing the list at
>         koha-owner at lists.katipo.co.nz
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Koha digest..."
>
>
> Today's Topics:
>
>    1. Can't Define or display libraries in staff client
>       (Abdulsalam Yousef)
>    2. Importing encrypted patron passwords (Mark Alexander)
>    3. Re: Importing encrypted patron passwords (Tomas Cohen Arazi)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 5 Feb 2022 12:00:48 +0300
> From: Abdulsalam Yousef <ayousef at kwareict.com>
> To: koha at lists.katipo.co.nz
> Subject: [Koha] Can't Define or display libraries in staff client
> Message-ID:
>         <CADRHuh37tuxsaHGJuUxewjKmOGwG5A=
> Pp1YD-jsJDQ+m7oyRVw at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
>  Hello All,
> I'm trying to Define new branches from Koha basic parameters in staff
> client (http://localhost/cgi-bin/koha/admin/branches.pl), but there are no
> branches displayed, I guess it's fetched through the API, and the http Get
> request for
> http://subdomain.com/api/v1/libraries?_page=1&_per_page=20&q=[]&_match=
> contains&_order_by=+me.name
> <http://subdomain.com/api/v1/libraries?_page=1&_per_page=20&q=[]&_match=contains&_order_by=+me.name>
> returned 500 Internal server error!
> All configurations seem to be good.
> Is it a compatibility issue?
>
> My current env vars are:
> OS: Debian10
> Koha version: 21.11.01.000
> Perl Version: 5.02800
> Mojoliciou: 9.22
> Mojolicious::Plugin::OpenAPI: 5.02
> JSON::Validator: 5.05
>
> Has anyone faced this problem before?
> Thanks in advance.
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 05 Feb 2022 08:30:45 -0500
> From: Mark Alexander <marka at pobox.com>
> To: koha <koha at lists.katipo.co.nz>
> Subject: [Koha] Importing encrypted patron passwords
> Message-ID: <1644067026-sup-2295 at t450s>
> Content-Type: text/plain; charset=UTF-8
>
>
> I'm in the process of upgrading a library's Debian 7/Koha 3.16 setup.
> This installation is so old that an in-place upgrade can't be done.
> My plan is to first create a test VM with Debian 10 and the latest
> stable koha-common.  Then after manually setting up various admin
> things (library, item types, ccode, loc, patron types), I'll import
> the catalog and the patron list.  Finally, I'll move the resulting
> database to the real (live) server.
>
> The snag here is the patron passwords.  I'll use a report from the SQL
> library to export the patron list from the old installation, but the
> passwords will be encrypted.  My understanding is that when importing
> the patron list, the passwords must be unencrypted.  So I'll need to
> remove the password column from the CSV file, and as a result,
> every patron password will have to be reset manually.
>
> Is there any workaround for this?  I would just like to move the
> encrypted passwords from the old installation to the new one.  I am
> comfortable doing some hand-crafted SQL updates to accomplish this.
> But before I make the attempt, is there any reason why this wouldn't
> work or why it's a bad idea?
>
> --
> Single-handedly, I have fought my way
> into this hopeless mess. --Ashleigh Brilliant
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 5 Feb 2022 10:42:12 -0300
> From: Tomas Cohen Arazi <tomascohen at gmail.com>
> To: Mark Alexander <marka at pobox.com>
> Cc: koha <koha at lists.katipo.co.nz>
> Subject: Re: [Koha] Importing encrypted patron passwords
> Message-ID:
>         <CABZfb=
> UZhzT5MCj2jh5oLg+kUFxXmxpznokEGk6AER9_+d92zQ at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> You should do all you mention, but instead of creating things, you should
> just paste the old db and trigger the upgrade process.
>
> El sáb., 5 feb. 2022 10:31, Mark Alexander <marka at pobox.com> escribió:
>
> >
> > I'm in the process of upgrading a library's Debian 7/Koha 3.16 setup.
> > This installation is so old that an in-place upgrade can't be done.
> > My plan is to first create a test VM with Debian 10 and the latest
> > stable koha-common.  Then after manually setting up various admin
> > things (library, item types, ccode, loc, patron types), I'll import
> > the catalog and the patron list.  Finally, I'll move the resulting
> > database to the real (live) server.
> >
> > The snag here is the patron passwords.  I'll use a report from the SQL
> > library to export the patron list from the old installation, but the
> > passwords will be encrypted.  My understanding is that when importing
> > the patron list, the passwords must be unencrypted.  So I'll need to
> > remove the password column from the CSV file, and as a result,
> > every patron password will have to be reset manually.
> >
> > Is there any workaround for this?  I would just like to move the
> > encrypted passwords from the old installation to the new one.  I am
> > comfortable doing some hand-crafted SQL updates to accomplish this.
> > But before I make the attempt, is there any reason why this wouldn't
> > work or why it's a bad idea?
> >
> > --
> > Single-handedly, I have fought my way
> > into this hopeless mess. --Ashleigh Brilliant
> > _______________________________________________
> >
> > Koha mailing list  http://koha-community.org
> > Koha at lists.katipo.co.nz
> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> >
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Koha mailing list
> Koha at lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
> ------------------------------
>
> End of Koha Digest, Vol 196, Issue 6
> ************************************
>