Software /
code /
prosody-modules
File
mod_invites_tracking/README.md @ 6113:c0cb43817b7c
mod_compliance_latest: using module:log_status
diff --git a/mod_compliance_latest/mod_compliance_latest.lua b/mod_compliance_latest/mod_compliance_latest.lua
--- a/mod_compliance_latest/mod_compliance_latest.lua
+++ b/mod_compliance_latest/mod_compliance_latest.lua
@@ -1,6 +1,6 @@
local success, err = pcall(function() module:depends("compliance_2023") end)
if not success then
- module:log("error", "Error, can't load module: mod_compliance_2023. Is this module downloaded in a folder readable by prosody?")
- return 1, "Error: Couldn't load dependency mod_compliance_2023."
+module:log_status( "error", "Error, can't load module: mod_compliance_2023. Is this module downloaded into a folder readable by prosody?" )
+return false
end
author | Menel <menel@snikket.de> |
---|---|
date | Mon, 23 Dec 2024 14:09:56 +0100 |
parent | 6091:a1f6fe0025d2 |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: 'Store who created the invite to create a user account' ... Introduction ============ Invites are an intermediate way between opening registrations completely and closing registrations completely. By letting users invite other users to the server, an administrator exposes themselves again to the risk of abuse. To combat that abuse more effectively, this module allows to store (outside of the user’s information) who created an invite which was used to create the user’s account. Details ======= Add it to `modules_enabled`. Assuming file based storage the information will be stored at your storage location under `./invites_tracking/` Caveats ======= - The information is not deleted even when the associated user accounts are deleted. - Currently, there is no integrated way to make use of that information. Compatibility ============= Prosody-Version Status --------------- --------------------- trunk Works as of 24-12-08 0.12 unknown