LoginSign Up
← Back to all sparks
H

HumHub

COLLAB
Velocity5.0

Open-source social network and intranet platform

humhub.com ↗

HumHub's public feed carries only betas, and 1.19's is still about surviving the upgrade.

social intranetbeta releasesupgrade migrationspermissionscontent visibility
◆Current state
The four releases visible here are all pre-release: 1.19.0-beta.2 and beta.1, and 1.18.0-beta.6 and beta.5 before them. The 1.19 line is dominated by upgrade-path and data-integrity repair — a foreign key violation aborting the comment content_id migration on databases with orphaned rows, fatal errors when purging content whose underlying record was gone, and in beta.2 a fatal SCSS build loop left behind when the 1.19 move of static/themes into protected/humhub stranded an empty theme skeleton. Beta.2 also fixes a real leak: activities from private spaces appearing in the summary mail and dashboard of users holding only a pending invite or join request.
◆Where it's heading
The 1.19 cycle is being spent making the migration survivable on real installations rather than adding capability, which is the usual shape when a schema and directory-layout change meets databases and webroots that have accumulated years of drift. Beta.2 extends that into the installer itself, where an unreachable database was offering to re-set-up a live instance during a transient outage. The permission and visibility fixes point the same way: tightening authorisation and content boundaries is cleanup of an existing model, not an extension of it.
◆Prediction
Only beta tags appear in this feed, so a 1.19.0 stable is the obvious next milestone, but nothing here dates it. The beta.1-to-beta.2 gap of about a month is a faster rhythm than the roughly six months between the 1.18 and 1.19 betas.

◆Recent moves

  1. 2mo ago

    Private-space activity leak, installer 503 handling and the stranded theme skeleton

    The most consequential item is a visibility fix: activities from private spaces were reaching the summary mail and dashboard activity box of users who only had a pending invite or join request. Alongside it, the installer now distinguishes an unreachable database server from a merely misconfigured one instead of offering to re-set-up a live instance, and the 1.19 theme relocation no longer leaves an empty skeleton that shadows the core theme and fails every request. Continued 1.19 upgrade-survival work rather than new capability.

    View source ↗
  2. 3mo ago

    1.19 upgrade migration and orphaned content fixes

    The first 1.19 beta clears the obstacles that would stop the upgrade outright: orphaned comments deleted before RESTRICT foreign keys are created, and purge jobs no longer crashing on content whose record is gone. A new UnreadCountChangedEvent and an iOS keyboard-scroll fix are the only additive items.

    View source ↗
  3. 9mo ago

    Login screen, theming and validator fixes

    A long list of small 1.18 polish items — login container width, child themes without build.scss, validator behaviour, email colour contrast helpers. Broad but individually minor, and characteristic of a beta line late in its cycle.

    View source ↗
  4. 11mo ago

    Group manager options and assorted UI fixes

    Optional add/remove group membership for group managers plus a long tail of Bootstrap 5 migration and form styling fixes. Mostly the visible surface of the BS5 move rather than product decisions.

    View source ↗