Description (in spanish) Lo sentimos, la página solicitada no se encuentra disponible Error 403 Este mensaje puede tener la(s) razón(es) siguiente(s): Tiene prohibido ver esta página. ¿Qué será lo próximo? Puede utilizar el menú y enlaces en el tope de la página Puede buscar en el catálogo usando el formulario de búsqueda en la parte superior de esta página. Regresar a la página principal del catálogo. Informar problemas y enlaces rotos Para informar sobre este error, por favor, póngase en contacto con el Administrador de Koha. Enviar correo electrónico.
After upgrading from 24.05 to 24.11
sudo apt upgrade message: ********************** 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up koha-common (24.11.02-1) ... Upgrading database schema XXXX dpkg: error processing package koha-common (--configure): installed koha-common package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: koha-common E: Sub-process /usr/bin/dpkg returned an error code (1) ******************************
"sudo koha-translate --update $lang" and all went fine.
I admit I had similar issue with `E: Sub-process /usr/bin/dpkg returned an error code (1)` on koha-staging repo branch. There's possibly some bug there, it's not supposed to happen, not sure if it should be marked as RESOLVED yet...
I think so too. It's an attention point to be considered. Reopened.
Third party auth is not working. Includes CASSIE, Libby, OverDrive, and self-checkout stations. Update from 24.04 to 24.11.
(In reply to taylor.emric.ae from comment #6) > Third party auth is not working. Includes CASSIE, Libby, OverDrive, and > self-checkout stations. Update from 24.04 to 24.11. Hi there :) I believe your issue is a separate bug or configuration issue. Are you self hosted or do you have a support commpany you could contact? For community support, please try the mailing list or community chat. Important information to include is how you are authenticating with those vendors. I guess it might be SIP2, as you say it also affects your self check stations.