Mercurial > prosody-modules
view mod_storage_muc_log/README.markdown @ 2670:6e01878103c0
mod_smacks: Ignore user when writing or reading session_cache on prosody 0.9
At least under some circumstances it seems that session.username is nil when
a user tries to resume his session in prosody 0.9.
The username is not relevant when no limiting is done (limiting the number of
entries in the session cache is only possible in prosody 0.10), so this
commit removes the usage of the username when accessing the prosody 0.9 session
cache.
| author | tmolitor <thilo@eightysoft.de> |
|---|---|
| date | Thu, 06 Apr 2017 02:12:14 +0200 |
| parents | 79b9bd84b91c |
| children | 37a6121b7373 |
line wrap: on
line source
--- labels: - 'Stage-Alpha' - ArchiveStorage summary: 'Storage module using mod\_muc\_log data with new stanza archive API' ... Introduction ============ [mod\_muc\_log](mod_muc_log.html) provided logging of chatrooms running on the server to Prosody's data store. This module gives access to this data using the 0.10+ stanza archive API, allowing legacy log data to be used with [mod\_mam\_muc](mod_mam_muc.html) and [mod\_http\_muc\_log](mod_http_muc_log.html). Details ======= Replace mod\_muc\_log (and mod\_muc\_log\_http) in your config with ``` {.lua} Component "conference.example.org" "muc" modules_enabled = { -- "muc_log"; -- functionality replaced by mod_mam_muc + mod_storage_muc_log "mam_muc"; -- Does logging to storage backend configured below -- "muc_log_http"; -- Replaced by the mod_http_muc_log "http_muc_log"; } storage = { muc_log = "muc_log"; } ``` Compatibility ============= Requires Prosody 0.10 or above.