ok Thanks

@stoccafisso said in Install errors: Will this work well for later updates of the app? I am trying to fix this issue without this dirty hands-on fix. So, if I get this fixed, my quickfix guide is not needed.

Hello @ccfu and @dffla Thanks for the assistance @ccfu Good to see that you got your issue resolved @dffla

Although just to let you know, I found a quicker and easier way of fixing just by adding the Birthday Field to a category called Profile Information fixed it. [image: 1750452496242-screenshot-intranettest_apes_org_uk-2025_06_20-21_47_50-resized.png]

Closed due to inactivity Note: This was a CSP issue and is fixed by setting the correct CSP headers in both apps.

I eventually figured it out, I suppose. I had activated several login plugins for Facebook, google, X, etc, but hadn't configured them. I just disabled all of them, and now registration works fine.

glad it worked out in the end, still pretty rough. I would recommend to take a fresh backup and clone the app instance from that into a new test instance, just to verify if that works then. Otherwise we have to investigate what the root cause is.

If clearing the cache doesn't help, check to see if the ServiceWorker HumHub automatically installs is still being loaded in the browser.

@joseph Great and thanks for that info Since i run everything at home, my setup is kinda secure already. But better be safe than sorry... Actually my Cloudron instance (VM) and Ubuntu ClamAV (VM) both live in a separate Vlan. Totally isolated and separated from the rest of the network(s).

Should be fixed now, thanks for reporting!

Thank you Joseph

Fix with latest package now.

It seems like they could use a gallery of cool custom themes for download..

@ccfu are you able to install it on the demo so I can try to understand what is different ? https://my.demo.cloudron.io (username / password: cloudron)

Getting a fork started is certainly a start I haven't really had a look at or even used previous versions of HumHub so I imagine it taking some time to find out exactly what changed with the newer version that broke old themes. My first guess though from the internal error and "It looks like you may have taken a wrong turn" messages in addition to one of the pull requests on github that suggests changing "$canWrite" to "$canEdit" almost makes me think there was a bunch of changes to how data is referenced that causes a mismatch in what the theme is attempting to reference because it's reference point is completely different. Could be wrong though; I'm not terribly experienced in web development.

What's the error? Maybe we need to make some path writable.

Confirmed, and THANKS!

OK, thanks for your help, it should be okay, I'll let you know if needed.