Indico 3.2 -> 3.3 upgrade after Ajax, jquery Error

Administrators
1

image

After moving & upgrading(3.3) the Indico server
After clicking the show button or event clone button, the error below occurs and an infinite loading state occurs.

Could this have something to do with not having SSL certification?

It works without problems on version 3.2.8, which was the original server. (have SSL Cert)

addScript.js:8 [Script Loader] TypeError: getObject is not a function
    at type (eval at n.exports (addScript.js:20:9), <anonymous>:18:13)
    at eval (eval at n.exports (addScript.js:20:9), <anonymous>:8:1)
    at eval (<anonymous>)
    at n.exports (addScript.js:20:9)
    at 10576 (Actions.js:1:1)
    at n (bootstrap:19:32)
    at 49713 (main.1eb9d2aa.bundle.js:1:517)
    at n (bootstrap:19:32)
    at main.1eb9d2aa.bundle.js:1:414493
    at n.O (chunk loaded:23:12)

Uncaught ReferenceError: moment is not defined
    at manage/:53:13
user.js:1 Uncaught ReferenceError: Indico is not defined
    at user.js:1:1
manage/:637 Uncaught ReferenceError: setupEventManagementActionMenu is not defined
    at manage/:637:9

display.js:115 Uncaught ReferenceError: handleAjaxError is not defined
    at HTMLAnchorElement.<anonymous> (display.js:115:20)
    at HTMLAnchorElement.dispatch (event.js:335:27)
    at x.handle (event.js:139:28)
2

This looks like some scripts could not have been loaded. Are there any 404 errors in the console or network tab before the JS errors?

And yes, if your config is using a https URL but you are accessing it via plain http such things may happen. You can use “view source” in the browser to get one of the JS URLs and open it directly to see if it 404s or fails for some other reason.

3

image
image1953×1191 236 KB

Error 403 occurs in /assets/i18n/en_GB.js

4

ok, open the URL directly to see the full error…

5

OK, I see you included your instance’s URL in the screenshot. It fails with a plain 403 error from nginx, so you need to check your nginx error log file why that’s happening. A likely reason could be incorrect permissions on some folders such as /opt/indico/cache or the files inside.