- Koha - lists.katipo.co.nz

Re: [Koha] Error: Something went wrong when loading the table
by bongiwe＠uks.co.za 21 Nov '23

21 Nov '23

Good day Aleisha, We checked the plack-error.log and this what we are finding: Process Backgrounded 2023/11/21-10:39:31 Starman::Server (type Net::Server::PreFork) starting! pid(1143836) Binding to UNIX socket file "/var/run/koha/library/plack.sock" Setting gid to "1002 1002" Setting uid to "1002" Kind regards, Bongiwe Shongwe Chief Technology Officer Universal Knowledge Software Tel.: +27(11) 375-4700 Fax : +27(11) 375-4710 e-mail: bongiwe(a)uks.co.za Web: www.uks.co.za -----Original Message----- From: Koha <koha-bounces(a)lists.katipo.co.nz> On Behalf Of koha-request(a)lists.katipo.co.nz Sent: Monday, November 20, 2023 1:00 AM To: koha(a)lists.katipo.co.nz Subject: Koha Digest, Vol 217, Issue 17 Send Koha mailing list submissions to koha(a)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(a)lists.katipo.co.nz You can reach the person managing the list at koha-owner(a)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. Re: Error: Something went wrong when loading the table (Aleisha Amohia) ---------------------------------------------------------------------- Message: 1 Date: Mon, 20 Nov 2023 09:04:14 +1300 From: Aleisha Amohia <aleisha(a)catalyst.net.nz> To: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Error: Something went wrong when loading the table Message-ID: <0b643a0b-44c6-40c6-8264-71db699608a4(a)catalyst.net.nz> Content-Type: text/plain; charset=UTF-8; format=flowed Hello, We've seen this error a few times with our libraries. In our experience is often related to data - dates (such as the order date) in the wrong format in the database, or having NULL values when they shouldn't, or a relationship to another table failing due to a NULL value. You should be able to get more information on the error in your plack-error.log on the server. Aleisha On 17/11/23 21:33, bongiwe(a)uks.co.za wrote: > Good day, Support. > > We are trying to receive some orders on the system, and we are getting > an error "Something went wrong when loading the table. 500: Internal > server error". This is not happening with all orders. > > We have just migrated to a new server. > > Bongiwe Shongwe > > _______________________________________________ > > Koha mailing listhttp://koha-community.org Koha(a)lists.katipo.co.nz > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha -- *Aleisha Amohia (she/her)* Technical Lead | Rōpū kohinga *Catalyst.Net Limited - Expert Open Source Solutions* *Catalyst.Net Ltd - a Catalyst IT group company* Tel: +64 4 803 2259 or +61 3 9116 2642 | www.catalyst.net.nz <http://www.catalyst.net.nz> Follow Catalyst Koha on Twitter <https://twitter.com/catalystkoha> | Subscribe to the Catalyst Koha newsletter <https://catalyst.us4.list-manage.com/subscribe?u=62457ff5060d15ee3c07d3fc4&…> Catalyst Logo CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267. ------------------------------ Subject: Digest Footer _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ End of Koha Digest, Vol 217, Issue 17 *************************************

1 0

CHAT: The Avenging Chicken goes forth. Twice!
by King, Fred 20 Nov '23

20 Nov '23

Esteemed colleagues, After far too long, or maybe too soon, I present two new Adventures of Fred and the Avenging Chicken. Last May we went to the MLA-SLA joint conference in Detroit, then in September we ventured north to Portsmouth, New Hampshire, for the koha-US conference. Thanks to everybody we met, and if you notice any errors please let me know. The polite fiction that my employer is unknown has probably worn out, so it's even more important to include this disclaimer: The opinions expressed here are my own, and are not necessarily representative of MedStar Health, its management, associates, affiliates, attending physicians, their families, or any of their household pets. And I mean it. The trip to Detroit is here: http://avengingchicken.online//mla-sla2023/<http://avengingchicken.online/mla-sla2023/> The trip to Portsmouth is here: http://avengingchicken.online/koha-us_2023/ Question to ponder: if the Chicken goes forth twice, is that eight or half? --Fred Fred King, MSLS, AHIP Medical Librarian, MedStar Washington Hospital Center fred.king(a)medstar.net 202-877-6670 ORCID 0000-0001-5266-0279 MedStar Authors Catalog: http://medstarauthors.org A conclusion is the part where you got tired of thinking. -- Anon

1 0

Electronic biblios checkout
by Alvaro Cornejo 20 Nov '23

20 Nov '23

Hi Does anyone lend electronic biblios? How do you manage the checkout time? Is it possible to define a deadline or expiry date for the checked out electronic biblio? What we want to achieve is to allow patrons to checkout electronic biblios but after the checkout period the document will lock and can no longer be accessed. Patron will need to do a new checkout. They might need to do a checking of the biblio even though they will not "return" the electronic document. We are thinking on creating unique links/url to the file where we define its validity time and can restrict document download, screen capture and printing. i.e. patrons will only be able to read the document online. Any ideas? Regards Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire

