Created attachment 130556 [details] Screenshot - Loading message fro advanced cataloguing editor When accessing the advanced editor for cataloguing it does not load - see the screenshot. The screen says "Loading, please wait.."
Browser console errors when trying to load the advanced cataloguing editor in master: 1. Internal server error - see also bug 29973: 06:56:33.005 GEThttp://127.0.0.1:8081/cgi-bin/koha/svc/cataloguing/framework?frameworkcode=&callback=define [HTTP/1.1 500 Internal Server Error 107ms] GET http://127.0.0.1:8081/cgi-bin/koha/svc/cataloguing/framework?frameworkcode=&callback=define Status 500 Internal Server Error VersionHTTP/1.1 Transferred15.05 KB (14.85 KB size) Referrer Policystrict-origin-when-cross-origin .... 2. Loading failed error: 06:56:33.114 Loading failed for the <script> with source “http://127.0.0.1:8081/cgi-bin/koha/svc/cataloguing/framework?frameworkcode=&callback=define”. editor.pl:1:1 3. Uncaught error: 06:56:33.114 Uncaught Error: Script error for: /cgi-bin/koha/svc/cataloguing/framework?frameworkcode=&callback=define http://requirejs.org/docs/errors.html#scripterror A http://127.0.0.1:8081/intranet-tmpl/lib/require_21.1200015.js:8 onScriptError http://127.0.0.1:8081/intranet-tmpl/lib/require_21.1200015.js:29 load http://127.0.0.1:8081/intranet-tmpl/lib/require_21.1200015.js:33 load http://127.0.0.1:8081/intranet-tmpl/lib/require_21.1200015.js:29 load http://127.0.0.1:8081/intranet-tmpl/lib/require_21.1200015.js:18 ..... Not sure what any of these mean though....
If you access the svc URL directly you can see the error: http://127.0.0.1:8081/cgi-bin/koha/svc/cataloguing/framework?frameworkcode=&callback=define The method Koha::Libraries->branchcode is not covered by tests! Trace begun at /kohadevbox/koha/Koha/Objects.pm line 572 Koha::Objects::AUTOLOAD('Koha::Libraries=HASH(0x5586f6325250)') called at /kohadevbox/koha/svc/cataloguing/framework line 33 eval {...} at /kohadevbox/koha/svc/cataloguing/framework line 2
The advanced cataloguing editor now loads as expected (in master on 31 May 2022), so closing this bug.