Bug: Release 2.1.4 breaks Organizr

[AmansRevenger]

When I update via the internal update function to 2.1.4, my homepage doesnt load anymore and I get the following erors

Uncaught SyntaxError: Illegal return statement (at functions.js?v=2.1.2490:8064:5)

Uncaught ReferenceError: local is not defined
    at (index):270:83
(anonymous) @ (index):270

Uncaught ReferenceError: timerIncrement is not defined
    at HTMLDocument.<anonymous> (custom.min.js?v=2.1.2490:1:1551)
    at i (jquery-2.2.4.min.js:2:27151)
    at Object.fireWith [as resolveWith] (jquery-2.2.4.min.js:2:27914)
    at Function.ready (jquery-2.2.4.min.js:2:29707)
    at HTMLDocument.J (jquery-2.2.4.min.js:2:29892)

When I revert to the functions.js to the one from before 11.01.2026 manually by replacing the functions.js , it works again.

I am no javascript expert, so I just wanted to make it known. I have tried clearing the cookies and cache and restarting the webserver (which is an nginx in docker and I have installed organizr as normal application in my www/ folder inside the docker container)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[fana13]

Same here, i do some activity to keep this issue alive

[HalianElf]

For all of you getting this, double check it's not trying to pull from the wrong repo: #2029

If you don't feel comfortable manually updating the script and runningit, you can download the zip and throw it over top and you should then be up to date and the script will have the correct repo for next update.

[fana13]

Thanks but still not working
Changed linux-update.sh by GITHUB_REPO="${GITHUB_REPO:-causefx/Organizr}"
No branch specified, using v2-master Updating Organizr from causefx/Organizr:v2-master Downloading update... Extracting files... Applying update... Update completed successfully
And my homepage doesn't load anymore

[HalianElf]

And it's the same exact error as the OP referencing 2.1.2490?

[fana13]

I don't really know because i've just my homepage which doesn't load

My log file : {"log_level":"NOTICE","message":"Updated config version to 2.1.2490","channel":"Update","username":"fab","trace_id":"c5189622-7738-477b-857f-30b8428a2975","file":"/var/www/Organizr/api/functions/upgrade-functions.php","line":110,"context":[],"remote_ip_address":"192.168.0.1","server_ip_address":"192.168.0.112","user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36 Edg/146.0.0.0","datetime":"2026-03-18 21:21:43.988174","timezone":"UTC","process_time":7.023096084594727}

No error into

[pugfantus]

Thanks but still not working Changed linux-update.sh by GITHUB_REPO="${GITHUB_REPO:-causefx/Organizr}" No branch specified, using v2-master Updating Organizr from causefx/Organizr:v2-master Downloading update... Extracting files... Applying update... Update completed successfully And my homepage doesn't load anymore

This fixed my update, thank you!

[codedesperate]

Thanks but still not working Changed linux-update.sh by GITHUB_REPO="${GITHUB_REPO:-causefx/Organizr}" No branch specified, using v2-master Updating Organizr from causefx/Organizr:v2-master Downloading update... Extracting files... Applying update... Update completed successfully And my homepage doesn't load anymore

This fixed my update, thank you!

This also fixed it for me. Changed it, and then ran the script with sudo.

[naisspas]

Thanks but still not working Changed linux-update.sh by GITHUB_REPO="${GITHUB_REPO:-causefx/Organizr}" No branch specified, using v2-master Updating Organizr from causefx/Organizr:v2-master Downloading update... Extracting files... Applying update... Update completed successfully And my homepage doesn't load anymore

This fixed my update, thank you!

This also fixed it for me. Changed it, and then ran the script with sudo.

Same resolution here, edit the "linux-update.sh" file to change le Github repo, ran the script manually and the update completed normally.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[aniqueta]

Not stale