1 0

Error: Something went wrong when loading the table
by bongiwe＠uks.co.za 19 Nov '23

19 Nov '23

Good day, Support. We are trying to receive some orders on the system, and we are getting an error "Something went wrong when loading the table. 500: Internal server error". This is not happening with all orders. We have just migrated to a new server. Bongiwe Shongwe

2 1

String freeze - 22.11.x
by Blenkinsop, Matthew 17 Nov '23

17 Nov '23

Hi all, We are now on string freeze for 22.11.x ahead of a release planned for the middle of next week. Get translating! Kind Regards. Matt Blenkinsop Junior Software Engineer PTFS Europe [image: Phone icon] M: +44 7311382399 | T: +44 1483 378728 ext. 1020 [image: Email icon] matt.blenkinsop(a)ptfs-europe.com [image: Link icon] www.ptfs-europe.com [image: Click to open Twitter] [image: Click to open YouTube] <https://www.youtube.com/@PTFSEurope> [image: Click to open PTFS Europe webpage]

1 1

custom homepage
by zen zenitram 16 Nov '23

16 Nov '23

Good day! When we install the update of the Operating System the custom homepage return to default page. We need to edit it again to make it the homepage design that we need. Operating System Ubuntu 22.04 Thank you!

1 0

500 error for News, HTML customizations, Pages
by Aida Djikic 15 Nov '23

15 Nov '23

Hello all, I have noticed that going to Tools, then to any of these: News, HTML customizations, Pages - results in a 500 error. This did not happen until I recently truncated tables in an effort to remove a faulty import and ended up having to re-create the super librarian user via the terminal. The pages exist in the OPAC but I cannot access them from the staff interface in order to edit them. Does anyone know how to solve this problem? Thank you in advance! -- Regards, Aida

3 9

Documentation Drop-in Sessions 2023-2024
by philip.orr＠lmscloud.de 15 Nov '23

15 Nov '23

Greetings all, the poll results for our Documentation workshops for the winter of 2023-2024 are in! Thanks to everybody who took the time to answer the poll. According to the results, we have decided on the following dates: * Friday 1st December 2023, 12:30 15:30 UTC * Tuesday 23rd January 2024, 14:00 17:00 UTC Background: Aude Charillon (Documentation Manager + PTFS Europe) and I are organizing informal Drop-in sessions for Documentation. Aude has updated the wiki, so go check it out for more information on the events and to see what time it will be in your timezone! https://wiki.koha-community.org/wiki/Documentation_Team_-_Drop-in_sessions As usual, contact one of us if you have any comments or questions. Looking forward to our meetings, Philip [krimsonkharne on Koha IRC] -- Philip Orr LMSCloud GmbH Office Bad Münstereifel Project management, Training, Support T +49 7121 144154 e <mailto:philip.orr@lmscloud.de> philip.orr(a)lmscloud.de w <http://www.lmscloud.de/> www.lmscloud.de

1 0

Re: [Koha] koha installation error
by Tom Obrien 14 Nov '23

14 Nov '23

Greetings, I upgraded ubuntu server 16 LTS to 22 LTS. I am trying to install koha but I get the following error: wget -O- https://debian.koha-community.org/koha/gpg.asc | sudo apt-key add - --2023-11-13 06:30:33-- https://debian.koha-community.org/koha/gpg.asc Resolving debian.koha-community.org (debian.koha-community.org) failed: Temporary failure in name resolution. wget: unable to resolve host address ‘debian.koha-community.org’ Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). gpg: no valid OpenPGP data found. Kindly assist me on how to overcome this problem. Thank in advance. Tom

2 1

Privacy/GDPR settings and Checkout History problem
by David Liddle 13 Nov '23

13 Nov '23

Greetings all! A librarian reported to us today that, since we began enforcing the preference "GDPR_Policy", a patron choosing to retain checkout history "forever" sees nothing after going to that view. The librarian confirmed that a history does exist for himself and for a patron reporting the same issue. Our system is running Koha 22.05.15. The following preferences are set: - GDPR_Policy >>> enforced - PrivacyPolicyURL >>> set to valid page - OPACPrivacy >>> Allow - opacreadinghistory >>> Allow - AnonymousPatron >>> set to valid patron entry If anyone could provide some insight into a misconfiguration, an oversight, or a missed step, we would be grateful. We have not implemented any workarounds in the meantime. Thank you! David Liddle System Administrator david.liddle(a)wycliff.de (but not for this list) Wycliff e.V., https://wycliff.de Seminar für Sprache und Kultur, https://spracheundkultur.org Internationales Tagungszentrum Karimu, https://karimu.de

1 0