[1.8.1]
Update humhub to 1.17.2
Full Changelog
Fix #7457: Fix changing of space visibility
Fix #7464: Fix searching with not full latin words
Fix #7465: Formatted Arabic numbers displays 0 instead of the number
Fix #7471: Fix advanced searching by space filter
Fix #7472: Fix missing fields when creating a new user from admin
Fix #7477: Refactor Registration Form Options
Enh #7455: Add Share Intend feature for the Mobile app
Fix #7482: Fix the post submit button title after back from draft mode
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)
@nebulon that's a rather strange requirement from Etherpad: to be able to embed the app (etherpad) but still need to authenticate each user with their individual account in the originating etherpad server (despite having an API to authenticate)
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.
@kris The default is admin / changeme . Does that work (or not) ? You can access this from the tool bar:
[image: 1674501165133-6ac6be5e-3a90-4b10-86c2-1fa362219540-image.png]