Alexander Horn

@luke- Thanks for the tip, but I think this should be fixed anyway. As it stands, the documentation suggests configuring a UUID attribute in the web interface. I would assume...

Kind of fixed in 509a076a494328d447c4c1181d90041fcf2be52d (but it could be done better).

As an example, the TU Munich has all of their WiFi access point statistics online: http://wlan.lrz.de/apstat/filter/unterbezirk/bb/

Maybe we could create this in a collaboration with brigk https://brigkmakerspace.digital/macherinnen/

We are running HumHub 1.8.1 from the `mriedmann/humhub:1.8` image. Here's our `docker-compose.yml`: ``` version: '3.1' services: humhub: image: mriedmann/humhub:1.8 restart: always links: - "db:db" volumes: - ./humhub_config:/var/www/localhost/htdocs/protected/config - ./humhub_uploads:/var/www/localhost/htdocs/uploads -...

It seems like this was our mistake. Somehow our permissions were all set to `root:root`. I didn't consider this as a possible issue because the `/runtime` folder from our error...

Our permissions somehow broke again, but this time it was the search which didn't work anymore: ``` 2021-10-06 17:15:22 [172.18.0.2][4][i8r2onj14ivgpi1o2mhoitric8][error][ZendSearch\Lucene\Exception\RuntimeException] ZendSearch\Lucene\Exception\RuntimeException: fopen(/var/www/localhost/htdocs/protected/runtime/searchdb/_48.sti): failed to open stream: Permission denied in /var/www/localhost/htdocs/protected/vendor/matthewbdaly/zendsearch/src/ZendSearch/Lucene/Storage/File/Filesystem.php:56...

Our permissions keep breaking whenever I update to a new HumHub version. I think @timwsuqld is right and something about the migration resets the permissions.