File

mod_muc_log/README.md @ 6303:d73cae8d80ce

mod_cloud_notify: actually fix labels diff --git a/mod_cloud_notify/README.md b/mod_cloud_notify/README.md --- a/mod_cloud_notify/README.md +++ b/mod_cloud_notify/README.md @@ -1,7 +1,7 @@ ---- --labels: --- 'Stage-Beta' --summary: 'XEP-0357: Cloud push notifications' +labels: +- 'Stage-Beta' +summary: 'XEP-0357: Cloud push notifications' ---- # Introduction
author Menel <menel@snikket.de>
date Fri, 13 Jun 2025 10:48:20 +0200
parent 6197:ba8f5cdc1676
line wrap: on
line source

---
labels:
- 'Stage-Obsolete'
summary: Log chatroom messages to disk
...

::: {.alert .alert-danger}
This module was an early and obsolete way to record group chat logs.

For a modern approach, use [mod_muc_mam][doc:modules:mod_muc_mam].

For converting legacy logs stored by this module, see [mod_storage_muc_log], it can be used with [mod_migrate] or [prosody-migrator][doc:migrator].
:::

Introduction
============

This module logs the conversation of chatrooms running on the server to
Prosody's data store. To view them you will need a module such as
[mod\_muc\_log\_http](mod_muc_log_http.html).

Details
=======

mod\_muc\_log must be loaded individually for the components that need
it. Assuming you have a MUC component already running on
conference.example.org then you can add muc\_log to it like so:

    Component "conference.example.org" "muc"
       modules_enabled = {
          "muc_log";
       }

Logging is not enabled by default. In 0.9+ logging can be enabled per
room in the room config form.

To enable logging in older versions, or to enable logging by default for
all rooms, set

    muc_log_by_default = true -- Log all rooms by default

Compatibility
=============

Does **not** work with currently supported versions of Prosody.