[1.9.5]
Update humhub to 1.18.5
Full Changelog
Fix #8340: Defer module update opcache_reset() to the end of the request to avoid interrupting the update in worker runtimes (e.g. FrankenPHP)
Fix #8357: Cast app name to string (This fixes the issue of instances with names consisting of numbers not being able to be added to the mobile app)
Enh #8346: Force Select2 dropdowns to always open below the field instead of flipping above when there's not enough space
Fix #8359: Display user sub name on invite after space creating
Fix #8361: Prevent non-creators from attaching or deleting another user's unassigned file
Fix #8365: Encode deletion reason in comment and content deletion notifications
Fix #8374: Ensure adding group members is restricted to groups the current user manages
Fix #8373: Ensure the oEmbed consent prompt encodes the requested URL so embedded markup stays inert
Fix #8381: Limit request supplied membership and friendship button options to presentation values, so titles, urls and action attributes stay server generated, and encode the membership button markup in the membership request response so it cannot break out of the script context
Fix #8376: Ensure space member role changes are limited to assignable roles
@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.
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]
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.
@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).
@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.
