Mercurial > prosody-modules
view mod_muc_config_restrict/mod_muc_config_restrict.lua @ 4688:05725276fac0
mod_bookmarks2: Use same default as mod_pep for max_items
Should fix the issue with max items until the proper "max" can be used,
by following the configured max.
While "max" is already in trunk, it's not easily usable in 0.11.x
This limit and option was added to mod_pep in Prosody rev aefb96a52f5f
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Wed, 15 Sep 2021 17:39:37 +0200 |
parents | ed7431fd3b47 |
children |
line wrap: on
line source
local is_admin = require "core.usermanager".is_admin; local t_remove = table.remove; local restricted_options = module:get_option_set("muc_config_restricted", {})._items; function handle_config_submit(event) local stanza = event.stanza; if is_admin(stanza.attr.from, module.host) then return; end -- Don't restrict admins local fields = event.fields; for option in restricted_options do fields[option] = nil; -- Like it was never there end end function handle_config_request(event) if is_admin(event.actor, module.host) then return; end -- Don't restrict admins local form = event.form; for i = #form, 1, -1 do if restricted_options[form[i].name] then t_remove(form, i); end end end module:hook("muc-config-submitted", handle_config_submit); module:hook("muc-config-form", handle_config_request);