Skip to main content
News

HumHub 1.19: what changes for administrators

HumHub 1.19.0 came out on 12 October 2026, with patch releases up to 1.19.3 on 27 October. Most of its 150 entries concern developers; this post keeps the ones an administrator or a member will notice, and says when CUZY communities receive them.

Published . Written by CUZY, which hosts HumHub and builds modules for it; facts about HumHub and other products link to their sources.

What members and administrators will notice

  • Sign-in. The two-step login shows the username on the password step, and the email address typed on the sign-in form is carried over to the sign-up and password-recovery forms, so nobody types it three times.
  • Impersonation is safer and logged. When an administrator impersonates a member, private content and private spaces are hidden, and every impersonation is written to the log; both behaviors are configurable.
  • External content under the member's control. A picker in the account settings lists the external sources (embedded videos, maps, feeds) a member has allowed, and lets them remove one.
  • Guest mode options. A community open to guests can hide the comment panel from them while keeping the Comment and Like buttons, which lead to the login.
  • Comments count what they show. "Comment (n)" includes replies to comments, the comment form shows its upload and submit buttons once the field is focused, and the "show previous comments" links state the real remaining number.
  • A "Create Space" button in the space directory, where members look for one that does not exist yet.
  • Keyboard and screen readers. Visible focus on card elements, focus moved to newly loaded content after a page swap, and a stream that no longer widens the page on narrow screens.
  • The marketplace wording changed: "Community modules" are now called "Non-curated modules", with no badge on the module card.

What administrators who install HumHub themselves will notice

  • The web installer gained an email (SMTP) step after the basic configuration, with a test send; under Docker the native mail() transport is no longer offered.
  • An unreachable database shows an error instead of the installer (a 503 while the database server is down), so a transient outage can no longer offer to re-install a running site.
  • The About page shows the Docker image's build information (tag, platform, build time).
  • For module developers: a central "user gate" system for mandatory flows such as a two-factor check, module dependencies declared in module.json and checked before a module is installed, updated or enabled, and a migration guide per release line.

When CUZY communities get it

Every hosted community runs the same version, moved forward together after a canary phase on CUZY's own communities: patch releases 1 to 2 weeks after HumHub publishes them, a new minor line from the .1 within 8 weeks, during the maintenance window (Tuesday 05:00 to 07:00 local time), security fixes within 48 hours whatever the day. The exact terms are in the update and support policy; nothing is to be done on the administrator's side.

Self-hosted administrators update from the administration screen or with php yii migrate/up after the files; a module's marketplace page says which HumHub versions it supports, and the modules CUZY maintains have run on the 1.19 line since its beta releases.

Sources

More news

Try HumHub with your own content

A hosted community in two minutes, all paid CUZY modules included, no card asked. Keep everything when you subscribe.

Start free trial Talk to us first

New to HumHub? What it is, who it is for and what you can do with it