LiveUpdate remove block
remote sources
LiveUpdate remote config page

This project is not covered by Drupal’s security advisory policy.

Drupal Live Update is the reusable event layer Drupal never had. Modules publish events to named channels; browsers receive them and refresh only the pieces that matter — no full page reload, no reinventing the wheel every time someone needs a live dashboard, notification or block.

The base module ships with Drupal-side polling. It works out of the box, zero extra services required. When you want real push, drop in a transport: WebSocket, Server-Sent Events, Node.js… or the purpose-built Live Update Go service.

How this differs from the usual suspects

  • Nodejs – classic Socket.IO bridge. Still stuck on pre-Drupal 8 releases; D11/D12 port is in the queue waiting for release-management access. Once it lands it becomes just another optional transport for Live Update.
  • Live content – WebSocket-only, content-centric, ships its own example block. Live Update is deliberately broader and transport-agnostic: same API whether you poll or push.
  • Chatroom – chat features. Also waiting on the D11/D12 release gate. Complementary, not competing: Chatroom owns the chat UI, Live Update owns the event pipe.

Live Update does not try to be your chat system or your real-time gateway. It just gives every Drupal module a clean, access-controlled way to publish and consume live events — polling today, Go (or anything else) the moment you need push.

Live demo

https://live.mindcore.org

Push transport (Go)

Want actual push instead of polling? → Live Update Go

Supporting organizations: 
Development and hosting

Project information

Releases